After failing 37 interviews, I built the interview prep tool I wish I had

Source: Dev.to

Introduction

Hey, I’m Ilyas 👋
If you’re a junior, mid‑level, or self‑taught developer who keeps getting rejected, this might help.

The Struggle

For a year and a half my cycle was:

• Apply → wait → reject
• Apply → interview → reject

Stats

• 1,000+ applications
• ~20–30 interviews
• Mostly failures

It was exhausting. I was putting in serious effort, but the results were close to zero.

Why It Happened

In 2021 I landed a remote US job in three weeks with almost no experience.
Now, after dozens of interviews, I noticed a pattern:

• I wasn’t failing hard problems.
• I was failing basic questions like “What are React portals?” or “Explain GET in HTTP.”

I knew the answers, but under pressure my mind went blank. The issue was recall, not understanding.

The Solution: Active Recall with Flashcards

I turned to flashcards and active recall:

1. Create small concept cards
2. Review them repeatedly until recall became automatic

This method has been proven for over a century—it works.

Building the Deck

I asked recruiters directly, “What topics should I prepare for the technical interview?” and got clear lists:

• React fundamentals
• JavaScript basics
• HTTP
• Browser behavior

Using ChatGPT, I generated 20–30 flashcards per topic.

Process

1. Read the question first.
2. Answer from memory.
3. Reveal the correct answer.

Note: AI can be wrong sometimes, so verification is essential.

The Tool: 99cards.dev

To address AI inaccuracies and streamline the workflow, I built 99cards.dev.

• Short, daily sessions
• High focus on recall
• Organized by topic with useful UI tweaks

Results

After a few weeks of consistent practice:

• Panic stopped
• Answers came naturally
• Concepts were explained clearly (not memorized)

Interview outcome

• Passed 4 rounds
• Scored 95 % on the technical test
• Received an offer: $5,500/month + paid relocation

Effort finally matched outcome.

Job‑Search Strategy

About six weeks before the offer, I changed how I searched:

• Moved away from LinkedIn, Arc.dev, and large job platforms
• Focused on Telegram job groups

Benefits

1. Less competition
2. Direct communication

Typical outreach: “I saw this role. Here’s my CV + LinkedIn. Am I a good fit?”

• If yes → apply.
• If no → move on.

This saved hours each week.

Key Takeaways

• Failing interviews ≠ being bad at coding
• Passive learning doesn’t prepare you for interviews
• Recall > cramming
• Job search is a skill
• Fewer, better applications beat mass applying
• You’re not broken

Free Interview Checklist

I compiled a free checklist based on my experience. It covers eight areas:

1. HR
2. Technical
3. Behavioral
4. Live coding
5. System design
6. Algorithms
7. Take‑home tasks
8. Cultural fit

You can download it now if you wish.

---

I hope this saves you time and stress. You’re closer than you think.

— Ilyas