Two careers, two CVs, one evidence base
Keep applying in your current field while you chase the pivot. Build the facts once, fork them into two versions, and check each one.
A master CV is the wrong tool for a dual-track search
The usual advice is to keep one master CV and trim it per application. That breaks the moment you're applying in two directions at once. Your safety-net applications want depth in the field you already know. Your pivot applications want the transferable half of the same career, told in the new field's vocabulary. Trimming one document back and forth means you're always half an edit behind whichever job you're chasing today.
The fix is to separate the facts from the framing. Your evidence base is everything that actually happened: employers, dates, projects, tools, budgets, headcount, results. That layer stays fixed and true for both tracks. What changes on top of it is the summary, the order of sections, which bullets survive, and how each achievement is described. Same career, two readings of it, no contradictions.
That split also protects you from the quiet risk of tailoring, which is drift. Copy a file twice and the numbers stop matching after three edits. Hold the evidence in one place and both versions inherit the same figures automatically. You change emphasis, not history, so nothing you say in an interview can be contradicted by the other document sitting in someone else's inbox.
Three steps
Build once, fork twice, score both
Build the base
Load every role, tool, number and result into one structured record. No framing yet, just facts you can prove in an interview.
Fork it
Generate two versions from that record. Each gets its own summary, section order, skills block and bullet selection for its target field.
Score both
Paste a real ad next to each version and check them separately. Two tracks, two targets, two sets of fixes.
What actually changes between the two versions
The summary carries the whole pivot
Three lines. The current-field version names your seniority and domain. The pivot version names the target role and the bridge into it.
Section order tells the reader what to weigh
Experience first when you're staying put. Skills, projects or a certification block first when the new field needs proof you can do the work.
Bullets get selected, not invented
Each version keeps the achievements its reader cares about. The rest stay in the evidence base, ready if the other track heats up.
Vocabulary follows the ad, per track
The same project can be a process improvement or an analytics deliverable. Use the words the target job posting uses, honestly.
The file name and title line stay consistent
Name each file for its track so you never attach the wrong one at eleven at night.
Track A and Track B, side by side
| What you decide | Current field version | Pivot version |
|---|---|---|
| Summary opens with | Years, domain, level of ownership | Target role, plus the bridge you already have |
| First section after the summary | Work experience | Skills, projects or training |
| Bullets you keep | Depth: scope, budgets, people, systems | Transfer: analysis, tools, delivery, stakeholders |
| Job titles | As written on your contract | As written, with a plain-language clarifier |
| Keywords sourced from | Senior ads in your current field | Entry and mid ads in the new field |
| What stays identical | Dates, employers, figures, contact details | Dates, employers, figures, contact details |
Stop rewriting. Start forking.
Load your history once, generate both versions, and send each one to the track it was written for.
Questions people ask when they're applying two ways at once
Can I just send the same CV to both fields?
You can, and it usually underperforms in both. A CV written for your current field buries the transferable evidence a hiring manager in the new field is looking for, while a pivot-flavoured CV can read as underqualified to people who already know your domain. Two versions cost one extra hour and give each reader the story they need.
How different should the two versions be?
Different in framing, identical in facts. Expect a new summary, a different section order, roughly half the bullets swapped, and a skills block rebuilt from the target ads. Employers, job titles, dates and numbers must match exactly across both files. If a fact changes between versions, that's not tailoring, that's a discrepancy waiting to surface in a reference check.
Will a recruiter find out I'm applying in two directions?
Almost certainly not, because each company only ever sees the version you sent them. Recruiters don't share applicant files across firms. The one place to be deliberate is your public profile: keep it broad enough to support both stories, or lean it toward the pivot and let the current-field CV carry the depth.
What goes in the summary on the pivot version?
Name the role you're applying for, the strongest transferable proof you have, and the shortest honest reason the move makes sense. Three lines, no career-change confession, no apology for the gap in direct experience. Then let the section order and the bullets underneath back it up with work you actually did.
Does an ATS treat the two versions differently?
Applicant tracking systems parse structure and match text against the job requisition, so each version is judged only against the ad it was sent to. That's exactly why you score them separately: keywords that make you a strong match in your current field can leave you looking thin against a posting in the new one, and the reverse is just as true.
How do I stop the two files drifting apart?
Never edit a fact inside a finished CV. Update the evidence base, then regenerate. New job, new certification, corrected date: change it once and both versions inherit it. That habit takes about five seconds and it prevents the classic dual-track failure, which is two CVs that quietly disagree about when you left your last job.