Amgen SDE onboarding and first 90 days tips 2026

TL;DR

Amgen SDE onboarding is a structured 6-week process with minimal hand-holding—your first 90 days determine whether you survive the probation period or get managed out. The biotech engineering culture values domain knowledge over speed; contrary to popular belief, shipping fast will not earn you credibility—demonstrating understanding of healthcare data compliance and Amgen's research workflows will. Compensation for Amgen SDEs ranges from $140K to $220K base depending on level, with equity vesting over 4 years.

Who This Is For

This is for software engineers who have received an offer from Amgen or are in final interview rounds, specifically for SDE roles in the product engineering or data infrastructure teams. If you're coming from a pure consumer tech background (Meta, Amazon, Google consumer products), you need to recalibrate your expectations—Amgen operates with pharmaceutical regulatory constraints that will fundamentally change how you write and deploy code. This is not for research scientists; this is for engineers building the systems that run clinical trials, manufacturing, and regulatory submissions.

What Actually Happens During Amgen SDE Onboarding

The first thing no one tells you: Amgen's onboarding is not a boot camp. Unlike Amazon's强制性的 "Amazonian" training or Google's structured boot camp, Amgen gives you a laptop, a badge, and access to their internal wiki—which contains 15 years of accumulated institutional knowledge in various states of obsolescence. You are expected to figure out what matters.

The official onboarding timeline spans 6 weeks, broken into three phases: Week 1-2 is access provisioning and compliance training (FDA 21 CFR Part 11, GxP systems, data integrity requirements), Week 3-4 is team integration and codebase orientation, and Week 5-6 is your first assigned task. But here's what actually happens: the compliance training is mandatory and pass/fail—you will be locked out of production systems if you fail the data integrity certification. Most engineers from consumer tech backgrounds fail at least once because they treat it as a checkbox exercise. Do not do this. The compliance material is genuinely important; Amgen has received FDA warning letters over data integrity issues, and engineers who don't understand the regulatory context will write code that creates liability.

In your first team meeting, expect silence. Not because people are unfriendly—because Amgen engineers tend to be introverted and deeply focused. Your manager will introduce you, share your onboarding buddy (a peer assigned to answer questions), and then the meeting will continue with actual work. This is not a welcome party. The signal you should take: start asking questions in writing on the team's Slack channel rather than expecting walk-throughs.

What SDEs Actually Do at Amgen in the First 90 Days

The work is not glamorous. In your first quarter, you will likely be assigned to one of three areas: maintaining legacy Java systems that run manufacturing tracking, building ETL pipelines for clinical trial data, or working on Amgen's internal developer platform. The ratio breaks down roughly as 40% legacy maintenance, 40% data pipeline work, and 20% greenfield projects—and the greenfield work goes to engineers who have demonstrated they understand the domain.

The critical insight most new SDEs miss: Amgen's engineering org is small relative to its R&D budget. You are not building consumer products with millions of users. You are building systems that handle data for drug manufacturing and clinical trials—systems where accuracy matters more than velocity. A bug in a consumer app causes inconvenience; a bug in a clinical data system can trigger an FDA audit. This is not hyperbole—Amgen received a Form 483 from the FDA in 2019 citing data integrity issues in their manufacturing systems.

Your first 90 days should focus on learning the domain, not shipping code. Engineers who try to prove themselves by shipping quickly in Q1 often produce work that doesn't meet the regulatory standards, requiring rework that damages their reputation. The judgment signal here: Amgen values correctness over speed, and the hiring manager in your debrief will have already been told by senior engineers whether you've demonstrated "domain readiness."

How Amgen's Engineering Culture Differs from Big Tech

The culture is closer to a regulated financial services company than a typical Silicon Valley tech giant—not the chaos of a startup, not the scale of Google, but somewhere in between where process actually matters. Decisions require sign-off. Deployments require documentation. Changes to production systems require change control board approval.

The compensation reflects this: Amgen SDE II roles pay $140K to $180K base, with L4 (senior) roles ranging from $170K to $220K. Equity vests over 4 years with a 1-year cliff. The total compensation packages typically land 10-15% below equivalent roles at Meta or Google, but the work-life balance is materially better—no pager duty, no shipping on-call for consumer-facing outages. In my observation of Amgen engineers who left for FAANG, the ones who succeeded had learned to operate with more autonomy; the ones who struggled had become accustomed to the slower pace and struggled with FAANG's velocity expectations.

