How to Write a Killer Resume (for Software Engineers)

How to Write a Killer Resume (for Software Engineers) by Niniane Wang, May 2005 In the past few years working as a software engineer for Google (and previously a dev lead at Microsoft), I've screened hundreds of resumes, to make the decision on whether to proceed with the interview process. Some resumes gave off a great impression, and others didn't. Increasingly, friends and relatives ask me for suggestions on improving their resumes, so I've created a a list of the

most common pitfalls I've seen, and how to avoid them: 1. Include technical details of your work: programming language, your individual contribution, metrics. Sometimes I see job descriptions that contain a single line, such as: * Worked with a team of 3 on an e-mail plugin. The screener is reading your resume with the mindset of judging 1. how challenging this work was, 2. how relevant it is to their own company, so you need to be specific. A better way to rewrite this is: * Implemented in C++ an Outlook e-mail plugin which performs automatic backups. Along with two other team members who wrote the backup storage server, shipped the product to 300,000 customers. 2. Don't dilute the impressive details with unimpressive ones. If you write too much fluff, it will drag down the overall quality of your resume. You don't need to say "The task was completed on time and met the original specifications." The reader assumes this, and writing a non-achievement as though it were an achievement weakens your resume. Free Example Resumes Use Cover Letter & Resume Tips From Monster & Get The Job You Want! www.Monster.com Reach Legal Employers Resume Writing and Distribution Guaranteed results,...

Website: www.ambriana.com | Filesize: 47kb
No of Page(s): 3
Download How to Write a Killer Resume (for Software Engineers).pdf