Solutions Architect: рынок

Вакансия

открытая вакансия, прошедшая гейт качества и содержащая не менее двух технологий

Наблюдаемый кандидат

кандидат, чей стек содержит эту технологию; агрегат, без единой записи наружу

Подходящий кандидат

пока не считается

Окно

открытые вакансии на момент сборки снимка

Топ-стек / навыки: 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 (Solutions Architect — breadth over depth vs Software Architect): compute (VMs / containers / serverless trade-offs), Kubernetes + managed K8s (EKS / GKE / AKS), databases (relational / NoSQL / data warehouse — выбор под 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 modeling, FinOps awareness, cost-architecture trade-offs — критичная часть solution proposal. Solution documentation: solution design documents (SDD), cloud architecture diagrams (AWS / Azure / GCP iconography standards), C4 model, draw.io / Lucidchart. Pre-sales skills (для vendor-side / outsourcing): RFP / RFI responses, POC development, solution demos, effort estimation, technical proposal writing, client workshop facilitation. Soft skills — критичны: client-facing communication, requirements elicitation, stakeholder management, presenting к C-level, translating business ↔ technical. Engineering background: Solutions Architect должен быть ex-Senior Engineer — нельзя проектировать solution без понимания implementation reality.

Software Architect — deep design внутренней структуры одной системы (компоненты + паттерны + код-level). Depth over breadth. См. Software Architect. Solutions Architect (эта страница) — end-to-end решение под business problem, composes из building blocks (часто cloud services), breadth over depth, часто client-facing. Cloud Engineer — hands-on cloud infrastructure provisioning + operations (implements то, что Solutions Architect спроектировал). См. Cloud Engineer. Sales Engineer / Pre-Sales Engineer — technical sales role, customer-facing, demos + RFP responses + POCs — overlap с vendor-side Solutions Architect (в cloud-provider context Pre-Sales Solutions Architect = Sales Engineer essentially). Reality 2026 (overlap heatmap): Solutions Architect ↔ Software Architect: 50% (Solutions — breadth + client-facing + cloud-composition, Software — depth + internal system design). Solutions Architect ↔ Cloud Engineer: 40% (SA designs, Cloud Engineer implements). Solutions Architect ↔ Sales Engineer: 60% для vendor-side SA. Два типа Solutions Architect: 1) Delivery-side SA (в companies / outsourcing — проектирует solutions для internal / client projects, ведёт до implementation). 2) Vendor-side / Pre-Sales SA (в cloud-providers / software vendors — customer-facing, помогает prospective customers architect solutions using vendor's products — technical sales + variable comp + commissions). Career-выбор: Software Architect if нравится deep technical system design + close to code, Solutions Architect (delivery) if нравится breadth + variety проектов + cloud, Solutions Architect (pre-sales) if нравится client-facing + technical sales + готов к variable comp (высокий ceiling), Cloud Engineer if hands-on implementation.

Reference engagement lifecycle Solutions Architect 2026: 1) Discovery / Requirements gathering — workshops с business stakeholders + technical teams, понять business goals + constraints (budget / timeline / compliance / existing systems), elicit functional + non-functional requirements, identify success criteria. Solutions Architect задаёт правильные вопросы — половина успеха здесь. 2) Current state assessment — анализ existing architecture / systems (для migration / modernization), technical debt, integration points, что reuse / replace / retire. 3) Solution design — спроектировать target architecture: выбор 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 — оценить cloud costs (pricing calculators), TCO modeling, представить cost-architecture trade-offs (cheaper vs more-scalable). Часто несколько вариантов с trade-offs для stakeholder decision. 5) Proposal / sign-off — представить solution stakeholders / C-level, defend trade-offs, получить approval. Для vendor-side SA — часть RFP response / sales process. 6) POC (Proof of Concept) — для risky / unproven parts — build minimal POC validating key assumptions (technology fit / performance / integration feasibility). De-risk перед full commitment. 7) Implementation planning — разбить solution на phases / milestones, team structure + skills, risk register, dependency mapping. 8) Delivery oversight — Solutions Architect ведёт solution через implementation (особенно Delivery SA role): design clarifications для dev teams, architecture governance, handle scope changes + blockers, adjust design под реальность. 9) Migration execution (для migration projects) — apply 6 Rs strategy, incremental migration (strangler fig — не big-bang), validation + rollback planning. 10) Go-live + handover — production cutover, operational handover, documentation, post-implementation review. 11) Optimization — post-launch Well-Architected review, cost optimization (FinOps), performance tuning. Cross-cutting: stakeholder communication throughout, risk + scope management. Vendor-side SA difference: lifecycle короче — focus на discovery + design + POC + proposal (помочь customer выбрать vendor's solution), implementation делает customer / SI.

Да, 33% Solutions Architect-вакансий — full-remote или гибрид. Solution design + documentation + cloud work — remote-friendly. Аутсорсеры — почти всегда remote на US / EU projects. Российские продуктовые / банки — гибрид или remote после probation. Caveat для client-facing SA: Solutions Architect — client-facing роль, много meetings / workshops / presentations. Pre-sales Solutions Architects (cloud-provider / vendor-side) — традиционно travel-heavy (customer visits), но 2024–2026 много remote / virtual engagements. Гибрид часто optimal для SA (client workshops + design reviews on-site, design work remote). Международные cloud-provider Solutions Architects — гибрид-standard. SI (Accenture / Deloitte / Capgemini) — традиционно travel-heavy, но больше remote post-2020. Релокант-хабы: Польша / Германия (enterprise + SAP ecosystem) / Канада / Сербия / ОАЭ. Английский для international Solutions Architect-remote — критичен — SA это client-facing + communication-heavy роль (presentations + workshops + proposals на английском).

Delivery-side Solutions Architect — работает в company / outsourcing / SI, проектирует solutions для internal или client projects + ведёт до implementation. Focus: complete engagement lifecycle (discovery → design → delivery oversight). Compensation: standard salary. Примеры: EPAM Solution Architect на client project, in-house Solutions Architect в банке. Vendor-side / Pre-Sales Solutions Architect — customer-facing technical role в sales organization. Focus: помогать prospective customers architect solutions using vendor's products, technical credibility в sales process, POC demos, RFP responses, technical objection handling, customer workshops. Compensation: base salary + variable comp / commissions (часть compensation tied к sales targets региона / team). High performers могут зарабатывать значительно выше base (variable может быть 20-50%+ от total comp). AWS Solutions Architect (vendor-side) — одна из самых известных pre-sales SA ролей: помогает AWS customers design на AWS, supports account teams. Skills difference: pre-sales SA нужны сильнее sales / communication / presentation skills + build trust quickly + handle objections + competitive positioning. Delivery SA нужны сильнее deep implementation knowledge + delivery management. Career paths: pre-sales SA → Principal SA → Pre-Sales Manager / Sales Engineering Director / Specialist SA (deep в одном domain). Delivery SA → Principal / Chief Architect / Enterprise Architect / Delivery Director. Career-выбор: pre-sales if нравится customer interaction + sales dynamics + variable comp upside + breadth; delivery if нравится seeing solutions до production + deeper implementation involvement. Pre-sales SA в cloud-providers — один из highest-comp architect paths.

Roadmap (Solutions Architect — senior-tier, путь через Senior Engineer): 1) Стать сильным Senior Engineer — prerequisite. Минимум 5+ лет hands-on, опыт shipping production systems, понимание implementation reality. 2) Cloud platform mastery — выбрать один (AWS — default 2026 за широту + узнаваемость certs; Azure если Microsoft-ecosystem; GCP если data / ML focus). Hands-on опыт build / deploy на cloud. 3) Cloud Solutions Architect certification — AWS Solutions Architect Associate (SAA-C03) → Professional (SAP-C02) (самая ценная architect-cert индустрии). Или Azure AZ-305. Или Google Professional Cloud Architect. Resources: A Cloud Guru / Tutorials Dojo (practice exams) / cloud-provider official training. 4) Well-Architected Framework — изучить AWS Well-Architected (6 pillars) deeply — core методология SA для solution review. 5) Architecture breadth — в отличие от Software Architect (depth), SA нужна breadth: trade-offs compute models (containers vs serverless vs VMs), database options, messaging, networking, integration. 6) System design practice — «System Design Interview» Alex Xu + practice проектировать solutions под разные 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 modeling, FinOps basics — cost критичная часть 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 (если vendor-side track интересен) — RFP response writing, POC development, presentation / demo skills, technical proposal writing. 12) Soft skills — критичны для SA — client-facing communication, requirements elicitation, stakeholder management, presenting к C-level, translating business ↔ technical. Книги: «Software Architect Elevator» Gregor Hohpe, «The Solutions Architect Handbook» Saurabh Shrivastava / Neelanjali Srivastav. 13) Practice в текущей роли — proactively брать solution-design задачи как Senior Engineer (предлагать architecture для new projects, участвовать в pre-sales / RFP, вести cloud migration). International (eng): 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+ лет) + cloud cert (AWS SAA / SAP) + demonstrated solution design → Solutions Architect.

