One reported Amgen software engineering process moved from a phone screen to a hiring-manager interview, panel, and on-site visit, with basic technical questions and a role-scope mismatch emerging later.
$128K
Avg. Base Comp
$150K
Avg. Total Comp
4 rounds
Typical Rounds
2-4 weeks
Process Length
For an Amgen Software Engineer interview, one candidate reported a four-stage sequence: an urgent phone screen after applying online, a hiring-manager conversation, a team panel, and a final on-site visit that included a facility tour. The first screen focused on basic questions and fit, while the candidate characterized the technical portion overall as not especially difficult.
The most concrete question to prepare is behavioral: describe a time you disagreed with management. Have a specific example that shows professional judgment, how you communicated the disagreement, and what happened next. The same candidate’s main frustration was role clarity: the opening initially appeared frontend-focused, but only after the third interview did full-stack expectations emerge. Ask early how the team defines the role, the expected frontend versus full-stack balance, and what success looks like.
This guide reflects one candidate report, so timing and technical depth may vary.
Synthesized from 1 candidate report 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.
My interview process was straightforward on the surface—phone screening followed by an on-site with multiple senior interviewers. During the phone call, they asked me to introduce myself and give an overview of my background. The on-site was where the real focus emerged, though it started with broad behavioral questions about my strengths and weaknesses. From there, the conversation quickly shifted into embedded systems fundamentals.
What I remember most is the depth they wanted on low-level understanding. They explored interrupt handling, memory constraints, timing behavior under load, concurrency and synchronization strategies. They pressed me on my approach to debugging hardware-software issues—how I use logs, oscilloscopes, breakpoints when things go wrong. We spent significant time on peripheral interfacing and communication protocols: UART, SPI, I²C, CAN. It wasn't academic; they wanted to know how I'd actually dealt with these in past projects and what drove my architectural decisions—when I chose abstraction over performance and when I didn't.
The on-site also touched on working across teams—how I'd collaborated with hardware engineers, mechanical folks, QA—and how I'd handled disagreements about complexity or timeline. But ultimately, I didn't move forward. I never heard back after the on-site, which left me guessing about where I'd fallen short.
Prep tip from this candidate
Prepare deep technical discussions on interrupt handling, RTOS, concurrency, and protocols (UART, SPI, I²C, CAN), with concrete examples from past embedded work showing how you balance abstraction against performance and approach hardware-software debugging.
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 | |
|---|---|
| 2nd Highest Salary | |
| Monthly Customer Report | |
| Weighted Keys | |
| Hurdles In Data Projects | |
| Cumulative Distribution | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| P-value to a Layman | |
| Detecting ECG Tachycardia Runs | |
| Last Transaction | |
| Size of Joins | |
| Brain Cancer Treatment Outcomes | |
| Always Excited Users | |
| Sum to Zero | |
| Flatten JSON | |
| Valid Anagram | |
| Cumulative Reset | |
| Rider Discount | |
| Digit Accumulator | |
| 85% vs 82% | |
| Multi-Reaction | |
| Search Linked List | |
| Time Difference | |
| Common Prefix | |
| Greatest Common Denominator | |
| Count Transactions | |
| Subscription Retention | |
| Possible Triangles | |
| Moving Window |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported being scheduled a few days after applying for an urgent phone interview. They described this first screen as straightforward, with basic questions and an initial fit check.
The candidate next reported a hiring-manager interview. Because the eventual role scope felt unclear, candidates may use this conversation to confirm whether the work is frontend, full stack, or another engineering focus.
One report placed a panel interview after the hiring-manager conversation. The memorable behavioral prompt asked about disagreeing with management, so prepare a concrete, professionally handled example.
The candidate reported a final on-site round that included a facility tour. They characterized the technical side of the process as not especially hard, while noting that expectations may need clarification.
