Screens, OA, onsites, hiring committee — what each round actually tests.
Covers: process · expectations
The typical loop
Recruiter screen — role fit, timeline, comp band, logistics.
Online assessment (OA) — timed coding; often auto-graded.
Phone / virtual technical — 45–60m live coding or light design.
Onsite / virtual onsite — 3–5 rounds: coding, system design, behavioral, sometimes domain (security, ML, frontend).
Hiring committee / bar raiser — calibration across interviewers; your packet matters more than one hero round.
What they optimize for
- Can you **solve under time** with clear communication?
- Do you write **correct, tested** code (edge cases)?
- Can you **design** at the right altitude for the level?
- Will you be a **safe teammate** (behavioral)?
Crucible mapping
Daily + problem bank ≈ OA/coding. Missions ≈ design depth. Timed company sims ≈ onsite pressure. Verified profile ≈ packet evidence.
Exercise
Write your target loop on one page: company → role → level → which round types. Then enroll in a matching study plan.