Amgen Software Engineer interview typically runs 4 rounds: phone screen, hiring manager interview, panel interview, on-site. It usually takes a few days to weeks and can be drawn out with unclear role expectations.
$104K
Avg. Base Comp
$172K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Amgen is less about trick questions and more about whether you can operate professionally in a setting where the business context matters. The standout behavioral prompt we saw was a disagreement-with-management scenario, which tells us they’re listening for judgment, diplomacy, and the ability to push back without creating friction. In a company built around regulated, high-stakes work, that kind of response seems to carry more weight than polished buzzwords.
A recurring theme is that the technical bar itself wasn’t the hardest part; the harder part was figuring out what the team actually needed. One candidate described the role as seeming frontend-focused until late in the process, when it shifted to full stack. That mismatch is a real signal: Amgen appears to value candidates who can stay composed while the scope evolves, but the process can feel frustrating if you need crisp expectations to showcase your strengths. We’ve seen that clarity of fit becomes a deciding factor here, not just technical ability.
The other pattern worth noting is the company’s pace and communication style. Multiple candidates described the experience as drawn out and, in one case, ending without a clear close. That means candidates who do best here are usually the ones who can connect their work to practical outcomes, ask precise questions about the team’s needs, and show they can handle ambiguity without losing momentum.
Synthetized from 1 candidates 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.
I applied online for a software engineer role and, after a few days, got scheduled for what they called an urgent phone interview. That first screen was pretty straightforward, mostly basic questions and an initial check on fit. After that, I moved on to a hiring manager interview and then a panel interview with the team. The process felt multi-stage and a bit drawn out, and the final round was on site, where they also gave me a tour of the facility.
The main behavioral question I remember was about a time I disagreed with management, so I’d definitely be ready with a concrete example that shows judgment and how you handled the situation professionally. The technical side wasn’t especially hard, but the bigger issue was that the requirements seemed unclear. At first it felt like they were looking for a frontend developer, and only after the third interview did it come up that they actually wanted a full stack developer. That mismatch made the process frustrating, especially since I was ghosted afterward instead of getting a clear rejection. Overall, the interviews themselves were not too difficult, but the lack of clarity around the role was the biggest takeaway for me.
Prep tip from this candidate
Be ready for a behavioral question about disagreeing with management, and make sure you clarify early whether the role is frontend, full stack, or something else. The process included a phone screen, hiring manager interview, panel, and an on-site tour, so prepare for multiple rounds even if the technical questions stay basic.
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 | |
| Hurdles In Data Projects | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Last Transaction | |
| Size of Joins | |
| Brain Cancer Treatment Outcomes | |
| Always Excited Users | |
| Total Spent on Products | |
| Sum to Zero | |
| Flatten JSON | |
| Valid Anagram | |
| Cumulative Reset | |
| Rider Discount | |
| Digit Accumulator | |
| Search Linked List | |
| Time Difference | |
| Impute Median | |
| Common Prefix | |
| Greatest Common Denominator | |
| Count Transactions | |
| Subscription Retention | |
| Possible Triangles | |
| Concurrent LLM Serving | |
| String Palindromes | |
| DDoS Attack Response | |
| Mapping Nicknames | |
| Moving Window |
Synthesized from candidate reports. Individual experiences may vary.
The candidate applied online and heard back within a few days. The company then scheduled an urgent phone interview, suggesting a relatively quick initial screening after application.
This first interview was described as straightforward and focused on basic questions and an initial fit check. It served as an early screen before moving candidates into the later stages.
The next step was a conversation with the hiring manager. The interview included behavioral discussion, including a question about a time the candidate disagreed with management, and likely covered role expectations.
The candidate then met with a panel from the team. The technical portion was not especially difficult, but the role requirements were still unclear at this stage, with the team only later clarifying that they wanted a full stack developer.
The final round was conducted on site and included a tour of the facility. This appears to have been the last stage before a decision, though the candidate reported being ghosted afterward rather than receiving a clear rejection.