From Systems Analyst to Solutions Architect: What the Promotion Actually Requires

A senior systems analyst or technical BA who moves into a first solutions architect role typically earns 15 to 25 percent more, and most make the move after 8 to 12 years in delivery. The promotion is not a title for more experience. It is a change of accountability, from documenting how systems connect to owning the design decision and answering for it. What gets you there is evidence: architecture decision records, a design you defended in review, ownership of non-functional requirements, a cost estimate, integration pattern fluency, and, in most markets, a cloud certification such as AWS Certified Solutions Architect Associate or Azure AZ-305.

The first time I presented at a design authority, I brought a clean sequence diagram of how a wire payment moved from the channel through sanctions screening to the ISO 20022 gateway, with the three options for handling screening timeouts. I had documented each one carefully. The chief architect listened, then asked: which one do you recommend, what does it cost if you are wrong, and who gets paged at 2 a.m.? I had the analysis for all three options and an answer for none of those questions. That gap is the whole distance between a senior systems analyst and a solutions architect.

Closing it starts with writing designs that other people can hold you to. The contract is usually the first place a design becomes concrete, which is why API Documentation From Scratch is a useful early step: it covers writing API documentation that a consuming team can build against without a meeting.

What does the move from systems analyst to solutions architect actually look like?

The move replaces “here is how it works and what must change” with “here is what we will build, why, and what it will cost us”. The role comparison itself is in systems analyst vs solutions architect; this article is about the promotion. The table below is the gap I see most often in candidates.

Skill	Senior systems analyst today	What the first SA role expects
Diagrams	Accurate context and sequence diagrams of the current state	Context and container views of the target state, with options
Decisions	Documents options and their impacts	Recommends one, records it in an ADR, defends it
Non-functional requirements	Collects them from stakeholders	Owns them: numbers, trade-offs, and how they are tested
Integration	Knows each pattern in use	Chooses the pattern and names the failure modes it accepts
Cost	Rarely asked	Estimates run cost at expected and peak volume
Cloud	Knows where things are deployed	Designs for a platform, usually AWS or Azure, and holds a certification
Audience	Delivery team	Design authority, security, vendors, sponsors

Everything in the left column is still needed. What a systems analyst does remains the foundation; architects who never did that work tend to draw boxes that do not match production.

Why do architecture decision records matter so much for this promotion?

Architecture decision records (ADRs) matter because they are the one artifact that proves you made a decision rather than described one. An ADR is short, numbered, and never edited after acceptance. Here is the shape I use:

ADR-014: Publish payment status changes as events instead of polling
Status: Accepted, 2026-05-12
Context: Four downstream systems poll GET /payments/{id} every 30 seconds.
  At month-end peak this is about 1,900 requests per second, 97% unchanged.
Decision: Publish PaymentStatusChanged to a Kafka topic, keyed by payment id.
  Keep the GET endpoint for reconciliation and ad hoc lookups.
Alternatives: Webhooks per consumer (rejected: four retry policies to own).
  Longer polling interval (rejected: breaks the 60 second notification NFR).
Consequences: Consumers must be idempotent; ordering is per payment only;
  we own a schema registry entry and a dead letter topic.

Every line of that record draws on analyst skills: knowing the consumers, the volumes, and the rule. The difference is the word “Decision”. The trade-offs behind it are covered in synchronous vs asynchronous integration, integration patterns every systems analyst should know, and event-driven requirements.

Which cloud certification helps a systems analyst become a solutions architect?

AWS Certified Solutions Architect Associate and Azure AZ-305 (the design exam for the Azure Solutions Architect Expert certification) are the two most commonly named in solutions architect job ads. Pick the platform your employer runs on. In most markets the certification is close to a CV filter, especially at consultancies; it gets you to the interview, and the defended design gets you the job. How it ranks against CBAP and other analyst certifications is in which analyst certifications are worth it.

How much does a solutions architect earn compared with a systems analyst?

A first solutions architect role typically pays 15 to 25 percent more than a senior systems analyst. The figures below are indicative 2026 base salary, permanent roles, large cities.

Role and level	US (USD)	Canada (CAD)	UK, London (GBP)	Eurozone (EUR)
Systems analyst, senior	115k to 140k	98k to 120k	58k to 75k	62k to 78k
Technical BA, senior	125k to 155k	100k to 125k	65k to 85k	65k to 82k
Solutions architect, first role	130k to 160k	115k to 145k	70k to 90k	70k to 90k
Solutions architect, senior	150k to 190k	140k to 175k	85k to 115k	85k to 110k
Enterprise architect, lead	170k to 220k	150k to 190k	95k to 130k	90k to 120k

The honest reading: from senior systems analyst, the first SA role is a clear gain with no short-term cut. From senior technical BA, the first step is smaller, often flat to 10 percent, because a senior TBA is already paid for technical depth; the premium arrives at senior SA and enterprise architect. Canada and London show the widest spread between senior systems analyst and first SA. Banking and capital markets in New York or London typically add 10 to 20 percent.

Verify against your own market before you negotiate. Posted ranges are public 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; and the EU as member states implement the Pay Transparency Directive. ITJobsWatch shows UK rates for “solutions architect” by keyword, the annual Robert Half, Hays, and Michael Page guides cover most markets, and two architects one level above you will tell you their band if you ask. The cross-role table is in the analyst salary guide for 2026, and the scripts for the conversation are in how analysts negotiate a raise or an offer.

What do real systems analyst to solutions architect moves look like?

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

A senior systems analyst at a Canadian bank who became a payments solutions architect

