How to Write a Resume That Survives ATS and a Seven-Second Human Scan

A recruiter opens your PDF on a Tuesday afternoon. They are not looking for your life story. They are hunting for a reason to keep reading, or a reason to stop. In the same pipeline, a parsing system has already tried to turn that PDF into fields: title, dates, employer, skills. If either audience fails, you do not get the interview.

That is the job of a modern resume. Not inspiration. Not aesthetics for their own sake. Clarity under pressure, for two very different readers at once.

This essay is not a 40-item checklist. Checklists make people feel busy while their resume stays vague. What follows is a craft framework: how the two audiences actually behave, what to change in your writing, and how to prove the rewrite worked. Along the way, you will see where ApplySharp fits if you want a live preview that stays honest to the page you will export.

The two-audience problem nobody explains cleanly

Almost every bad resume fails for the same reason: it was written for one audience and shipped to two.

Audience one: the machine

Applicant tracking systems are not mystical. They are brittle. They prefer predictable structure: clear section labels, standard date ranges, job titles near employers, skills that appear as words rather than icons. They struggle with text trapped in images, multi-column layouts that scramble reading order, and decorative lines that look clever in Figma but explode in a parser.

The industry myth says “stuff keywords everywhere.” That is cargo cult behavior. Parsers care that your content is extractable. Recruiters care that the extracted content is credible. Keyword stuffing can satisfy a naive filter while destroying trust for the human who opens the file next.

Audience two: the seven-second human

When a human lands on page one, they do not read linearly. Eye tracking and hiring practice both point to the same pattern: name and current role, then evidence of scope, then proof that you moved a number that mattered. Everything else is optional until those land.

Those weights are directional, not a lab study you should tattoo on your forehead. The point is strategic: if your header is weak, your recent bullets are soft, and your skills are a junk drawer, no amount of typography will save you.

A resume is not a biography. It is a product spec for a specific buyer: this team, this role, this week.

What “ATS friendly” actually means in practice

Ignore the influencers selling fear. Here is the operational definition that matters:

1. Selectable text. If you cannot highlight a sentence in the PDF, a parser often cannot either.

2. Standard section names. Summary, Experience, Education, Skills. Clever synonyms (“Quest Log”) are cute and expensive.

3. Dates that a human and a machine can both parse. Month Year - Month Year, or Year - Present. Consistency beats creativity.

4. One primary reading order. If your layout requires the eye to hop columns like a magazine spread, you are gambling.

5. Skills as language, not ornament. Icons, skill bars, and star ratings look “designed.” They often travel poorly.

Notice what is missing: a demand that your resume look like a 1998 Word template. Clean visual hierarchy is allowed. Broken information hierarchy is not.

ApplySharp’s free Plain template exists for this reason: sharp enough for humans, boring enough for machines, and free so you can ship without waiting for permission from a pricing page.

The seven-second scan: what humans actually decide

In those first seconds, a hiring manager is answering three questions, usually in this order:

1. Can I place you? Do I understand your current altitude: title, domain, seniority?

2. Have you done work like ours? Not identical. Adjacent enough that training cost feels low.

3. Do you create outcomes or just occupy seats? Activity language loses. Ownership language wins.

If your resume answers those with fog (“responsible for supporting cross-functional initiatives”), you force the reader to invent your value. Busy readers do not invent generously. They move on.

The bullet that gets interviews (and the one that wastes space)

Most resume bullets are diaries of attendance. The rewrite goal is simple: make the change visible.

Before

Responsible for managing Salesforce reports and supporting the sales team with pipeline updates.

This tells me you were near Salesforce. It tells me almost nothing about skill, judgment, or results.

After

Rebuilt weekly Salesforce pipeline reporting used by a 14-person sales team, cutting forecast prep from ~3 hours to 25 minutes and raising stage hygiene so late-stage slip dropped 18% over two quarters.

Why the second version works for both audiences:

• Object + action: rebuilt reporting (not “supported”).

• Scope: 14-person team (scale without bragging).

