Genentech PM onboarding first 90 days what to expect 2026

The first 90 days as a product manager at Genentech are not about shipping features—they’re about learning the regulatory spine of biotech product development. You will spend 60% of your time in cross-functional immersion, not roadmap execution. Success is measured by how quickly you stop thinking l

Title: Genentech PM Onboarding First 90 Days What to Expect 2026

TL;DR

Who This Is For

This is for product managers with 3–7 years of experience in tech or digital health who have just accepted or are preparing to start a PM role at Genentech. It does not apply to research, clinical, or manufacturing roles. If you’ve worked only in consumer tech or SaaS, your mental models are liabilities, not assets.

What does the Genentech PM onboarding schedule look like in the first 30 days?

The first 30 days are structured around controlled exposure, not autonomy. Day 1 to 10 is classroom-style immersion: regulatory frameworks (FDA 21 CFR Part 11, ICH E6), drug development lifecycle phases, and Genentech’s internal stage-gate process. You will sit through 18 mandatory compliance modules—each 45–60 minutes—delivered by Legal and Clinical Ops, not Engineering.

The problem isn’t your lack of biotech background—it’s your assumption that onboarding is about tools and access. In a Q3 2025 debrief, a new hire was flagged because they asked for Jira permissions on Day 3. The hiring manager said, “We don’t care if you can write a user story. We care if you know when a protocol deviation invalidates a trial dataset.”

Not learning regulations, but applying them contextually is the real test. Most PMs fail their first stakeholder meeting not because they’re unprepared, but because they frame questions in terms of “user pain points” instead of “risk mitigation.” One PM lost credibility by suggesting a “lean MVP” for a companion diagnostics app—this was interpreted as undermining clinical validation rigor.

By Day 15, you’ll be assigned two shadowing tracks: one clinical (e.g., observing a safety review team meeting) and one commercial (e.g., pre-launch planning for an oncology indication). Attendance is tracked. Missing one session triggers a note in your 30-day check-in with HR Business Partner.

You won’t have a direct report or budget authority in Month 1. Your manager will assign you a “buddy” — always a senior PM who has survived a Phase III submission. Their job is not to help you navigate Slack channels, but to interrupt you when you use tech metaphors inaccurately. “Agile” is not a safe word here. Saying “let’s pivot” in a room with regulatory affairs will mark you as an outsider.

How do Genentech PMs prioritize work in the first 90 days?

Prioritization at Genentech is not a product-led exercise—it’s a risk-calibrated negotiation. In your first 90 days, you are not expected to lead prioritization. You are expected to observe how decisions are really made: through safety thresholds, not ROI projections.

In a Q1 2025 portfolio review, a digital PM proposed accelerating a patient-reported outcomes (PRO) platform to improve trial enrollment. The project was tabled—not due to technical debt or bandwidth, but because Medical Affairs raised a signal about potential unblinding risk. That decision was made in a 12-minute sidebar between the Medical Monitor and the Regulatory Lead, not during the formal agenda. If you weren’t in the room, you wouldn’t know why.

Not velocity, but alignment with clinical endpoints is the true north. Your roadmap will be empty of epics and sprints. Instead, you’ll see “Q1: Complete HIPAA-compliant audit of third-party eCOA vendor” or “Q2: Align with Safety Team on adverse event reporting triggers.”

You will attend weekly “Stage Lock” meetings where cross-functional leads vote on whether a development phase can proceed. Your role is not to advocate for features, but to document dependencies and escalation paths. If you try to “drive outcomes” like a tech PM, you’ll be gently sidelined.

A PM who survived their 90-day review told me: “I stopped writing ‘prioritization frameworks’ in my updates. I started mapping decision rights. That’s what got me a ‘meets expectations’ instead of ‘needs development.’”

What cross-functional teams will I work with as a new PM at Genentech?

You will interface with six core teams: Clinical Operations, Medical Affairs, Regulatory Affairs, Safety, Commercial, and Companion Diagnostics. Engineering and Data are secondary stakeholders. This is not a technology-led organization.

In a debrief after a failed onboarding cycle, the hiring manager said, “She spent two weeks optimizing API latency with the tech team. The problem wasn’t the API—it was that the clinical site coordinators didn’t trust the data capture flow. She never talked to them.”

Not engineering integration, but clinical workflow adoption is the bottleneck. Your primary interface is not the backend team, but the Clinical Research Associates (CRAs) who use your tools in the field. They don’t care about uptime SLAs. They care whether the mobile app works in rural clinics with spotty Wi-Fi and whether it complies with local privacy laws in EU trial sites.

Medical Affairs owns the scientific narrative. If you’re building a tool for investigator engagement, you don’t define the requirements—you interpret the KOL (Key Opinion Leader) feedback funneled through Medical Science Liaisons (MSLs). Pushing your own agenda here is career-limiting.

Regulatory Affairs has veto power. Not on design or usability, but on anything that touches data integrity, audit trails, or subject consent. One PM had their entire eConsent prototype scrapped because the “continue” button didn’t meet FDA human factors guidance for readability in elderly populations.

Safety is your silent partner. They don’t attend your standups, but they review every data field you collect. If your tool captures “nausea severity,” Safety needs to know whether that’s patient-entered, clinician-assessed, or algorithmically inferred—and how it maps to MedDRA coding.

