Solutions Architect: market
Data as of November 19, 2026: 3,919 open Solutions Architect jobs, 39% remote among jobs that state a work format; median advertised salary $12,346/mo (from 521 postings that state a salary). Source: Zorky, updated daily.
Solutions Architect — the largest role of the architect direction. Designs an end-to-end solution for a specific business problem: bridge between business requirements and technical implementation. Unlike a Software Architect (deep design of internal system), a Solutions Architect composes a solution from existing building blocks (often cloud services), covers breadth of technology, often client-facing + pre-sales involvement. Role family: Solutions Architect (general — end-to-end solution design), Senior / Principal Solutions Architect (complex multi-system solutions + technical strategy), Cloud Solutions Architect (AWS / GCP / Azure-specific — largest sub-segment 2026), Pre-Sales Solutions Architect / Sales Engineer (vendor-side — customer-facing + technical sales + RFP responses + POC demos), Delivery Solutions Architect (focus on the implementation phase — leads the solution from design to production), Technical Solutions Architect (alternative title). Well-Architected Frameworks: AWS Well-Architected (6 pillars — operational excellence + security + reliability + performance + cost optimisation + sustainability), Azure Well-Architected, GCP Architecture Framework — solution review methodology. Architecture breadth (vs Software Architect depth): compute (VMs / containers / serverless), Kubernetes + managed K8s (EKS / GKE / AKS), databases (relational + NoSQL + data warehouse — choice per use case), messaging (Kafka / SQS-SNS / Pub-Sub / Service Bus), caching (Redis / CDN), networking (VPC / load balancing / DNS / hybrid connectivity), IaC (Terraform — must + cloud-native CloudFormation / Bicep / Deployment Manager). Integration: enterprise integration patterns, API management (Apigee / AWS API Gateway / Azure API Management), iPaaS (MuleSoft / Dell Boomi / Workato — integration platform), event-driven integration, ETL / ELT pipelines. Migration strategies: cloud migration 6 Rs (Rehost / Replatform / Refactor / Repurchase / Retire / Retain), strangler fig pattern, lift-and-shift vs cloud-native trade-offs. Cost estimation / TCO analysis: cloud pricing calculators, TCO (Total Cost of Ownership) modelling, FinOps awareness, cost-architecture trade-offs (critical part of solution proposal). Solution documentation: solution design documents (SDD), architecture diagrams (cloud-provider iconography — AWS / Azure / GCP diagram standards), C4 model, draw.io / Lucidchart / cloud-provider diagram tools. Pre-sales skills (for vendor-side / outsourcing Solutions Architects): RFP / RFI responses, POC (Proof of Concept) development, solution demos, effort estimation, technical proposal writing, client workshop facilitation. Domain: a Solutions Architect must have engineering background (typically ex-Senior Engineer) — you can't design a solution without understanding implementation reality. According to Zorky, 3919 active openings — the largest architect sub-niche. Top stack: solutions architect, cloud, aws, azure, agile. Among jobs with a stated work format, 39% are remote.
Data as of:
Key numbers for the Solutions Architect market: open jobs, median salary, observed talent pool and remote share.
The Solutions Architect market currently has 3,919 open roles, 3,396 of them freshly observed. Median salary $12,346/mo.
Among jobs with a stated work format, 39% are remote. Solution design + cloud work — remote-friendly, but SA is a client-facing role (workshops + presentations) → hybrid often optimal. Outsourcers — almost always remote. Pre-sales Solutions Architects (cloud-provider) — traditionally travel-heavy, but 2024–2026 more virtual. International tech companies + SI — hybrid / remote.
⚠ salary known for 521 of 3919 jobs; remote share from 3103 with a stated format; 3396 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Solutions Architect postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 76 |
| 2026-06-08 | 58 |
| 2026-06-15 | 79 |
| 2026-06-22 | 246 |
| 2026-06-29 | 260 |
| 2026-07-06 | 878 |
| 2026-07-13 | 598 |
| 2026-07-20 | 428 |
| 2026-07-27 | 274 |
| 2026-08-03 | 363 |
| 2026-08-10 | 285 |
| 2026-08-17 | 311 |
| 2026-08-24 | 332 |
| 2026-08-31 | 350 |
| 2026-09-07 | 304 |
| 2026-09-14 | 334 |
| 2026-09-21 | 738 |
| 2026-09-28 | 566 |
| 2026-10-05 | 646 |
| 2026-10-12 | 1,688 |
| 2026-10-19 | 809 |
| 2026-10-26 | 860 |
| 2026-11-02 | 728 |
| 2026-11-09 | 839 |
Active sources per week
Sources over the period: 192. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 17 |
| 2026-06-08 | 14 |
| 2026-06-15 | 20 |
| 2026-06-22 | 32 |
| 2026-06-29 | 41 |
| 2026-07-06 | 42 |
| 2026-07-13 | 56 |
| 2026-07-20 | 64 |
| 2026-07-27 | 42 |
| 2026-08-03 | 41 |
| 2026-08-10 | 38 |
| 2026-08-17 | 34 |
| 2026-08-24 | 37 |
| 2026-08-31 | 43 |
| 2026-09-07 | 35 |
| 2026-09-14 | 44 |
| 2026-09-21 | 61 |
| 2026-09-28 | 59 |
| 2026-10-05 | 56 |
| 2026-10-12 | 63 |
| 2026-10-19 | 73 |
| 2026-10-26 | 64 |
| 2026-11-02 | 66 |
| 2026-11-09 | 82 |
New sources connected: Jun 22 +18 · Jun 29 +20 · Jul 6 +16 · Jul 13 +17 · Jul 20 +21 · Nov 9 +10 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +3 | 58 |
| Jun 15 | +8 | 79 |
| Jun 22 | +18 | 246 |
| Jun 29 | +20 | 260 |
| Jul 6 | +16 | 878 |
| Jul 13 | +17 | 598 |
| Jul 20 | +21 | 428 |
| Jul 27 | +5 | 274 |
| Aug 3 | +5 | 363 |
| Aug 10 | +4 | 285 |
| Aug 17 | +5 | 311 |
| Aug 24 | +3 | 332 |
| Aug 31 | +1 | 350 |
| Sep 7 | +3 | 304 |
| Sep 14 | +1 | 334 |
| Sep 21 | +7 | 738 |
| Sep 28 | +2 | 566 |
| Oct 5 | +2 | 646 |
| Oct 12 | +6 | 1,688 |
| Oct 19 | +8 | 809 |
| Oct 26 | +3 | 860 |
| Nov 2 | +7 | 728 |
| Nov 9 | +10 | 839 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 76 | 17 |
| 2026-06-08 | 58 | 14 |
| 2026-06-15 | 79 | 20 |
| 2026-06-22 | 246 | 32 |
| 2026-06-29 | 260 | 41 |
| 2026-07-06 | 878 | 42 |
| 2026-07-13 | 598 | 56 |
| 2026-07-20 | 428 | 64 |
| 2026-07-27 | 274 | 42 |
| 2026-08-03 | 363 | 41 |
| 2026-08-10 | 285 | 38 |
| 2026-08-17 | 311 | 34 |
| 2026-08-24 | 332 | 37 |
| 2026-08-31 | 350 | 43 |
| 2026-09-07 | 304 | 35 |
| 2026-09-14 | 334 | 44 |
| 2026-09-21 | 738 | 61 |
| 2026-09-28 | 566 | 59 |
| 2026-10-05 | 646 | 56 |
| 2026-10-12 | 1,688 | 63 |
| 2026-10-19 | 809 | 73 |
| 2026-10-26 | 860 | 64 |
| 2026-11-02 | 728 | 66 |
| 2026-11-09 | 839 | 82 |
Salaries over time
Median Solutions Architect salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-08-31 | 8,826 | 12 |
| 2026-09-07 | 8,563 | 14 |
| 2026-09-14 | — | 8 |
| 2026-09-21 | 10,507 | 17 |
| 2026-09-28 | 8,931 | 42 |
| 2026-10-05 | 8,146 | 42 |
| 2026-10-12 | 11,556 | 88 |
| 2026-10-19 | 13,469 | 114 |
| 2026-10-26 | 11,269 | 172 |
| 2026-11-02 | 12,417 | 159 |
| 2026-11-09 | 12,423 | 134 |
The series starts on Aug 31: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | 8,826 |
| 2026-09-07 | 8,563 |
| 2026-09-14 | — |
| 2026-09-21 | 10,507 |
| 2026-09-28 | 8,931 |
| 2026-10-05 | 8,146 |
| 2026-10-12 | 11,556 |
| 2026-10-19 | 13,469 |
| 2026-10-26 | 11,269 |
| 2026-11-02 | 12,417 |
| 2026-11-09 | 12,423 |
Remote work over time
Share of Solutions Architect postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 53.5 |
| 2026-06-08 | 35.4 |
| 2026-06-15 | 29.4 |
| 2026-06-22 | 37.1 |
| 2026-06-29 | 42.7 |
| 2026-07-06 | 39.7 |
| 2026-07-13 | 46.8 |
| 2026-07-20 | 45.2 |
| 2026-07-27 | 60.7 |
| 2026-08-03 | 34.4 |
| 2026-08-10 | 32.4 |
| 2026-08-17 | 32.7 |
| 2026-08-24 | 28.5 |
| 2026-08-31 | 24.7 |
| 2026-09-07 | 24.5 |
| 2026-09-14 | 23.1 |
| 2026-09-21 | 37.6 |
| 2026-09-28 | 45.1 |
| 2026-10-05 | 42.8 |
| 2026-10-12 | 42.2 |
| 2026-10-19 | 42.8 |
| 2026-10-26 | 44.3 |
| 2026-11-02 | 43.2 |
| 2026-11-09 | 34.7 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 53.5 |
| 2026-06-08 | 35.4 |
| 2026-06-15 | 29.4 |
| 2026-06-22 | 37.1 |
| 2026-06-29 | 42.7 |
| 2026-07-06 | 39.7 |
| 2026-07-13 | 46.8 |
| 2026-07-20 | 45.2 |
| 2026-07-27 | 60.7 |
| 2026-08-03 | 34.4 |
| 2026-08-10 | 32.4 |
| 2026-08-17 | 32.7 |
| 2026-08-24 | 28.5 |
| 2026-08-31 | 24.7 |
| 2026-09-07 | 24.5 |
| 2026-09-14 | 23.1 |
| 2026-09-21 | 37.6 |
| 2026-09-28 | 45.1 |
| 2026-10-05 | 42.8 |
| 2026-10-12 | 42.2 |
| 2026-10-19 | 42.8 |
| 2026-10-26 | 44.3 |
| 2026-11-02 | 43.2 |
| 2026-11-09 | 34.7 |
Technologies over time
How the share of Solutions Architect postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | solutions architect | cloud | AWS |
|---|---|---|---|
| 2026-08-10 | 68.8 | 41.6 | 33.8 |
| 2026-08-17 | 65.9 | 38.4 | 27.8 |
| 2026-08-24 | 67.6 | 33.8 | 20.7 |
| 2026-08-31 | 62.3 | 36 | 32 |
| 2026-09-07 | 70.3 | 33.2 | 28.6 |
| 2026-09-14 | 68.6 | 34.9 | 24.1 |
| 2026-09-21 | 62.3 | 36.9 | 20.1 |
| 2026-09-28 | 57.8 | 46.8 | 31.3 |
| 2026-10-05 | 52.1 | 53.4 | 38.9 |
| 2026-10-12 | 53.2 | 49.8 | 26.4 |
| 2026-10-19 | 55.2 | 54.6 | 27.7 |
| 2026-10-26 | 57.4 | 52 | 26.7 |
| 2026-11-02 | 54.5 | 46.8 | 27.3 |
| 2026-11-09 | 53.7 | 50.2 | 29.1 |
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | solutions architect | cloud | AWS | Azure | Python |
|---|---|---|---|---|---|
| 2026-08-10 | 68.8 | 41.6 | 33.8 | 10 | 2.6 |
| 2026-08-17 | 65.9 | 38.4 | 27.8 | 3.9 | 3.5 |
| 2026-08-24 | 67.6 | 33.8 | 20.7 | 8.4 | 2.2 |
| 2026-08-31 | 62.3 | 36 | 32 | 8.1 | 1.7 |
| 2026-09-07 | 70.3 | 33.2 | 28.6 | 4.6 | 1.5 |
| 2026-09-14 | 68.6 | 34.9 | 24.1 | 4.2 | 2.3 |
| 2026-09-21 | 62.3 | 36.9 | 20.1 | 10.6 | 5 |
| 2026-09-28 | 57.8 | 46.8 | 31.3 | 21.1 | 6.3 |
| 2026-10-05 | 52.1 | 53.4 | 38.9 | 31.2 | 10 |
| 2026-10-12 | 53.2 | 49.8 | 26.4 | 22.1 | 9.7 |
| 2026-10-19 | 55.2 | 54.6 | 27.7 | 23.7 | 12.6 |
| 2026-10-26 | 57.4 | 52 | 26.7 | 22.3 | 12 |
| 2026-11-02 | 54.5 | 46.8 | 27.3 | 19.9 | 12.8 |
| 2026-11-09 | 53.7 | 50.2 | 29.1 | 21.2 | 13.2 |
Countries over time
How the share of Solutions Architect postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | UK | Poland |
|---|---|---|---|
| 2026-06-01 | 31 | 5.6 | 39.4 |
| 2026-06-08 | 40 | 7.3 | 3.6 |
| 2026-06-15 | 24.7 | 2.7 | 19.2 |
| 2026-06-22 | 13.9 | 3.4 | 54 |
| 2026-06-29 | 18.9 | 4 | 30.4 |
| 2026-07-06 | 42.7 | 8.7 | 5.8 |
| 2026-07-13 | 37.7 | 8.2 | 12.4 |
| 2026-07-20 | 16.3 | 22 | 28 |
| 2026-07-27 | 20.2 | 16.6 | 26.5 |
| 2026-08-03 | 24.1 | 19.9 | 4.8 |
| 2026-08-10 | 27.8 | 28.2 | 2.4 |
| 2026-08-17 | 33 | 30.8 | 2.2 |
| 2026-08-24 | 29.5 | 35.6 | 1.4 |
| 2026-08-31 | 19.7 | 35.8 | 2.9 |
| 2026-09-07 | 24.5 | 32.6 | 1.9 |
| 2026-09-14 | 24.7 | 26.8 | 2.7 |
| 2026-09-21 | 32.4 | 20.1 | 3.9 |
| 2026-09-28 | 26.5 | 16.1 | 16.1 |
| 2026-10-05 | 25 | 12.9 | 26.1 |
| 2026-10-12 | 25.9 | 10.6 | 11.8 |
| 2026-10-19 | 30.8 | 15 | 12.1 |
| 2026-10-26 | 30.4 | 15.9 | 8.1 |
| 2026-11-02 | 31.4 | 16.6 | 10.7 |
| 2026-11-09 | 25.5 | 20.1 | 6.6 |
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | UK | Poland | India | Australia |
|---|---|---|---|---|---|
| 2026-06-01 | 31 | 5.6 | 39.4 | 5.6 | 0 |
| 2026-06-08 | 40 | 7.3 | 3.6 | 14.5 | 1.8 |
| 2026-06-15 | 24.7 | 2.7 | 19.2 | 13.7 | 2.7 |
| 2026-06-22 | 13.9 | 3.4 | 54 | 7.6 | 0.8 |
| 2026-06-29 | 18.9 | 4 | 30.4 | 6.6 | 1.8 |
| 2026-07-06 | 42.7 | 8.7 | 5.8 | 7.3 | 3 |
| 2026-07-13 | 37.7 | 8.2 | 12.4 | 8.8 | 4 |
| 2026-07-20 | 16.3 | 22 | 28 | 5.4 | 9.4 |
| 2026-07-27 | 20.2 | 16.6 | 26.5 | 5.4 | 5.8 |
| 2026-08-03 | 24.1 | 19.9 | 4.8 | 5.5 | 7.7 |
| 2026-08-10 | 27.8 | 28.2 | 2.4 | 7.7 | 8.1 |
| 2026-08-17 | 33 | 30.8 | 2.2 | 5.1 | 6.2 |
| 2026-08-24 | 29.5 | 35.6 | 1.4 | 2.8 | 6.4 |
| 2026-08-31 | 19.7 | 35.8 | 2.9 | 4.8 | 6.1 |
| 2026-09-07 | 24.5 | 32.6 | 1.9 | 5.4 | 3.8 |
| 2026-09-14 | 24.7 | 26.8 | 2.7 | 5.8 | 10.5 |
| 2026-09-21 | 32.4 | 20.1 | 3.9 | 6.8 | 5.8 |
| 2026-09-28 | 26.5 | 16.1 | 16.1 | 5 | 7.9 |
| 2026-10-05 | 25 | 12.9 | 26.1 | 5.8 | 5 |
| 2026-10-12 | 25.9 | 10.6 | 11.8 | 6.5 | 3 |
| 2026-10-19 | 30.8 | 15 | 12.1 | 3.6 | 5.3 |
| 2026-10-26 | 30.4 | 15.9 | 8.1 | 5.2 | 6.8 |
| 2026-11-02 | 31.4 | 16.6 | 10.7 | 4.3 | 4.1 |
| 2026-11-09 | 25.5 | 20.1 | 6.6 | 5.1 | 3.1 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Solutions Architect.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Solutions Architect jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 3,919 |
| Open demand | 3,919 |
| Observed supply | — not published |
Solutions Architect — the largest architect sub-niche with steadily high demand. Drivers 2026: continued cloud adoption (most solutions cloud-based), cloud migration projects (legacy → cloud — banking + enterprise), multi-cloud reality, outsourcing (EPAM-style Solution Architecture practice — largest SA channel in CIS), tech-vendor Sales Engineering growth (Snowflake / Databricks / Confluent growing SA organisations). Cloud-provider Solutions Architect — premium-tier path. Russian cloud providers growing SA teams.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Solutions Architect jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 2 |
| $1–2k | 2 |
| $2–3k | 4 |
| $3–4k | 2 |
| $4–5k | 5 |
| $5–6k | 25 |
| $6–7k | 20 |
| $7–8k | 29 |
| $8–9k | 34 |
| $9–10k | 37 |
| $10–12k | 85 |
| $12–15k | 101 |
| $15–20k | 137 |
| $20k+ | 38 |
- usable for the calculation: 521 (13.3%)
- stated but not converted to USD/month: 472 (12%)
- not stated: 2,926 (74.7%)
One in ten postings offers under $6,635, one in ten over $18,800. Half of the postings offer between $9,316 and $16,031. Sample: 521.
Senior-tier role. Lower grades in the histogram — mis-titled positions, not representative.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 2 |
| $1–2k | 1,000 | 2,000 | 2 |
| $2–3k | 2,000 | 3,000 | 4 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 5 |
| $5–6k | 5,000 | 6,000 | 25 |
| $6–7k | 6,000 | 7,000 | 20 |
| $7–8k | 7,000 | 8,000 | 29 |
| $8–9k | 8,000 | 9,000 | 34 |
| $9–10k | 9,000 | 10,000 | 37 |
| $10–12k | 10,000 | 12,000 | 85 |
| $12–15k | 12,000 | 15,000 | 101 |
| $15–20k | 15,000 | 20,000 | 137 |
| $20k+ | 20,000 | — | 38 |
Which countries have the most open Solutions Architect jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 1,197 | 36.4% |
| United Kingdom | 382 | 11.6% |
| Poland | 282 | 8.6% |
| Germany | 205 | 6.2% |
| India | 178 | 5.4% |
| Canada | 121 | 3.7% |
| Singapore | 87 | 2.6% |
| France | 52 | 1.6% |
| Japan | 50 | 1.5% |
| Australia | 45 | 1.4% |
| Other countries | 690 | 21% |
The leader by Solutions Architect job count is the US (1197 positions). Poland — SA-friendly EU hub. Germany — enterprise + SAP ecosystem. International remote via EPAM-style outsourcing + tech-vendor Sales Engineering (Snowflake / Databricks / Confluent / MongoDB).
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 1,197 |
| GB | 382 |
| PL | 282 |
| DE | 205 |
| IN | 178 |
| CA | 121 |
| SG | 87 |
| FR | 52 |
| JP | 50 |
| AU | 45 |
Which technologies are most often required in the same job as Solutions Architect.
Used together with
Share — how many of the 3,919 jobs in the Solutions Architect market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Solutions Architect stack / skills 2026: cloud platforms deep, Solutions Architect certifications, Well-Architected Frameworks (AWS 6 pillars + Azure + GCP), architecture breadth (compute containers/serverless/VMs + Kubernetes managed K8s + databases relational/NoSQL/DWH + messaging + caching + networking), IaC (Terraform must + CloudFormation / Bicep), integration (enterprise integration patterns + API management Apigee/API Gateway + iPaaS MuleSoft/Boomi/Workato + event-driven + ETL), migration strategies (cloud migration 6 Rs + strangler fig + lift-and-shift trade-offs), cost / TCO (pricing calculators + TCO modelling + FinOps), solution documentation (SDD + cloud diagrams + C4 model + draw.io / Lucidchart), pre-sales skills (RFP/RFI responses + POC + demos + proposal writing + workshop facilitation), client-facing soft skills (requirements elicitation + stakeholder management + C-level presenting + business↔technical translation).
Common pairs: AWS + Terraform + Kubernetes + microservices (cloud-native solution stack), Azure + Bicep + AKS (Microsoft-ecosystem solution), AWS Well-Architected + Solutions Architect Professional cert (SA toolkit), cloud migration 6 Rs + strangler fig + Terraform (migration project stack), MuleSoft / Boomi + API Gateway + event-driven (integration solution stack), Yandex.Cloud + Terraform + Managed K8s (Russian cloud solution). Learning roadmap: become Senior Engineer (5+ years, prerequisite) → cloud platform mastery (AWS / Azure / GCP) → Solutions Architect cert (AWS SAA → SAP) → Well-Architected Framework → architecture breadth → system design practice → migration strategies (6 Rs) → cost / TCO modelling → integration patterns → solution documentation → pre-sales skills → client-facing soft skills.
Chart data
| Name | Count |
|---|---|
| solutions architect | 1,945 |
| cloud | 1,823 |
| aws | 1,076 |
| azure | 740 |
| python | 381 |
| gcp | 297 |
| databricks | 278 |
| kubernetes | 275 |
| sql | 274 |
| java | 266 |
| sap | 251 |
| salesforce | 196 |
How many Solutions Architect jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| principal | 1,405 |
| senior | 1,230 |
| lead | 228 |
| middle | 78 |
| junior | 18 |
Senior-tier role (lower grades = mis-titled; realistic benchmarks — Senior / Lead). Path: Senior Software Engineer (5+ years) → Solutions Architect (via solution design + client-facing skills + cloud certs) → Senior / Principal Solutions Architect → either Enterprise Architect, Chief Architect, cloud-provider Solutions Architect (pre-sales premium track), Pre-Sales Director, or CTO / VP at a startup.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| principal | 1,405 |
| senior | 1,230 |
| lead | 228 |
| middle | 78 |
| junior | 18 |
Who hires the most for Solutions Architect and how concentrated demand is among the largest companies.
Employers
Demand is spread across 1,882 employers. The largest accounts for 9.8%, the top ten for 18.7%; the remaining 81.3% is long tail.
| share | value |
|---|---|
| top-1 | 9.8% |
| top-3 | 14.1% |
| top-10 | 18.7% |
| long tail | 81.3% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Solutions Architect jobs from.
Where Zorky sees this market
Observed across 107 sources; the largest accounts for 16.2% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 2,648 | 0.6757 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 1,100 | 0.2807 |
| telegram | Telegram | Telegram | 168 | 0.0429 |
| community | сообщества и публичные профили | community & public profiles | 3 | 0.0008 |
The newest Solutions Architect jobs from company career sites.
Recent openings
- Solution Architect — Ташкент · UZ
- Solutions Architect - (69851) · CA
- Solution Architect · NG
- Senior Product Manager Solution Architecture · GB · $10,507
- Mobile Solutions Architect · PT · $2,880
- [Job - 32354] AI Solution Architect, Colombia · CO
- Senior AI Agentic Developer / Solution Architect · BG
- Salesforce Experience Architect, AI and Agentforce (Solution Architect) · CO
Latest open Solutions Architect jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
Solutions Architect overlaps with Software Architect (~50% — Solutions breadth+client-facing, Software depth+internal-design), Cloud Engineer (~40% — SA designs, Cloud Engineer implements), Sales Engineer (~60% for vendor-side SA), Enterprise Architect (org-level strategy), Cloud Architect / DevOps Cloud (cloud expertise overlap). Comparison with software/enterprise/data/security/integration — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Architecture
Related specializations
Inside Solutions Architect: Solutions Architect (general — end-to-end solution design), Senior / Principal Solutions Architect (complex multi-system solutions), Cloud Solutions Architect (AWS / GCP / Azure-specific — largest sub-segment 2026), Pre-Sales Solutions Architect / Sales Engineer (vendor-side — customer-facing technical sales + RFP + POC), Delivery Solutions Architect (focus on implementation phase), Technical Solutions Architect (alternative title). Comparison with software/enterprise/data/security/integration architect — in the bar below.
Frequently asked questions
Answers recompute automatically.
What does a Solutions Architect Junior, Middle, Senior, or Lead earn?
Solutions Architect is a senior-tier role ("Junior Solutions Architect" rarely exists; lower grades in the sample = mis-titled positions — for realistic benchmarks see Senior / Lead). Career flow: Senior Software Engineer (5+ years) → Solutions Architect (via demonstrated solution design + client-facing skills + cloud certifications) → Senior / Principal Solutions Architect → either Enterprise Architect (org-level strategy), Chief Architect / Head of Architecture, cloud-provider Solutions Architect, Pre-Sales Director, or CTO / VP Engineering at a startup. Solutions Architect — one of the highest-ceiling architect paths thanks to the cloud-provider pre-sales role (variable comp + commissions can significantly exceed base).
What stack / skills are most often required of a Solutions Architect?
Top stack / skills: solutions architect, cloud, aws, azure, agile. Well-Architected Frameworks: AWS Well-Architected (6 pillars — operational excellence + security + reliability + performance + cost + sustainability), Azure Well-Architected, GCP Architecture Framework — solution review methodology. Architecture breadth (SA — breadth over depth vs Software Architect): compute (VMs / containers / serverless trade-offs), Kubernetes + managed K8s (EKS / GKE / AKS), databases (relational / NoSQL / data warehouse — choice per use case), messaging (Kafka / SQS-SNS / Pub-Sub / Service Bus), caching (Redis / CDN), networking (VPC / load balancing / DNS / hybrid connectivity — Direct Connect / ExpressRoute). IaC: Terraform (must — multi-cloud) + cloud-native (CloudFormation / Bicep / Deployment Manager). Integration: enterprise integration patterns, API management (Apigee / AWS API Gateway / Azure API Management), iPaaS (MuleSoft / Dell Boomi / Workato), event-driven integration, ETL / ELT. Migration strategies: cloud migration 6 Rs (Rehost / Replatform / Refactor / Repurchase / Retire / Retain), strangler fig, lift-and-shift vs cloud-native trade-offs. Cost estimation / TCO: cloud pricing calculators, TCO modelling, FinOps awareness, cost-architecture trade-offs — critical part of solution proposal. Solution documentation: solution design documents (SDD), cloud architecture diagrams (AWS / Azure / GCP iconography standards), C4 model, draw.io / Lucidchart. Pre-sales skills (for vendor-side / outsourcing): RFP / RFI responses, POC development, solution demos, effort estimation, technical proposal writing, client workshop facilitation. Soft skills — critical: client-facing communication, requirements elicitation, stakeholder management, presenting to C-level, translating business ↔ technical. Engineering background: Solutions Architect must be ex-Senior Engineer — you can't design a solution without understanding implementation reality.
Solutions Architect vs Software Architect vs Cloud Engineer vs Sales Engineer — what's the difference?
Software Architect — deep design of one system's internal structure (components + patterns + code-level). Depth over breadth. See Software Architect. Solutions Architect (this page) — end-to-end solution for a business problem, composes from building blocks (often cloud services), breadth over depth, often client-facing. Cloud Engineer — hands-on cloud infrastructure provisioning + operations (implements what Solutions Architect designed). See Cloud Engineer. Sales Engineer / Pre-Sales Engineer — technical sales role, customer-facing, demos + RFP responses + POCs — overlap with vendor-side Solutions Architect (in cloud-provider context Pre-Sales Solutions Architect = Sales Engineer essentially). Two types of Solutions Architect: 1) Delivery-side SA (in companies / outsourcing — designs solutions for internal / client projects, leads to implementation). 2) Vendor-side / Pre-Sales SA (in cloud-providers / software vendors — customer-facing, helps prospective customers architect solutions using vendor's products — technical sales + variable comp + commissions). Career choice: Software Architect if you like deep technical system design + close to code, Solutions Architect (delivery) if you like breadth + project variety + cloud, Solutions Architect (pre-sales) if you like client-facing + technical sales + comfortable with variable comp (high ceiling), Cloud Engineer if hands-on implementation.
How does the Solutions Architect engagement lifecycle work (discovery → design → POC → delivery)?
Reference Solutions Architect engagement lifecycle 2026: 1) Discovery / Requirements gathering — workshops with business stakeholders + technical teams, understand business goals + constraints (budget / timeline / compliance / existing systems), elicit functional + non-functional requirements, identify success criteria. Solutions Architect asks the right questions — half the success here. 2) Current state assessment — analysis of existing architecture / systems (for migration / modernisation), technical debt, integration points, what to reuse / replace / retire. 3) Solution design — design target architecture: choice of cloud services + compute model (containers / serverless / VMs) + data stores + integration approach + networking + security. Apply Well-Architected Framework review (6 pillars). Solution design document (SDD) + architecture diagrams. 4) Cost estimation / TCO — estimate cloud costs (pricing calculators), TCO modelling, present cost-architecture trade-offs (cheaper vs more-scalable). Often several options with trade-offs for stakeholder decision. 5) Proposal / sign-off — present solution to stakeholders / C-level, defend trade-offs, get approval. For vendor-side SA — part of RFP response / sales process. 6) POC (Proof of Concept) — for risky / unproven parts — build minimal POC validating key assumptions (technology fit / performance / integration feasibility). De-risk before full commitment. 7) Implementation planning — break solution into phases / milestones, team structure + skills, risk register, dependency mapping. 8) Delivery oversight — Solutions Architect leads solution through implementation (especially Delivery SA role): design clarifications for dev teams, architecture governance, handle scope changes + blockers, adjust design to reality. 9) Migration execution (for migration projects) — apply 6 Rs strategy, incremental migration (strangler fig — not big-bang), validation + rollback planning. 10) Go-live + handover — production cutover, operational handover, documentation, post-implementation review. 11) Optimisation — post-launch Well-Architected review, cost optimisation (FinOps), performance tuning. Cross-cutting: stakeholder communication throughout, risk + scope management. Vendor-side SA difference: lifecycle shorter — focus on discovery + design + POC + proposal (help customer choose vendor's solution), implementation done by customer / SI.
What share of jobs are remote?
Among jobs with a stated work format, 39% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is cloud-provider (pre-sales) Solutions Architect different from delivery-side?
Delivery-side Solutions Architect — works in company / outsourcing / SI, designs solutions for internal or client projects + leads to implementation. Focus: complete engagement lifecycle (discovery → design → delivery oversight). Compensation: standard salary. Examples: EPAM Solution Architect on a client project, in-house Solutions Architect at a bank. Vendor-side / Pre-Sales Solutions Architect — customer-facing technical role in sales organisation. Focus: helping prospective customers architect solutions using vendor's products, technical credibility in sales process, POC demos, RFP responses, technical objection handling, customer workshops. Compensation: base salary + variable comp / commissions (part of compensation tied to region / team sales targets). AWS Solutions Architect (vendor-side) — one of the most famous pre-sales SA roles: helps AWS customers design on AWS, supports account teams. Skills difference: pre-sales SA needs stronger sales / communication / presentation skills + build trust quickly + handle objections + competitive positioning. Delivery SA needs stronger deep implementation knowledge + delivery management. Career paths: pre-sales SA → Principal SA → Pre-Sales Manager / Sales Engineering Director / Specialist SA (deep in one domain). Delivery SA → Principal / Chief Architect / Enterprise Architect / Delivery Director. Career choice: pre-sales if you like customer interaction + sales dynamics + variable comp upside + breadth; delivery if you like seeing solutions to production + deeper implementation involvement. Pre-sales SA at cloud-providers — one of the highest-comp architect paths.
Where to start the path to Solutions Architect in 2026?
Roadmap (Solutions Architect — senior-tier, path via Senior Engineer): 1) Become a strong Senior Engineer — prerequisite. Minimum 5+ years hands-on, experience shipping production systems, understanding of implementation reality. 2) Cloud platform mastery — choose one (AWS — default 2026 for breadth + cert recognition; Azure if Microsoft-ecosystem; GCP if data / ML focus). Hands-on experience build / deploy on cloud. 3) Cloud Solutions Architect certification — AWS Solutions Architect Associate (SAA-C03) → Professional (SAP-C02) (the most valuable architect cert in the industry). Or Azure AZ-305. Or Google Professional Cloud Architect. Resources: A Cloud Guru / Tutorials Dojo (practice exams) / cloud-provider official training. 4) Well-Architected Framework — study AWS Well-Architected (6 pillars) deeply — core SA methodology for solution review. 5) Architecture breadth — unlike Software Architect (depth), SA needs breadth: trade-offs of compute models (containers vs serverless vs VMs), database options, messaging, networking, integration. 6) System design practice — "System Design Interview" Alex Xu + practice designing solutions under different business scenarios. 7) Migration strategies — cloud migration 6 Rs, strangler fig pattern, lift-and-shift vs cloud-native trade-offs. AWS / Azure migration whitepapers. 8) Cost / TCO — cloud cost estimation (pricing calculators), TCO modelling, FinOps basics — cost is a critical part of solution proposal. 9) Integration patterns — "Enterprise Integration Patterns" Hohpe / Woolf, API management, iPaaS awareness. 10) Solution documentation — solution design documents, cloud architecture diagrams (AWS / Azure / GCP iconography), C4 model. 11) Pre-sales skills (if vendor-side track is of interest) — RFP response writing, POC development, presentation / demo skills, technical proposal writing. 12) Soft skills — critical for SA — client-facing communication, requirements elicitation, stakeholder management, presenting to C-level, translating business ↔ technical. Books: "Software Architect Elevator" Gregor Hohpe, "The Solutions Architect Handbook" Saurabh Shrivastava / Neelanjali Srivastav. 13) Practice in current role — proactively take solution-design tasks as Senior Engineer (propose architecture for new projects, participate in pre-sales / RFP, lead cloud migration). International (EN): AWS Skill Builder (free official) + A Cloud Guru + Tutorials Dojo (cert prep), "The Solutions Architect Handbook" Shrivastava / Srivastav (Packt — canonical SA book), AWS / Azure / GCP architecture whitepapers + reference architectures. Senior Engineer (5+ years) + cloud cert (AWS SAA / SAP) + demonstrated solution design → Solutions Architect.
How many open jobs are in this sample?
The published sample contains 3919 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior / Principal Solutions Architect need?
A Senior / Principal Solutions Architect owns the full solution design + client engagement + technical leadership cycle. Cloud platform mastery: one of AWS / Azure / GCP at Professional cert level (AWS SAP / Azure AZ-305 / GCP Professional Cloud Architect) + working knowledge of others for multi-cloud solutions. Well-Architected Framework mastery: AWS Well-Architected 6 pillars — apply review methodology to solutions. Architecture breadth: deep enough understanding of compute (containers / serverless / VMs trade-offs), databases (relational / NoSQL / data warehouse selection), messaging, caching, networking, integration patterns — breadth for composing complete solutions. Migration expertise: cloud migration 6 Rs methodology, legacy modernisation strategies, strangler fig pattern, lift-and-shift vs cloud-native trade-off analysis, incremental migration planning. IaC: Terraform mastery (multi-cloud) + cloud-native IaC awareness. Cost / TCO mastery: cloud cost estimation accuracy, TCO modelling, FinOps principles, presenting cost-architecture trade-offs to decision-makers (often several options with explicit trade-offs). Integration architecture: enterprise integration patterns, API management strategy, iPaaS, event-driven integration, hybrid connectivity. Solution documentation: clear solution design documents (SDD), cloud architecture diagrams (provider iconography standards), C4 model, decision rationale. Requirements engineering: elicit functional + non-functional requirements via stakeholder workshops, identify constraints + success criteria, ask the right discovery questions. POC development: scope + build proof-of-concepts to de-risk uncertain parts of solution. Pre-sales skills (for vendor-side / outsourcing): RFP / RFI response writing, effort estimation, technical proposal writing, solution demos, competitive positioning, technical objection handling, client workshop facilitation. Client-facing communication — critical: present to different audiences (engineers → C-level executives), build trust quickly, translate business ↔ technical fluently, manage stakeholder expectations, handle difficult conversations (budget / scope / timeline). Engineering credibility: Senior Engineer-level technical foundation (you can't design a solution without implementation understanding — anti-pattern "PowerPoint architect"). Domain expertise: deep knowledge of one-two industries (fintech / telecom / retail / healthcare) — main premium driver. Soft skills: stakeholder management, negotiation, influence without authority, facilitation, mentoring Junior architects. English for Senior+ ABSOLUTE MUST — Solutions Architect is the most communication-heavy architect role (client presentations + workshops + proposals + RFP responses in English in international context). Optional bonus: multiple cloud certifications (AWS + Azure + GCP), domain specialisation certs, conference speaking (AWS re:Invent / cloud conferences), published solution case studies — sharply increase market value for Principal SA / cloud-provider Solutions Architect / Chief Architect roles.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.