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.
2. Depth and Breadth at the Same Time
AWS has over 200 services, and customers expect you to have a working knowledge across most of them. You’ll never be an expert in all of them and nobody is. But you develop a strong mental map of what each service does and when to reach for it.
The trick is knowing how to go deep quickly, and you don’t have to do it alone. Beyond the broad generalist role, you have the option to specialize through a Technical Field Community (TFC). I’ve been part of the Serverless TFC for many years, and it’s shaped my whole career. It’s how you turn broad awareness into genuine, hard-earned depth in a domain you’re passionate about, surrounded by peers who obsess over the same problems.
Going deep with a TFC also opens doors to create things that outlive any single customer engagement. Over the years, that depth in Serverless has given me the opportunity to build content the whole community can use, like the Java on Lambda workshop and blog posts such as AWS Lambda now supports Java 25.
It’s also taken me on the road as a speaker. I’ve had the chance to present at AWS Summits in Warsaw, Amsterdam, and Berlin, and to be part of AWS re:Invent three years running. There’s nothing quite like standing in front of a room of builders, sharing something you learned the hard way, and then having someone come up afterward to tell you it unblocked them.
3. The Work Beyond the Day Job
And it doesn’t stop at technical content. The role gives you room to get involved in programs that matter to you personally. I’ve joined initiatives like the AWS Get IT program, which introduces students to careers in tech, and AWS SheBuilds, which supports women building on AWS. I also help organize the AWS User Group and Community Day in Greece, bringing our local cloud community together to learn from one another. These aren’t side quests; they’re some of the most meaningful work I do.
Is It For You?
If you love technology but get energized by people and problems more than by code alone, being a Solutions Architect at AWS might be one of the best jobs out there. It rewards curiosity, communication, and a genuine desire to help others succeed.
It’s demanding, the context switching is real, and the pace can be relentless, but it’s rarely boring. And at the end of a good week, you’ve helped a customer build something that genuinely moves their business forward. That’s a pretty great way to spend your days.