Which resume should you send for this job?

The case for more than one

A resume is read against a specific job, and the same career can look like a strong fit or a weak one depending on what is at the top. An engineer who has done both frontend and infrastructure work is a better candidate for each of those roles when the relevant half leads.

That is not deception. Everything on both versions is true; what changes is the order and the emphasis, which is exactly what a reader uses to form a judgement in the thirty seconds they spend.

The case against five of them

Every version is a thing to keep current. You fix a typo in one and not the others. You add a new role to the one you happened to open. Six months later you have four resumes, three of them subtly out of date, and no idea which one you sent to the company that just called.

Two or three is usually the ceiling for one person. Past that, the upkeep cost exceeds what the extra targeting buys, and the risk of sending a stale version starts to dominate.

How to choose between them

Put the posting beside each version and count the terms the posting emphasises that the resume actually contains. The version that covers more is the one to send, and the gap between them is usually obvious rather than marginal.

This is the same thing a keyword filter does, which is the point: you are approximating the screen you are about to go through. A tool can do the counting - the ATS checker here, or the match percentage in the job feed - but the manual version takes two minutes and teaches you something the number does not.

Where two versions score closely, send the one whose most recent role matches better. Recency is weighted heavily by human readers even when the earlier experience is more relevant.

When a version is worth creating

Create one when you are genuinely pursuing two different kinds of role, not when you are applying to two companies. A frontend version and a full-stack version earn their keep. A version for each employer does not - that is tailoring, which is editing one version for one application rather than maintaining a second.

• Worth a version: two distinct disciplines you would both accept.
• Worth a version: a career change, where one resume leads with transferable work and the other with your established track record.
• Worth a version: wildly different seniority, such as hands-on and leadership roles.
• Not worth a version: a different company in the same discipline. Tailor instead.

Keeping them from drifting

Pick one as the master. When something changes - a new role, a new achievement, a corrected date - it goes into the master first, and the others are updated from it rather than edited independently.

Name them so the name says what the version is for. 'Frontend - React focus' tells you something; 'Resume 2026 final' does not, and in six months neither will 'Resume 2026 final v2'.