Program Manager Interview Experience

• Recruiter screen
• Phone interview
• Final round

Interview tips

Prep for a Leadership-Principle marathon. AWS builds almost the whole loop around the LPs, so come in with 8–12 specific STAR stories with real metrics, and make sure they're flexible enough to map to more than one principle (you'll get overlapping questions across interviewers). Have a clear story for each of the big ones — Ownership, Dive Deep, Bias for Action, Deliver Results, Customer Obsession, and Earn Trust (they will ask about a mistake, a conflict, or a time you disagreed, so don't skip the "failure" stories). For this infrastructure delivery role specifically, be ready to walk the full delivery lifecycle out loud — receiving a facility, racking and cabling, configuration, turn-up testing, and clean handover to production — plus vendor coordination and a "a deployment went sideways, what did you do" story. Have your numbers ready (error rates, on-time delivery, risk reduction). What surprised me: how deep they dive on follow-ups — they don't accept the surface answer, they keep asking "why," "what data," "what would you do differently," so your stories need real depth, not just a headline. And the back-to-back loop is genuinely draining, so pace your energy and don't let the last interview get your weakest answers.

Company culture

It's a high-ownership, data-driven culture — the Leadership Principles aren't just interview props, you can feel them in how people talk. There's a strong bias for action and a real "dive deep" mentality, so decisions are expected to be backed by data and you're expected to own outcomes end to end, even outside your lane. For an infrastructure delivery team it's operationally intense and high-standards — 24/7 production reality, tight timelines, and a lot of cross-team and vendor coordination. [Optional if true: It's fast-paced and can feel high-pressure, but the flip side is a lot of autonomy and ownership if you like that.

Questions asked