# Technical Interviews Without the Hazing

Somewhere along the way, technical interviews turned into a hazing ritual in most people's heads: memorize
three hundred algorithm problems, whiteboard under fluorescent lights while a stranger judges your every
pause, get rejected for reasons nobody explains. That reputation is mostly earned - some interviews really
are bad. But the fear it creates makes people prepare for the wrong thing entirely.

Interviews are not trying to catch you out. A reasonable interviewer wants to know if you can think clearly
about a problem, communicate while you do it, and work with people afterward. That's a learnable skill, not
a trivia contest. This guide covers what interviews actually measure, how to get through the coding round
without your brain locking up, and how to handle the parts nobody prepares for - system design, "tell me
about a time," and the offer conversation at the end.

## The phases

1. **[What Interviews Are Actually Testing For](01-what-interviews-are-testing-for.md)** - signal versus
   noise, why memorizing everything is the wrong strategy, and how to tell a good interview process from a
   bad one.
2. **[The Coding Round Without the Panic](02-the-coding-round-without-the-panic.md)** - thinking out loud,
   asking clarifying questions, admitting you forgot the syntax, and what to do when you get stuck.
3. **[System Design and the Human Round](03-system-design-and-the-human-round.md)** - why the non-coding
   rounds still count, good questions to ask them, and a clear-eyed look at negotiating an offer.

Read them in order if an interview is coming up. If you're already mid-loop and the coding round is what's
looming, skip to Phase 2.