Amgen logo
AmgenSoftware Engineer
Updated Jul 30, 2026

Amgen Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Amgen, newest first and distilled into what to expect across the loop.

Get your personalized Amgen Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
1 month ago
Average Positive Cambridge, MA

My process started with a recruiter phone screen where they asked questions tied to my current work and some background from earlier roles. It didn’t feel overly technical—more like they were trying to understand my experience and how I’d fit the role.

After that, about a week later, I had a call with the hiring manager. That round felt like a mix of a “vibe check” and targeted technical questions. The technical part leaned toward clarifying concepts rather than deep problem-solving.
2 months ago
Average Neutral India

The whole process felt unusually well organized. From the beginning, the recruiter team shared clear timelines and kept communication transparent, which made it feel professional and predictable.

My first round was virtual and focused on a deep-dive technical assessment. It tested core competencies, problem-solving, and how I handled real-world scenarios, blending theory with practical thinking.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Recruiter Interaction

The initial recruiter interaction sets the tone for the entire process, with candidates noting variability in communication quality and clarity. A well-informed recruiter can lead to a smoother experience, while a distant one may create confusion and frustration.

Recruiter qualityCommunicationInitial contact

Technical Assessments

Candidates typically face a technical assessment early in the process, often focusing on specific programming languages and practical problem-solving. Expect questions that require detailed implementation knowledge rather than just theoretical understanding.

Technical screenCoding questionsJavaScript

Behavioral and Cultural Fit

Subsequent interviews often emphasize behavioral and cultural fit, assessing leadership qualities and team collaboration. Candidates should prepare to discuss their work style and how they handle conflict and teamwork scenarios.

Behavioral questionsCultural fitLeadership

Interview Structure and Flow

The interview process generally follows a structured format, starting with a phone screen, followed by technical and behavioral rounds, often culminating in a panel interview. However, some candidates noted that the number of rounds felt excessive or repetitive.

Interview structurePanel interviewProcess flow

Feedback and Follow-Up

Many candidates expressed frustration over a lack of timely feedback after interviews, with some experiencing ghosting or long delays in communication. It's advisable to follow up proactively if you don't hear back within the expected timeline.

FeedbackFollow-upCommunication delays

Expectations and Role Clarity

Some candidates reported inconsistencies in role expectations, such as shifts in job requirements from frontend to full stack. Clarifying the role and expectations early in the process can help avoid wasted time and misalignment.

Role clarityJob expectationsAlignment