Solutions Architect (Consulting-Side)
Solutions Architect (Consulting-Side) is the systems-integrator/professional-services version of this title — and in current live postings, that means as much at SaaS-vendor professional-services orgs (Anaplan, Klaviyo, Contentful, New Relic, Chainguard) and AWS-reseller shops like Caylent as at the classic Big SI names (Accenture, Deloitte, Slalom, Capgemini). The real dividing line from vendor-side SA isn't employer size, it's scope: you're expected to work fluently across a client's mixed stack — cloud platforms, integration tooling, sometimes a specific enterprise platform's own build environment (Anaplan models, Adobe AEP, Salesforce Commerce Cloud, SAP) — rather than going deep on one vendor's product. Certifications matter here in a way they don't for most engineering archetypes: about two-thirds of current postings name a required or preferred cert (AWS or Azure Solutions Architect, CISSP, platform-specific credentials), and cloud depth — AWS most often, then Azure, then GCP — is close to table stakes. Don't assume this is a slide-deck job, either: roughly half of postings also expect hands-on DevOps/infrastructure-as-code work (Terraform is the name that shows up most), and Python scripting is common enough to not be optional. There's also a real security-cleared pocket of this title (concentrated in GDIT postings) that looks nothing like the client-portfolio version described below — no proposal or SOW language at all, just a cleared architect hands-on-building a single government cloud migration under FedRAMP/NIST rules. If a posting under this title mentions a clearance requirement, expect that job instead.
What matters most for this role
Needs 'breadth across platforms, integration technologies, cloud services, enterprise patterns,' directly contrasted against vendor SAs who go deep on one platform — one of the archetype's most central traits.
Leads technical discussions, solutioning workshops, and architectural reviews, acting as 'an alignment point between the bid team and the client.'
Per the resolved comp note, Levels.fyi-anchored figures show a modest bonus (~6-15% of base) tied to utilization/margin, explicitly NOT commission.
Reinforces the utilization-model finding: Cortex's Sr PS Engineer posting (a close analog) describes a regional 'book of business,' and the archetype's own utilization-rate staffing model (75-85% target) structurally requires juggling a portfolio of concurrent billable engagements — one of the most confidently wide-breadth archetypes in the taxonomy.
Produces solution blueprints, sequence diagrams, and integration models across multiple environments/cloud stacks — genuine cross-system design, though per-client rather than for many internal teams.
A day in this role
Your day splits between two modes that show up across nearly every posting: pre-sales-to-SOW work, and delivery oversight of engagements already sold. In discovery and scoping workshops you're translating a client's requirements into a solution design, a level-of-effort estimate, and eventually a proposal or Statement of Work — the same handoff pattern whether you're at Klaviyo, Caylent, or Anaplan. Once an engagement is live, you're often the senior technical owner accountable for it landing on time and on budget, coordinating with (not being) a project manager, and staying accountable through go-live. You're also the trusted-advisor voice in the room — presenting architecture and strategy directly to CTOs, CIOs, and steering committees, not just to the engineering team you're embedded with. The concrete output of most of this is architecture artifacts: reference architectures, landing zones, blueprints, sequence and integration diagrams, IaC standards — plus, depending on the company, mentoring the client's own engineers or a reseller partner's team through architecture reviews and playbooks. Some firms split this into two distinct jobs under one title: Caylent runs a dedicated pre-sales "Customer Solutions Architect" track separately from its hands-on delivery "Cloud Architect" track, so how much of your week is spent selling versus building depends heavily on which specific seat you're in, not just the job title.
Comp structure
Typical: $179K
Per the resolved comp figures for this archetype (Levels.fyi as the primary, level-segmented anchor): Accenture Solution Architects run from Associate at $115K up to Team Leader at $169K, with Senior Solution Architect median total comp around $196K (base ~$181K + modest stock + roughly $11.5K bonus — about 6% of base). Live postings outside the Big SI names back up a similar or higher band: Effectual and Trace3 currently list $160K-$215K base for Senior Cloud/Security Solutions Architects, Caylent lists $165K-$216K for Senior Customer Solution Architect and Principal AI/ML Architect roles, and Anaplan's Professional Services SA ladder runs $147K-$232K base from Senior to Principal. At the high end, security-cleared federal-SI roles (GDIT) post noticeably higher — $187K-$345K — which reflects the scarcity of cleared talent more than a different comp model. Most of this market is still base-plus-modest-bonus rather than commission: Chainguard, Trace3, Effectual, GDIT, Caylent, and Anaplan postings all describe bonus tied to utilization and project margin, not deal-by-deal attainment, with equity essentially absent below partner/MD level. Treat that as the majority pattern rather than a hard rule, though — Contentful's Associate Solution Architect posting is explicit "OTE" (base plus commission, $102K-$138K), so if a posting for this title specifically says OTE, read the fine print before assuming it's structured like the rest of this market. Wider Glassdoor-aggregate ranges (which blend many levels and geographies into one number and run meaningfully higher at the top end) are the overall observed market spread, not a conflicting figure — the level-segmented numbers above are the better anchor. Whichever number you're looking at, the structural point mostly holds: this leans utilization-linked bonus, not the deal-linked variable comp of Sales Engineer or vendor-side SA, and not the equity-heavy, no-quota comp of Forward Deployed Engineer — just don't assume that's universal without checking the specific posting.
▸ Data notes▾ Data notes
▸ Full compensation breakdown by level and company tier▾ Full compensation breakdown by level and company tier
Compensation by Company Tier
Total compensation (base + bonus + annualized equity) across five company tiers, at each career level. The same role pays very differently depending on where you take it.
solutions-architect-consulting · total comp (base + bonus + annualized equity) · P25–P75 band, P50 median
Equity Reality Check
The guaranteed money (base + bonus) against the equity upside. Startup equity is illiquid — the equity figure is annualized paper value at vest, not cash in hand.
Examples of real job postings
snapshot from 2026-07-12Real postings from the research corpus behind this archetype. Click one to read the actual listing.
How to test this cheaply
Take on (or volunteer for) a cross-team or cross-vendor integration problem at your current job — something that forces you to reason across two unfamiliar platforms or cloud stacks rather than your usual one — and notice whether the context-switching feels energizing or just tiring.
Separately, try drafting a solution blueprint or level-of-effort estimate for a hypothetical multi-vendor client problem and see whether you'd rather own that design document or be the one implementing it — that distinction (design-and-handoff versus build-and-run) is the sharpest real test of fit for this archetype.
Do this role, or hire for it? Rate how much each trait actually matters. Role-holder and hiring-manager ratings are kept separate, and no single rating changes the model; ratings are aggregated with anti-gaming thresholds before they factor in.