Hey Reader,

Last week, I asked what’s blocking you from clearing DSA interviews.

The most common response: “I know DSA but can’t perform consistently under pressure.”

I’ve seen this hundreds of times as a hiring manager at Google and Walmart.

Engineers who solve LeetCode mediums at home freeze on easy problems in interviews.

The problem isn’t knowledge. It’s a training environment mismatch.

Here’s what I mean:

How you practice:

• Unlimited time, no one watching
• Can pause, Google, restart
• Think silently, then code

How you’re tested:

• 45 minutes, someone judging every word
• Must explain thinking out loud
• No Google, no restarts

You’ve trained for one game. You’re being tested in another.

The fix: Train how you’ll be tested.

Here’s the 8-week pressure training method:

Week 1-2: Add time pressure

Set 45-min timer per problem. No extensions.

Track completion rate. Goal: 80%+ problems finished in time.

This builds decision-making speed.

Week 3-4: Add verbal layer

Solve problems out loud. Record yourself.

Explain your thought process as if an interviewer is listening.

Play it back: Where did you stammer? Where were you unclear?

By problem 10, your explanations should be clear without major hesitations.

Week 5-6: Add observer pressure

Do mock interviews with real people.

Where to find partners:

• Pramp.com (free peer mocking)
• Interviewing.io (paid, real engineers)
• LinkedIn (ask peers to exchange mocks)

Do 2-3 mocks per week.

Track nervousness level (1-10). By mock 5-6, should drop to 4-5.

Observer pressure is the closest simulation to real interviews.

Week 7-8: Simulate high stakes

Make mocks feel real:

• Treat it as “real FAANG interview”
• Use video calls (more formal)
• Ask partner to push back on your approach

If you can handle challenging mocks without spiraling, you’re ready.

Three techniques to use in every interview:

1. Pause and narrate

When pressure rises, say: “Let me think through this for a moment.”

Then narrate: “I’m considering two approaches: X and Y. X has this trade-off…”

Buys thinking time. Shows structured thinking.

2. Acknowledge and redirect

Realize you’re going wrong? Say: “Actually, there’s a better approach. Let me pivot to…”

Shows adaptability. Prevents confidence collapse.

3. Good enough first, then optimize

Brute force working solution in 15 mins.

Optimize in remaining 30 mins.

Interviewers care about working code + thought process, not just optimal solution.

The sooner you understand this, the better:

500 problems solved in comfort ≠ Interview readiness

50 problems solved under simulated pressure = Interview readiness

Most engineers optimize for quantity. Winners optimize for environment match.

Your action this week:

Pick 3 problems you’ve solved before.

Solve them again:

1. 45-min timer
2. Out loud (record yourself)
3. Without looking at solutions

If you can’t do this smoothly, you’re not ready. No matter how many problems you’ve solved.

Start training for pressure, not just problems.

- Abhishek

The Guided Growth