What does it take to make a ‘good’ developer resume?
veerasundar.com
veerasundar.com
You also seem to imply that experienced developers [i]wouldn't[/i] be using a cutting-edge tool to share code. Why wouldn't they? Does 'experienced' have to mean 'curmudgeonly'?
"You also seem to imply that experienced developers [i]wouldn't[/i] be using a cutting-edge tool to share code. Why wouldn't they? Does 'experienced' have to mean 'curmudgeonly'?"
Straw man. My implication is only that it's foolish to screen for experience using a trendy tool that is adopted by only a tiny percentage of programmers.
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.
Do you elaborate on your work experience (like, job description, responsibilities, etc.) or you want to keep it short?
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.
Do you have more than one resume, like a master one with all details and one page resume targeted to a particular position?
Just a custom one pager specially made for each company. I show them the same level of special attention that I expect in return.
In what order you present information in the resume: Objective, Experience, Skills, Education, Summary?
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."
2. Applicable accomplishments in reverse chronological sequence. (Emphasis on "accomplishments".)
3. Degrees.
Do you really think the resume layout matters more than the content itself?
No.
Which font do you use for your resume? Arial? Verdana? Webdings?
Who cares.
Do you prefer to maintain an online version of your resume?
No. I'll contact them. I don't want anyone contacting me.
What of the developer who works on something ambitious that ultimately flops and becomes a total write-off for the company or client? What of the developer who coasted along doing nothing on a team of people who built some billion dollar product? What of the developer who can't really itemize their contribution in dollar amounts because they don't have the foggiest idea how much in dollar amounts they contributed, apart from how much they charged for their time?
Failure on a project is not a communicable disease that spreads to other projects through developers; success is likewise. Failure is so common that a developer without decades of work experience runs a non-negligible risk of not having a big success. And having a big success does not predict with a high degree of certainty future successes.
To add to the trickiness of this problem, we can't just tell people "sniff out projects that smell of failure, and avoid." How would they know? Developers are not clairvoyant, so the solution to this is to use heuristics. Some of these heuristics are unique to one individual who got burned in some particular way. Some are as ubiquious as development best practices. Either way, they can be wrong for a particular context, or sometimes wrong in general but kept in peoples' minds by inertia and repetition.
This is a harder problem than just quoting dollar amounts, and assuming that zero net dollars means zero talent. I can't help but think that when someone can put on their resume "Built a site that made $x million dollars," it may be as much a reflection on their luck of being at the right place at the right time as it is on their ability to execute after finding themselves there.
Just highlight the most relevant points of past projects, related to the position for which you're applying.