No matter how thoroughly you build your Story Bank and polish answers for teamwork, failure, leadership, and technical challenges, some question will land that you did not prepare for. Something like:

"Tell me about a time you had to work with a vague or incomplete specification."

You run through your stories. The "API Optimization" one and the "Database Failure" one are both close, but neither is a clean fit, and the silence is starting to stretch.

This moment is unavoidable, and how you handle it can matter as much as the answer itself. This chapter is about what to do in it: moving past reciting prepared answers into a harder skill, thinking on your feet.

The first instinct is to start talking right away to fill the silence. Resist it. An instant, rambling answer is worse than a thoughtful, delayed one.

When a curveball question lands, buy yourself a little room before answering.

Pause

Take a deliberate breath. A 5-10 second silence is not awkward; it's professional. It shows you are taking the question seriously.

Acknowledge

Verbally acknowledge the question. This buys you more thinking time and shows you were listening.

Clarify When Needed

If the question is ambiguous, ask for clarification. This ensures you answer the right question and gives your brain even more time to search for an answer.

The PAC method buys you 15-30 seconds of thinking time while looking composed, which is often all you need to find a story.