Instead of listing your responsibilities, talk about concrete numbers and achievements. If you list things like "interfaced with QA", "participated in planning

Instead of listing your responsibilities, talk about concrete numbers and achievements. If you list things like "interfaced with QA", "participated in planning with product management", or "used JSPs and Servlets to write web-based mail client", you will not stand out much from other applicants. You should focus on (preferably quantifiable) results. Examples: "designed and implemented QA testing plan that raised code coverage of a 100 KLOC email service from 18% for 63%", "wrote web-based mail client that handles 8000 users and up to 50 requests per second", etc. Try to show what you have achieved, not what you have worked on. Along with making your resume stronger, specific points often help guide your interview predictably. I have 1-2 bullet points that everyone asks about, and it's great to have a few interview questions that you know you will ace.