cswork / libraryOpen practice workspace

Interview guides · Amgen

Amgen Software Engineer Interview Guide

Amgen Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Amgen, you play a direct role in driving digital innovation across one of the world's leading biotechnology companies. Amgen leverages advanced software engineering, cloud computing, data science, and embedded systems to pioneer treatments in therapeutic areas including Oncology, Inflammation, General Medicine, and Rare Disease. Your technical work sits at the critical intersection of software development and life science innovation, empowering research scientists, streamlining manufacturing operations, and enhancing global commercial platforms. The modern software landscape at Amgen spans diverse technical domains.

This guide is scoped to a Software Engineer candidate at Amgen.

Focus areas

  • JavaScript
  • React
  • System Design

The Amgen interview process

Amgen candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Screening Call

Initial call with a recruiter to assess candidate fit and discuss the role.

What to demonstrate

  • Initial call with a recruiter to assess candidate fit and discuss the role
  • Depth in JavaScript

How to prepare

  • Be able to walk your CV end to end in two minutes, and say why this company specifically.
  • Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.

Technical Evaluation

Candidates undergo either an online coding assessment or a 1:1 technical interview.

What to demonstrate

  • Candidates undergo either an online coding assessment or a 1:1 technical interview
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: "What strategies do you use to manage state and asynchronous API requests cleanly in single-page applications?"
  • Answer aloud and timed: "How do you optimize frontend bundle sizes and web performance for enterprise application dashboards?"

Comprehensive Panel Interviews

Candidates participate in individual 1-on-1 interviews or group panel discussions with team members and directors.

What to demonstrate

  • Candidates participate in individual 1-on-1 interviews or group panel discussions with team members and directors
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: "Walk through how you handle form validation and error handling across distributed frontend forms."
  • Answer aloud and timed: "How would you design an enterprise book borrowing and tracking system from the ground up?"

Onsite Presentation

In specialized roles, candidates may present past technical projects to the evaluation team.

What to demonstrate

  • In specialized roles, candidates may present past technical projects to the evaluation team
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: "Describe how you would structure a microservices deployment on AWS using container technology and API gateways."
  • Answer aloud and timed: "How do you decide between SQL and NoSQL databases when designing data persistence layers for high-throughput applications?"

Where candidates lose points

Master the STAR Method for Behavioral Questions

Structure your behavioral answers using Situation, Task, Action, and Result. Ensure your narrative clearly highlights your individual technical contribution and personal ownership in every project scenario.

Prepare to Deep-Dive Into Your Resume

Expect interviewers to ask detailed questions about projects listed on your resume. Be ready to explain the system architecture, hardware/software tradeoffs, and business outcomes of your past work.

Be prepared to walk through past projects in technical detail

Panel members at Amgen frequently ask candidates to white-board prior system architectures, discuss data modeling trade-offs, or explain debugging choices.

Clarify Role Expectations and Leveling Early

Because software engineering titles at Amgen span digital cloud, data analytics, and operational technology, confirm the specific team scope, expectations, and compensation benchmark during your initial recruiter discussion.

Questions & practice

"How do you use the array reduce function in JavaScript to manipulate complex data structures?"

Medium · Full-Stack & Frontend Development

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

"How do interrupt handling, timing constraints, and synchronization primitives work within a Real-Time Operati

Medium · Low-Level & Embedded Systems

"How do interrupt handling, timing constraints, and synchronization primitives work within a Real-Time Operating System (RTOS)?"

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

"How do you approach firmware abstraction without sacrificing critical system execution performance?"

Medium · Low-Level & Embedded Systems

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

"Explain the operational differences between communication protocols such as UART, SPI, I2C, and CAN bus."

Medium · Low-Level & Embedded Systems

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

"How do you manage severe memory constraints and timing delays when writing firmware for specialized hardware

Medium · Low-Level & Embedded Systems

"How do you manage severe memory constraints and timing delays when writing firmware for specialized hardware devices?"

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Write the update path that detects a concurrent edit

Medium · optimistic concurrency · transactional outbox · audit history

resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.

Approach

  1. One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
  2. Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
  3. State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
  4. Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.

Follow-up

  • A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
  • Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?

Replace offset paging on the resource feed with keyset

Easy · keyset pagination · composite index · sort order

resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.

Approach

  1. Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
  2. Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
  3. Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
  4. Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.

Follow-up

  • The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
  • Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?

"How would you design and implement a reusable client-side pagination component in React?"

Medium · Full-Stack & Frontend Development

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"What strategies do you use to manage state and asynchronous API requests cleanly in single-page applications?

Medium · Full-Stack & Frontend Development

