Skip to content

CV tailoring for software engineers: honest edits that match the job

Tailoring a CV means choosing what to put first and describing it in the employer's terms. It never means adding skills, titles, or numbers you cannot back up.

CVs5 min readUpdated

On this page

Sending the same CV to every role is simple, and for closely similar roles it is often fine. But when you apply to a backend role one day and a platform role the next, the version that leads with the wrong work makes a reader dig for the part they care about. Tailoring fixes that by changing order and emphasis, not facts.

This guide explains what honest tailoring looks like for engineers, a repeatable process for doing it in about fifteen minutes, and the line you should not cross, no matter what a tool or a friend suggests.

What tailoring is, and what it is not

Tailoring is editorial work on true material. You are deciding which of your real accomplishments deserve the top of the page for this particular reader, and phrasing them so the reader recognizes them quickly.

Honest tailoring versus fabrication
Tailoring (fine)Fabrication (not fine)
Moving your Kafka pipeline work to the first bullet for a data platform roleAdding Kafka to your skills because the posting lists it
Calling it event-driven architecture when that is what you built and the posting uses the termDescribing a proof of concept as a production system
Dropping an unrelated side project to make roomChanging your title from Software Engineer to Senior Software Engineer
Stating a metric you measured, such as p95 latency down from 800 ms to 300 msEstimating a percentage improvement you never measured
Grouping skills so the relevant ones appear firstRounding 3 years of experience up to 5

The test is simple: could you talk about every line for five minutes in an interview, and would a former colleague agree with it? If not, it does not belong on the page. Fabricated details tend to surface in technical interviews and reference checks, and they undermine the true parts of your CV along with the false ones.

Reading the job post for tailoring

Before editing anything, extract three things from the posting:

  • The core problem. What is this team actually building or fixing? A payments team scaling for new markets reads differently from a team rebuilding a mobile app.
  • The must-haves. Usually three to five technologies or experiences listed as required. Separate them from the nice-to-haves.
  • The vocabulary. The words the team uses for things you may have done under a different name: developer experience for internal tooling, reliability for on-call, design system for component library.

Then compare against your own history. For each must-have, write down the real evidence you have, or note that you do not have it. Gaps are fine; they are information for you, not something to paper over.

A fifteen-minute tailoring process

  1. Start from a complete master CV that contains every real accomplishment, even ones that do not fit on one page. Tailoring is selection, so you need a full set to select from.
  2. Rewrite the summary line (if you use one) to name the kind of work this role needs that you have done. One sentence, no adjectives you cannot back up.
  3. Reorder bullets within each role so the most relevant real accomplishment comes first.
  4. Adjust vocabulary where your wording and the posting's describe the same thing. If you built a CI system and they call it build infrastructure, use their term.
  5. Cut what does not serve this reader to keep the page readable. A mobile role probably does not need three bullets about a data warehouse migration.
  6. Reorder the skills section so relevant tools appear first. Do not add tools you have not used in real work.
  7. Read it once as the hiring manager and check that every number, title, and date is identical to your master version.

A worked example

Alex Rivera is a backend engineer with four years at a fictional company, Paperplane. The master CV has this as the fourth bullet under that role:

For a general backend role, that bullet can stay fourth. For a platform engineering role at Harbor & Vale that talks about developer experience and deployment safety, Alex moves it to the top and rewrites it using the posting's terms:

Same project, same numbers, same scope. What changed is position and vocabulary. What Alex does not do is add Argo CD to the skills list because the posting mentions it; Alex has not used it, so it stays out, and if it comes up in the interview Alex can say so directly.

When not to bother tailoring

Tailoring takes time, and not every application deserves it. If a role is very close to your current work, your master CV, trimmed to fit, may already lead with the right things. If a role is a long shot where you are missing most of the must-haves, tailoring will not close that gap, and time is better spent on applications where you are a real fit.

A reasonable pattern is to keep a few base versions, for example backend, platform, and mobile, and tailor further only for roles you are most interested in. For keeping track of which version went where, see our guide to a job application tracker for engineers.