3766 активных открытых Solutions Architect-вакансий — самая ёмкая architect-субниша (широкая роль, много спроса в outsourcing + cloud-providers + enterprises). География: 🇷🇺 Россия / 🇵🇱 Польша / remote. Реальный рынок шире за счёт международного remote-сегмента (EPAM-style outsourcing Solutions Architects + tech-vendor Sales / Solutions Engineering — full-remote-friendly). Время закрытия Senior Solutions Architect — 6-14 недель (seniority + client-facing skills assessment + cloud certifications verification).

Senior / Principal Solutions Architect владеет полным циклом solution design + client engagement + technical leadership. Cloud platform mastery: один из AWS / Azure / GCP на Professional cert level (AWS SAP / Azure AZ-305 / GCP Professional Cloud Architect) + working knowledge других для multi-cloud solutions. Well-Architected Framework mastery: AWS Well-Architected 6 pillars — apply review methodology к solutions. Architecture breadth: deep enough understanding compute (containers / serverless / VMs trade-offs), databases (relational / NoSQL / data warehouse selection), messaging, caching, networking, integration patterns — breadth для composing complete solutions. Migration expertise: cloud migration 6 Rs methodology, legacy modernization 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 modeling, FinOps principles, presenting cost-architecture trade-offs к decision-makers (часто несколько options с 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 через stakeholder workshops, identify constraints + success criteria, ask the right discovery questions. POC development: scope + build proof-of-concepts to de-risk uncertain parts solution. Pre-sales skills (для 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 — критично: present к разным аудиториям (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 (нельзя проектировать solution без implementation understanding — anti-pattern «PowerPoint architect»). Domain expertise: deep knowledge одного-двух industries (fintech / telecom / retail / healthcare) — главный premium-driver. Soft skills: stakeholder management, negotiation, influence without authority, facilitation, mentoring Junior architects. Английский для Senior+ ABSOLUTE MUST — Solutions Architect — самая communication-heavy architect-роль (client presentations + workshops + proposals + RFP responses на английском в international context). Optional bonus: multiple cloud certifications (AWS + Azure + GCP), domain specialization certs, conference speaking (AWS re:Invent / cloud conferences), published solution case studies — резко повышают market value для Principal SA / cloud-provider Solutions Architect / Chief Architect roles.