Kudos to the developer :)
Your CV is for judging your work history and experience. What can I learn from a photo that I would legally be able to take a decision about?
But I completely understand where you are coming from. Photos can cause bias in the hiring process and it's certainly debatable. That's why I've provided the option to either add an image or not have one, and designed the templates especially to fit both use cases.
In Portugal and Spain for example, it is long not welcomed that people send resumes with pictures.
You even have photography shops specialized in doing CV photos.
For certain of them you will also get points, if the CV is delivered in a nice portfolio folder, and there are whole sites dedicate to how you should organise the contents of it.
Thankfully due to the uniformization of employment rules across UE and the fight against discrimination, that is slowly going away, specially in digital industry where you just get to send a PDF or fill out a form, instead of that bureaucratic process.
But if you are applying to a company where work colleges still talk to each other with formal "Sie" after working together for decades alongside each other, then expect that process to still be the way how everything rolls.
I also seem to remember -- can you either correct me, or confirm this -- in these same companies that expect the photo resume, don't they expect your full salary history as well?
There is a saying, "He who talks money first loses." In the US, I'm certain that I've never seen a resume with salary figures.
I also always found it strange.
IANAL: I don't know if it is outright illegal to request a picture but it sure seems like a great way to open yourself up to a lawsuit.
> Title VII of the Civil Rights Act of 1964 (Title VII), which prohibits employment discrimination based on race, color, religion, sex, or national origin
> the Equal Pay Act of 1963 (EPA), which protects men and women who perform substantially equal work in the same establishment from sex-based wage discrimination
> the Age Discrimination in Employment Act of 1967 (ADEA), which protects individuals who are 40 years of age or older
> Title I and Title V of the Americans with Disabilities Act of 1990, as amended (ADA), which prohibit employment discrimination against qualified individuals with disabilities in the private sector, and in state and local governments
> the Civil Rights Act of 1991, which, among other things, provides monetary damages in cases of intentional employment discrimination.
The simple reason is that a photo just opens up a ton of bias accusations. There is literally 0 information a photo can provide that can be legally used to make hiring decisions, but on the other hand, there are a whole host of biases it can introduce.
While I was at PyCon, I had prepped a version of my resume that had my photo on it, and during the job fair I shared them with folks and companies that interested me.
I figured, if there's any chance of someone remembering a person and wanted to recommend them, a photo would go well with the name and info. But maybe it was ineffective :) I didn't think it would hurt to include, at the very least.
 I initially typed that as 'whored'. FYI.
Bonus points for keeping everything offline because if I use this I would be afraid you would be keeping track of my keystrokes as I type in all of my personal information into the form. < - Please don't ever do this, anyone who may read this comment.
Thank you so much :) That was exactly what I was going for, complete privacy and complete customization possibilities. Plus, a lot of my friends keep saying that I have good resume design skills as I've made mine, and I used to release templates as PSD or Figma documents previously, but not everyone could edit them, so that's why I made this :)
I would never ever make it monetized or put ads or collect personal data in any sort of way. In all honesty, the only thing I have on the site is a Google Analytics script, and that's just to see how many people are using the site (to fuel my ego :D). But even that can be disabled if you use few browser extensions.
I really hope you keep using the app, please do let me know how I can make the experience much better :) Thank you!
Depending on whether you have access to your server logs, consider using something like GoAccess  instead.
Kudos for your project :)
It's very alpha, but I'd love to hear what folks think. Here's an example profile:
I plan to ship a public GraphQL API that makes your data available for any use you can imagine, including generating a "standard" resume or building a personal website.
Other than that, it looked better than most such things I’ve seen.
But anyway, I'll try to add some validation across the app so that this doesn't happen again. For now, to fix any issues at all, you only need to clear your local storage of the site. Here's how you can clear Local Storage on Chrome (https://www.leadshook.com/help/how-to-clear-local-storage-in...), similar steps for other browsers too.
Please let me know if that resolved the issue temporarily for you.
TypeError: "can't access property "r", r is null"
TypeError: can't access property "r", r is null
Only has a single template though. But my main concern was being able to export to both word and pdf, because recruiters always want word documents.
I really like the way the templates look on yours :)
May have to try and implement live preview myself.
Whilst interviewing people, if I know their resume came via a recruiter, I tend to ask for their real one. The reason is not to cut the recruiter out of the process. Rather, it is to make sure the resume (and the questions about its content) are based on an unaltered version. Sadly, some recruiters will modify a resume to fit the position description, and the process, make claims on behalf of the candidate which are... untrue.
So, PDF, being more difficult to modify, seems safer.
I used to say they can get it in either PDF or JSON ;)
I doubt I’m going to have any time to contribute, but I’ll have a look.
Did you base your schema on jsonresume? I did that with a few extensions.
Small heads up, there are many dead scrollbars: https://i.imgur.com/FImuHVn.png
If you are developing on OSX, I recommend turning on scrollbars to make detecting dead scrollbars easier.
And thank you very very much, I really hope you continue to use the app and please do let me know if there's anything I can do to help make the experience much better :)
But I will definitely look into the option in which uploading a Gist or something would generate the resume as well, it shouldn't be that difficult.
Tested on: Safari 13.1 / MacOS 10.15.4
It looks OK on Opera 67.
Curious, do you have any interest in having the ability to import/export from the various cloud storage vendors (Dropbox, GDrive, possibly even Github Gist), or do you feel like it would go against the offline/"no servers" theme of the app?
Maybe when there's a clear need of one or more cloud services, this could be explored?
Anyways if you are interested in adding this feel free to give me a ping I'd be happy to help! daniels.bytes at the google (daniel-bytes on Github). Again amazing job on this! <3
- It would be nice to be able to see a preview of the template in full size
- How do you export the résumé at the end?
- I couldn't find the code. Where is it?
I'll definitely look into what can be done about those previews. Right now, it's not that hard to just load the dummy data (from the Actions Tab) and cycle through the templates, but I'll look into making the process easier.
As for the export options, as defined in the Actions Tab, you can print the resume at any time and the browser has options to print as PDF. Also, you can export the data as JSON and import it back again, keeping it completely portable.
The GitHub Repository can be found here: https://github.com/AmruthPillai/Reactive-Resume
There is an About Tab as well which has the link to the repository from within the app :)
The dummy data loading, that's exactly what I was looking for when I suggested adding a bigger template preview.
Everything else is perfect!
Sadly, I can't suggest any fix except using Safari or Chrome for now. I will look into what can be done to fix the issues regarding Firefox soon. Thank you for bringing this to my attention :)
Still I respect their effort to try. Machines are already parsing resumes for keywords anyway.