From Technical Analyst to Software Developer: Is the Move Worth It in the AI Era?

Moving from technical analyst to software developer is still possible in 2026, but the honest verdict is that the external route is harder than it was: junior developer hiring is tight and AI compresses the routine coding work juniors used to be hired for. The route that works is internal, on your own team’s codebase, using your domain knowledge as the edge. The pay case is real but smaller than people assume: a mid technical BA earns about US$95k to US$125k and a mid software developer about US$110k to US$145k in US large cities, and the first developer title often resets an experienced analyst to a lower level.

On a payments team I worked with, a technical BA traced a failed settlement batch to a date parsing bug: the parser read 2026-03-08 in the file header as local time, and the daylight saving change in March shifted a cut-off by an hour. She wrote up the evidence, then wrote the failing test to prove it. The developer who picked up the ticket looked at the test and said: you have done the hard part, just send the pull request. She did. Over the next year she sent 40 more. That is the most reliable route from analyst to developer I have seen, and it looks nothing like a bootcamp.

What made it work was not a course. She could read the service, run it locally, write a test, and use Git without fear. Those are the skills in The Tech Skills Guide for BAs, which covers reading code, SQL, APIs, and delivery tools for analysts who want to contribute beyond requirements.

What does the move from technical analyst to developer actually look like?

The move changes what you are accountable for: an analyst answers for the understanding the team builds on, a developer answers for the code running in production. The difference is sharper than the shared tools suggest, and technical BA vs software engineer sets it out in detail.

Dimension	Technical BA or developer analyst	Software developer
Main deliverable	Specs, verified analysis, test evidence, scripts	Production code, merged and deployed
Code you write	Scripts, API tests, queries, prototypes	Features, fixes, migrations, infrastructure as code
Who reviews your work	Product owner, developers, QA	Other developers, in every pull request
Measured on	Rework avoided, clarity, defects prevented	Delivery, quality, incidents
On call	Rarely, or as incident analyst	Often, for services you own
Where AI hits hardest	Drafting documents	Generating routine code

The last row matters. The developer analyst vs backend developer comparison shows two roles that use the same tools with different accountability. AI is compressing the part of the developer job that consists of translating a clear ticket into routine code, which is exactly where a new developer used to start. The parts it leaves (deciding what to build, testing it against the rule, reviewing, owning it in production) are covered in the developer’s job when AI writes the code.

When is the move to software developer worth it?

The move is worth it when three things are true: you want to own code in production, not just write it; your employer will let you move internally or your domain makes you rare on a developer team; and you can accept a possible level reset for a year or two. If one of those is false, the better bet is often a developer analyst or technical BA role that ships code, described in what a developer analyst does. That role keeps your seniority, and a senior technical BA who writes code is scarcer than a junior developer.

How much does a software developer earn compared with a technical analyst?

A mid software developer earns more than a mid technical BA in every market, but the gap is smaller than people expect and it disappears if the move resets your level. The figures below are indicative 2026 base salary, permanent roles, large cities, outside big tech.

Role and level	US (USD)	Canada (CAD)	UK, London (GBP)	Eurozone (EUR)
Technical BA, mid	95k to 125k	80k to 100k	50k to 65k	52k to 65k
Technical BA, senior	125k to 155k	100k to 125k	65k to 85k	65k to 82k
Software developer, junior	85k to 110k	75k to 95k	40k to 55k	45k to 55k
Software developer, mid	110k to 145k	95k to 125k	55k to 75k	55k to 70k
Software developer, senior	140k to 180k	120k to 155k	75k to 100k	70k to 90k

The honest reading: a mid technical BA who lands a mid developer title gains roughly 10 to 20 percent. A senior technical BA who is offered a junior or mid developer title takes a cut in every market; in London, £65k to £85k against £55k to £75k. The premium arrives later, at senior developer and beyond, and only if you progress there. Big tech total compensation is a different world, but it is also where coding interviews are hardest for career changers. Banking and capital markets in New York or London typically add 10 to 20 percent to both roles.

To check your own market, read posted ranges in pay transparency jurisdictions (New York, California, Colorado, Washington, Illinois and several other US states; British Columbia and, since January 1, 2026, Ontario for employers with 25 or more employees; the EU as member states implement the Pay Transparency Directive). ITJobsWatch covers UK rates by keyword, the annual Robert Half, Hays, and Michael Page guides cover most markets, and Levels.fyi covers tech companies with equity. Ask two developers one level above you what their band is. The full table is in the analyst salary guide for 2026.

What should an analyst build to become a developer?

Build production code with review, tests, and a real feature in your team’s repository. Nothing else carries the same weight with a hiring manager, internal or external, because it proves the three things a developer is trusted with: changing a real system, proving the change, and taking feedback.

Data structures and algorithms deserve exactly as much time as the interviews at your target employers require. An internal move usually needs none. A product company may run one or two coding rounds, where a few weeks on arrays, hash maps, trees, and basic graph traversal is enough. Only big tech needs sustained practice. Spending six months on algorithm puzzles instead of merged pull requests is the most common way I see analysts stall.

Use AI to learn faster, not to skip the learning. Pointing an assistant at your team’s repository to ask where a rule lives, as described in AI in the codebase for analysts, cuts weeks off onboarding. Submitting generated code you cannot explain does the opposite: reviewers notice, and trust is the currency of an internal move. Learn to review AI-generated code with the same rigour you would apply to anyone else’s, and derive your tests from the requirement as developer testing in the AI era explains.