The hierarchy is flatter than you'd expect for a pharma company. There are no "IC tracks" in the traditional tech sense—engineering levels exist but are less rigidly enforced. What matters more is your relationship with your manager and your ability to navigate the matrix structure where you may have a functional manager (technical) and a dotted-line manager (project-based). This is where most new SDEs get confused: your performance review comes from your functional manager, but your day-to-day work is assigned by project leads who may not have direct reporting authority over you.

> 📖 Related: Amgen TPM interview questions and answers 2026

The Political Reality of Your First Quarter

Here is the conversation that happens in every new hire debrief: the hiring manager asks senior engineers "Is this person someone you'd want on your team for a critical project?" The answer is not about code quality—it's about whether you're easy to work with, whether you ask good questions, and whether you've demonstrated you understand why Amgen exists (making medicines, not building apps).

The political reality is straightforward: Amgen's engineering org has about 800 engineers globally, concentrated in Thousand Oaks, San Francisco, and Cambridge. Everyone knows everyone. Your reputation forms in your first month. The fastest way to damage it is to complain about the tooling (yes, the internal systems are dated), to skip compliance training, or to submit code reviews without context. The fastest way to build it is to ask thoughtful questions about why certain architectural decisions were made, to document your learning publicly on the internal wiki, and to deliver your first assigned task with comprehensive test coverage—even if it takes longer than expected.

One specific scenario you'll face: in your first sprint planning, you'll be assigned a task that seems trivial. Do not try to swap it for something more interesting. Complete it, document what you learned, and ask for something slightly more complex next time. This is how you signal growth without signaling entitlement.

Preparation Checklist

Complete FDA 21 CFR Part 11 training before your start date if possible—Amgen provides the materials to new hires early. This is not optional prep; it's the single highest-leverage thing you can do to hit the ground running.

Review Amgen's pipeline and approved products on their investor relations page. You need to understand what the company actually does—manufacturing biopharmaceuticals for oncology, immunology, and cardiovascular diseases. When engineers can't explain what Amgen sells, it shows in debriefs.

Set up your development environment before day one. Amgen uses a mix of Java, Python, and internal tooling. Get access to their GitHub Enterprise instance and review the onboarding documentation in the engineering wiki—it's publicly available in parts on their tech blog.

Identify your onboarding buddy and schedule a 1:1 in week one. This is your primary resource for navigating the "unwritten rules" of the team. Ask them what they wish they'd known in their first 90 days.

Read the engineering blog posts on Amgen's technology site. They discuss their data infrastructure, ML platforms, and cloud migration. This will give you conversation topics for your first team meetings and signal that you're invested.

Work through a structured preparation system—the PM Interview Playbook covers biotech engineering role expectations with real examples of what hiring managers look for in the first 90 days, including the specific compliance frameworks you'll encounter at regulated companies like Amgen.

Prepare 3 substantive questions for your manager in your first 1:1 about team priorities and what success looks like at 90 days. Managers notice when new hires are trying to understand expectations rather than just waiting to be told what to do.

Mistakes to Avoid

BAD: Skipping compliance training because "it's just bureaucratic paperwork" and trying to speed to code.

GOOD: Treating FDA 21 CFR Part 11 training as the most important learning in your first two weeks—because it is. Engineers who treat compliance as beneath them get flagged in performance reviews.

BAD: Asking "Why do we use this old technology?" in your first team meeting.

GOOD: Asking "What's the history of this architecture decision? What constraints were we working with?" This signals curiosity rather than judgment, which is how you build political capital.

BAD: Volunteering for high-visibility projects in your first month to "prove yourself."

GOOD: Completing your initial assigned tasks reliably before expressing interest in more complex work. Amgen's engineering culture rewards demonstrated competence over declared ambition—the reverse of consumer tech where visibility matters more.

FAQ

Is Amgen a good place for software engineers compared to FAANG?

Amgen offers better work-life balance and less on-call pressure than FAANG, but lower compensation and slower career progression. If you want to work on systems that directly impact drug development and don't need top-of-market salary, it's a strong choice. If you want rapid skill development and higher compensation, FAANG pays more but expects more.

How long is the probation period for Amgen SDEs?

The formal review happens at 90 days, but your manager will have informal check-ins at 30 and 60 days. The 90-day review is when assignments to permanent projects are confirmed. Engineers who haven't demonstrated domain understanding by this point are often moved to lower-priority teams or managed out.

What technologies do Amgen SDEs actually use?

Java and Python dominate the backend, with increasing adoption of Kubernetes and cloud infrastructure (AWS and Azure). Data engineering roles work heavily with Apache Spark, Snowflake, and custom healthcare data platforms. The tooling is less modern than FAANG—expect to maintain systems that would have been replaced years ago at a consumer tech company.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.