Skip to main content
PProfileMatch

59 open Solutions Architect jobs

Real, currently-open Solutions Architect roles synced directly from company career pages. Upload your resume to see which of these match your skills, or browse all open roles. New to the role? Read our Solutions Architect guide.

Hiring snapshot for Solutions Architect

The most common locations right now are Remote, United States (7), McLean, Virginia (4), United States (3). 19 of these 59 roles (32%) list a remote option. 46 were posted in the last two weeks. By team, the biggest groups are Engineering (59).

Computed from the 59 open listings shown below.

Guide: working as a Solutions Architect

Solutions architects design technical solutions that fit a specific customer or business unit, often bridging sales, engineering and the client. They gather requirements, propose architectures, build proofs of concept, explain trade-offs to executives and developers alike, and guide implementation so the agreed design holds up in production.

Core skills employers look for

  • Requirements gathering
  • Cloud and integration architecture
  • Proof-of-concept builds
  • Whiteboarding and diagrams
  • Presenting to mixed audiences
  • Cost and trade-off analysis
  • APIs, messaging and data flows
  • Security and compliance awareness

How to stand out when you apply

  • Keep a portfolio of architecture diagrams with short decision records explaining why you chose each component and which alternatives you rejected.
  • Show customer-facing experience: workshops you ran, technical questions you answered during a sale, or migrations you planned with a client's own engineers.
  • Build a working reference project, for example an event-driven order system using queues and a managed database, and document how it would scale and fail.
  • Practise explaining one design twice, once for a CTO focused on risk and cost and once for developers focused on APIs and deployment.

What the interviews usually cover

Most processes include a whiteboard architecture session built on a customer scenario, where you should ask clarifying questions before drawing anything. Many also include a presentation or mock customer meeting, deep dives on cloud services and integration patterns, and behavioural questions about handling objections or a deal where the technical fit was poor.

Prepare for free on ProfileMatch

Browse jobs by role

Browse jobs by company