"What strategies do you use to manage state and asynchronous API requests cleanly in single-page applications?"

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

"How do you optimize frontend bundle sizes and web performance for enterprise application dashboards?"

Medium · Full-Stack & Frontend Development

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

"Walk through how you handle form validation and error handling across distributed frontend forms."

Medium · Full-Stack & Frontend Development

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"How would you design an enterprise book borrowing and tracking system from the ground up?"

Medium · System Design & Cloud Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"Describe how you would structure a microservices deployment on AWS using container technology and API gateway

Medium · System Design & Cloud Architecture

"Describe how you would structure a microservices deployment on AWS using container technology and API gateways."

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"How do you decide between SQL and NoSQL databases when designing data persistence layers for high-throughput

Medium · System Design & Cloud Architecture

"How do you decide between SQL and NoSQL databases when designing data persistence layers for high-throughput applications?"

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"What approaches would you take to integrate Large Language Models (LLMs) and vector databases into an enterpr

Medium · System Design & Cloud Architecture

"What approaches would you take to integrate Large Language Models (LLMs) and vector databases into an enterprise software workflow?"

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

"How do you ensure zero-downtime deployments and design reliable CI/CD pipelines for production applications?"

Medium · System Design & Cloud Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"Describe a past project where you took full technical ownership from architectural design to production deliv

Medium · Behavioral & Cross-Functional Leadership

"Describe a past project where you took full technical ownership from architectural design to production delivery."

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

"Walk us through your step-by-step diagnostic process when using oscilloscopes and logic analyzers to debug in

Medium · Low-Level & Embedded Systems

"Walk us through your step-by-step diagnostic process when using oscilloscopes and logic analyzers to debug intermittent hardware/software issues."

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics Amgen candidates report.

Day 1 — Map the Amgen loop

  • Write out the reported sequence: Recruiter Screening Call, Technical Evaluation, Comprehensive Panel Interviews, Onsite Presentation.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

Day 2 — Work JavaScript

  • Spend the session on JavaScript, which Amgen candidates report being tested on.
  • Write one worked example in JavaScript and time yourself on it.

Deliverable: One timed worked example in JavaScript.

Day 3 — Work React

  • Spend the session on React, which Amgen candidates report being tested on.
  • Write one worked example in React and time yourself on it.

Deliverable: One timed worked example in React.

Day 4 — Work System Design

  • Spend the session on System Design, which Amgen candidates report being tested on.
  • Write one worked example in System Design and time yourself on it.

Deliverable: One timed worked example in System Design.

Day 5 — Answer out loud: Full-Stack & Frontend Development

  • Answer aloud, timed: "How do you use the array reduce function in JavaScript to manipulate complex data structures?"
  • Answer aloud, timed: "How would you design and implement a reusable client-side pagination component in React?"

Deliverable: Spoken answers to 2 reported Full-Stack & Frontend Development question(s), under time.

Day 6 — Answer out loud: System Design & Cloud Architecture

  • Answer aloud, timed: "How would you design an enterprise book borrowing and tracking system from the ground up?"
  • Answer aloud, timed: "Describe how you would structure a microservices deployment on AWS using container technology and API gateways."

Deliverable: Spoken answers to 2 reported System Design & Cloud Architecture question(s), under time.

Day 7 — Answer out loud: Low-Level & Embedded Systems

  • Answer aloud, timed: "How do interrupt handling, timing constraints, and synchronization primitives work within a Real-Time Operating System (RTOS)?"
  • Answer aloud, timed: "How do you approach firmware abstraction without sacrificing critical system execution performance?"

Deliverable: Spoken answers to 2 reported Low-Level & Embedded Systems question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

"Describe a situation where you had to manage heavy workloads and competing technical priorities under tight d

Medium · Behavioral & Cross-Functional Leadership

"Describe a situation where you had to manage heavy workloads and competing technical priorities under tight deadlines."

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

"How do you handle technical disagreements when working in cross-discipline teams with non-software profession

Medium · Behavioral & Cross-Functional Leadership

"How do you handle technical disagreements when working in cross-discipline teams with non-software professionals?"

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

"Why did you choose to apply for a Software Engineer position at Amgen, and how does your background align wit

Medium · Behavioral & Cross-Functional Leadership

"Why did you choose to apply for a Software Engineer position at Amgen, and how does your background align with our mission?"

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

"Tell me about a time when a project requirement changed late in the development cycle, and how you navigated

Medium · Behavioral & Cross-Functional Leadership

"Tell me about a time when a project requirement changed late in the development cycle, and how you navigated the transition."

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?