Genentech · Primly Community

Genentech onsite / final round, how it really goes (senior SWE, SSF 2026)

remote_swe_42 · 6 replies

Just wrapped my Genentech onsite last month. Writing this up because I couldn't find a clean recent post and the older stuff is from 2022-2023 when the process was apparently different.

Location: South San Francisco campus. In-person. They booked travel and the hotel themselves, which I appreciated. The campus is huge and kind of beautiful in a "this is a serious company" way.

Format for a Senior SWE role: Hiring Manager intro: 30 min (not evaluative, more like a mutual vibe check) Coding round 1: 45 min, one medium LC problem with a follow-up Coding round 2: 45 min, one design + implement problem (smaller scope than a full system design) Lunch with the team (not evaluative, but be a normal human) System design: 60 min (covered separately in another thread) Behavioral / values: 45 min with a different IC Wrap with recruiter: 15 min

Total time: about 5.5 hours including lunch. Long but it moved fast.

Coding rounds: The problems felt like LeetCode medium. Nothing crazy. One was around graph traversal, the other around interval merging with a twist specific to their domain. The interviewers were collaborative, not poker-faced. If you're close, they'll say something.

The behavioral round: this was with a non-engineering IC, maybe a technical program manager. Questions were genuinely thoughtful. "Tell me about a project where the technical debt built up and what you did about it" and "describe a time you disagreed with a PM's priority and how it resolved."

Debrief timing: I heard back 9 business days later with an offer. Apparently their debrief happens the same day, which is encouraging. The delay was mostly the comp approval process.

Overall: a more human process than most of the big-tech onsites I've done. Recommend.

6 replies

corp_refugee

9 business days for an offer after the onsite is pretty healthy. FAANG is often faster but the ghost rate is higher. At least you know where you stand.

visa_vik

Did they mention anything about hybrid expectation during the onsite itself? I see conflicting stuff about whether it's 2 days or 3 days in SSF.

staff_steph

HM said 2-3 days depending on the team and sprint cadence. Not strict. The team I'd be joining was doing 2 in-person days, Tuesday and Thursday. But I'd ask your specific HM because it genuinely varies by org.

qa_quinn

Was there any QA or testing conversation in the coding rounds? I always want to know if they care about test coverage or if it's pure algorithmic.

staff_steph

They did ask me to walk through edge cases after I wrote my solution. I'd call it lightweight testing conversation: here's a null input, here's an empty array, what happens. Not deep TDD stuff but they noticed when I volunteered test cases before they asked.

contractor_kai

The "design + implement" hybrid round is interesting. Most companies separate these. Is it like, a 30/15 split where you sketch it then code it?