• Mechanism: stage hygiene (shows you understand the system).

• Outcome: time saved and slip reduced (buyers can feel this).

• Parsable vocabulary: Salesforce, pipeline, forecast (real terms, not spam).

You will not always have a perfect percentage. That is fine. Use ranges, baselines, and operational outcomes: cycle time, error rate, coverage, retention, margin, conversion, capacity. If you truly have no signal, the problem is not formatting. The problem is that the role was never measured, and you need to reconstruct proxies from decisions you owned.

A rewriting system you can finish in one evening

Open your current resume. For each recent role, run this pass. Do not rearrange fonts yet. Writing first. Layout second.

1. Name the altitude

In one line under the company, state the job as the market would recognize it. Internal titles that sound poetic and mean nothing outside your building should be translated. “People Partner, Growth Guild” might need “HR Business Partner, Growth” beside it.

2. Pick three proof pillars per role

Not twelve bullets of equal weight. Three pillars: the problems you were hired to touch, the systems you owned, the outcomes you can defend in an interview. Everything else is optional detail or delete.

3. Force every bullet through the same skeleton

Action + object + scope + constraint + result.

Example skeleton filled: “Migrated billing ops for 2,200 accounts onto a single reconciliation sheet after a messy CRM merge, reducing month-end close exceptions from 40+ to under 5.”

4. Kill the soft verbs

Helped, assisted, participated, exposed to, tasked with. Replace with verbs that imply ownership: shipped, cut, raised, rebuilt, negotiated, automated, closed, launched, recovered.

5. Align language to the posting without lying

Read the job description once for required evidence, not for keywords to spray. If they need pipeline forecasting and you did pipeline forecasting, say it in their dialect. If you did not, do not invent it. Adjacent truth beats mirrored fiction. Fiction dies in the first screen.

6. Only then choose a layout

Now pick a design that does not fight the writing. If the template needs a headshot, upload one deliberately. If it is a dense executive layout, give it real density, not filler. ApplySharp’s Letter templates exist for people who want the page to feel finished without becoming a graphic design project.

The formatting traps that still wreck strong writers

• Text in images. Beautiful. Unparseable. Unsearchable. Fragile.

• Two-column experience where dates live in a sidebar. Humans can adapt. Many parsers reorder the story into nonsense.

• Skill meters. “Python: 4/5 stars” communicates insecurity more often than mastery.

• Wall-to-wall jargon with no nouns of consequence. If a smart outsider cannot picture the work, a hiring manager may not either.

• One PDF that pretends to serve every role. A sharp general resume plus a tailored top third beats a shapeless mega-resume.

Design is not the enemy. Design that steals reading order is the enemy.

How to know the rewrite worked

Before you send another application, pressure-test the page:

1. The stranger test. Hand the resume to someone outside your field for 20 seconds. Ask them what you do and what you are good at. If they shrug, rewrite the top third.

2. The highlight test. Open the PDF and highlight a full sentence in your latest role. If you cannot, fix the export.

3. The delete test. Remove half your bullets. If the story gets clearer, you were padding.

4. The posting mirror test. For one target role, highlight the posting’s must-haves, then highlight matching evidence on your page. Gaps should be honest, not hidden.

ApplySharp is built around that last mile: enter your experience once, preview the live Letter page, adjust spacing and emphasis, then download a package that still looks like the thing you approved on screen. The free builder gets you moving. The paid Letter designs are for when the page needs to feel inevitable.

A closing standard worth holding

You do not need a theatrical personal brand document. You need a page that survives extraction, rewards a hurried human, and gives an interviewer a clean set of stories to pull on.

Write like the work mattered. Measure what you can. Stop decorating uncertainty. Choose a layout that protects reading order. Then send it while the rewrite is still sharp in your mind.

If you want a place to do that without fighting Word margins for an hour, build on ApplySharp. Plain is free. The craft is still yours.

Continue the series: Write a Cover Letter That Does Not Apologize, Turn Resume Bullets Into Interview Stories, and When Plain Is Enough.