The brutal truth about modern hiring: your resume is read first by an Applicant Tracking System, then skimmed by a tired recruiter for less than ten seconds. That double filter shapes every choice you make on the page. Optimise for the human and forget the machine, you never reach the human. Stuff it with keywords and ignore the human, you get filtered at the first screen. Win both rounds, in that order.

Understand the funnel before you format a single line

A mid-sized company posting one role receives 150 to 300 applications. The recruiter is not reading 300 resumes. The ATS ranks them, the recruiter opens the top 25, the hiring manager sees 5 to 10. Eye-tracking studies from Ladders and similar platforms show the same thing every time: on the first pass, a recruiter looks at your name, most recent title, company, dates, and one or two bullets. Six to eight seconds. If nothing lands, the tab closes.

That is the funnel you are writing for. A document built to survive two filters: a parser that does not understand context, and a human who has read forty CVs today.

The rule: every choice should be defensible against the question “does this help me clear the ATS or hold the recruiter’s eye in seven seconds?” If the answer is no, cut it.

Use a single column, plain layout

Two-column “designer” templates break ATS parsing. The parser reads top to bottom, left to right, and when it hits a sidebar it either drops your skills section or merges your job titles into your education. Save Canva for your portfolio site. For the document a recruiter actually reads, use a single column, black text on white, with clear section headings.

Specifics that matter:

  • One font, sans-serif, 10.5 to 11pt body, 13 to 14pt headings.
  • No tables, text boxes, images, or icons. The parser mangles them.
  • Standard section names: “Experience,” “Education,” “Skills.” Not “Where I’ve Made an Impact.” The ATS scans for the standard words.
  • Real bullets (hyphen or round bullet), not custom glyphs.

Ugly? A little. Effective? Yes. The most expensively designed resume is worth nothing if it parses as garbled text.

Lead with impact, not duties

The most common resume mistake is describing what you were responsible for instead of what you changed. Hiring managers do not care what you were “responsible for.” They care what moved while you were in the chair.

Instead of:

Responsible for managing the customer support queue.

Write:

Cut customer response time from 14 hours to 2 by introducing tiered triage and macros, lifting CSAT from 78% to 92%.

Every bullet should follow the pattern action -> mechanism -> measurable result.

A few more rewrites to calibrate:

Instead of “Handled social media,” write “Grew Instagram from 4k to 31k in nine months by shifting to short-form video, lifting referral traffic 3x.”

Instead of “Worked on accounting,” write “Cut month-end close from 11 days to 4 by automating the reconciliation pipeline in QuickBooks.”

Instead of “Helped onboard engineers,” write “Rebuilt engineering onboarding, cutting ramp-up from 9 weeks to 4 across 12 new hires.”

A real verb at the front, a mechanism in the middle, a number at the end.

The five sections you actually need

  1. Header — name, phone, email, LinkedIn, city. No photo, no full address, no date of birth.
  2. Summary — 2 to 3 lines, written for this job.
  3. Experience — reverse-chronological, 3 to 5 bullets each.
  4. Skills — concrete tools and methods, no soft-skill fluff.
  5. Education / Certifications — short. Move it above experience only if you are a new grad with no work history.

That is the spine. Anything else — “Interests,” “Languages,” “Volunteer Work,” “Publications” — earns its place only if it directly supports the role.

Tailoring the summary to the role you actually want

The summary is the first thing a recruiter reads after your name. A generic summary is wasted lines and signals you sent the same document to forty other companies.

Tailor it to what the role really is:

  • IC specialist — lead with depth. “Backend engineer with 6 years scaling payments systems in fintech. Led the ledger rewrite that cut reconciliation errors 80%.”
  • IC generalist — lead with adaptability and outcomes across domains. “Full-stack engineer who has shipped across web, mobile, and internal tools. Owns features from spec to launch.”
  • Management — lead with team size, scope, and business outcomes, not technical depth. “Engineering manager, 12 reports across two squads. Took the team from 30% on-time delivery to 85% in a year.”
  • Career changer — lead with the transferable thread, not the gap. “Former physics teacher moving into data analysis. Six months of applied projects in SQL and Python, plus eight years explaining hard concepts to skeptical audiences.”

If you cannot write three different summaries for three different roles, you have not thought hard enough about which role you want.

Showing impact when you don’t have hard metrics

Numbers are the cleanest currency on a resume, but plenty of real work does not come with a dashboard. Internal tooling, research, design, ops — much of it is hard to quantify. Do not invent numbers. Reach for the next-best signals.

  • Scope. “Owned the design system used by 40 engineers across 6 product teams.”
  • Complexity. “Migrated a legacy Rails monolith handling 200k daily users with zero downtime.”
  • Stakes. “Led incident response for a Sev-1 outage affecting the company’s largest client.”
  • Recognition. “Selected from 80+ engineers to present at the company-wide all-hands.”
  • Before-and-after. “Inherited a release process that took three days and four people. Got it to one-click deploy any engineer can run.”

Qualitative impact done well beats vague quantitative impact. “Grew revenue significantly” is worse than “Rebuilt the onboarding flow the CEO called out as the quarter’s biggest unlock.” Specificity is the point.

Match the keywords from the job description

