Free The Google Resume by Gayle Laakmann McDowell Page B

and marketing professional with 10 years of experience growing new business unit from $10 million to $100 million seeking a position as a marketing lead in consumer software.
    If you don’t need to redirect your résumé to a new role, you should probably stick to just a summary or a list of key accomplishments.
    Be aware that objectives may prevent you from getting roles that could have interested you. What if that program manager lead position would have been perfect for you, but the recruiter doesn’t contact you because you said you were interested in marketing roles?
    Summary (or Key Accomplishments)
    While summaries can wow the reader, they’re usually so vague that they have no impact at all. Roy, an ex-Microsoft and current Google developer, says, “I would never look at a résumé and say, ‘Well, this person says he’s a go-getter. Let’s hire him.’ It’s like putting ‘Loves to Laugh’ on a Match.com dating profile. No one’s buying it.”
    Your summary should read much more like key accomplishments—so much so, in fact, that these sections are often called “Summary and Key Accomplishments.”
    The following objectives will demonstrate your value-add to the prospective company:
“Software engineer lead with several years’ experience implementing large back-end systems in Java and C++, including three as a lead/team manager; led re-architecture of critical system that serves 50 million requests per month, reducing request latency by 20 percent; designed new API for financial product used by 5 of the 10 biggest banks, which accounted for an additional $10 million in revenue; awarded the prestigious ‘Green Sticker’ award, given to the top 5 percent of engineers based on total impact to firm.”
“Program manager with five years of experience leading feature design of enterprise-oriented products; proposed solution and built team to solve number one cause of customer complaints, and completed project three months ahead of schedule; reduced development costs by 35 percent by creating plan to merge related products into one, more generalized product; oversaw integration of acquired technology by leading 17 developers and 9 testers from two companies, resulting in an additional $50 million of sales.”
    Work Experience
    For most candidates, the Work Experience section is the most important section of their résumé. Your work experience should, at the minimum, list your job title, company name, firm location, and dates of employment. If you are working for a large firm with many products, such as Microsoft or Amazon, you may also want to list your team.
    Your most recent job should have around four or five bullets of one to two lines each. Each bullet should focus on your accomplishments , not your responsibilities, and should be backed up with numbers whenever possible.
    If you have trouble creating this section, start with listing your biggest accomplishments on a sheet of paper. Remember, though, that what was the most impressive to you or your team, who understand the full complexities of the problem, may not be as impressive when described out of context and in a mere 25 words.
    How Far Back Should It Go?
    Without showing any gaps, you should list only as far as the positions are relevant—and usually no more than three to five jobs. This means that if your career started as an information technology (IT) technician, but you then moved to testing, and then later had a few programming positions, you can probably cut the IT technician. A résumé does not need to be a complete employment history.
    Projects
    Software engineers with substantial nonwork experience should include a Projects section. For recent graduates or current students, this is a great way to diversify your résumé and show some additional accomplishments.
    Desktop Calendar (Fall 2010, Individual Project): Implemented web-based calendar supporting online storage and syncing, meeting invites, and conflict resolution. Python,