Unity · Primly Community

Unity onsite / final round, how it really goes (senior SWE, remote, 2026)

market_realist · 4 replies

Completed my Unity final round loop in March 2026. Sharing the actual structure because the 'what to expect' posts I found were mostly from 2021-2022 and things have changed.

Format: Fully remote. Five rounds across two days (you can request to split them). Each round is 55 minutes with 5 minutes of admin/transition.

Round breakdown: Coding (1 hour) - algorithmic, medium difficulty, similar to what you'd expect from the OA but harder. They timed me loosely, weren't strict about 'now stop', more interested in seeing how you think. System design (1 hour) - as described in other posts here: game-aware, drill-down heavy, expect to go two or three levels deep on any component you mention. Behavioral / leadership (1 hour) - senior IC so they were probing for influence without authority, decision-making under ambiguity, and a few retrospective questions about past projects. Technical depth / architecture (1 hour) - this one surprised me. It wasn't another system design, it was more of a technical conversation: 'given this existing design, what would you change and why.' They gave me a fictional but realistic architecture doc beforehand (sent the night before). You're expected to come in with thoughts. Don't skip reviewing it. Hiring manager round (55 min) - culture, team fit, questions for them. This felt lower-stakes but I later learned it's actually a real vote in the debrief, not just a formality.

Wait time after: 10 business days. Got the call from the recruiter, not the HM.

One thing I wish I'd done differently: prepped more on the 'read this doc beforehand' round. It's a genuine differentiator for senior-level hiring there.

4 replies

brand_ben

The 'read the architecture doc beforehand' round is interesting. That's a sophisticated signal. Most candidates prepare hard for the performative design-on-the-spot round and show up less ready to actually critique and improve an existing system, which is arguably more representative of real work.

ux_uma

Exactly my reaction when I got the material. I'd spent days prepping blank-slate design questions and spent maybe 45 minutes on the doc. Won't make that mistake again. Treat it like a take-home case: read it twice, note what's missing, note what's over-engineered.

firsttime_mgr

Five rounds feels like a lot for a senior IC role. Was there any redundancy across rounds or did each one clearly test something distinct?

ae_andre

Minimal redundancy in my experience. The two 'design' rounds (system design vs. architecture critique) felt distinct. The behavioral and HM rounds overlapped a bit thematically but had different energy. Five rounds is normal for senior at Unity from what I've seen, not padded.