What are some good examples of how a developer's resume should differ from the norm? What sort of tactics have been used in these resumes that have proven successful?
I posted some notes about my résumé a while ago: <a href="https://github.com/jloughry/CV/blob/master/README.md" rel="nofollow">https://github.com/jloughry/CV/blob/master/README.md</a><p>In addition:<p>1. Put it somewhere findable like GitHub.<p>2. Consider telling the reader something subtle by the way your résumé is implemented. Maybe it's automatically generated, maybe it's something else:<p>(the following quotation is from Reddit <a href="http://www.reddit.com/r/programming/comments/7py77/ask_reddit_what_latex_resume_template_do_you_use/c072ck7" rel="nofollow">http://www.reddit.com/r/programming/comments/7py77/ask_reddi...</a> )<p><i>As someone working as an engineer, with part of my job consisting of recruiting other engineers: Please don't encourage usage of LaTeX resume templates! Keep it underground :)</i><p><i>The secret indication of a CV with high potential is that it's made in LaTeX and not Word or some other mainstream software. It's actually proven to be an excellent interview filter. Almost a majority of our best hires had CV's created with LaTeX</i><p>3. Include links to social media sites, like this one, where you've written comments you want to be found. You already know they're going to Google you before the interview. Make it easy to find the bits you want them to find. I can learn more about prospective candidates from a few minutes scanning their comments on HN than in an hour of interview time.<p>4. Put all the keywords you like <i>at the end</i>. Machine searches will find them there and it won't distract humans trying to read the thing.<p>Edit: fixed URL
I'm currently researching and developing my own resume. The current iteration is here: <a href="http://bliti.github.io/resume/" rel="nofollow">http://bliti.github.io/resume/</a><p>Its built on top of bootstrap 3, and I open sourced the markup and css that I used to construct mine. Find it here (with clear usage instructions): <a href="https://github.com/bliti/resume" rel="nofollow">https://github.com/bliti/resume</a><p>Aside from the presentation, I have been testing structure and content. Aside from the usual experience and skills, I have included other non-standard fields (in the software world). So far, I have been getting a better response rate than the first iterations. I plan to blog about my findings after I finish the research.<p>By the way, go and fork my stuff if you want to save time building a pretty web/mobile/pdf resume.