ATS & resumes

How to tailor your resume to a job without making things up

A fifteen-minute method for tailoring a resume to each job posting using only true experience: what to change, what to leave alone, where AI tools go wrong.

By Arivu, founder of Shortlist22 October 2026 · 4 min read

Short answerMap each of the posting's requirements to real evidence from your experience, then reorder and reword so that evidence is easy to find. Lead with the core skills, use the posting's terms for skills you actually have, and cut what is irrelevant. Never add a tool, number or responsibility you cannot talk about in an interview.

Tailoring a resume does not mean rewriting it. It means making the evidence a particular employer is looking for easy to find. Done well, it takes about fifteen minutes per job and makes a real difference, both to search inside an applicant tracking system and to the recruiter who reads the page. Done badly, it turns into keyword stuffing or quiet invention, which falls apart in the first interview.

Start from a master list, not your last resume

Keep one long document with everything you could truthfully put on a resume: every role, project, tool, result and number, with the details. Each tailored resume is a selection from that list. This stops versions drifting apart and makes it obvious when you are tempted to add something that is not on it.

Step 1: list what the posting needs

Read the requirements, not the duties. Write down:

  • the core skills the role is built around (usually in the title and the first lines);
  • the other required items;
  • the preferred items.

Most postings come down to five to ten things that matter.

Step 2: find your evidence for each

For each item, find where your experience shows it: a job bullet, a project, a certification. Be strict. A skill you used on one ticket two years ago is weak evidence; a skill you built a system with is strong.

Mark items where you have no evidence. Those are not to be filled in; they are gaps you should know about before you apply. If you are missing a core skill, read should you apply if you don't meet every requirement? first.

Step 3: move the evidence up

Recruiters spend little time on each resume, so order matters:

  • Summary: two lines naming the role you are applying for and your strongest evidence for its core skills.
  • Experience bullets: within each job, put the bullets that match this posting first. Cut bullets that are irrelevant to this job, especially in older roles.
  • Projects: include the ones that show a required skill your jobs do not.
  • Skills: group them ("Languages: Go, Java, SQL"), core skills first.

Step 4: use the posting's words for what you have

If the posting says "PostgreSQL" and your resume says "Postgres", or it says "CI/CD" and you wrote "build pipelines", use their term, once, in the bullet where you describe the work. This helps both a recruiter's search and a quick read. It only applies to things you actually did. Our guide to finding resume keywords in a job description shows how to tell the terms that matter from the ones that do not.

Step 5: check numbers and claims

Every number should be one you can explain: where it came from and what it measured. Every tool should be one you could answer questions about. If you rewrote a bullet to fit the posting, check it still says what happened.

What not to do

  • Do not add skills you do not have because the posting lists them. They are the first thing interviewers ask about.
  • Do not copy the posting's sentences into your resume. It is obvious to anyone who has read both.
  • Do not hide keywords in white text or tiny fonts. Parsers and recruiters both see them.
  • Do not rewrite your job titles to match the posting. Titles are checked with references.

Where AI tools help, and where they go wrong

AI tools are good at the mechanical parts: rewording a bullet, reordering sections, spotting a posting's terms you have not used. They go wrong when they are given the posting and your resume and asked to "optimise": they tend to add the posting's tools and inflate numbers, because that is what makes the match look better.

If you use one, give it only your real experience as the source, and read every line it changes. Shortlist is built this way: it writes the resume only from your profile, flags any tool or number your profile does not back up, and reads the finished PDF back the way an applicant tracking system would, so you can check it with the free ATS checker too.

FAQ

How much should I change my resume for each job?

Usually the summary, the order of bullets and the skills section. The experience itself does not change; what you put first does. Fifteen minutes is enough for most applications.

Is it dishonest to tailor a resume?

No. Choosing which true things to emphasise is what a resume is for. It becomes dishonest when you add experience you do not have or overstate what you did.

Should I tailor my resume for every application?

For every job you really want, yes. If you are applying to so many that you cannot, you may be applying to too many jobs that do not fit.

Does a tailored resume pass ATS better?

It is more likely to be found by a recruiter's search and to look like a match when opened. Whether it is read correctly depends on the layout, which you can check by uploading it to an ATS checker and reading the extracted text.

Written by Arivu, founder of Shortlist

Arivu builds Shortlist, a browser extension that checks each job against your profile before you apply. When a guide says how a parser or a form behaves, it was tested in Shortlist; when it describes another company's product, the facts come from that company's own pages.

Check your own resume

See what a tracking system reads from your PDF: sections, contact details, dates and broken words. Free, no account.

Keep reading