How to a killer resume (for software engineers) by Niniane Wang, May 2005 work in recent years to write engineer for Google (and previously a dev lead at Microsoft), like a software I hundreds of resumes, the decision about whether the interview process to continue to have shown. Some applications were not from a good impression, and others. Increasingly, friends and family their CVS ask me for suggestions to improve, so I made up a list
most frequent pitfalls I've seen, and how to avoid them: 1. technical details of your work include: programming language, your individual contribution, measurement data. Sometimes I see job descriptions, the a single line, such as contain: b. worked with a team of 3 on an E-mail plug-in. The message screener reads your resume with the mentality of assessing 1. how difficult was this work, 2. as is relevant to their own company, so you need to just to be. A better way to write this is: born an Outlook E-mail plugin that performs automatic backups is implemented in C++. The product was together with two other team members who wrote the backup storage server delivered 300,000 customers. 2. Dilute the details of impressive with inconspicuous. If you write too much fluff, it will pull your resume the overall quality down. You don't need to say "The task was completed in time and met the specifications." The reader assumes this, and to write, as if it were a performance a performance not weakens your resume. Free sample resume use cover letter & resume tips from Monster & get the job you want!
Download How to write killer resume (for software engineers) .pdf
Advertisement:
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.