Six years into mechanical engineering, you want to work in data. Eight years into banking operations, you want to do product. Four years into teaching, you want to work in learning design at a company.
The advice you will receive is either “you cannot, you are too deep” or “do a ₹3 lakh bootcamp and start fresh.” Both are wrong, and the second one is expensive. Most successful mid-career changes are neither a leap nor a reset — they are two or three deliberate sideways moves, each of which is individually credible.
The mistake: treating it as a reset
Candidates changing fields routinely apply to entry-level roles, drop their salary by half, and describe their previous career as irrelevant.
This fails in both directions. You will be rejected from junior roles for being overqualified — a hiring manager filling a fresher position sees a 32-year-old with eight years of experience and assumes you will leave within a year, which is usually correct. And you will have discarded the thing that actually makes you employable in the new field: the domain knowledge nobody else applying has.
The bank operations person who wants to do product is not competing with product graduates. They are the only candidate who understands reconciliation, and a fintech building settlement tooling would rather have that than another generalist.
Move adjacent, not across
An adjacent move keeps one thing constant and changes the other. There are two axes — your function (what you do) and your domain (the industry you do it in) — and changing one at a time is dramatically easier than changing both.
Same domain, new function:
- Insurance claims processing to insurance business analyst. Same products, new skill.
- Pharma quality control to pharma regulatory affairs.
- Teaching to curriculum design at an edtech company.
Same function, new domain:
- Manufacturing supply chain to e-commerce supply chain.
- Agency copywriting to in-house content at a SaaS company.
- Hospital HR to technology company HR.
Either of those is a story a hiring manager can accept in one sentence, and neither requires you to explain away your history. Two such moves, two or three years apart, will take you somewhere a single leap could not — mechanical engineering to manufacturing analytics to a data role, and the second move is now internal to your own resume.
The intermediate step is often available at your current employer, which makes it the cheapest version of this. An internal transfer to a role that touches your target function costs you no salary and no seniority, and after eighteen months you have relevant experience rather than an aspiration.
Find out what the new field actually values
Before spending money on a course, spend two weeks on research. Read thirty job descriptions for your target role — properly, with a document open — and record what appears repeatedly.
Sort what you find into three lists:
- Already have it. Usually longer than expected. Stakeholder management, working to a deadline, reading a P&L, writing a specification, handling a difficult client.
- Adjacent — one project away. You know SQL but not Python; you have run projects but never written a PRD.
- Genuinely missing. This list is what your learning budget is for, and it is normally much shorter than the marketing for any course implies.
Then talk to four people doing the job. Not for a referral — for calibration. “I'm moving from X into this. What did you underestimate?” is a question people answer generously, and the answers will not match the course syllabus. Frequently the real barrier turns out to be something unglamorous, like never having presented to a leadership team.
Learn the shortest thing that produces evidence
The market does not reward certificates from career-changers, because everybody has one. It rewards evidence of doing the new work.
So the test for any course is whether it ends with something you can show. A twelve-week programme that produces one real project you can discuss beats a nine-month one that produces a PDF.
Better still, produce the evidence at work. This is the single highest- leverage move available to a career changer and it is consistently underused:
- Volunteer for the project in your company that touches your target function. The analytics piece nobody wants. The migration. The vendor evaluation.
- Solve a real problem in your current role using the new skill, even if nobody asked. An operations analyst who automates their own team's reporting in Python now has production Python experience with a business outcome attached, which is not a portfolio project — it is a job.
- Offer it free, once, to a small organisation. An NGO or a local business will let you build the thing you cannot yet get paid to build.
Be careful with paid programmes promising job guarantees. Read the conditions closely, particularly where the fee is funded by an income-share or loan agreement — the guarantee is often defined narrowly enough that it cannot be invoked, and the loan is not conditional at all.
Rewrite your resume for the new reader
The same fifteen-year history can read as irrelevant or as an unusual advantage depending entirely on how it is written. Nobody will do that translation for you.
Lead with a summary that states the move. Do not make the reader infer it:
Operations manager, 7 years in retail banking, moving into product. Built and now own the branch reconciliation tool used by 40 branches — scoped it, wrote the spec, ran it with two developers. Looking for an associate product role in fintech where knowing how banking operations actually work is an advantage.
That paragraph does three things: it names the transition so it is not a puzzle, it presents concrete evidence of the target function, and it states why the old career is an asset rather than baggage.
Rewrite your bullets in the new field's vocabulary. The same work, described for a different reader:
- Before: “Handled escalations from branch operations teams.”
- After: “Ran the feedback loop between 40 branch teams and the technology group; translated recurring complaints into a prioritised list that shaped two quarters of the reconciliation roadmap.”
This is reframing, not fabrication — the underlying facts are unchanged. The line is that you must be able to defend every word in an interview.
Reorder the page. If your evidence for the new function sits in projects rather than job titles, put a “Relevant Projects” section above your work history.
Be honest with yourself about the pay
A well-executed adjacent move is often lateral on salary, occasionally upwards. A genuine function-and-domain change usually costs something, and pretending otherwise leads people to accept an offer they resent within three months.
Rough expectations: an adjacent move where you bring relevant domain knowledge, flat to slightly up. A change into a field where you have a real portfolio but no professional history, a 10–25% dip that typically recovers within two years because you are progressing from a mid-level base rather than a fresher one. A complete reset into an entry-level role with no bridge, 40% or more, and it takes years.
Work out what dip you can actually absorb, for how long, before you start interviewing. Then negotiate on the things that are easier to grant than base pay — a six-month review, a title that reflects your seniority, a joining bonus to cover the transition. That is often available even when the salary band is not.
The interview question you must have an answer to
“Why are you leaving a field you have spent seven years in?”
This is asked in every process, and it is a risk assessment: will you leave again in a year, and do you understand what you are moving into? The answer has to be forward-looking and specific.
The part of my job I've consistently enjoyed most is the two years I spent specifying and running the reconciliation tool — deciding what to build and why. I want to do that as the job rather than as a side project. I'm not leaving banking; I'm staying in it and changing what I do inside it.
Avoid the two failing versions: criticising the field you are leaving, which reads as an unwillingness to be satisfied anywhere, and vague aspiration — “I've always been passionate about technology” — which invites the obvious follow-up about what you have actually done about it.
Expect the search to take longer
Career changers get a lower response rate, and the reason is mechanical rather than personal: keyword filters and screening recruiters both work by matching your last title to the open one.
Which changes where you should spend your effort. Cold applications through portals work poorly for this profile. What works is warm routes — referrals from people in the target field, hiring managers approached directly with your evidence attached, smaller companies where a human reads every application and one person makes the decision, and internal moves.
Give it six to nine months rather than six to nine weeks, and start producing the evidence while you still have the salary. Almost everyone who does this successfully began the change eighteen months before they changed jobs.