How a resume gets read: the four readers, and how we write for each

4 min read

When an application disappears without a reply, most people assume someone read their resume and decided they weren't good enough. Usually that's not what happened. Before anyone decides anything, a resume passes four readers in a fixed order: two pieces of software, then two busy people. Each one has its own job, its own pressures and its own reasons to say no.

Who reads your resume, and in what order?

The first reader is the ATS parser. An applicant tracking system takes your PDF and turns it into a database record: jobs, titles, dates, and a list of skills with months of experience attached to each. It doesn't care how the page looks. It cares whether it can tell where one job ends and the next begins.

The second is the ATS job ranking. The same system holds your record up against the job posting and scores it next to everyone else who applied. When a role gets three hundred applicants, the recruiter starts at the top of that list and rarely reaches the bottom.

The third is the recruiter, the first person to see your resume. A recruiter is juggling many open roles, usually outside their own field, with a list of keywords from the hiring manager. They give your resume a few seconds and one question: does this person fit, or is there a reason to pass?

The last is the hiring manager, the person who leads the team and owns the problem you'd be hired to solve. They read slowly, looking for one or two pieces of work that tell them you've been here before, and they start writing interview questions as they go.

Why does the order matter?

Because each reader only sees what the one before it let through. A brilliant story for the hiring manager is wasted if the parser glued two of your jobs together and the ranking put you on page twelve. A resume stuffed with every keyword might rank well and then lose the recruiter in five seconds.

That's why ResumeBuilder's Optimize journey has four steps in the same order. You fix what would stop the resume first, then what would stop it next. It's a calmer way to work than a single list of fifty suggestions, and it matches how the resume will actually travel.

Where do ResumeBuilder's checks come from?

ResumeBuilder is a structured collection of real feedback given to real candidates' resumes over the last five years, by recruiters and by engineers who work as hiring managers and interviewers at companies like Google, Microsoft, Amazon and Mastercard.

Those reviewers left their comments the way reviewers do: in the margins of real resumes, one line at a time. Read enough of them and the same notes keep coming back. A bullet that describes a duty instead of a result. A tech stack that lists every tool ever touched. An opener like "Responsible for" where "Led" was true. A project with no hint of its scale. And many more, each one written by someone who has sat on the other side of the table and decided who gets the call.

We sorted that feedback into the problems it kept pointing at and the way reviewers fixed each one, and wrote each into a check with a name, an explanation and a suggested fix. So the same problem reads the same way on every resume, and every suggestion traces back to something a real reviewer said to a real candidate. We keep comparing the checks with how experienced reviewers grade resume bullets, and when they disagree, the check changes.

What makes the checks different from generic resume advice?

A check never speaks in generalities. It highlights the exact words it's about in your resume, says why a reader would stumble on them, and offers a rewrite you can use, edit first, or ignore. If you ignore it, it stays ignored on that resume.

A check also never makes things up. When a bullet would be stronger with a number you haven't given, the suggestion leaves an X for you to fill in with a real, honest one. An invented number might get past the software, but it falls apart in the first interview.

And the job ranking gives the same answer every time for the same resume and the same job. That turns it into a measuring stick: rank, edit, rank again, and the difference is your edit.

Was the format tested against real ATS parsers?

Yes. We printed resumes from ResumeBuilder and ran them through Textkernel Tx (formerly Sovren) and Affinda, two of the parsing engines behind many applicant tracking systems, and through Klippa. Then we compared every field that came back with what the resume said: which section headings were found, whether each job kept its own title and dates, and how many months of experience each skill earned. What we learned shaped the format and the ATS checks. The details are in How an ATS parser reads your resume.

Read the four steps

1. How an ATS parser reads your resume
2. How an ATS ranks your resume against a job
3. What recruiters look for in a resume
4. What hiring managers look for in a resume