What does it take to make a ‘good’ developer resume?

My gut reaction to this question is the old saw about <i>any</i> writing: show, don't tell. You need the target audience of your resume to <i>see</i> why you'd be valuable to them. Instead of listing a bunch of buzzwords, explain relevant projects you worked on, including the relevant technologies. I always list skills first, then under my work experience I detail the projects that developed/took advantage of those skills.

GitHub url, big and center.

Sometimes it helps to look at examples of bad resumes. Some real gems here: <a href="http://resumedoctor.com/WorstResumes.asp" rel="nofollow">http://resumedoctor.com/WorstResumes.asp</a>.

Java, web and web design! have you any idea on how to do web surveys in a smart way? You could've written a survey app using those 3, or used existing ones to save your visitors from thinking and writing for questions that could've been fairly objective. And then maybe you could apply some statistics on the data and do something better with it :) At least I wont like writing something more than this

<i>Do you prefer a single page resume or multi-page? If multi, then how many pages of resume you think is good enough to sell you?</i><p>Single page. If I absolutely, positively have more to say, I occasionally attach a one page Appendix, "Sample of Project Particulars," which includes 5 or 6 quick stories about major projects I completed that are relevant to the company and position I'm submitting to.<p><i>Do you elaborate on your work experience (like, job description, responsibilities, etc.) or you want to keep it short?</i><p>Yes, but I wouldn't say "elaborate". More like "itemize". Forget about things like "experience", "job description", or "responsibilities". Focus on one thing only: results. What I did, who it was for, why they needed it, and what they accomplished with it. "Built an AJAX e-commerce site that enabled a $10 million catalog distributor to double sales in 6 months." Show that I understand the forest in which I'm planting trees. Short, sweet, and to the point. If it catches their attention, they'll ask you more about it. If it doesn't, then you probably don't want to work for them, anyway.<p><i>Do you have more than one resume, like a master one with all details and one page resume targeted to a particular position?</i><p>Just a custom one pager specially made for each company. I show them the same level of special attention that I expect in return.<p><i>In what order you present information in the resume: Objective, Experience, Skills, Education, Summary?</i><p>1. Very short summary (with embedded skills) that pretty much says it all, "AJAX programmer, expert level in e-commerce, 100 projects completed, ready for next long term challenge in Big City, USA."<p>2. Applicable accomplishments in reverse chronological sequence. (Emphasis on "accomplishments".)<p>3. Degrees.<p><i>Do you really think the resume layout matters more than the content itself?</i><p>No.<p><i>Which font do you use for your resume? Arial? Verdana? Webdings?</i><p>Who cares.<p><i>Do you prefer to maintain an online version of your resume?</i><p>No. I'll contact them. I don't want anyone contacting me.

Be real, don't be redundant. When I used to interview contractors, I got so tired of reading "enterprise Java developer experienced with all aspects of the SDLC" blah blah blah followed by globs of alphabet soup.<p>Just highlight the most relevant points of past projects, related to the position for which you're applying.

Computer Modern.