Video summary

Engineering resume review (with top ex-Google recruiter)

Main summary

Key takeaways

News and Commentary

Overview

This video is a “resume roast” where an ex-Google recruiter, Cody, reviews two engineering resumes. The core takeaway is that recruiters and hiring managers spend very little time on resumes, so the document must be:

  • Easy to scan
  • Prioritized at the top
  • Backed by concrete, quantified impact (not generic descriptions)

General Problems Cody Says Most Resumes Have

Wasted “top real estate”

The first section (summary/header) is often filled with filler that doesn’t answer key questions quickly.

Fluff summaries

Phrases like:

  • “Well-versed in latest technologies”
  • “Adaptable”
  • “Purpose and fulfillment”

…don’t help recruiters assess fit because they provide no specifics or proof.

Not enough quantifiable impact

Words aren’t enough—Cody emphasizes adding numbers to demonstrate scope and results, such as:

  • iterations
  • devices impacted
  • revenue/traffic changes
  • hiring outcomes
  • attrition rates

Too much filler instead of answers

Resumes should be tailored to the role and structured to answer likely recruiter questions within seconds.

Unnecessary location/address details

A full home address is unnecessary. Include only what’s relevant, such as:

  • name
  • contact info
  • LinkedIn link
  • work location preferences (e.g., hybrid/remote/Austin)

Resume 1: “Johnny Johnson”

Cody’s criticisms

  • Summary is pure fluff: vague claims like “latest technologies” and “extremely adaptable” without specifying technologies or evidence of staying current.
  • Unclear mapping of tech/experience: Cody wants a quick view of relevant years of experience (e.g., tracking “intern in 2021” and entering the industry in March 2022).
  • Bullets lack quantitative detail: claims about designing software, sensors, devices, plugins, etc. without measurable outcomes.

Cody’s recommendations

  • Keep the resume easy to read and remove unnecessary information (like a full address).
  • Replace generic language with specific, measurable impact, including:
    • what was implemented
    • how many iterations
    • number of devices impacted
    • scale and results Even early-career work should still be quantified to show real contribution.

Resume 2: “Kevin” (Engineering Manager Targets)

Cody’s criticisms

  • Values/mission-style summary without evidence: leadership should be demonstrated with measurable outcomes.
  • Early lack of strong data: the opening section is treated as filler; Cody wants more relevant detail sooner.
  • Manager impact isn’t specific enough: even if management responsibilities appear, Cody says recruiters assume them—what they need are results and impact.

Cody’s recommendations

  • Include measurable management metrics, such as:
    • attrition rate over multiple years
    • hiring volume
    • promotions
    • revenue impact
    • cost savings
    • major project outcomes
  • Highlight 2–3 standout bullets that show direct leadership results; otherwise, the resume doesn’t earn immediate attention.

Overall Takeaway

Across both resumes, the message is consistent: resumes should be scannable, tailored, and evidence-driven.

  • The top section must answer recruiter questions immediately.
  • The work history should tell a results story using numbers, not generic claims.

Presenters/Contributors

  • Cody — ex-Google recruiter (primary resume reviewer)
  • Host / “hey everyone” narrator — uncredited in the subtitles
  • Additional contributors — none mentioned explicitly beyond the host and Cody

Original video