Photos on resumes are never a good idea. They introduce so much possibly for bias, both intentional and unintentional, while adding very little benefit. They also don't print well and don't look good unless you've got a pro shot.<p>Resumes aren't memorable when there's a picture but rather when they are well written.
Author here. I made this using Haskell for the web server, and Preact for the JavaScript. The resume is converted to PDF by translating HTML into canvas and using JSPDF to turn the canvas into a PDF. Hosted on Linode. Cached with CloudFlare.
Very clean, nice work!<p>My main feedback would be to make the photo optional - it's quite culture and job dependent whether a photo is included on a CV.
Cool idea, I suggest you add some disclaimer about data policy. My first thought on the landing page was "neat way to gather some personal data" :D
As a technical person who hires people occasionally, the one guaranteed thing that will make me read a resume is LaTeX. I dislike profile pictures because it causes me to have unavoidable bias.<p>Just a data point
I like it. Very to-the-point.<p>One thing that annoys me is when I click "Job #5" it expands a new form and jumps to it immediately. It is very confusing. For me it would be better if the whole form was expanded at all times. Then I can just scroll up and down and know what I am editing. Same thing when I click "+ Education", it takes me out of the flow.<p>Good job.
Great tool! What's your business model though?<p>Collecting data comes to mind first. If it's not the case, I would recommend to say this explicitly on the page somewhere.
This looks like a solid tool. Love that there is no mandatory account creation. A couple tiny constructive criticisms:<p>+ All instances of "resume" should be "résumé" or at least "resumé".<p>+ Maybe add some help formatting phone numbers to the one true format of (###) ###-####.<p>+ Finally maybe consider adding color to the most important buttons, like the Save buttons, so people's eyes are drawn to them
Not sure what is going on in the hiring world, since I have been in the same job for a long time, but there seems to be a misalignment about the proper length of a resume.<p>This app suggests to keep it to one page. When I've been involved in hiring new people, the resumes that get attention are the ones with detailed descriptions of project experience. They are 3 or 4 pages long. The managers want something to read because the candidates without adequate education and/or experience for the posted position will not make it into their hands.<p>In my field (computer engineer), the "short" description that matters is 1 line: masters degree, 15 years experience, security clearance, not a diversity hire.<p>After that, they want deep detail about skills.
Looks good! An alternative is <a href="https://resumake.io/" rel="nofollow">https://resumake.io/</a>, which also allows one to export and then later import the JSON which defines the resume.
Be nice if a service like this allowed us to keep all the responses as meta data so that we can auto-fill every recruiters and job application site's fields automatically with our pre-existing answers.<p>I'm sure there is a browser extension somewhere that does this.<p>"Thanks for uploading your resume! Now forget we ever asked and fill all the same details out for us again!"
This looks absolutely solid, nice work. Super easy to build. Only reason I use latex is for formatting and crappy word indents, this solves that problem.<p>Would be great with a few more templates, and some way to "pazzazify" each one. Maybe a little streak of color.<p>I did not realize you were hosting the resume as well.
This is a slick tool. I like how the thumbnail and PDF preview is live updating with changes.<p>It'd be a really nice addition if the tool could output the resume data in other supporting formats (plain text, Markdown, JSON, etc.)