Nadia was a senior systems analyst on a Toronto bank’s wire payments platform, on C$112k, with ten years of delivery. During the ISO 20022 migration she started writing ADRs for decisions the team was already making (where to enrich structured addresses, how to handle truncation for legacy consumers) and presenting them at the design authority with the lead architect’s blessing. She passed AWS Certified Solutions Architect Associate, owned the migration’s NFR catalogue, and led two design reviews. Eighteen months later she was named solutions architect for payments at C$135k. What she would do differently: ask to attend design authority as an observer years earlier; she learned more from six meetings than from the certification.

A technical BA at a London insurer who became a solutions architect through a consultancy

Grace was a senior technical BA at a London insurer, on £72k. Her employer had no architect vacancies for two years, so she joined a consultancy that titled people by client work and certifications. She passed AZ-305 in four months, used a claims integration she had specified as her defended design in interviews, and joined as a solutions architect at £85k. The first year was harder than expected: three clients, travel, and utilisation targets. What she would do differently: ask about utilisation and bench policy before signing, and keep one ADR portfolio she could show without breaching confidentiality.

A systems analyst who became a solutions architect and moved back to principal analyst

Ben was a senior systems analyst at a Chicago asset manager, on US$130k, promoted to solutions architect at US$155k. After eighteen months of governance meetings, slide decks, and vendor calls, he realised he missed the payloads, the edge cases, and the rules. He moved to a principal technical BA role at another firm at US$165k, within the US$150k to US$180k principal band. What he would do differently: nothing about the move, but he would have tested the architect’s week by shadowing one for a month first. The trade between leading, architecting, and staying deep is laid out in head of business analysis vs principal analyst.

What is the 12 month plan from systems analyst to solutions architect?

This plan assumes you stay in your current role and pull architecture work toward you. Each step ends with an artifact a hiring panel can read.

1. Months 1 and 2: the diagrams. Draw the system context diagram and a container diagram for the platform you know best, current state and one target state, using the C4 model (context, container, component, code). Artifact: two diagrams the lead architect agrees are accurate.
2. Months 2 to 4: three ADRs. Write ADRs for three real decisions your team is facing: one integration pattern, one data store or data platform choice (the lakehouse vs data warehouse trade-off is a common one), one security or resilience decision. Artifact: three numbered ADRs, reviewed by an architect.
3. Months 3 to 5: the NFR catalogue. Take over the non-functional requirements for your programme: latency, throughput, availability, recovery point and recovery time objectives, retention, each with a number and a test. Artifact: an NFR catalogue with owners and how each is verified.
4. Months 4 to 6: the cloud certification. Study for AWS Certified Solutions Architect Associate or AZ-305, whichever your employer runs. Artifact: the certificate, plus one design from work redrawn on that platform with a monthly cost estimate.
5. Months 6 to 9: lead a design review. Run the API design review or the solution review for one feature: circulate the options, facilitate, record the decision. Artifact: a design you defended, with the questions asked and your answers.
6. Months 9 to 12: make the case. Assemble the portfolio: diagrams, ADRs, NFR catalogue, the review, the cost estimate. Ask for the title internally before you apply outside, as changing role inside your company explains. Artifact: an architecture portfolio of eight to ten pages.

For practice on a system you can discuss openly, use Northline Pay, the fictional payments platform behind the Labs: draw its context and container diagrams and write an ADR for one of its integrations. The Analyze a Payment API mission exercises the contract review muscle that design reviews depend on. A free account saves your progress and unlocks the solutions, and the Become a Technical Analyst track orders the missions. If your API foundations need tightening before you lead a review, API Fundamentals for Analysts covers the fundamentals every contract decision rests on.

What mistakes stall the move to solutions architect?

• Documenting options without recommending one. An analyst lists trade-offs; an architect picks one and writes down what they are accepting.
• Treating the certification as the promotion. It clears the CV screen. Panels hire on the design you defended.
• Ignoring cost. “What does this cost per month at peak?” is a standard architecture interview question. Have a number, even a rough one.
• Leaving NFRs to someone else. Architects own the non-functional contract. If nobody on your programme owns it, take it.
• Drawing only the happy path. A design that does not say what happens on timeout, retry, and replay is not finished.
• Losing the detail entirely. The architects I trust most can still read a pacs.008 or an OpenAPI contract. The ISO 20022 architecture is the kind of depth that makes a payments architect credible.

In banking and payments, domain depth is often what separates the analyst who gets the architect title from the one who does not. Break Into Banking covers the domain knowledge that unlocks premium pay in banking and payments, which is the same knowledge a payments architect is expected to hold.

Which other moves should a senior systems analyst consider?

Solutions architect is the most common next step for a senior systems analyst, but not the only one. Analysts who prefer client work with code look at technical analyst to forward deployed engineer, and analysts who want to stay deep compare the principal track in head of business analysis vs principal analyst. The career paths map shows the full set, and the technical analyst skill matrix is a quick way to see which gaps are real.

The takeaway

The promotion from systems analyst to solutions architect is earned with decisions, not with years. After 8 to 12 years of delivery you usually know enough; what is missing is evidence that you will choose, write it down, defend it, and answer for it. Three ADRs, a context and container diagram, an NFR catalogue, a design review you led, and a cloud certification make that evidence visible, and a first SA role typically pays 15 to 25 percent more than senior systems analyst.

Make your designs concrete with API Documentation From Scratch. If you want your architecture portfolio or an SA offer reviewed by someone who has sat on the other side of design authority, book a 1:1 Tech BA Coaching Call. The free downloads are a good place to start, and every guide is in The Tech BA Toolkit. More on mapping and designing systems lives in the Systems 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 Architecture, Systems Analysis, Career Growth, Cloud, Banking