Program Manager applicants have rated the interview process at Amazon Web Services with 3.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 57.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Program Manager roles take an average of 35 days to get hired, when considering 36 user submitted interviews for this role. To compare, the hiring process at Amazon Web Services overall takes an average of 35 days.
Common stages of the interview process at Amazon Web Services as a Program Manager according to 36 Glassdoor interviews include:
Phone interview: 25%
One on one interview: 21%
Skills test: 20%
Background check: 13%
Personality test: 8%
Group panel interview: 8%
IQ intelligence test: 2%
Other: 1%
Presentation: 1%
Here are the most commonly searched roles for interview reports -
I interviewed at Amazon Web Services (London, England)
Interview
they follow the STAR method & add numbers to every scenario choose a recent scenario & dont repeat situation within the interview. The key is aboyt clarifying all possible questions
I interviewed at Amazon Web Services (Munich, Bavaria)
Interview
Typical Amazon blend of leadership principles and technical questions. Panel interview. Short and relatively awkward if you’re not used to the questions. Lots of digging deeper on the stories. Need to prepare the stories in detail in advance.
The interview was conversational and focused on both behavioral and situational questions. The interviewer asked about my background, project experiences, and how I approach problem-solving in team environments. They were particularly interested in how I handle ambiguity, manage multiple deadlines, and communicate technical concepts to non-technical clients.
On the technical and consulting side, they asked about my familiarity with digital transformation, ERP systems, and how I would approach implementing technology solutions for business problems. They also explored my motivation for joining PwC, my understanding of what differentiates technology consulting from management consulting, and how I see my skills contributing to long-term client impact.
Interview questions [1]
Question 1
The interview was conversational and focused on both behavioral and situational questions. The interviewer asked about my background, project experiences, and how I approach problem-solving in team environments. They were particularly interested in how I handle ambiguity, manage multiple deadlines, and communicate technical concepts to non-technical clients.
On the technical and consulting side, they asked about my familiarity with digital transformation, ERP systems, and how I would approach implementing technology solutions for business problems. They also explored my motivation for joining PwC, my understanding of what differentiates technology consulting from management consulting, and how I see my skills contributing to long-term client impact.