• In the US, it is strongly advised to keep a resume to one page if you have less than ten years of experience. More experienced candidates can often justify 1.5 - 2 pages otherwise. Think twice about a long resume.
• Resume screeners look for the same things that interviewers do. They want to know that you're smart and that you can code.
• For each role, try to discuss your accomplishments with the following approach:"Accomplished X by imple-menting Y which led to Z." Here's an example:
  • "Reduced object rendering time by 75% by implementing distributed caching, leading to a 10% reduc-tion in log-in time."
  • "Increased average match accuracy from 1.2 to 1.5 by implementing a new comparison algorithm based on windiff."
• Developing the projects section on your resume is often the best way to present yourself as more experi-enced. This is especially true for college students or recent grads.
• State what the project was and which languages or technologies it employed.
• Be conservative about what software you list, and understand what's appropriate for the company. Soft-ware like Microsoft Office can almost always be cut.
• Listing everything you've ever worked with is dangerous. Many interviewers consider anything on your resume to be "fair game"as far as the interview.
• Some companies will throw out your resume just because of a typo. Please get at least one native English speaker to proofread your resume.
• Additionally, for US positions, do nof include age, marital status, or nationality. This sort of personal informa-tion is not appreciated by companies, as it creates a legal liability for them.