Career Change: The Relevance Argument No Builder Can Make

When you change fields, the hard part of your resume is not formatting and not phrasing. It is an argument: that specific things you did in your old domain constitute evidence for something the new domain wants. Making that argument requires knowing both domains well, and knowing your own record in detail. No software has either. This post therefore recommends no tool and instead sets out where the actual work sits.

What a career-change resume is really doing

A same-field resume can rely on shared vocabulary. You write your old job title and the reader knows roughly what it involved, what it was hard about, and what a good version of it looks like. Almost all of the interpretation happens for free.

Change fields and that goes away. Your reader knows their own domain and has no reliable model of yours. Every line now has to carry its own explanation of why it belongs on this page. That is a different genre of document, not a reskinned version of the old one — and it is why “which builder is best for a career change” is a question about the wrong layer of the problem.

The document has to do three things a same-field resume never has to do: translate, select, and order.

Translation: the same word means different work

Domains reuse words. “Client”, “campaign”, “case”, “audit”, “operations”, “escalation” — each of these names something quite different depending on where you are standing. When you write in your old sense and your reader reads in theirs, you get a silent misunderstanding rather than a question.

The reverse move is more dangerous. Reaching for the new field’s vocabulary to describe old work is how people end up asserting experience they do not have, because the borrowed term carries assumptions that were not true of your job. Rewriting a bullet in the target field’s language is not a neutral act, and there is a real line between re-emphasising what you did and quietly claiming something new — which is exactly the distinction in re-emphasising versus acquiring when you tailor with AI.

A model is a fluent translator with no way to check either dictionary. It will produce the target field’s phrasing on request, and it cannot tell you whether the phrase is true of what you did.

Selection: most of your history is now off-topic

In a same-field application, more history is generally better. In a change, it is not. Some of your strongest past work is simply irrelevant to where you are going, and including it costs you space and dilutes the argument.

Deciding what goes requires knowing what the new field considers evidence — which is knowledge you build by reading postings closely, talking to people already in the role, and noticing what gets asked about. It cannot be inferred from your resume, and a generator working from your resume will keep everything, because keeping everything looks complete and looks complete is what its objective rewards.

The related decision is how much of the old history to show at all. Cutting the earliest roles tidies the page but also removes context that sometimes explains the move, so what cutting old roles hides matters more in a change than in a straight-line career.

Ordering: what leads is the argument

The most consequential choice on a career-change resume is what a reader hits first. A summary that states the move plainly. A projects or skills block before the experience block. A relevant recent role ahead of a longer, less relevant one. Grouping unrelated jobs briefly at the bottom so the top can breathe.

Each of these is a strategic bet about how this employer reads. A tool can render any of these layouts; none can tell you which bet to place, because that depends on the target field’s conventions and on what you are trying to make unavoidable.

Two ordering choices carry a cost worth naming. Dropping roles to shorten the page can leave a gap that reads as concealment — the tradeoff in which jobs to list and what omitting one creates. And leading with recent training instead of experience raises the obvious question about whether the training is finished, which is only survivable if an unfinished qualification is written honestly rather than blurred.

Where a tool genuinely helps, and where it does not

Useful: producing three phrasings of a bullet you have already decided to include, so you can pick the clearest. Tightening a summary you wrote. Catching inconsistent tense across a document you have restructured several times. These are all editing tasks on material you control.

Not useful, and actively risky: asking anything to work out what is transferable. That request has no grounding — the model does not know your record beyond what you pasted, does not know the target field’s actual hiring criteria, and has every incentive to produce a confident answer. What comes back is a plausible-sounding relevance claim, and plausible-sounding relevance claims are precisely what falls over when someone asks a follow-up question. If you cannot say concretely why a line belongs, it is a claim that needs narrowing or cutting, not better wording.

The sequence that works

Read ten real postings in the target field and write down what they keep asking for, in their words. Go through your own history and mark only the items that speak to those things, with the specific facts attached. Draft the relevance sentence for each one in plain language, as if explaining it to a friend in the new field. Then, and only then, open whatever tool you like and let it help you tighten.

Do it in that order and the choice of builder stops mattering, which is the honest answer to the question in the title. Do it in the other order and you will get a well-formatted document making an argument you did not choose.