This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
You want to list your work experience, in reverse chronological order, explaining what you did at each company. You'll list both your responsibilities and what you did to make things better, and how you helped make the company money.
Every company exists to make money. It either wants to make more money, or to make projects happen faster. Anything you did to make those happen are your key selling points.
Mainly your accomplishments that will be of interest to your prospective employer. You will have to customize your resume and your interview discussions to preospective employer's needs.
-- Some employers put more emphasis on training and mentoring ability since they may have a fairly young team of Java/JEE developers while others require customer facing experience.
-- Some employers are keener on candidates with good domain knowledge and experience e.g. insurance, financial products, telecom services, etc while others are keener on candidates with good analytical and problem solving ability since their applications require complex processing logic with lots of calculations.
-- Existing projects facing performance issues would prefer candidates who can identify and fix performance issues while new projects may prefer candidates with stronger design skills.
-- Applications requiring complex reporting requirements may see your experience in writing complex SQL queries more favorably.
-- Some employers are very particular about excellent soft skills since they may have large development teams with multi-disciplinary approach where you would be expected to liaise with staff at all levels.
-- Organization that is reviewing their existing software development process or embarking on the SOA initiative may prefer candidates who have exposure or experience with development methodologies such as RUP, agile development methodologies like XP, etc, and SOA itself.