Solutions Architect means two different things depending on where you work, and a CV that doesn't signal which type you are will fail both. At cloud vendors, software companies, and systems integrators, a Solutions Architect is customer-facing: you design solutions for prospects and customers, deliver proofs of concept, respond to RFPs, and influence deals. At enterprises, a Solutions Architect is an internal design authority: you own architecture decisions across engineering teams, chair review boards, and translate business requirements into technical blueprints. Most solutions architect CVs read as a generic list of technologies without communicating which archetype the candidate is — and recruiters screening for a specific type move on quickly. The second failure is describing system designs without outcomes: what was designed matters far less than what it solved and at what scale. This guide covers how to position a solutions architect CV correctly, the ATS keywords that matter, and the bullet patterns that prove design authority rather than just claiming it.

What Solutions Architect Job Descriptions Require in 2026

Solutions architect JDs split clearly into two archetypes. Understanding which you are applying for determines which skills and evidence to lead with:

Pre-sales Solutions Architect (vendor-side, systems integrator, consulting): Customer-facing role. Primary deliverables: technical qualification of prospects, PoC delivery, RFP/RFI response, and executive presentation. JDs at AWS, Salesforce, ServiceNow, SAP, and major SIs consistently require: a commercial mindset (ability to connect technical solutions to business value), PoC delivery experience, and a track record of supporting deals above a threshold ARR. Technical breadth across the vendor's platform is expected; certification in the vendor's ecosystem is often listed as required.

Internal Solutions Architect (enterprise, product company): Design authority role. Primary deliverables: architecture blueprints, architecture decision records, cross-team design governance, and technical roadmap input. JDs consistently require: system design depth, integration architecture experience (connecting ERP, CRM, data, and application layers), and evidence of influencing engineering teams without direct management authority. TOGAF or equivalent architecture framework knowledge appears in senior internal SA JDs.

Requirements common to both archetypes:

  • System design at scale — designing for reliability, scalability, and security at production load, not just for functionality
  • Integration architecture — connecting enterprise systems (Salesforce, SAP, Workday, custom APIs) via event-driven patterns, REST/GraphQL APIs, or middleware; this is the most common technical gap in SA applications
  • Stakeholder communication — presenting architecture trade-offs to non-technical executives, product managers, and business owners; this is listed as a core requirement across both archetypes
  • Cloud platform depth — AWS, Azure, or GCP as the primary deployment target; IaC (Terraform, CloudFormation) expected for internal roles

Solutions architect salaries in 2026: £70K–£130K UK; $130K–$200K US. Senior and Principal SA roles at major cloud vendors exceed $250K total compensation.

ATS Keywords for a Solutions Architect CV

Solutions architect ATS filtering varies significantly by company type. Vendor SAs are filtered by platform certification and commercial language; internal SAs are filtered by architecture methodology and integration patterns.

Essential ATS terms for a solutions architect CV:

  • Title variants: Solutions Architect, Enterprise Architect, Technical Architect, Pre-Sales Architect, Principal Solutions Architect, Staff Solutions Architect
  • Architecture: system design, solution design, reference architecture, architecture blueprint, architecture decision record, ADR, architecture review board, TOGAF, Well-Architected Framework
  • Integration: REST API, API Gateway, microservices, event-driven architecture, ESB, MuleSoft, Kafka, middleware, integration patterns, enterprise integration
  • Cloud: AWS, Microsoft Azure, GCP, Terraform, CloudFormation, IaC, Kubernetes, serverless
  • Pre-sales specific: proof of concept, PoC, RFP, RFI, statement of work, SOW, technical pre-sales, deal support, ARR
  • Platforms: Salesforce, SAP, ServiceNow, Workday, Oracle — name the specific platforms relevant to the role
  • Long-tail phrases: solutions architect resume examples, how to write a solutions architect resume, technical architect cv, enterprise architect resume, pre-sales architect resume

Placement: Signal your archetype in the headline. "Solutions Architect | Pre-Sales · AWS · Salesforce · PoC Delivery" versus "Solutions Architect | Enterprise · TOGAF · Integration Architecture · AWS" tells the recruiter immediately which type they are reviewing. Your Skills section should lead with architecture patterns, then platforms, then tools — not the reverse.

