The Engineering Resume: What Reviewers Actually Read

A resume screener spends roughly two minutes on your resume, reading maybe a quarter of it, checking it against a short list of role requirements. Your resume’s job is to survive that pass: make the match obvious, make the impact concrete, and give the reader nothing to trip over. This guide is written from the reviewer’s side of the table, because the employer version of this document (how companies read technical resumes and screen in two minutes) is exactly what your resume is up against.

What the two-minute screen actually checks

Structured screeners read against the role’s must-have list, in roughly this order:

1. Current role and scope. Title, company, how long, and what you actually own. This is the ten-second read that decides whether the next hundred seconds happen.
2. Skill match. The three to five requirements from the job description, checked against your recent work, not your skills section.
3. Impact evidence. Numbers, outcomes, and specifics that suggest the work was real and yours.
4. Trajectory. Growing scope over time, or a coherent story when scope changed. Gaps and pivots need one framing line, not an apology; addressing career gaps confidently covers this well.

Note what is absent: hobbies, objective statements, and long skill inventories. Screeners at well-run companies check criteria; give them the criteria.

Impact bullets: the core skill

The difference between a forgettable resume and a strong one is almost entirely in the bullets. The pattern that works: what you did, how, and what changed, with a number.

Weak: “Responsible for improving API performance.” Strong: “Cut p95 API latency from 800ms to 120ms by adding request-level caching and rewriting the three hottest queries; support tickets about timeouts dropped ~70%.”

Rules that follow from how these get read:

• Lead with the outcome when the outcome is impressive, with the action when the craft is the story.
• One number per bullet minimum where you can defend it. Estimates are fine (“~40%”, “roughly 2×”); invented precision is not, because interviews probe bullets, and a bullet you cannot back up in depth is worse than no bullet. Interviewers using structured, criteria-based evaluation will ask you to walk through exactly how you got that number.
• “We” versus “I” honestly. Claim your part specifically (“designed the schema and led the migration”) rather than absorbing the team’s work. The follow-up questions find the seam anyway.
• Cut the first verb cliché tier: “spearheaded,” “leveraged,” “utilized.” Plain verbs read as confidence.

Format: boring is a feature

• One page under ~8 years of experience; two pages after that is fine. Nobody reads page two of a junior resume.
• Reverse-chronological. Functional formats read as hiding something.
• Single column, standard headings, no photos, no skill-bar graphics. Clever layouts cost you in both ATS parsing and reviewer patience.
• PDF, unless the application explicitly asks otherwise.

What ATS systems actually do

Candidates over-fear the robot. Most applicant tracking systems parse your resume into fields and make it searchable; very few auto-reject on keywords. What actually happens: a human searches or filters, and resumes that parsed badly (tables, text boxes, headers containing contact info, two-column layouts) come up garbled or not at all. Optimize for clean parsing and honest keyword coverage (name the technologies you really used, in context), then stop worrying about the machine and write for the human.

Tailoring without rewriting your life

You need one strong base resume and ten minutes of tailoring per application, not ten resumes:

1. Reorder bullets so the role’s must-haves appear in your top third.
2. Mirror the job description’s exact terms where they are true (“Kubernetes” if they say Kubernetes and you mean Kubernetes).
3. Cut anything on the base resume that is irrelevant to this role.

Tools to streamline applying covers keeping this fast across many applications, and using AI for job searching covers where AI drafting helps and where it produces the exact generic mush screeners have learned to skip.

Special cases

• Early career / no “official” experience: projects, contributions, and community work count when framed as work; see the engineering portfolio guide and leveraging community contributions. A portfolio carries weight a thin resume cannot.
• Freelance to full-time: consolidate client work into one entry with scope and outcomes; converting from freelance covers the framing.
• Career changers and veterans: translate domain vocabulary into engineering outcomes; military/government transitions has the pattern.
• Senior+ candidates: shift bullets from “built X” toward “owned X area, grew Y people, made Z call.” Scope is the signal; navigating age bias covers trimming decades-old detail without hiding experience.

Get human eyes on it

After you have applied everything above, get feedback from people who screen resumes for a living. The community at r/EngineeringResumes gives blunt, specific reviews for free, and their wiki is genuinely good. One round of outside feedback catches the blind spots this guide cannot.

Then put the resume down. Past the screen, nobody hires the document; the interview prep guide takes over from here.