·5 min read·The WunderJob Team

Stop optimizing for the ATS. Optimize for humans.

The applicant tracking system folklore is mostly wrong. Here's what actually happens to your resume, and who you should be writing for.

job-searchstrategy

A friend of mine spent three weekends rewriting her resume to "beat the ATS." She replaced nice phrases with awkward keyword stuffing. She made her formatting weirdly plain. She added a hidden block of white text at the bottom listing every skill the job description mentioned.

Then she asked a recruiter friend what she thought. The recruiter laughed and said: "Nobody was going to filter you out. You had 12 years at brand-name companies. The ATS doesn't work the way you think it does."

There's an entire industry built on ATS panic. Most of it is wrong, outdated, or actively harmful. Let's clear up what's actually happening, and then talk about what matters.

What the ATS actually does

An applicant tracking system is, for the most part, a database. It stores resumes so recruiters can search them later. That's it. It's not a gatekeeper with secret rules.

Yes, some ATS platforms can auto-reject resumes based on keyword matches or knockout questions ("Do you have 5+ years of experience?"). But the hard filters are usually set up for legal and basic-qualification reasons — work authorization, minimum years of experience, location. They're rarely set up to filter on "number of times the word 'Python' appears."

When a recruiter searches the database, they type something like "senior backend engineer, Kafka, GCP" and skim the results. They read the resumes of the top 20 or 30 matches. They make decisions based on what they see.

That means the reader is a human, 95% of the time. And humans read resumes for about 7 seconds before deciding whether to read further.

What humans actually notice

Seven seconds. Not a lot. Here's what a recruiter notices in that window, in rough order:

  • Your current or most recent title and company. This is the single biggest signal.
  • The visual shape of the resume. Is it clean? One column or two? Does it look like you cared?
  • The bullet at the top of your most recent role. Does it say something specific and impressive?
  • Dates. Any suspicious gaps or bounces?
  • Whatever you've chosen to put in the header — a line of positioning, a summary, a title.

After seven seconds, they decide whether to read more. Everything you've done to please the mythical ATS robot — keyword dumps, weird formatting, giant skills sections — is invisible to this process. Worse, some of it hurts you, because it makes the resume look desperate or bad.

What to actually do

Write for the recruiter reading 80 resumes that morning with a lukewarm coffee.

Lead with positioning. One line at the top, under your name, that says what you are. "Senior product manager — B2B SaaS, growth-stage, consumer subscription backgrounds." This is more powerful than a fluffy two-paragraph summary. It lets the reader file you in three seconds.

The top bullet of each role should be specific and outcome-focused. "Led a team of 7 engineers" is a description. "Led a team of 7 engineers through a re-platforming that cut infrastructure costs 34%, shipped in Q2 2024" is a story a recruiter can picture. Numbers, time, scope.

Use normal formatting. A single column, reverse chronological, sensible headings, real dates. Save the PDF. Use a real font. You do not need to avoid two columns out of ATS fear — most modern systems parse them fine. You should avoid them because they make the resume harder for the human reader to scan.

Mirror the company's vocabulary. If they say "platform engineering," don't say "DevOps" on your resume. This isn't keyword stuffing, it's translation — same work, different word, helps the reader match you to the role.

The cover letter question

Cover letters are weirdly contentious. Some recruiters say they never read them. Some say they're the first thing they look at.

Here's the honest take: 80% of cover letters are generic and don't help. The other 20%, which are specific and smart, can make a real difference when the role is competitive or when your background doesn't obviously match.

A useful cover letter is short — three paragraphs max — and does three things. Says why you're interested in this specific company (not generic flattery — something real). Says why you'd be useful for this specific role (one concrete example from your past, not a recap of your resume). Says what you're looking for in your next role, briefly and honestly.

If you can't write those three paragraphs in 20 minutes, you haven't done enough research on the company. Go back to that step.

A concrete example

A candidate we talked to — a data scientist with a PhD — had been applying for six weeks with nearly zero response. Her resume opened with "Highly motivated data scientist with strong analytical skills and passion for solving complex problems." It was two pages of similar generic phrases.

We rewrote the top. New header: "Senior Data Scientist — ML for recommendations, 6 years at consumer-scale (30M DAU)." New first bullet under her current role: "Rebuilt the recommendation model powering the home feed; shipped in Q3 2024; lifted session length 8.2% in A/B test across 14M users."

Same person, same experience. Response rate went from ~3% to ~22% over the next month.

The ATS didn't change. What changed is she stopped writing for a robot and started writing for the recruiter who'd see her resume on a Wednesday morning.

Takeaway

The ATS is mostly a ghost you've been trained to fear. Write a resume a smart, busy, slightly tired human would respect. Lead with positioning, support with specifics, and get out of the way. The rest is noise.

Build your next CV with intent.

Know your values. Check job fit. Build a CV that matches.

Start Free