Two second-round interviews, and the real gap wasn't knowledge — it was how fast the wide view I have while preparing collapses down to one path under pressure.
Day 33 was probably the most intense interview day of this journey so far.
Two second-round interviews were scheduled, and I could feel the nervousness even before the day began. There was also another challenge running in parallel: trying to keep the schedule I had built for myself intact while dealing with the pressure of two important interviews.
The first interview went reasonably well. The interviewer was positive, but I couldn't complete the problem exactly as expected.
What made it interesting was what happened with the approach.
In yesterday's interview, I was expected to build modular components. So today, I went into the interview deliberately trying to build things in a modular way — separating responsibilities, creating reusable pieces, and keeping the implementation structured.
But that decision had a cost.
I spent so much time making the solution modular that I couldn't complete all the acceptance criteria within the available time.
It was a strange realization. The approach itself wasn't necessarily wrong. The problem was knowing how much engineering was appropriate for the time and context.
Yesterday, one thing was emphasized. Today, another thing mattered more.
That is probably something I need to get better at: adapting quickly instead of carrying the expectations of the previous interview into the next one.
The second interview was a design discussion, starting around component and library design. That conversation went much deeper than expected — it was scheduled for an hour but continued for roughly an hour and a half.
I felt good about that one.
But the most valuable part of the day wasn't whether either interview eventually turns into an offer. It was noticing a pattern in how I think under pressure.
During preparation, I can usually see the entire picture.
I think about different scenarios, possible trade-offs, alternatives, edge cases, and ways of approaching the problem. But once the interview starts, that wide view becomes narrower.
I find one possible direction and start following it.
Then everything else begins to disappear.
It's almost like having a map before entering a room and then forgetting that the map exists once you start walking.
That happened during both interviews in different ways — during implementation in the first, and during the design discussion in the second.
I don't think the problem is that I don't know the alternatives. The problem is that I'm not accessing them quickly enough while under pressure.
That is a different kind of preparation.
It isn't another topic I need to study. It's a thinking muscle I need to train.
Instead of immediately asking, "How do I solve this?", I need to create the habit of first asking, "What are the possible ways I can approach this, and what does this situation actually require?"
That small pause could change the entire interview.
And this is where I can see the difference between knowing something and being able to use it in a real situation.
The good part is that the productivity system I built over the last couple of weeks is finally giving me the space to work on these things. I'm consistently entering each quadrant with a fresh mindset, and that itself has made this week feel incredibly productive.
There are still gaps — DSA patterns are one of them, and now this broader thinking under pressure is another.
Next week, there are currently no interviews scheduled, although a few processes are still pending. That uncertainty is uncomfortable, but it also gives me some time to work on these weaknesses instead of simply preparing for the next calendar invite.
For the weekend, I'm going to step back a little.
Then Monday, we start again — with a clearer understanding of what needs fixing.
Day 33 done.
Comments