ATS systems rank you by keyword overlap. If the job says “Salesforce administration,” don’t write “CRM management.” Use their exact phrasing — that is not gaming the system, it’s speaking the recruiter’s language.

The practical move: pull the job description into a text editor and highlight every noun phrase that looks like a skill, tool, or methodology. Cross-reference your resume. Ones you have but described differently — rewrite to match. Ones you don’t have — leave alone. Padding with skills you cannot defend is a fast way to burn a referral.

Spread the matched keywords across skills, summary, and naturally inside your bullets. Do not hide a wall of white-text keywords at the bottom — modern ATS platforms flag it and recruiters auto-reject.

Chronological vs functional vs hybrid: pick one, and pick well

Three formats dominate. The debate is mostly settled.

  • Chronological lists jobs newest to oldest with bullets under each. This is what 90% of resumes should be. Recruiters expect it, ATS parses it cleanly, career progression is visible at a glance.
  • Functional groups experience by skill area instead of job, often burying dates at the bottom. Recruiters read this as “trying to hide something” — a gap, a short tenure, a pivot. Avoid it.
  • Hybrid opens with a short skills or highlights block, then drops into a chronological history. The right answer for career changers, returners, or anyone whose most relevant experience is not their most recent job.

Recommendation: default to chronological. Reach for hybrid only when a straight timeline genuinely misrepresents what you can do. Skip functional entirely.

Keep it to one page (almost always)

Unless you have 15+ years of relevant experience, one page is the right answer. Anything you can’t fit was probably not interesting enough to keep. Recruiters do not read a second page on the first pass — it exists for the follow-up reader, not the screener.

If you are bumping the limit, the cut list is always the same: older jobs get one line instead of four bullets, education loses GPA and coursework, skills drops anything you have not touched in three years.

Resumes for career changers, returners, and new grads

The standard advice assumes a clean linear career. Most are not. Adjustments by situation:

Career changers. Lead the summary with the destination, not the origin. Build a “Relevant Experience” section that pulls projects, freelance work, and initiatives from your old role that map to the new one. Bury unrelated history below with shorter bullets. The deeper playbook lives in our piece on pivoting careers without starting over — the resume is one tool inside that larger move.

Returners. Address the gap briefly and confidently in the summary — “Returning to engineering after two years caregiving” — and move on. List contracting, volunteer, or upskilling work in that period as real experience with real bullets. The worst move is an unexplained gap; the second-worst is over-apologising for it.

New grads. Education at the top. Lead with internships, capstone projects, research, and anything you built outside coursework. Three impressive projects beat a list of clubs. If you did not intern, build something publicly — a side project with real users beats a 3.9 GPA.

What to cut today

  • “References available upon request” — assumed, not useful.
  • Hobbies — unless directly relevant to the role.
  • A profile photo — bias risk for the employer, parsing problem for the ATS.
  • The word “synergy” — and “results-oriented,” “team player,” “go-getter,” “passionate about excellence.” Filler.
  • Outdated tools — they date you and invite questions about why you stopped.
  • Your full mailing address — city and country are enough.
  • High school education — once you have a degree or three years of work, drop it.
  • Months on jobs older than five years — years are fine, precision is noise.
  • A long objective statement — replaced by the summary, which is about the employer, not you.
  • Personal pronouns — “I led the migration” reads worse than “Led the migration.”

A great resume is a marketing document, not an autobiography. Edit ruthlessly.

The document itself is part of the message.

  • Format. Submit PDF unless the portal asks for Word. PDF preserves formatting; DOCX renders differently on every screen. Modern ATS platforms parse PDFs fine — the old “PDFs break the ATS” advice is years out of date.
  • Filename. Use Firstname-Lastname-Resume.pdf. Not resume_final_v7.pdf, not CV.pdf. A recruiter’s downloads folder has a dozen files called “Resume” by Friday. Yours should be findable.
  • LinkedIn. Always include it. Make sure the profile matches the resume — mismatched titles or dates are the most common reason recruiters quietly disqualify a candidate they liked on paper.
  • GitHub or portfolio. Include only if it represents you well. An empty GitHub with a pinned tutorial repo from 2021 hurts more than no link.
  • Personal site. Valuable if it shows writing, taste, or work the resume cannot. Skip it if it is a placeholder.

Hyperlinks should be live in the PDF. Test the file on a different machine first.

The resume is one piece of the application stack

Here is the part nobody wants to hear: a great resume does not get you hired. It gets you to the next step. The application stack has four parts, and the resume is one of them.

The cover letter is where you explain why this company, why this role, why now. Three paragraphs, tailored. A generic cover letter is worse than none. A specific one is the highest-ROI hour you will spend on the application.

The referral outperforms everything else. Internal referrals are dozens of times more likely to result in an interview than a cold application. Before you hit submit, spend twenty minutes on LinkedIn finding someone who works there and write a short, honest note. Most will not respond. One yes is all you need.

The follow-up is the cheapest leverage in the process. A thank-you email within 24 hours, a polite nudge a week after a recruiter has gone quiet, a short note when you accept somewhere else. Most candidates skip this step. Doing it consistently puts you in the top decile on signal alone.

Treat the resume seriously, then put it in its place. It is the ticket through the door, not the conversation in the room. The candidates who get hired write it well, then go do the other three things while everyone else is still tweaking bullet points.