You will have limited authority. Influence is earned by speaking their language, not by “unblocking” them. Not facilitating, but translating is your job.

How are new PMs evaluated during the first 90 days at Genentech?

You are evaluated on three criteria: regulatory literacy, stakeholder mapping accuracy, and escalation judgment. Technical output—wireframes, specs, dashboards—is not scored.

In a hiring committee meeting in February 2025, a PM was marked as “at risk” not because they missed a deadline, but because they escalated a UI inconsistency directly to the VP of Digital without looping in Safety and Legal. The HC noted: “They didn’t understand the chain of risk ownership.”

Not task completion, but escalation protocol adherence is what gets reviewed. Your 30-, 60-, and 90-day check-ins are not progress reports. They are oral exams on decision rationale. Expect questions like: “Why did you choose that endpoint definition?” or “How did Regulatory weigh in on that change request?”

You will submit a “Stakeholder Influence Map” at Day 60. It must name individuals, not roles. Listing “Clinical Ops Lead” is failing. Writing “Dr. Lena Park, Clinical Ops Lead for Phase III Hematology trials, resists decentralized trials due to site monitoring concerns” is passing.

Your manager will assess whether you’ve moved from “seeking approval” to “anticipating blocking conditions.” One high performer documented a potential ICH E2B(R3) compliance gap in a third-party data pipeline three weeks before it became a formal audit finding. That wasn’t her job. That’s why she got fast-tracked.

Compensation is not tied to 90-day reviews—base salary for L5 PMs is $185K–$210K with 15% target bonus—but failing triggers a Performance Improvement Plan (PIP). PIPs in biotech are not remediation tools. They are off-ramps.

What tools and systems will I use as a Genentech PM?

You will use Medidata Rave for clinical data capture, Veeva Vault for regulatory documents, and Microsoft Teams for communication. Jira exists, but it’s secondary. Confluence is used, but only after Legal signs off on content classification.

Access to systems is granted in phases. You get read-only access to Rave on Day 8, edit rights on Day 22—after completing GCP (Good Clinical Practice) training and passing a quiz with 100% score. One PM had their access revoked for sharing a screenshot of a patient dashboard in a Teams chat—violation of internal data handling policy.

Not speed of execution, but audit trail integrity is the priority. Every change in Vault requires a deviation justification. Even updating a typo in a document version history requires a change control record.

You will not use Figma freely. Prototypes must be reviewed by Human Factors Engineering before any external testing. One PM ran a usability test with nurses without this step. The session was invalidated, and the vendor contract was audited for GDPR compliance.

PowerPoint is your primary deliverable format. Not pitch decks—evidence dossiers. Your slides will be packed with footnotes, reference codes (e.g., “ICH E6 Section 5.20”), and approval stamps. Visual minimalism is seen as lack of rigor.

You will spend 3–5 hours per week updating governance trackers—Excel sheets that log review cycles, approvers, and pending risks. These are not “nice to have.” They are subpoena-ready documents.

If you come from a startup where “move fast and break things” is a mantra, you are already at risk.

Preparation Checklist

Complete GCP (Good Clinical Practice) and HIPAA training before Day 1—Genentech accepts externally certified modules from accredited providers.
Map the Phase III trial process end-to-end, including safety reporting, DSMB reviews, and regulatory submission gates.
Study FDA guidance on software as a medical device (SaMD) and ICH E6(R2) for clinical trial conduct.
Practice writing risk-benefit tradeoffs in narrative form, not bullet points.
Work through a structured preparation system (the PM Interview Playbook covers biotech stakeholder dynamics with real debrief examples from Roche and Genentech).
Identify three recent Genentech drug approvals and understand their clinical endpoints and safety profiles.
Prepare to shadow CRAs and MSLs—your first 30 days will include field visits.

Mistakes to Avoid

BAD: Sending a Jira invite to a Medical Monitor to “get alignment on sprint goals.”

GOOD: Scheduling a 15-minute sync to walk through a change impact assessment, pre-circulated with regulatory implications called out.

BAD: Referring to patients as “users” or “customers” in a cross-functional meeting.

GOOD: Using “trial participants” or “subjects” consistently—this isn’t semantics, it’s protocol.

BAD: Proposing a “beta release” for a safety-critical application.

GOOD: Framing the same concept as a “pilot phase with predefined exit criteria and adverse event monitoring.”

FAQ

What’s the biggest cultural shock for tech PMs joining Genentech?

The biggest shock is realizing that speed is not a value. In tech, shipping fast is rewarded. At Genentech, shipping correctly is mandatory. One misstep in data handling or protocol compliance can delay a submission by months. Your instinct to “iterate quickly” will be seen as recklessness until you learn the risk thresholds.

Do new PMs get a mentor during onboarding?

Yes, but not in the Silicon Valley sense. You get a “Functional Buddy” (senior PM) and a “Process Coach” (from Clinical Operations). The buddy answers unspoken questions. The coach ensures you complete governance steps. Neither will advocate for you in reviews—Genentech does not believe in subjective sponsorship.

Is remote work allowed during the first 90 days?

Yes, but with restrictions. You must attend at least two in-person site visits: one at a clinical trial hub, one at the South San Francisco campus. Remote-only participation in safety or regulatory meetings is not permitted. VPN access requires hardware token authentication—plan for shipping delays.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.