When people hear “Solutions Architect at AWS,” they often picture someone hunched over a whiteboard drawing boxes and arrows all day. There’s some truth to that, but the reality is far more varied, more human, and honestly more interesting than the job title suggests. After 4 years in this role, I’ve come to see it less as “the person who designs cloud architectures” and more as a translator, a coach, and a trusted advisor who happens to speak fluent cloud.
In this article, I’ll walk you through what the Solutions Architect role at AWS actually looks like.
1. The Majority of Time Is With Customers
The single biggest thing to understand is that most of my time is spent with customers. Not designing in isolation, but in the room (or on the call) with the people who actually run the business. That means nurturing relationships across the whole spectrum: earning the trust of C-level executives who care about outcomes, cost, and risk, and building deep credibility with the technical teams who will live with whatever we design.
A lot of that work is deceptively simple: asking the right questions. It’s tempting, especially early on, to hear “we want to build a data lake” and immediately start sketching S3 buckets and Glue jobs. But the good SAs slow down and ask why. What business outcome are they chasing? What does success look like in six months? What’s the team’s actual skill level? Everything a Solutions Architect does starts and ends with the customer’s problem. AWS has this deeply ingrained principle of “working backwards” from the customer, and as an SA you live it every single day.
From there, the days fill up with the fun stuff: sketching architectures on the whiteboard, putting together demos, spinning up proofs of concept to de-risk a big decision, and running workshops to level up a customer’s team. One morning I might be helping a fintech startup process payments at scale without falling over on Black Friday; that same afternoon I could be walking a CTO through a multi-year migration strategy. No two days look the same.
Travel is a real part of the mix, too. Meeting customers where they are has taken me to London, Munich, Berlin, Barcelona, Amsterdam, Latvia, Las Vegas, Seattle, and plenty of places in between. There’s a lot you can accomplish over a video call, but nothing replaces sitting across a table from a team, sketching on their whiteboard, and building the kind of trust that only happens face to face.
