The interview went well, mostly. Then came the question about how two parts of a system should handle a message that arrives twice. You knew you had read about it. Nothing came out except a few half sentences and a long pause. You have replayed that moment on every walk since, and you still feel your face get hot.
Before you file it under embarrassment, treat it as information. A question you could not answer under pressure is one of the clearest views you will ever get of where your knowledge is thin. Very little at work shows you that so precisely.
Start by working out what kind of gap it was. Sit down the next day, with no clock and no audience, and try the question again on paper. If you can answer it comfortably, the problem was not knowledge. It was recall under stress, and that is a different thing to practise. If you still get stuck, you have found something you only half learned, and now you know exactly where to start.
For a real knowledge gap, go back to the idea underneath the question, not just the answer to it. Read about why the problem exists, find an example in a system you know and try to explain it in your own words. The goal is to understand it well enough that a differently worded version would not catch you out.
For a recall gap, practise out loud. Explain the topic to a friend, or to an empty room, while a timer runs. Thinking aloud with someone watching is a skill, and like any skill it improves with repetition rather than more reading.
Notice whether this is a pattern. If every interview stalls on the same area, it is worth a proper month of study. If it was one unlucky question, let it go after a week.
And be kind about the pause. Interviewers see people freeze all the time, and many of them care more about how you recover than whether you knew instantly. Next time, saying I want to think about this for a moment, and then thinking out loud, will serve you better than the silence did.
– Asael Shinder
Top comments (0)