When Technical Interviews Go Wrong

More interview stories from the trenches. The good, the absurd, and the lessons learned.

The Live Coding Disaster

"Build a React component that fetches and displays users."

Simple enough. But my hands were shaking. The interviewer was watching every keystroke via screen share. I mistyped `useState` as `useStat` and my brain just... stopped.

Five minutes of frozen debugging. Eventually got it working. Didn't get the job.

**Lesson**: Practice under observation. Do mock interviews with screen sharing.

The Gotcha Question

"What happens when you type a URL in the browser and hit enter?"

I started explaining: DNS lookup, TCP handshake, HTTP request...

"Go deeper on the TCP handshake."

I explained the three-way handshake.

"What about TCP window scaling?"

I had no idea. This went on. Every answer led to a deeper "but what about..." question until I hit my knowledge ceiling.

**Lesson**: It's okay to say "I don't know." They were testing depth, not expecting perfection.

The Culture Fit Curveball

"Tell me about a conflict with a coworker."

I shared a professional disagreement about architecture. How we discussed options, compromised, and moved forward.

"But did you WIN the argument?"

Weird framing. I explained we found a middle ground.

"So you compromised your position? Would you do that here?"

Red flag. This company wanted combativeness, not collaboration. I withdrew from the process.

**Lesson**: Interviews are mutual evaluation. Culture fit goes both ways.

The Ghost

Five rounds of interviews. Technical screens, system design, manager chat, VP chat. "We'll have an answer by Friday."

Friday: nothing. Monday: nothing. Following Friday: "We're moving in a different direction."

No feedback. Two weeks of my mental energy, evaporated.

**Lesson**: Don't stop applying after a "good" interview. Nothing is real until the offer is signed.

What Actually Matters

After dozens of interviews:

1. **Communicate your thinking** - Talk through your approach 2. **Ask clarifying questions** - Don't assume 3. **Stay calm** - Easier said than done, but practice helps 4. **Know your resume** - If it's on there, be ready to discuss it 5. **Interview them too** - You're evaluating the company

The process is broken in many ways. But that's the game we're playing.

Back to Journal