Candidates describe Amgen Engineering Manager interviews as centered on management experience and project deep dives, with STAR behavioral stories and scenario-based DevOps and data platform discussion in one report. Communication gaps between stages are a recurring complaint.
$140K
Avg. Base Comp
$185K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Amgen Engineering Manager interviews, as candidates describe them, lean on management and project-leadership experience. One candidate was asked to open with a self-introduction and then spent most of the time on one difficult project, with follow-up questions probing that same story. Reports of a panel conversation likewise centered on management style, how the candidate leads projects and whether they had led work in the field. So prepare one project you can defend through several layers of follow-up, and a short introduction that ties your background to leading engineers.
The technical weight may depend on the team. One candidate for a data platform and cloud engineering group reported scenario questions on CI/CD pipelines, Terraform-based deployment strategy and observability. Some turned into system design discussions that touched DevOps, SRE and data engineering. Behavioral questions in that process were expected in STAR format and covered leading a project, getting a team through difficult challenges and working with a cross-functional team.
The reports also describe a slow, unclear process. Candidates mention rescheduled interviews, little feedback after a later round and having to chase for updates. One candidate who reached an offer stage described an HR session on benefits and stock options. Ask early how many rounds remain and who decides, and follow up in writing.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Amgen process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Amgen
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Greatest Common Denominator | |
| Ranking Metrics | |
| Client Solution Pushback | |
| Sum to Zero | |
| Flatten JSON | |
| Valid Anagram | |
| Digit Accumulator | |
| Rider Discount | |
| Search Linked List | |
| Merchant Dashboard Design | |
| Common Prefix | |
| Moving Window | |
| K Nearest Entries | |
| Possible Triangles | |
| Concurrent LLM Serving | |
| String Palindromes | |
| Three Indexes Adding Zero | |
| Uber Eats Customer Experience | |
| Marketing Workflow Optimization | |
| Vision Setting and Execution Strategy | |
| Why Do You Want to Work With Us | |
| Distributed Authentication Model | |
| Boosting Instagram Stories | |
| Stakeholder Communication | |
| Azure Kubernetes Infrastructure | |
| Simple Explanations | |
| Account Personalization Strategy | |
| Maximal Substring |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or internal screen before the main interviews. One candidate said months passed between the first phone screen and the panel, and that the interview was rescheduled several times. Timing likely varies by team, so ask for a written schedule.
Candidates report a heavy focus on management background and leadership style. One was asked to introduce themselves and then walk through a difficult project in detail, with related follow-ups on the same project. Another described a panel centered on whether they had led projects. Prepare one project story that holds up under probing.
For a data platform and cloud engineering group, one candidate reported scenario questions on CI/CD pipelines, Terraform deployment strategy and observability. Some turned into system design discussions touching DevOps, SRE and data engineering. Other teams may weigh technical depth differently, so confirm the expected scope with the recruiter.
One candidate was asked to describe leading a project, how the team handled difficult challenges and how they collaborated with a cross-functional team. Answers were expected in STAR format with measurable results. Prepare a few specific stories about your own teams rather than general principles.
Outcomes in the reports were mixed. One candidate reached an HR session on benefits, an on-site tour and a compensation conversation including stock options, then declined the offer. Others received no offer or little feedback after later rounds and had to follow up themselves. Expect to chase for updates.
