Marcus spent eleven years in logistics operations, the last four of them running a 40-person warehouse team in Doncaster on a salary of £54,000. He wanted into fintech — specifically into operations at a payments company, where the pay ceiling was closer to £80,000 within three years. Every recruiter told him the same thing: no financial services background, so start at £38,000 as an "operations associate" and work back up. He didn't take that deal. Eight months later he was running vendor operations for a Series B payments firm at £57,000, a small rise on his old salary, with a clear path to £72,000 inside eighteen months. The difference wasn't luck. It was that he stopped applying for jobs and started building a bridge.
Why most pivots take a pay cut (and why yours doesn't have to)
The pay cut isn't a law of nature — it's what happens when you let a hiring manager compare your CV against a job title instead of against the actual work. When you apply cold for a "Product Manager" role with a background in retail merchandising, the recruiter's software matches keywords, not competence, and you lose to someone with "Product Manager" already on their LinkedIn. That's a title problem, not a skills problem. Most people respond to it by accepting a junior title and a junior salary, on the theory that they'll "prove themselves" and climb back. Some do. Most get stuck two rungs down for three to five years, because once a company has you at a price, there's rarely urgency to move you off it.
Here's the uncomfortable part: your fifteen years of experience are worth less than you think in a straight comparison, and worth more than you think if you frame them correctly. A warehouse operations manager who ran vendor contracts, managed a £2m stock budget, and cut fulfilment errors by 30% has done product operations work — just not with that label on it. The fix isn't to downplay the mismatch and hope nobody notices. It's to name the overlap explicitly, on paper, before a recruiter has to guess at it.
The transferable-skills audit: three columns, no vague verbs
Most "transferable skills" exercises fail because they stop at adjectives — "strong communicator," "strategic thinker" — which say nothing a hiring manager can act on. Run this instead, on paper, before you touch a job board:
- Column one: every recurring task from your current or last three roles, written as a verb plus an object plus a number. Not "managed vendors" — "renegotiated contract terms with 14 suppliers, saving £180,000 over two years."
- Column two: the job description language from five postings in your target industry, copied verbatim, including the boring bits — "cross-functional stakeholder management," "budget forecasting," "process documentation."
- Column three is where the audit earns its keep: draw a line between each item in column one and the closest match in column two, and if you can't draw a line, that's a genuine gap, not a rebranding job — write it down separately and treat it as something to close, not to hide.
Do this properly and you'll usually find 60–70% overlap you weren't crediting yourself for, and 15–20% that's a real gap. That real gap is what the next step is for.
Closing the real gap: what's worth paying for, and what isn't
Priya ran marketing for a mid-sized retail chain for six years and wanted into product marketing at a SaaS company, where the pay bands started £8,000 higher than anything retail marketing offered locally. Her audit came back clean on positioning, campaign strategy, and stakeholder management — but every SaaS posting she copied into column two mentioned Amplitude or Mixpanel, and she'd never opened either. That's the kind of gap an audit is supposed to surface: specific, nameable, and closeable in weeks rather than years. She didn't enrol in a broad "digital marketing" course, which would have cost £900 and taught her nothing she couldn't already do. She paid £180 for a two-day Amplitude certification, then spent a weekend rebuilding her employer's app retention dashboard in it as an unpaid internal project, so she'd have a named, working artefact to describe in an interview rather than a certificate nobody asks to see.
That distinction is the one most people get backwards when they're anxious about a gap: they reach for the credential that looks most impressive on paper — an MBA module, a six-month bootcamp, a generalist qualification — instead of the smallest, most specific thing that produces a deliverable. A hiring manager doesn't want to hear that you completed a course. They want to hear what you built, fixed, or shipped with the tool the course taught you, and a two-day certification with a real dashboard attached beats a six-month diploma with nothing to show for it. Budget £150–£600 and one or two weekends for this step, not £3,000 and six months — if the gap you've identified needs more than that to close, it's usually a sign you picked the wrong pivot target, not that you need a bigger course.
One category of gap doesn't respond to this approach at all, and it's worth naming so you don't waste time on it: regulatory gates. If your target role legally requires FCA accreditation, a professional licence, or a specific safeguarding certification, no side project substitutes for it, and the honest move is to check the requirement before you invest a single evening in a bridge project that legally can't lead anywhere. Everything else — tooling, methodology, domain vocabulary, a specific framework the industry runs on — is learnable and demonstrable inside a month.
The bridge project: get paid to prove the fit before anyone hires you for it
A pivot doesn't happen in the interview room — it happens in the six months before it.
The single highest-leverage move in a pay-preserving pivot is a paid bridge project — a short, contracted piece of work inside or adjacent to your target industry that lets you put the new job title on your CV before you've been formally hired into it. This isn't a course certificate, which employers correctly treat as low-signal. It's actual delivered work, invoiced, with a client or employer willing to give you a reference. Marcus found his through a former colleague who'd moved into fintech operations and needed someone to audit a supplier onboarding process for eight weeks, three days a week, at £280 a day — a drop from his full-time salary, but a controlled, time-boxed drop with a clear exit date, not an open-ended demotion. That contract became the first line on his CV that said "payments operations," and it's what got him past the keyword filter on his next application.
Finding one takes more legwork than applying to postings, and that's precisely why it works — most of your competition won't bother. Search for fixed-term contract or interim roles specifically, not permanent ones; companies take more risk on a three-month contract than on a permanent hire, and that lower bar is your way in. Freelance platforms like PeoplePerHour and specialist interim-management firms both carry these listings, but the better source is usually a direct message to someone one step ahead of you on LinkedIn, asking if their team ever brings in short-term help. Two or three of those conversations a week, for two months, will surface more real opportunities than two hundred cold applications.
Negotiating your new-industry salary from experience, not job title
Once you're negotiating an offer, the title on your last payslip is the weakest evidence in the room — lead with numbers instead. Don't say "I was an operations manager for eleven years." Say "I managed a £2m operational budget and cut fulfilment errors by 30%, and in the last eight months I've delivered the same kind of work inside payments operations specifically." That second sentence does two things at once: it anchors your value to outcomes a hiring manager can compare against their own budget, and it neutralises the "no direct experience" objection before anyone raises it.
Refuse to let a recruiter set the anchor number first if you can help it — ask what the band is, and if they push you to name a figure, name one 10–15% above your current salary, not below it, because a pivot is not the moment to signal that you'll accept less. If they counter with a title-based argument — "we usually start pivots at associate level" — the correct response is to point back at the bridge project and ask directly what specific gap, beyond the label, still needs closing. Sometimes there's a real answer, and it's worth hearing. More often there isn't one, and naming that gap explicitly is what moves the conversation off the title and back onto the work.
What a realistic pivot timeline actually looks like
Expect three to nine months from a standing start to a signed offer, and treat anyone promising six weeks with suspicion — that's a career-coaching sales pitch, not a plan. Month one is the skills audit and five to ten conversations with people already doing the target role. Months two and three are spent finding and negotiating a bridge project, which is the slowest part and the one most people quit during, because it's unglamorous and doesn't feel like "job searching." Months four through six are the bridge project itself, plus applying in parallel to permanent roles with the new line already on your CV. By month seven or eight, you're negotiating from a position where your last two roles both say the new industry, and the pay-cut argument has nowhere left to attach itself.
None of this works if the bridge project sits in a drawer instead of on your CV and LinkedIn the day it starts, updated live rather than after it wraps — recruiters searching for candidates mid-project will find you months before you'd otherwise apply. Update your headline the day the contract starts, not the day it ends.