The last solutions architect CV that made me stop reading opened with a re-platforming project and the money it saved, not a job title and a wall of acronyms.
Most do the opposite. They list every technology the candidate has touched and leave the reader guessing whether they design cloud, Salesforce, or telecom systems. Name your specialisation in the first two lines, then prove it with architecture you have actually owned.
Key takeaways
- Lead with your specialisation, cloud, Salesforce, or telecom, in the headline and the first line of your personal statement. Recruiters filter architects by domain first.
- Solutions architect roles skew senior. Frame yourself at lead level by the decisions you signed off, not the tasks you completed.
- Quantify the architecture: cost removed, latency cut, systems integrated, users served, and downtime avoided.
- AWS, Agile, and Azure recur most in UK postings. Mirror the stack from the advert wherever it is genuinely yours.
- Most UK roles are onsite or hybrid, so put your location and working pattern near the top.
- Two pages, reverse chronological, sent as a PDF unless the advert asks otherwise.
Lead with your architecture specialisation
"Solutions architect" is not one job. It is at least three, and a recruiter screens for the one they are hiring before they read a single bullet.
Cloud architects design on AWS or Azure. Salesforce architects design orgs, data models, and integrations across the Salesforce clouds. Telecom solution architects design carrier networks and OSS/BSS. Enterprise and integration architects sit across all of them. Pick the one that matches the role and make it unmissable in the first two lines.
Signal it in four places: your CV headline, the first sentence of your personal statement, the top of your skills list, and your most recent role. If a hiring manager has to hunt for your domain, you have already lost the six-second scan.
Then prove the specialisation with architecture you owned, not tools you touched:
- Cloud (AWS or Azure): migrations, landing zones, well-architected reviews, infrastructure as code with Terraform, and the cost you took out. "Migrated 40 services to AWS and cut monthly spend by 32%" beats "experienced with AWS".
- Salesforce: data model and org strategy, Sales and Service Cloud design, integration patterns, and governance over Apex and flows. Name the clouds and the integration approach, not just "Salesforce".
- Telecom: OSS/BSS design, network function virtualisation, 5G core, and service orchestration at carrier scale. Quantify subscribers served or provisioning time saved.
- Enterprise and integration: target operating models, API strategy, event-driven design, and the systems you connected. Show the decision, the trade-off, and the outcome.
You can hold more than one specialisation, and many senior architects do. Choose the primary one for this application, lead the CV with it, and let the second appear as supporting depth further down.
If you are moving between domains, say from on-premise integration into cloud, do not hide it. Frame the transferable core, systems thinking, trade-off analysis, and stakeholder sign-off, then show the new stack in your most recent project and your certifications. Architecture principles travel better than tools.
Depth in one domain reads as senior. A shallow sweep across all four reads as a generalist who has never led an architecture end to end.
PRO TIP
Put the specialisation in your headline, not just "Solutions Architect". "AWS Solutions Architect" or "Salesforce Solutions Architect" tells the recruiter and the ATS exactly which shortlist you belong on. Match the wording to the advert wherever it is genuinely true of you.
What the UK solutions architect market looks like
Knowing the market shapes the CV. Here is what the role pays and what UK employers actually ask for.
| What | UK solutions architect roles |
|---|---|
| Typical pay | £36,000 to £85,000 a year (National Careers Service (gov.uk)) |
| Where the work happens | Onsite 53%, hybrid 43%, remote 4% (111 UK postings in the last ~30 days, Enhancv's internal job feed) |
| Seniority most asked for | Lead level in 89% of postings, senior in 6% |
| Most-listed skills | AWS, Agile, and Azure, then security, networking, and Python |
Three of those numbers should shape your CV.
Nearly nine in ten postings are pitched at lead level, so frame yourself by the decisions you owned rather than the tasks you completed. A solutions architect who "chose the integration approach and signed off the design" outranks one who "worked on integrations".
The work is overwhelmingly onsite or hybrid, with barely any fully remote roles, so put your location and the pattern you can offer near the top. If you can commute to a client site, say so.
AWS, Agile, and Azure recur most across the postings, followed by security, networking, and Python. Mirror the stack from the advert wherever it is genuinely yours, and lead with the cloud the employer names.
The pay range is wide because the title spans mid-level design roles and lead architects who own multimillion-pound programmes. Where you sit in that band is set by the scale you can prove, which is one more reason to quantify.
Formatting your solutions architect CV
Use a reverse chronological structure. At lead level your recent architecture is the strongest evidence you have, so it belongs at the top.
Keep it to two pages. Open with a three-line technical summary under the header, add a grouped tech stack (cloud, integration, data, tooling), and put certifications where a reader can find them in seconds.
One column is safer than two for this role. Architecture CVs are dense with stack names and dates, and a single column parses more reliably and reads better on a recruiter's second screen. If you reference an architecture diagram or a GitHub profile, add a plain link rather than embedding an image that an ATS cannot read.
Send a PDF unless the advert or agency asks for a Word file. A PDF holds your layout and the grouped stack exactly as you built them.
Solutions architect applications almost always pass through an ATS, so keep headings standard and spell out each acronym once, for example Amazon Web Services (AWS). Build from a tested layout rather than a blank page: Enhancv's CV templates export to a clean, ATS-friendly PDF.
Writing your solutions architect personal statement
Three or four sentences at the top: your specialisation, the scale you operate at, one signature outcome, and the kind of role you want. See more personal statement examples if the opening line is not coming.
Lead with a number and a decision, not a list of technologies. The weak version reads like a stack: "Experienced solutions architect skilled in AWS, Azure, Salesforce, Python, Terraform, Kubernetes, and Agile looking for a challenging new role." It gives a hiring manager nothing to picture.
Rewrite the statement for each specialisation you apply to. A Salesforce role wants to see org strategy and integration first, a telecom role wants OSS/BSS and network scale, and a cloud role wants the migration and the cost. The structure stays the same, but the first noun after your name should change with the advert.
Write the version that shows an architect who has owned outcomes:
Solutions architect personal statement example (cloud)
AWS solutions architect with eight years designing cloud platforms for regulated UK financial services. Led a 40-service migration from on-premise to AWS that cut infrastructure spend by 32% and halved release times. AWS Certified Solutions Architect (Professional) and TOGAF 9 certified. Looking to own end-to-end cloud architecture for a hybrid team in the London area.
When I read a solutions architect CV, I am looking for one thing in the first three lines: what do you actually architect, and how big was the last thing you owned? Name the domain, cloud, Salesforce, or telecom, then give me one decision and the number that came with it. A migration that saved 32% or a design that carried two million users tells me more than a stack of ten certifications. Architects who lead with the outcome get the call. Architects who lead with the toolset get filtered.
Writing your solutions architect experience section
Write each role as decisions and outcomes, not responsibilities. Lead every bullet with a strong action verb and close it with a measurable result.
Architecture is measurable even when it feels abstract: cost removed, latency cut, systems integrated, uptime protected, users served, and delivery time saved. Those are your CV achievements.
Show the trade-off, not just the tool. "Chose event-driven integration over point-to-point to cut coupling across 12 services" proves architectural judgement in a way "used Kafka" never will.
If a client or figure is confidential, quantify the shape of it instead: a percentage, an order of magnitude, or a relative improvement. A range is stronger than a blank.
Tailor each application to the advert: pull the cloud, the patterns, and the certifications it names and mirror them where they are true of you. Enhancv's CV tailoring feature reads the ad and suggests the matching edits, which saves rewriting from scratch for every role.
- Owned the target architecture for a 40-service migration from on-premise to AWS, cutting monthly infrastructure spend by 32% and halving average release time
- Chose an event-driven integration pattern over point-to-point, reducing coupling across 12 services and cutting incident volume by 28%
- Ran well-architected reviews and defined the Terraform landing zone standards adopted by four delivery teams
- Presented design trade-offs to the CTO and risk board, securing sign-off for a £2.4m platform programme
- Designed the integration architecture for a retail order system handling 1.2m transactions a day, cutting checkout latency by 40%
- Introduced infrastructure as code across three environments, reducing provisioning time from two days to under an hour
- Mentored four engineers into senior roles and set the API design standards used across the delivery organisation
PRO TIP
Recruiters and hiring managers skim architecture CVs for scale and ownership. Put a number on the blast radius of every design: services, users, transactions, spend, or downtime avoided. One quantified decision outranks a paragraph of responsibilities.
Top skills for your solutions architect CV
Read a dozen live UK adverts and the same demands repeat. AWS, Azure, and Agile lead, followed by security, networking, and Python. Those are your hard skills, listed in the words the adverts use.
Group them so a reader can scan your domain fast: cloud, integration, data, security, and tooling. A grouped stack reads as an architect. A flat alphabetical list reads as a junior developer.
The soft skills that matter here are the ones that get a design approved: stakeholder management, communication, and the judgement to defend a trade-off. Prove each in an experience bullet rather than claiming it.
Top skills for your solutions architect CV:
Solution and systems design
Cloud architecture (AWS, Azure)
Integration and APIs
Microservices and event-driven design
Infrastructure as code (Terraform)
Security and compliance
Networking
Python
Agile delivery
Data architecture
Stakeholder management
Communication
Requirements gathering
Technical leadership
Problem solving
Certifications that prove your architecture credibility
Architecture is one of the few fields where certifications genuinely move a shortlist, because they map to the stack an employer already runs.
List the ones that match your specialisation, newest first, with the year:
- Cloud: AWS Certified Solutions Architect (Associate or Professional), Microsoft Certified: Azure Solutions Architect Expert, or Google Professional Cloud Architect.
- Enterprise: TOGAF 9 or 10, the most widely recognised architecture framework in UK enterprise roles.
- Salesforce: Salesforce Certified Application Architect or System Architect, building towards Certified Technical Architect.
- Telecom and networking: Cisco CCNP or CCIE where the role is network-heavy.
Prioritise the certification that matches the advert, and drop any that have expired unless you are actively renewing them. A lapsed cloud badge dated four years ago raises a question you do not want asked in the screen.
Put them in a dedicated block near the top, not buried under education. For an architect, a current AWS Professional certification often carries more weight than a decade-old degree.
Conclusion
Name your specialisation in the first two lines, frame yourself at the lead level the market hires for, and quantify the architecture you have owned.
Do that, and your CV stops reading like a tech stack with a name on top and starts reading like an architect a hiring manager wants in the room. Pair it with a short cover letter that names the one design you are proudest of.
Author's take - the Enhancv team
When I read a solutions architect CV, I am looking for one thing in the first three lines: what do you actually architect, and how big was the last thing you owned? Name the domain, cloud, Salesforce, or telecom, then give me one decision and the number that came with it. A migration that saved 32% or a design that carried two million users tells me more than a stack of ten certifications. Architects who lead with the outcome get the call. Architects who lead with the toolset get filtered.