Why I Failed 7 Tech Interviews (And What Finally Changed)

Day 1 of building in public. Let me start with the uncomfortable truth.

I failed 7 technical interviews at companies I really wanted to work for. Google, Meta, Amazon - you name it, I bombed it.

The thing is, I wasn't a bad programmer. At work, I shipped features, fixed bugs, and my code reviews were solid. But interviews? I'd freeze. My mind would go blank. Problems I'd solved before suddenly felt foreign.

After interview #7, I sat down and analyzed what was actually happening.

The Problem Wasn't What I Thought

I assumed I needed to solve more LeetCode problems. So I grinded. 100 problems. Then 200. Then 300.

My LeetCode profile looked impressive. But in interviews, I was still choking.

The real issues were:

1. I was pattern-matching, not problem-solving

I'd see a problem, think "oh this looks like that LeetCode problem I did," and try to remember the solution. But interview problems are never exactly the same. When the pattern didn't match perfectly, I was lost.

2. I never practiced explaining my thought process

Solving a problem in your head is completely different from explaining it out loud while someone watches. I had zero practice with this.

3. I had no retention system

Problems I solved a month ago? Completely forgotten. So I was essentially starting from zero every time I prepared for an interview.

What Changed

The turning point was embarrassingly simple. I stopped trying to solve 5 problems a day and started solving 1 problem deeply.

Here's what "deeply" means:

After 100 days of this approach, something clicked. Problems stopped feeling random. I started recognizing patterns. I could adapt to variations.

Why I'm Building DSA 100 Days

This experience is why I'm building DSA 100 Days. I want to create the tool I wish I had:

I don't know if this will work as a product. But I know the method works for learning.

That's day 1. Tomorrow I'll write about the LeetCode trap and why quantity doesn't equal quality.

If this resonates with you, follow along. I'll be sharing everything - the wins, the failures, and the data.

— Marcus