A post doing the rounds on DEV this week describes a developer who got rejected from 50 jobs, deleted almost everything on the resume except one story, and started getting callbacks. I believe it, and I have seen the same pattern in resumes I review. I have also seen the failure mode that follows: the one-story resume reads beautifully to a human and then scores near zero in the applicant tracking system (ATS), because the keywords that used to sit in six weak bullets disappeared with them.

I wrote this with help from AI tools and checked every example and claim myself. I build Smart Resume Analyzer, an ATS and resume-matching tool, and this post opens a new series about engineering resumes that get callbacks. Part 1 is the structural move most resumes are missing: a flagship story that a recruiter remembers and a parser can still index.

📚 Series Roadmap — Engineering Resumes That Get Callbacks

  • Part 1 (This Post): The One-Story Resume Test: Building a Flagship Project Section That Still Passes ATS
  • Part 2: Tailoring Without Lying: Mapping Job Description Keywords to Real Evidence
  • Part 3: AI-Drafted Resumes and Recruiter Skepticism: Making LLM Bullets Sound Like You
  • Part 4: Summary or No Summary in 2026: What Recruiters and Semantic Screeners Actually Read
  • Part 5: Engineering Leadership Bullets: Mentoring, Hiring and Incident Command Without Fluff
  • Part 6: The 15-Minute Pre-Submit Resume QA Pipeline

Previous series: 2026 Tech Hiring & AI Screening Playbook

How do you make one strong story work on a resume without failing ATS keyword filters?

Direct answer: Lead each recent role with one flagship bullet group that tells a single problem, action and measured result story, then keep two to four short supporting bullets that carry the remaining job-description keywords. Recruiters remember the story; the ATS still finds the skills in standard section headings and plain text.

Why the one-story resume works on humans

A recruiter skimming 200 applications is not reading; they are pattern-matching for one reason to keep going. Six bullets of equal weight ("Developed REST APIs", "Worked with Docker", "Participated in code reviews") give them nothing to hold. One specific story does:

Cut checkout p95 latency from 2.4 s to 380 ms by replacing synchronous inventory calls with a reservation queue, lifting conversion 3.1% across 40k daily orders.

That bullet answers the three questions every hiring manager asks: what was broken, what did you do, and did it matter.

Why it can fail on the ATS

Most ATS search is still a recruiter typing terms into a box: Kafka AND Kubernetes AND "Go". Semantic rankers (covered in Part 1 of the previous series) are more forgiving, but they still compare your text with the job description. When you delete five bullets, you delete the evidence for five skills. The story survives; the search hits do not.

Here is a real-shaped example (details changed) of what that looks like:

Version Bullets in latest role JD skills found in text Recruiter impression
Original 8 generic bullets 11 of 14 "Another backend dev"
One-story rewrite 1 long story 4 of 14 "Interesting, but is she a Go engineer?"
Flagship + support 1 story + 3 supporting 12 of 14 "Strong story, clear stack match"

The flagship + support structure

1. Pick the story with the right ingredients

Not every project is a flagship. Score your candidates honestly:

Criterion Weak story Strong story
Problem "Improve the API" "Checkout timed out at peak, losing orders"
Your role Team effort, vague Your design, your PR, your rollout
Measurement None or "significantly" Before/after number with a baseline
Relevance Unrelated stack Uses the target role's core skills
Recency 6+ years ago Last 2–3 years

If your best story is old, it can still lead a "Selected Project" line under that role, but the most recent role still needs its own evidence.

2. Write it as problem, action, result 

BEFORE - Worked on performance improvements for the checkout service. - Used Redis and Kafka. - Collaborated with the payments team. AFTER (flagship) - Cut checkout p95 latency from 2.4 s to 380 ms by redesigning inventory checks as a Kafka-backed reservation queue with Redis idempotency keys; led design review, rollout behind a feature flag and on-call handover (conversion +3.1% on ~40k daily orders).

Put the skill words inside the story where they are true. "Kafka-backed reservation queue" is both a better sentence and a search hit.

3. Add supporting bullets that carry the rest

Pull the job description's required skills and check which ones the flagship does not mention. The job description keyword finder I built does this extraction, but a highlighter and the posting work too. Then write two to four short bullets, each tied to real work:

- Migrated 14 Go services from EC2 to Kubernetes (EKS) with Helm charts and GitHub Actions pipelines; deploy time 25 min -> 6 min. - Added OpenTelemetry tracing across payment and order services, shortening incident triage from hours to minutes. - Mentored 2 junior engineers through their first on-call rotations.

Short is fine here. Their job is coverage and credibility, not drama.

4. Keep it parseable

The structure only helps if the parser reads it:

  • Use standard headings: Experience, Skills, Projects, Education.
  • Keep the flagship as a normal bullet under its role, not in a text box, sidebar or table cell.
  • Do not bold half the sentence; some parsers drop or split styled runs. Bold the metric at most.
  • Keep a plain Skills line that repeats core terms in the employer's spelling ("PostgreSQL", not just "PG").

A magnifying glass resting on a blank sheet of paper on a wooden desk, representing how recruiters and ATS parsers inspect each resume line, AI-generated
AI-generated image.

Where the flagship goes on the page

Career stage Flagship location Supporting bullets Projects section
Student / new grad Projects section, first item Coursework, internship Primary
2–5 years First bullet of latest role 2–3 per role Optional
Senior / staff First bullet of latest two roles 3–4 per role Only for open source
Career switcher Projects + transferable role Mapped prior skills Primary

For seniors, two flagships (one per recent role) is the ceiling. More than that and nothing stands out again.

Diagnostic checklist

  1. Can a stranger repeat your flagship in one sentence after reading it once?
  2. Does it have a baseline and an after number, or a clearly stated scale?
  3. Is it obvious which part was your work?
  4. Does it name the stack, using words from the job description where true?
  5. Do supporting bullets cover the remaining must-have skills?
  6. Are all bullets under standard headings in plain text?
  7. Does the Skills line use the employer's spelling of each tool?
  8. Did you run the file through a parser and confirm the flagship text came out intact?
  9. Did you check the match against the actual posting, for example with a resume vs. job match check?
  10. Would you be comfortable explaining every number in an interview?

FAQ

How long should the flagship bullet be?

Two to three lines on the page. If it needs a fourth, split the context into a supporting bullet. Longer than that, recruiters skim past it.

What if I don't have metrics?

Use scale and outcome instead: traffic handled, team size, number of services, an incident that stopped recurring. "Removed the nightly manual reconciliation step for finance" is measurable without a percentage.

Should I delete old roles to make room?

Shorten them to one or two lines rather than deleting them. Removing roles creates gaps that raise more questions than a short entry does.

Is a one-page resume still required?

Not for experienced engineers. One page is a good target up to about five years; two pages is normal beyond that, provided page one carries the flagship.

Can the flagship be a side project?

Yes, if it is relevant and real: users, stars, downloads or production traffic. Put it under Projects with links, and keep your job bullets honest about day-to-day work.

Do semantic AI screeners care about the story?

They compare meaning, so a specific story with real technical nouns usually matches better than generic bullets. They still cannot reward skills you never mention.

Next in this series, Part 2 goes deeper on tailoring: how to map each job description requirement to real evidence on your resume without inventing experience.

Follow & Connect