Solutions Architect CV Structure and Bullets That Prove Design Authority

Section order:

  1. Headline — signal archetype (pre-sales vs. internal) and top 3–4 keywords
  2. Certifications — AWS/Azure/GCP professional or associate, TOGAF, platform certifications (Salesforce Architect, ServiceNow CSA); near the top
  3. Skills — Architecture Patterns / Integration / Cloud Platforms / Tools / Methodologies
  4. Experience — 4–5 bullets per role; outcomes from design decisions, not service lists
  5. Education — CS, engineering, or business degree; bottom

Two pages standard. Link to public architecture diagrams, GitHub IaC repositories, or documentation if available — tangible artefacts are persuasive.

Pre-sales SA bullets should show commercial impact alongside technical design. Internal SA bullets should show design decisions and their outcomes. Three examples:

  • Supported £18M in ARR as pre-sales Solutions Architect — delivered 23 enterprise PoCs over 12 months with 78% conversion rate; architected 4 strategic deals above £1M requiring custom integration design between Salesforce, legacy ERP, and bespoke data pipelines, each closing within 90-day sales cycles
  • Designed a hybrid integration architecture connecting Salesforce CRM, SAP ERP, and a proprietary data warehouse via MuleSoft — 14 integration flows processing 180K daily transactions; eliminated manual reconciliation consuming 3 FTE weekly and reduced order-to-cash cycle from 8 days to 26 hours
  • Chaired the architecture review board for a 160-engineer organisation — reviewed 38 solution designs over 12 months, blocked 7 proposals with systemic scalability or security risks before they reached production, and established a pattern library of 22 reusable architecture components that reduced design time for common scenarios by 60%

Solutions architect interviews test whiteboardability: "design a system that does X at Y scale" — often under time pressure and with deliberate ambiguity. For pre-sales SAs, this extends to presenting that design to a simulated customer stakeholder. The CV evidence you include determines the complexity of the problem you receive and the level of design authority the interviewer assumes you hold walking in.

Three Solutions Architect CV Mistakes That Cost You the Interview

Not signalling pre-sales versus internal. Mixing customer-facing language with internal governance language — "presented to 40 enterprise prospects" alongside "chaired architecture review board" — produces a CV that looks unfocused. Recruiters hiring for a vendor SA role are filtering for customer impact and commercial evidence. Those hiring for an enterprise SA role are filtering for design authority and cross-team influence. A CV that doesn't signal clearly which it is will be screened out for both. Lead with whichever archetype represents the majority of your experience, and frame everything else to support that positioning.

System designs described without scale or outcome. "Designed a microservices architecture for a retail platform" communicates almost nothing. The design details that distinguish a senior SA from a junior one are: the number and boundaries of services, the problems the decomposition solved, how inter-service communication was handled, what the failure modes are and how they're mitigated, and what the result was for the business. "Designed a 12-service event-driven architecture replacing a monolithic order management system, eliminating a deployment dependency that had required full-team coordination for every release; deployment frequency increased from monthly to daily and rollback time fell from 4 hours to under 8 minutes" is a design statement with evidence.

No communication evidence for pre-sales applications. Pre-sales solutions architecture is fundamentally a sales-adjacent role. Vendors hire SAs to win deals — the technical credibility is in service of commercial outcomes. A CV that shows only technical depth, with no evidence of customer-facing presentation, PoC delivery, or deal influence, will not shortlist for vendor SA roles regardless of architecture ability. Track your commercial contribution: deals supported (by ARR or count), PoC conversion rate, executive presentations delivered. One commercial metric changes the category your CV lands in.

If you are applying to solutions architect or enterprise architect roles and want your CV rebuilt around the specific design, integration, and platform requirements in a target job description, Resumegpt generates your solutions architect CV from your work history in under 60 seconds — archetype positioned correctly, design authority evidenced, ATS-optimised, and exported as a PDF ready to submit.