Depends if aws stays up during your interview ha. Sorry couldn’t resist

More on reddit.com

Try to turn your solution into a narrative with a good storyline that captures attention. Don’t leave out the technical key points but also don’t spend slide after slide poring over data or lines of code. Situation, problem statement, what you specifically did to create the solution and help the customer, and what the positive results were for them (hard data if you have it). You want to show that you speak with knowledge and authority but you also need to show that you can explain something without overcomplicating it or losing attention. Highlight anything you did to go above and beyond (customer obsession and earning trust). Try to be upbeat and conversational, handle any tough questions with as much humility and grace as you can. More on reddit.com

Working at AWS as a Solutions Architect is more of a pre-sales type of role where you are hosting workshops, showing decks, passing on best practises, drafting high level architectures, doing small POCs, and interacting with the customer. So in other words, it's not really a hardcore hands-on position where you are cranking code all day long. But SA roles at APN partners are normally more about delivery, so you will spend most of your time writing CloudFormation/Terraform, Python, Ansible, etc. If you are interested in this kind of role at AWS, then you should be looking at Professional Services.

More on reddit.com

I'm an engineer at Amazon and have done numerous tech interviews for both the e-commerce and AWS side of Amazon. I can't speak for aws architect roles, but I can shed some lights on LP questions. Your behavior question matters. It'll be indirect, some interviewers will ask prepared questions such as "tell me about a time when you disagree with your manager" others might be more creative and bake them into discussions. Your response will be heavily dissected by a group of manages and engineers either right after the interview or the day later, we will share what you told us, cross reference for consistency, discuss various points for LP and technical strength and weaknesses. It all boils down to "is this candidate better/equals/below the current average Amazon engineer?" Aka "raise/meets/lowers" the bar for each LP. We're expected to see some "meets" but mostly "raises" for the ideal candidate. If it's meets across the board you won't get the offer. The idea is to consistently hire someone that's better than the average employee at Amazon. Also we almost never give the benefit of the doubt. It's on you to study and be prepared. So make sure you answer in such a way that clearly highlights your LP and technical field. It may be worthwhile to practice a bit. More on reddit.com