🎓 Our next Cohort is starting November 12th, 2026
Career Articles › CV & applications
CV & applications · 7 min read

How to Write a CV That Beats the ATS and Gets Interviews

Most CVs are filtered out by software before a human ever sees them. Here is how to write one that passes the applicant-tracking system and earns the interview.

Before a single person reads your CV, an applicant-tracking system usually scores it against the job and decides whether it is worth a human’s attention. If your CV is not built for both the software and the person, it can vanish into a black hole without ever being rejected by anyone you could learn from. The good news is that beating the ATS is not about tricks or hidden white text, it is about clarity, relevance and evidence. Do those three things well and you satisfy the machine and the manager at the same time.

Watch: writing a CV that beats the ATS

A short, practical video on writing a CV that beats the ATS, to watch alongside this guide.

Mirror the language of the job advert

An ATS works by matching your CV against the advert, largely on keywords. So the advert is not just a description of the role, it is a spelling list. Read it closely, note the exact skills and tools it names, and make sure the ones you genuinely have appear on your CV in the same words. To a keyword scanner, "managed stakeholders" and "stakeholder management" are not the same phrase, and small mismatches quietly cost you.

This does not mean keyword stuffing, which reads as desperate to humans and can be penalised by better systems. It means weaving the real, relevant terms naturally into your experience and skills sections. If the advert asks for "SQL, data visualisation and stakeholder reporting", those exact phrases should appear where they are true of you.

Tailor this per advert. A CV mirrored to one specific role beats a generic one every time, and the tailoring is usually a few small edits, not a rewrite.

Lead with outcomes, not duties

A CV made of tasks reads like a job description that happens to be about you. A CV made of outcomes reads like a performer. Rewrite each bullet as an achievement with a result: what you did, how, and the impact, ideally with a number attached. Numbers cut through because they are concrete and comparable.

This works even without paid experience. Your projects and any mentored work count. "Built a dashboard that cut a weekly report from three hours to fifteen minutes" is a real, hireable line, and it says more about your value than a paragraph of adjectives.

A useful formula for each bullet: action verb, what you did, the result or number. "Redesigned the onboarding email sequence, lifting completion from 40 to 62 percent." Start with the verb, finish with the impact.

  • Start each bullet with a strong action verb, not "responsible for"
  • Attach a number or concrete result wherever you honestly can
  • Cut pure duty statements that have no outcome
  • Put your strongest, most relevant achievement first in each role

Keep the format ATS-safe

Fancy layouts are where good candidates lose to worse ones. Many parsers cannot read tables, text boxes, images, columns, or content in headers and footers, so information placed there can simply disappear from the scan. Use a clean, single-column layout with standard section headings the software expects: Experience, Skills, Education.

Save and send as a PDF unless the employer asks for a specific format such as .docx, and name the file clearly, for example "Firstname-Lastname-CV.pdf". A clearly named, cleanly structured file is easier for both the system and the recruiter to handle.

Resist the temptation to be visually clever. The job of the CV is to be read, parsed and understood, not to win a design award. Save your creativity for the content.

Common CV mistakes that get you filtered

A handful of avoidable errors sink otherwise strong CVs. The most common is sending the identical generic CV to every role, which guarantees a weak keyword match everywhere. Another is burying the relevant experience on page two while the top of the page lists an unrelated objective. A third is listing tools and skills you cannot actually back up, which unravels the moment an interview probes them.

Fix these deliberately: tailor per role, front-load your most relevant evidence, and only claim what you can defend. Then proofread ruthlessly, because typos in the one document meant to show your attention to detail do real damage.

A weak bullet rewritten, step by step

The fastest way to see the difference between a duty and an outcome is to watch one bullet transform. Start with a typical weak line: "Responsible for producing weekly reports for the team." It states a task, gives no result, and sounds like a hundred other CVs in the pile.

Now rebuild it. Add the action, the method and the impact, ideally with a number: "Automated the weekly team report in a dashboard, cutting production from three hours to fifteen minutes and freeing a half-day each week." Same underlying work, but now it reads as value delivered. Run every bullet on your CV through this same transformation, and the whole document shifts from describing a job to proving a performer.

  • Start with the plain task you performed
  • Add the specific action and how you did it
  • Add the result, with a number wherever it is honest
  • Cut filler like "responsible for" and "duties included"

Do this today

  • List the exact skills and tools named in the advert
  • Mirror the real, true ones in your CV wording
  • Rewrite bullets as outcomes with numbers
  • Use a clean single-column, ATS-safe layout
  • Front-load your most relevant evidence at the top
  • Tailor the summary and top bullets per role
  • Proofread ruthlessly before sending

Frequently asked questions

How long should my CV be?

One to two pages. Recruiters skim, so lead with your strongest, most relevant evidence and cut anything that does not support your target role. Length for its own sake works against you.

Should I include a photo?

In most markets, no. It can confuse ATS parsing and is not expected, and in some regions it raises bias concerns for the employer. Use the space for outcomes and relevant skills instead.

Do those "beat the ATS" tricks like hidden keywords work?

No, and they can get you rejected outright. Better systems flag them, and a human who spots hidden text loses trust immediately. Clarity, relevance and genuine keyword matches are what actually pass.

Your next step

Turn advice into a career transformation.

Guides get you oriented. Real work experience and verifiable proof get you hired. That is what UstackSchool is built for.