How to Tailor Your CV to a Job Description in 15 Minutes

Sending the same CV to every posting is the quickest way to apply and one of the slowest ways to get replies. Tailoring your resume to a job description does not mean rewriting it from scratch: in about 15 minutes you can adjust the parts a recruiter reads first so they match what this particular team asked for. This guide gives you a routine for that, covering the summary, the top bullets, keywords used honestly, and what applicant tracking systems actually do with your file.

What tailoring is, and what it isn't

Tailoring is choosing and ordering true things. You decide which of your real projects, skills and results go at the top for this role, and you describe them in words the posting would recognise. It is not inventing experience or listing a tool you once read about.

It also works best on top of a good base. If you keep two or three CV variants for the role types you target, as described in our checklist for applying within an hour, tailoring becomes a small final layer rather than a new document every time.

Before you start: mark up the posting (3 minutes)

Read the posting once with a single goal: find what they will check first. Note down:

The exact title and level, for example "Senior Backend Engineer, Payments".
Three to five must-haves, usually under "Requirements" or "What you'll bring".
Words they repeat. If "reliability" appears in the intro, the responsibilities and the requirements, it matters to them.
The problem the team is solving. "Scaling our ledger", "rebuilding onboarding", "moving to Kubernetes".

If you are unsure which requirements are real and which are wishes, our guide on how to read a job description goes through that in detail.

The 15-minute routine

1. Pick the closest variant (1 minute)

Start from the version of your CV that already fits best. Save a copy with the company in the file name, such as Anna-Petrova-Backend-CV-Brightline.pdf, so you never send the wrong one.

2. Rewrite the summary (4 minutes)

The two or three lines at the top are what a busy reader sees first. Make them answer "is this person the kind of engineer we asked for?"

Before:

Software engineer with 6 years of experience in various technologies, passionate about clean code and learning.

After, for a payments backend role:

Backend engineer with 6 years in Go and PostgreSQL, the last 3 on payment and billing services. Focused on reliability: on-call owner for a service processing card transactions, led the move to idempotent APIs.

The second version uses the posting's vocabulary and makes one concrete claim you can discuss in an interview.

3. Reorder and adjust the top bullets (6 minutes)

For your most recent one or two roles, move the bullets that match the must-haves to the top. Then check each of those bullets:

Does it say what you did, with which tools, and what changed as a result?
Does it use their term where yours means the same thing? If they write "CI/CD" and you wrote "build pipelines", use "CI/CD".
Is there a result you can state honestly? Real numbers from your own work are fine; if you don't have one, describe the outcome in plain words rather than guessing.

A quick way to see the change:

The posting asks for	Your bullet before	Your bullet after
Experience running services on Kubernetes	Worked on infrastructure tasks	Migrated four services from VMs to Kubernetes and wrote the team's deployment runbook
Strong SQL and data modelling	Wrote database queries	Designed the PostgreSQL schema for invoicing and reviewed query plans for slow reports
Mentoring	Helped new colleagues	Onboarded and mentored two junior engineers through their first production releases

4. Check keywords honestly (3 minutes)

Go back to your list of must-haves and repeated words. For each one, ask: have I done this, and does my CV say so in words they would recognise?

Use the standard spelling of tools: "PostgreSQL", "Kubernetes", "TypeScript".
If you have the skill but the CV doesn't mention it, add it where you used it, inside a bullet, not only in a skills list.
If you don't have it, leave it out. You can mention in a cover note that you're learning it, which our short cover note templates show how to do in one sentence.

Don't paste a block of keywords at the bottom or hide text in white font. People read these CVs.

5. Final check and export (1 minute)

Check the company name anywhere it appears, re-read the summary once, and export to PDF unless the form asks for another format.

ATS basics, without the myths

Greenhouse, Lever and Ashby are applicant tracking systems (we explain them in what Greenhouse, Lever and Ashby are). Broadly, an ATS stores applications, pulls text from your CV into fields, and lets recruiters search, filter and move candidates through stages. Some forms add screening questions, such as work authorisation or location, and a company can choose to filter on those answers.

How much any one company automates varies, and from the outside you usually can't tell. What you can control is making your CV easy to read for both software and people:

One column, standard section headings ("Experience", "Education", "Skills").
Real text, not text inside images or icons.
Consistent dates, such as "Mar 2022 – Present".
Contact details in the body, not only in a page header.
Honest answers to screening questions, because those are often read directly.

What not to change

Your past job titles, employers and dates. You can add a short clarification, like "Software Engineer (backend, payments)", but not a different title.
Skills you can't discuss for five minutes.

Keep track of what you sent

Note which variant and summary you used for each application, so you know what a recruiter read when they call. A simple sheet is enough; our job application tracker suggests the columns.

Hot Jobs doesn't write or review CVs. What it does is send new postings from 390+ company career pages and two remote boards to Telegram, usually within about half an hour of them going live, which leaves you time to tailor properly while the role is still fresh. €3, paid once. Connect the bot