The Tech Interview is Broken (And Everyone Knows It)

Let me tell you about my worst interview.

I was asked to implement a red-black tree. On a whiteboard. In 45 minutes. While someone watched.

The job? Building React dashboards.

Did you know? The creator of Homebrew was rejected by Google because he couldn't invert a binary tree in an interview. He literally wrote software used by millions of developers, but failed the whiteboard test.

The system is broken. Everyone knows it. No one changes it.

🎭 The Theater We All Perform

The Interviewer's Script:

• "Here's an algorithmic puzzle you'll never use on the job"
• "Pretend I'm not watching you sweat"
• "Think out loud so I can judge your brain in real-time"
• "You have 45 minutes" (actual job tasks take days)

The Candidate's Script:

• Has memorized 100 LeetCode problems
• Performs calm confidence while panicking inside
• Pretends this is how they normally code
• Never mentions that they'd just Google this in real life

We're all acting. The play is called "Proving Technical Competence." It has nothing to do with actual technical competence.

📊 What Interviews Test vs. What Jobs Need

Did you know? Studies show that interview performance has almost ZERO correlation with job performance. The interview process is essentially random selection with extra steps.

🎪 The LeetCode Industrial Complex

LeetCode Premium: $35/month Interview prep courses: $200-2000 Coaching services: $100-300/hour

There's an entire industry built on the premise that interviews don't test real skills.

If interviews tested relevant skills, you wouldn't need to pay someone to teach you irrelevant skills.

Think about that.

🤡 My Personal Circus Highlights

Interview 1: Asked to implement a linked list. Job was building email templates. Never touched a linked list in 2 years there. Pretty sure the interviewer didn't know what a linked list was either.

Interview 2: 6-hour take-home project. Detailed feedback? "We went with someone else." Thanks for the free work!

Interview 3: Asked about my "weakness." I said "perfectionism." They loved it. Reader, perfectionism is not a real weakness. It's probably the most common lie in interview history.

Interview 4: Pair programming where the interviewer literally didn't know the codebase. We debugged together. Actually useful! Rare.

🔥 The Hot Takes

Hot Take 1: Take-homes Are Free Labor

"Build us a mini-app to evaluate your skills." Translation: "Do unpaid work we might actually use."

Hot Take 2: Culture Fit Is Often Discrimination

"They weren't a culture fit." Translation: "They weren't like us." (Sometimes legit. Often... concerning.)

Hot Take 3: Years of Experience Is Meaningless

"5+ years required." Someone with 1 year of growth beats someone with year 1 repeated 5 times.

Hot Take 4: Most Interviewers Are Untrained

Did you know? At most companies, interviewers receive less than 2 hours of interview training. They're winging it. The evaluation is random.

✨ What Would Actually Work

1. Paid trial days — Work with the team for a day. See real fit.
2. Portfolio review — Look at what they've actually built.
3. Realistic problems — Debug this production bug. Explain your approach.
4. Team-based evaluation — Have multiple people assess, reduce individual bias.
5. Transparent criteria — Tell candidates what you're actually looking for.

🎯 The Bottom Line

The interview process is:

• Stressful for candidates
• Time-consuming for companies
• Poorly predictive of performance
• Biased toward people who can afford prep resources

Everyone knows this. Companies keep doing it because "that's how it's done."

If you're job hunting: the game is rigged, but you still have to play it. LeetCode. Practice. Perform.

If you're hiring: maybe try something different? Revolutionary concept: evaluate people on skills they'll actually use.

But what do I know. I'm just someone who once whiteboarded a red-black tree for a React job. 🎭