Learn to interview to passing on-sites in three months

Three months of evening practice — about 100 hours for a tech role, less for non-tech — gets a prepared candidate from "I freeze on whiteboard questions" to walking into an on-site and getting offers. This page is biased toward software roles because that's the loop with the most structured prep. The behavioral half applies everywhere.

~3 months · ~100 hours · pass a four-round on-site at a senior level

Weeks 1–8 · 8 hours/week

1.Cracking the Coding Interview — Gayle McDowell

Still the standard. McDowell ran hiring committees at Google and the book contains 189 questions with full solutions, plus the meta-skill chapters on how to communicate while you code. Work through chapters 1–11 (data structures and algorithms) doing the problems on paper first, then on a whiteboard, before checking the answer. Skim the rest as reference. Pair it with grinding 100–150 LeetCode mediums of similar topics.

~$30 paperback; LeetCode free tier is enough

crackingthecodinginterview.com →
Weeks 6–12 · 3 hours/week

2.The Pragmatic Engineer — for system design

For senior roles you'll get a system-design round and CtCI doesn't cover it. Gergely Orosz's Pragmatic Engineer newsletter publishes the clearest writing on real-world distributed systems, on-call practice and design tradeoffs. Read his system-design archive deeply, then drill against a free question bank — design Twitter, design a URL shortener, design WhatsApp — out loud, with a whiteboard, in 45 minutes. The clock is part of the skill.

Free archive; paid newsletter $19/month if you want depth

Pragmatic Engineer →
Weeks 9–12 · 2 hours/week

3.STAR-method behavioral practice — out loud

Write down ten stories from your career — a conflict, a failure, a leadership moment, a technical decision, an ambiguous project — each in Situation/Task/Action/Result form, each under two minutes spoken. Practice them on video, watch yourself back, cut every "um" and "I think." A cleanly delivered behavioral round is the cheapest performance gain in the whole loop and almost everyone neglects it.

Free

STAR method guide →

If you're interviewing for non-tech roles

If you're not interviewing for engineering, replace the first two steps with "60 Seconds and You're Hired" by Robin Ryan. It's the most-cited general interview book and Ryan teaches a "60-second sell" — a tight pitch you can deliver to any "tell me about yourself" opener — plus 125 specific question scripts. Keep the STAR-stories step exactly as written. Three weeks at five hours a week is usually enough.

Why this path

Most interview prep fails because candidates read instead of practice, and practice silently instead of out loud. CtCI gives you the algorithmic vocabulary; Pragmatic Engineer gives you the design vocabulary; the STAR drills give you the soft-skill vocabulary. The recurring pattern: write the answer, say it out loud, record yourself, watch it back. The discomfort of watching your own video is the fastest tutor in interview prep.