Recognition is not recall
When you read a strong answer, nearly every sentence feels familiar and clear. The text supplies hints, creating confidence that you know the topic. In an interview, those hints disappear, and a familiar subject can suddenly turn into a few disconnected phrases.
The only way to test your knowledge is to reproduce it before opening the answer.
Build your answer around a structure
A simple framework works for most technical questions:
- Give a concise definition.
- Explain the mechanism or causal relationship.
- Provide a practical example.
- Name a limitation or trade-off.
This structure does not turn your response into a memorized script. It helps you keep your train of thought and demonstrate depth gradually.
Assess the gap, not the delivery
If you explained the idea but missed an important limitation, mark the answer as partial. If you could not begin without a hint, choose “I don't know.” Self-assessment is not about giving yourself a score; it is about scheduling the next review correctly.
Review at intervals
Repeating an answer immediately only tests short-term memory. Return to the question the next day, then again after several days. The interval reveals whether the mental model remained and whether you can rebuild the explanation in your own words.
Cards are useful not because they shorten the material, but because they repeatedly put you in the position of answering independently.