The Interview Loop

Recruiter screen (~30 min)

Non-technical. The recruiter confirms your background, explains the role and timeline, and sniffs out comp expectations and red flags. You almost can’t “win” here — but you can lose by being unprepared, evasive about comp, or flaky on scheduling. Be warm, concise, enthusiastic about this role, and have 2–3 thoughtful questions ready.

Technical phone screen (~45–60 min)

The real filter, and where most candidates are cut. One or two coding problems (usually a medium) in a shared editor — often no autocomplete and no “run” button, so your code has to compile in your head. The bar: a working, reasoned solution communicated clearly. Pass this and you reach the onsite.

Onsite / virtual onsite (4–6 rounds)

The main event, back-to-back ~45-minute rounds:

• 2 coding rounds — harder mediums / easy-hards, sometimes two problems per round.
• 1 system design — expected for mid-level and senior (and the whole bar for senior). See the system design round.
• 1–2 behavioral — “tell me about a time…” mapped to company values. See the behavioral round.
• Sometimes a domain round — OS, ML, frontend, depending on the role.

Each interviewer scores you independently. You reset and re-earn the room every 45 minutes.

Hiring committee / debrief (async)

Interviewers write detailed feedback and vote on a scale (Strong Hire → Hire → Lean Hire → Lean No-Hire → No-Hire → Strong No-Hire). At Google a committee (who never met you) reads the packets; elsewhere the hiring manager reconciles. One confident “No-Hire” on a core signal can sink an otherwise strong loop — consistency across rounds matters.

Offer & negotiation (days)

The recruiter calls with numbers. Compensation is almost always negotiable — a competing offer, market data, and a calm, specific counter routinely move base, equity, and sign-on. Never accept on the spot; get the full breakdown in writing and take time to think.