Analyst Career Moves: The Complete Map for Switching In, Moving Up, and Earning More
Written by Ahmed at Analyst Engineering, a Senior Technical Business Analyst with 10+ years in banking and payments delivery.
Key takeaways
- Every analyst career move is one of five kinds: switching in from another career, going more technical, going less technical, moving up a level or into leadership, or earning more for broadly the same work.
- The most reliable pay gain for a working business analyst is the move to technical business analyst, typically 10 to 20 percent at the same level after about six months of deliberate skill building.
- Career changers from outside tech usually land in the junior business analyst band, about US$65k to US$85k or C$58k to C$72k base in a large city, which is a short term cut for anyone leaving a well paid profession.
- Career paths are the ladders; career moves are the steps between rungs and across ladders. Most analysts change ladder at least once.
- One question picks the move: on an ordinary Tuesday 18 months from now, do you want more systems, more people, more decisions, or more money for the work you already do?
An analyst career move is one of five kinds: switching in from another career, going more technical, going less technical, moving up (a level or into leadership), or earning more for broadly the same work. One question picks yours: on an ordinary Tuesday 18 months from now, do you want more systems, more people, more decisions, or more money for what you already do? Most moves take 3 to 12 months, and the pay effects are predictable: business analyst to technical BA adds 10 to 20 percent at the same level, manual QA to SDET adds 25 to 40 percent, and a career changer from outside tech usually starts in the junior band, about US$65k to US$85k base.
In one week this spring three people asked me the same question in Montréal: what should I do next? A secondary school teacher who wanted out of the classroom. A bank BA who kept being pulled into API defects and wanted the matching title and pay. A senior developer tired of tickets. Three different moves, and the advice that would have helped one would have cost another a year.
I have spent ten years on delivery teams in banking and payments, and I have hired and coached analysts on most of the routes below. This page maps the Career Moves series: 31 articles, each on one move. If you already know you want the technical route, the Complete Tech BA Bundle is where I would start.
What are the five kinds of analyst career move?
Every analyst career move changes one of two things: what you do all day, or what you are paid for doing it. The five kinds below cover every move I have watched on delivery teams.
| Kind of move | What changes | Typical time | Typical pay effect |
|---|---|---|---|
| Switch in | You enter analysis from teaching, nursing, operations, support, development, QA, data, or project management | 3 to 6 months from inside tech, 6 to 12 from outside | Junior band from outside tech; flat or up from operations |
| More technical | You add SQL, APIs, scripting, automation, or architecture | 6 to 18 months | +10 to +40 percent, depending on the target role |
| Less technical | You trade hands-on system work for decisions, people, and change | 6 to 18 months | Roughly flat to +10 percent at first |
| Move up | Junior to senior, then lead, head of practice, or principal | 1 to 3 years per level | About +20 to +30 percent per level |
| Earn more | Same work, better paid: negotiate, change employer or domain, go contract | 1 to 6 months | Bottom to top of a band is about 20 to 30 percent |
The Tuesday question maps onto this table. More systems means more technical. More people or decisions means less technical or up. More money for the same work means earn more. Outside tech, the question is which analyst seat to switch into.
Which career move fits your goal?
Find the sentence that sounds like you and read the last column first. Deltas are derived from the 2026 bands in the analyst salary guide: indicative base salary, permanent roles, large cities.
| Your goal | The move | Typical time | Typical pay delta | Read first |
|---|---|---|---|---|
| ”I want to earn more, fastest” | Negotiate, or change employer inside your band | 1 to 3 months | Up to the top of your band, about 20 to 30 percent above the bottom | Negotiation, employer types |
| ”I want a lot more and accept risk” | Go contract | 2 to 4 months | +40 to 70 percent gross on paper, much less after bench time, benefits, and tax | Contracting day rates |
| ”I want more pay for skills I can build” | Business analyst to technical BA | About 6 months | +10 to 20 percent at the same level | Become a technical BA |
| ”I want more coding” | QA to SDET, analyst to analytics engineer, analyst to developer | 6 to 12 months | +25 to 40 percent (SDET), +20 to 40 percent (analytics engineer) | QA to SDET, analytics engineer |
| ”I want less coding” | Delivery manager, business architect, change lead | 6 to 12 months | Roughly flat to +10 percent | Less technical roles |
| ”I want to own product decisions” | BA to product owner to product manager | 1 to 3 years | Flat to +10 percent to PO; +15 to 30 percent to senior PM over time | BA to product manager |
| ”I want to design systems” | Senior systems analyst to solutions architect | 1 to 2 years | +15 to 25 percent | Solutions architect |
| ”I want to lead people” | Lead BA to head of business analysis | 2 to 4 years | Head of practice band sits about 35 to 50 percent above senior BA | Manager vs principal |
| ”I want client-facing technical work” | Technical BA to forward deployed or solutions engineer | 6 to 12 months | FDE base US$150k to US$220k plus equity vs US$125k to US$155k | Forward deployed engineer |
| ”I am outside tech” | Career change into BA | 6 to 12 months | Junior band, or low mid band when your domain transfers | Career change, at 40 or 50 |
| ”I work in operations or support” | Operations to BA | 3 to 9 months | From about US$55k to US$75k into the junior or mid BA band | Operations to BA |
What is the difference between career paths and career moves?
Career paths are the ladders; this series is the moves between rungs and across ladders. The career paths page lays out five step-by-step ladders (product, engineering, architecture, test architecture, and data architecture) with the signal and skills for each rung. It answers “where does this ladder go?”
This series answers a narrower question: “what step do I take this year, what does it pay, and how long will it take?” Most analysts I know climbed one ladder for a few years, then stepped across: QA to BA, BA to product owner, systems analyst to architect. Use the ladders for direction and this series for the step.
Every move in the series, grouped by kind
Each article covers one move with four-market pay tables, composite cases, and a dated plan.
| Kind | Article | Who it is for |
|---|---|---|
| Reference | Analyst salaries in 2026 | Anyone who needs the band before deciding anything |
| Switch in | Career change into business analysis | Teachers, nurses, retail managers, support staff |
| Switch in | Operations or production support to BA | People one desk away inside a bank or tech company |
| Switch in | Developer to business analyst | Developers who want scope and stakeholders, not tickets |
| Switch in | QA tester to business analyst | Testers who already write missing acceptance criteria |
| Switch in | Project manager to BA and back | PMs who miss the content of the work |
| Switch in | Data analyst to business analyst | Data analysts who want to shape systems |
| Switch in | Becoming a BA at 40 or 50 | Experienced professionals whose first career is the asset |
| Switch in | Restarting in a new country | Newcomers to Canada, the UK, the EU, or the US |
| Switch in | Back to work after a layoff or break | Analysts restarting a search on a deadline |
| More technical | How to become a technical BA | BAs pulled into API and data defects |
| More technical | QA analyst to SDET | Manual testers ready to write the automation themselves |
| More technical | Technical analyst to developer | Analysts who already script and want to ship code |
| More technical | Analyst to analytics engineer | Data and BI analysts who live in SQL |
| More technical | Systems analyst to solutions architect | Systems analysts consulted before integrations |
| More technical | To forward deployed or solutions engineer | Technical BAs who like clients as much as systems |
| Less technical | BA to product manager | Analysts who want to own the decision, not document it |
| Less technical | BA to delivery manager or scrum master | Analysts who unblock teams better than they write specs |
| Less technical | Business architect, change lead, consultant | Senior analysts who prefer strategy and people |
| Move up | Head of business analysis vs principal analyst | Leads choosing between managing people and staying hands-on |
| Move up | Junior to senior business analyst | Analysts who want to know what gets people promoted |
| Move up | Highest paying domains | Analysts who want domain knowledge to show up in pay |
| Move up | Certifications ranked by return | Anyone about to pay for CBAP, CCBA, ISTQB, or PSPO |
| Earn more | Negotiating a raise or an offer | Analysts paid at the bottom of their band |
| Earn more | Going contract | Senior analysts weighing day rates against a salary |
| Earn more | Employer type and pay | Anyone comparing banks, consultancies, SaaS, and public sector |
| Any move | The analyst portfolio | Anyone whose best work is under NDA |
| Any move | Rewriting your CV for a role change | Anyone whose CV describes the old job |
| Any move | Interviewing as a career changer | Anyone who will be asked “why the switch?” |
| Any move | Changing role inside your company | Anyone who would rather not start from zero |
| Any move | Business analysis and AI | Anyone wondering which analyst roles AI exposes |
How much does each move pay?
Technical moves pay more within a year; less technical moves pay about the same at first; switching in from a well paid profession usually costs money for one to three years. Senior bands for the main destinations, as indicative 2026 base salary, permanent roles, large cities, excluding bonus and equity.
| Destination role (senior unless noted) | US (USD) | Canada (CAD) | UK (GBP) | Eurozone (EUR) |
|---|---|---|---|---|
| Business analyst | 110k to 135k | 90k to 110k | 55k to 72k | 60k to 75k |
| Technical BA | 125k to 155k | 100k to 125k | 65k to 85k | 65k to 82k |
| SDET | 130k to 160k | 105k to 130k | 65k to 85k | 68k to 85k |
| Analytics engineer | 140k to 170k | 110k to 135k | 70k to 90k | 72k to 88k |
| Solutions architect (first role) | 130k to 160k | 115k to 145k | 70k to 90k | 70k to 90k |
| Product manager | 140k to 180k | 115k to 150k | 75k to 100k | 70k to 90k |
| Head of business analysis (lead) | 150k to 190k | 130k to 165k | 85k to 115k | 85k to 110k |
| Junior business analyst (entry point) | 65k to 85k | 58k to 72k | 32k to 42k | 38k to 48k |
The technical premium over a senior BA is fast: 10 to 20 percent for technical BA, more for analytics engineering. The leadership premium is larger but takes years. Banking in New York or London typically adds 10 to 20 percent. Verify before relying on any number: posted ranges in pay transparency jurisdictions (New York, California, Colorado, Washington, Illinois, British Columbia, and Ontario since January 1, 2026 for employers with 25 or more employees), ITJobsWatch in the UK, the annual Robert Half, Hays, and Michael Page salary guides, Levels.fyi for companies with equity, and two people one level above you.
What do real analyst career moves look like?
The cases below are composites of moves I have watched on delivery teams, with details changed.
Nadia: from teacher to business analyst in Toronto
Nadia taught secondary school mathematics in Toronto on about C$98k, near the top of the Ontario scale. Over nine months of evenings she learned SQL, built three artifacts (a process map of grade submission, a functional specification for parent notifications, a UAT test plan), and completed the Become a Technical Analyst track. She landed a BA role at an education software vendor at C$74k, the low end of the mid band because her domain transferred. That is a C$24k cut before counting the pension. What she would do differently: apply to her school board’s IT project office first, where the pension would have continued.
Priya: from business analyst to technical BA in London
Priya was a mid business analyst at a London retail bank on £50k. Developers already pinged her about payment defects, so she spent six months making it official: SQL against the reporting replica, the payments OpenAPI contract, a Bruno collection of her own checks, and the Analyze a Payment API mission as practice. She moved internally to a technical BA seat on an ISO 20022 migration at £58k, a 16 percent rise inside the mid technical BA band of £50k to £65k. What she would do differently: ask for the title change in writing a quarter earlier: she did technical BA work at BA pay for three months.
Karim: from senior developer to technical BA in New York
Karim was a senior Java developer at an insurer in New York on US$160k. In four months he rewrote his CV around decisions rather than code and wrote two specifications from projects he had built. His first offers were plain senior BA roles at about US$125k, a 22 percent cut. He switched targets to senior technical BA roles in payments and landed one at a bank in New York at US$150k, a cut of about 6 percent that banking pay nearly closed. What he would do differently: target technical BA roles in banking from day one.
How do you choose your move in 20 minutes?
Use the Technical Analyst Skill Matrix and a timer. The output is one sentence.
- Minutes 0 to 7: score yourself. Go through the 25 skills in the matrix and write Level 1, 2, or 3 next to each.
- Minutes 7 to 9: answer the Tuesday question. One word: systems, people, decisions, or money. If you are outside tech, write the domain you know best instead.
- Minutes 9 to 12: pick the row. Find your goal in the decision table and note the move and its time.
- Minutes 12 to 15: count the gap. List the skills your target role needs at Level 2 where you score Level 1. Three or fewer is a 6 month move. Six or more is a 12 month move or a two-step move.
- Minutes 15 to 18: check the money. Find your current band and the target band in the salary guide. Write the delta and whether a short term cut is acceptable.
- Minutes 18 to 20: write the sentence. “In N months I will be a TARGET ROLE at an EMPLOYER TYPE, paid about X, and the first artifact I will build is Y.” If the roadmap shows a level in between, start there.
What does a 90 day plan look like for any career move?
Every successful move I have watched produced visible artifacts in 90 days. This sequence works for all five kinds.
- Week 1: decide. Run the 20 minute exercise. Artifact: the one sentence, written where you will see it.
- Weeks 2 to 3: benchmark. Collect three pay data points for the target role. Artifact: a one-page pay sheet with bottom, middle, and top of the band.
- Weeks 2 to 8: close the top gap. Work on the two skills furthest below Level 2. Artifact: a SQL investigation, an API contract review, or a specification.
- Weeks 4 to 10: build proof you can show. Complete missions in the Labs; a free account saves your progress and unlocks the worked solutions. Artifact: a portfolio page with two write-ups.
- Weeks 6 to 10: rewrite the story. Artifact: a CV with before and after bullets and a 90 second answer to “why this move?” The question bank in the BA and Technical BA Interview Guide covers what each question tests and how to answer from real work.
- Weeks 8 to 12: have the conversations. Internal first, then external. Artifact: a log of ten conversations and their next steps.
Switching in from outside tech, the search itself needs structure. Land Your First Job is a week-by-week plan from the search to day 90 for career changers, with templates that get a reply.
What mistakes stall an analyst career move?
- Choosing by title instead of by Tuesday. Product manager sounds like a promotion until you realise you hate saying no every day.
- Collecting certificates instead of artifacts. A hiring manager spends ten seconds on a certificate and ten minutes on a specification you wrote. Rank certifications by return before paying for one.
- Applying to the generic version of the role. A developer applying to generic BA roles takes a 20 percent cut that a technical BA role in banking would have avoided.
- Ignoring the internal route. Your employer already trusts you, and an internal move skips probation.
- Hiding a pay cut from yourself. If the move costs C$20k for two years, write it down and decide with the number in front of you.
- Waiting for permission. Do the target role’s work for a quarter, then ask for the title with evidence.
The takeaway
There are five kinds of analyst career move, and the right one follows from what you want more of on an ordinary Tuesday. Technical moves pay 10 to 40 percent more within a year, less technical moves pay about the same at first, and switching in from outside tech usually starts in the junior band. Pick one move, benchmark the pay, build two artifacts, and have the conversations.
If you want the full set of guides and templates behind the technical moves, start with the Complete Tech BA Bundle. For a second opinion on your own move plan, CV, or offer, book a 1:1 Tech BA Coaching Call. Grab the free downloads first, or browse everything at The Tech BA Toolkit. More on the analyst role itself lives in the Business Analyst hub.
Ahmed is a Senior Technical Business Analyst with 10+ years in banking and payments. He builds practical guides and tools for analysts at The Tech BA Toolkit.
Tags: Business Analysis, Career Growth, Career Change, Salary, Technical Analysis
About the author
Analyst Engineering is written by Ahmed, a Senior Technical Business Analyst with 10+ years of banking and payments delivery experience: ISO 20022 and SWIFT messaging, payments API integration, Kafka event validation, and production support. Every article comes from real delivery work, and each one is reviewed and updated as tools and standards change.
Related articles
- Analyst Salaries in 2026: Realistic Pay by Role, Level, and Country Realistic 2026 analyst pay by role and level in the US, Canada, UK, and Eurozone: BA, technical BA, QA, SDET, data, architecture, product, and contract rates.
- How to Become a Technical Business Analyst: The Six Month Plan and the Pay Jump How to become a technical business analyst: SQL, APIs, logs, and scripting in six months on your project, one artifact a month, and a 10 to 20 percent pay jump.
- How to Switch Careers Into Business Analysis in 2026 (From Teaching, Nursing, Retail, and Support) Switching into business analysis from teaching, nursing, retail, or support: the real timeline, first-role pay by country, the pay cut, and the tech kit.
- Changing Role Inside Your Company: The Cheapest Career Move an Analyst Can Make An internal move is the cheapest analyst career change: 3 to 9 months, usually no pay cut. The step plan, the move proposal, and how to ask for a regrade.
Go deeper on this
Not ready to buy? The free downloads are a no-cost place to start, and every article here stays free.
Free account
Practice on the Labs, keep your progress
A free account, no password: an email link signs you in. It saves your steps and self-assessments on the Labs, shows your missions on a dashboard, unlocks the solutions, and, if you tick the box, sends you new missions and articles when they ship.
Your email is used to sign you in. Nothing else, unless you ask. Privacy.