What do real analyst to developer moves look like?

The cases below are composites of moves I have watched on delivery teams, with details changed.

A technical BA in Toronto who moved into the team’s backend

Arjun was a mid technical BA on a Toronto bank’s payments team, on C$92k. He started by writing failing tests for bugs he had analysed, then fixing the simpler ones himself in the team’s Java service, always through a pull request. After about a year and 30 merged changes, including one small feature (a new validation rule on a payment initiation endpoint he had specified), his manager moved him to an intermediate developer title on the same team at C$105k. What he would do differently: ask for a written development plan in month three instead of month nine, so the title change had a date.

A BA in Lyon who tried a bootcamp and went back to technical BA with code

Camille was a mid business analyst in Lyon on €48k. She left her job for a 12 week web development bootcamp, then spent six months applying for junior developer roles: dozens of applications, three interviews, one offer at €45k, a cut from where she started. She declined it, took a technical BA role at a payments company that valued her new Python and SQL, and started at €56k. She now writes scripts and API tests every week. What she would do differently: learn the same skills while employed and move to technical BA first; the bootcamp taught her to code, but the market paid for code plus analysis.

A systems analyst in Seattle who became a platform engineer

Dana was a senior systems analyst at a Seattle logistics company on US$125k, the person who knew how every integration was wired. She started automating environment checks with Python, then Terraform changes for the integration layer, reviewed by the platform team. Eighteen months later she moved into a platform engineer role, at the mid developer level, on US$138k (Washington job ads carry ranges, which helped). What she would do differently: pick one cloud and one infrastructure tool early instead of sampling four.

What is the 12 month plan from technical analyst to developer?

This plan assumes you stay in your current role and move internally. Each step ends with an artifact.

1. Month 1: run the service locally. Clone your team’s main repository, get it running with its tests, and fix anything wrong in the setup instructions. Use Git for analysts if branches still feel risky. Artifact: your first merged pull request, a README fix.
2. Month 2: write a test for a known bug. Take a defect you analysed and write the failing test that reproduces it. Artifact: a merged test the developer used to fix the bug.
3. Month 3: fix a small bug yourself. Pick a low-risk defect, fix it with a test, and take the review comments without defending. Artifact: three merged pull requests and a written development plan agreed with your manager.
4. Months 4 to 6: ship one small feature end to end. A validation rule, a new field, a report endpoint. Specify it, build it, test it, write the release note, and watch production for the first day. Artifact: a feature in production with your name on the commits and the runbook.
5. Months 7 to 9: review others’ code. Review at least 20 pull requests with substantive comments on behaviour and tests. Artifact: a review history your tech lead can point to.
6. Months 10 to 12: make the case. Write a one page summary of merged changes, the feature, and incidents you helped resolve. If the move is external, add a few weeks of interview practice for your target employers. Artifact: the promotion case, or an interview-ready portfolio.

If you want practice outside your codebase first, the Investigate a Duplicate Refund mission in the Labs takes you from a vague ticket to a root cause with evidence from APIs, logs, and data, which is the same investigation that precedes most bug fixes. A free account saves your progress and unlocks the solution, and the Become a Technical Analyst track orders the missions. For the small automations that build coding habit inside your current job, The BA Automation Guide covers automating the analyst workflow. If you start with nothing, scripting checks in Python is the first rung.

What mistakes stall the move from analyst to developer?

• Quitting for a bootcamp before trying the internal route. You give up your domain edge and your salary to compete as a generic junior, where demand is weakest.
• Tutorial apps instead of reviewed code. A to-do app nobody reviewed proves little. One merged fix in a real payments service proves a lot.
• Algorithm practice as the whole plan. It matters for some interviews; it does not replace production work.
• Hiding your domain. “I know why this rule exists” is your advantage on a developer team. Lead with it.
• Accepting a title that costs you money without a plan. A senior analyst taking a junior developer title should see a written path back to their current pay within two years.
• Shipping AI code you cannot explain. Reviewers notice within a week, and it costs the trust an internal move depends on.

Which other technical moves should an analyst compare?

Compare the developer route with the moves that keep more of your analysis seniority before you commit. QA analyst to automation engineer is a shorter step into code with a clear pay jump. Analyst to analytics engineer suits analysts who live in SQL. Technical analyst to forward deployed engineer pays more than most developer roles for people who like clients and code together, and The Forward Deployed Engineer Career Guide maps that route from technical BA: the role, the pay, the transferable skills, and the gap. For the internal mechanics of any of these, read changing role inside your company, and if AI risk is the reason you are looking, is business analysis a safe career with AI weighs which roles are exposed. Score yourself first with the technical analyst skill matrix and the career paths map.

The takeaway

The move from technical analyst to software developer is worth it for people who want to own production code and can make it inside their own team. It is a poor bet as an external restart in 2026, when junior hiring is tight and AI does much of the work juniors were hired for. Your domain knowledge is the advantage; a route that throws it away throws away the reason anyone would hire you over a stronger generic coder. For many senior analysts, a technical BA or developer analyst role that ships code is the better paid, lower risk version of the same ambition.

Build the base with The Tech Skills Guide for BAs. If you want to test your plan or an offer against someone who has hired on delivery teams, book a 1:1 Tech BA Coaching Call. Start with the free downloads, browse The Tech BA Toolkit, and find more on the coding side of analysis in the Developer 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: Software Development, Career Change, Career Growth, Artificial Intelligence, Banking