01 / 07
THE FOUNDATION
What is PACE and why does it matter?
STAR helps you build a strong answer when you already know what you want to say. PACE is for the moment you do not. It is what you reach for when a question catches you off guard.
Interviewers are not only listening to the content of your answer. They are reading real time signals that have nothing to do with what you actually say. Does this person pause and think, or do they freeze? Can they ask a clarifying question naturally, or does it read as stalling? When a question is poorly worded or ambiguous, do they make a reasonable interpretation and run with it, or do they get stuck? These signals are being read whether you are aware of it or not, often within the first few seconds after a hard question lands.
WHY TOUGH OR UNEXPECTED QUESTIONS GET ASKED
Some interviewers ask questions with no obvious right answer on purpose. This is rarely a trick for its own sake. A few honest reasons it happens: the role is high stakes or requires staying calm under pressure, such as client facing work, leadership, or anything involving incomplete information and fast decisions. The role requires composure in front of others, where falling apart visibly would be a real problem. Or the interviewer is testing how you think when there is no script to follow, because the job itself often will not come with one either. Once you understand this, a hard question stops feeling like an unfair trap and starts feeling like a specific, recognisable kind of test you can actually prepare a method for.
PACE gives you that method. It is not a way to build a polished answer in advance. It is a way to stay steady and think clearly in the two seconds after a question lands, when you do not yet know what you are going to say.
PACE IS NOT A REPLACEMENT FOR STAR
STAR structures an answer once you know what story or example you are telling. PACE gets you to the point where you have something to say at all, especially when there is no obvious example to draw on. Use PACE first to find your footing, then use STAR if the question turns out to need a structured story.
02 / 07
THE FRAMEWORK
The four parts in detail
Four steps, run in the space of a few seconds. The goal is not to follow them mechanically. The goal is for them to become automatic.
P
PAUSE
Let a beat of silence happen before you speak.
A
ANCHOR
Understand the question, and what it might really be testing.
C
CONNECT
Find the nearest thing you know, and build from there.
E
ENGAGE
Speak steadily, and keep your reasoning visible.
P, PAUSE
A short pause before you answer reads as thoughtful, not weak. Most people feel pressure to fill silence immediately, and that pressure is exactly what causes rambling or a panicked, unfinished answer. It is completely acceptable to say "that's a good question, let me think for a moment" before responding. Interviewers read this as composure.
A, ANCHOR HAS TWO LAYERS
The first layer is simple comprehension. Make sure you have actually understood the question. If it is unclear, ask. Do not answer the question you assumed was coming. The second layer happens in the same breath: take a half second to consider why this question might be asked at all, given the role you are sitting for. A question about a colleague's misconduct is rarely just about that colleague. It is usually testing whether you can be trusted with responsibility. A question asking you to estimate a number is rarely about the number. It is usually testing whether you can reason through uncertainty in a structured way. You will not always know the exact reason a question was asked, and that is fine. Even a rough sense of intent will shape a stronger answer than ignoring it completely.
C, CONNECT WORKS TWO WAYS
Sometimes you can connect to a past example, the same way STAR questions work. Other times, especially with curveball or hypothetical questions, there is no past example to draw on. In that case, connect to a principle instead, something you understand and can reason from, even if you have never faced this exact situation. Either way, the move is the same: find the nearest legitimate starting point, not the perfect answer, and build forward from there.
E, ENGAGE MEANS STAYING VISIBLE
Speak at a steady pace once you start, and let your thinking stay visible rather than disappearing into a polished final answer. Phrases like "I'm thinking about this in two ways" or "the way I'd approach this is" keep the interviewer inside your reasoning, not just listening to a conclusion. Interviewers are often assessing how you got to an answer as much as the answer itself. Hiding your process gives them nothing to actually evaluate except how smooth you sound.
03 / 07
WORKED EXAMPLE
The ethical dilemma question
A question with no clean answer, used to see how you reason through competing responsibilities in real time.
THE SITUATION
You are interviewing for a Finance Officer role. The interviewer asks: "If you found out a close colleague was falsifying expense reports, what would you do?"
A Finance Officer has regular access to financial processes and is often the last line of defence against exactly this kind of misconduct. The interviewer is not testing whether you know a textbook correct answer. They are testing whether you will actually act with integrity when loyalty to a colleague and responsibility to the organisation come into direct conflict, because in this role, that conflict is not hypothetical. It will happen eventually.
PAUSE
Take a beat. This is not a question to answer instantly. A short pause here signals you are taking it seriously, not stalling.
ANCHOR
Understood literally, the question asks what action you would take. Understood for intent, the role handles money and trust directly, so the interviewer is really asking whether you will act on integrity even when it is personally uncomfortable, not just whether you know the policy.
CONNECT
There may be no past example of this exact situation. Connect to a principle instead: organisations rely on people noticing and reporting issues internally, through the right channel, rather than staying silent to protect a relationship. Build the answer from that principle out loud. "I'd think about this in terms of my responsibility to the organisation versus my relationship with a colleague, and the way I'd reconcile that is..."
ENGAGE
"I'd want to be fair to my colleague by raising it with them directly first, in case there's an explanation I'm missing. But if it was confirmed, I would escalate it through the appropriate channel, because protecting the integrity of the finance function has to come before protecting a friendship in that situation." Notice the reasoning stays visible the whole way through, not just the final position.
04 / 07
WORKED EXAMPLE
The estimation question
A question with no factual answer expected, used to see how you structure reasoning under uncertainty.
THE SITUATION
You are interviewing for a Business Analyst role. The interviewer asks: "How would you estimate the number of people who fly out of Brunei International Airport in a year?"
A Business Analyst will regularly be asked to produce a reasonable estimate with incomplete data, for things like market sizing, demand forecasting, or budget planning, often without perfect information available. The interviewer does not actually care about the final number. They are testing whether you can build a logical chain of reasonable assumptions out loud, in a structured way, under time pressure. That is the actual skill the job requires every week.
PAUSE
Resist the urge to guess a number immediately. A guess with no reasoning behind it fails the test even if it happens to be close.
ANCHOR
Understood literally, this asks for a method to reach a number. Understood for intent, this is testing structured thinking under uncertainty, the exact skill needed for forecasting and planning work in this role.
CONNECT
There is no memory to draw on here, so connect to a reasoning principle: break an unfamiliar number into smaller, more knowable pieces, then build up. "I'd start by thinking about how many flights typically depart per day, then estimate average passengers per flight, then multiply that out across a year."
ENGAGE
"If I think about it as maybe 15 to 20 flights a day on average, with around 150 passengers each, that's roughly 2,500 to 3,000 passengers a day, so somewhere around 1 million a year. I'd want to check that against any published tourism or aviation figures to sense check it, but that's the structure I'd use to get there." The number is almost irrelevant. The visible structure is the entire answer.
WHY BOTH EXAMPLES MATTER
These two questions test different things. The ethical dilemma tests values reasoning under conflicting loyalties. The estimation question tests structured logical reasoning under uncertainty. Most curveball questions you will face fall into one of these two categories, or a close variation of one. Recognising which type you are facing helps you connect to the right kind of starting point faster.
05 / 07
COMMON FAILURE PATTERNS
What breaks composure, and how to fix it
Most composure failures follow a small number of recognisable patterns. Knowing them in advance makes them easier to catch in yourself.
RUSHING TO FILL SILENCE
Speaking immediately, before you have any direction, just to avoid the discomfort of a quiet pause. This almost always produces a rambling opening that you then have to recover from mid sentence. The fix: treat the pause as expected and useful, not as a failure. Interviewers are far more comfortable with silence than candidates assume.
FREEZING COMPLETELY
Going blank and staying silent for too long, with no visible sign you are working through the problem. The fix: narrate that you are thinking. "Let me take a moment to think this through properly" turns a freeze into a visible pause, which reads completely differently to the interviewer even though the silence itself is similar in length.
TALKING IN CIRCLES
Restating the question or your own opening sentence repeatedly without ever moving the answer forward. This usually means you started speaking before you had connected to anything solid. The fix: if you notice yourself circling, pause again deliberately and say "let me restart that" before continuing with a clearer direction.
ABANDONING A THOUGHT MID SENTENCE
Starting down one line of reasoning, losing confidence in it, and jumping to a different one without finishing the first. This reads as scattered thinking even if either direction alone would have been fine. The fix: finish the thought you started, even briefly, before introducing a second angle. "One way to think about this is X. Another way is Y" is far stronger than abandoning X halfway through.
THE UNDERLYING PRINCIPLE
Every one of these patterns comes from the same root cause: searching for a perfect, ready made answer instead of building from the nearest thing you actually know. You are rarely starting from zero. You are usually one connection away from something you already understand. PACE works because it gives you somewhere to start, so you stop searching for perfect and start building from real.
06 / 07
PRACTICE
Practice questions
No worked answers here. Read each question, run it through PACE out loud, and notice where you naturally pause, where you connect to, and how visible your reasoning stays.
ETHICAL OR VALUES QUESTIONS
"Your manager asks you to do something you believe is against company policy. What do you do?"
"You notice a teammate taking credit for your work in a meeting. How do you handle it?"
"You are given a deadline you know is unrealistic. What is your first move?"
ESTIMATION OR STRUCTURED REASONING QUESTIONS
"How many coffee shops do you think operate in Bandar Seri Begawan?"
"How would you estimate the amount of paper a mid sized office uses in a year?"
"How many working hours does a typical retail store have in a month?"
HYPOTHETICAL PRESSURE QUESTIONS
"If two senior people gave you conflicting instructions, what would you do?"
"A client is upset and demanding an immediate answer you do not have. What do you say?"
"You realise mid project that the approach you chose is not working. What now?"
HOW TO PRACTISE THIS PROPERLY
Say your answer out loud, not silently in your head. Time yourself. Notice if you rushed the pause, skipped the intent check in Anchor, or hid your reasoning instead of speaking it. The goal is not a polished answer to memorise. The goal is to notice your own patterns and correct them before they show up in a real interview.
07 / 07
RESPONSE BUILDER
Build your own PACE responses here
Choose a few practice questions from the previous page and work through them here. Write what you would actually say at each step, not what sounds impressive.
BEFORE YOU FINISH
Read each response back. Did you pause before answering, or rush in? Did you check what the question was really testing? Did you build from something real, an example or a principle, rather than searching for a perfect answer? Did your reasoning stay visible the whole way through? If yes to all four, you have a strong PACE response.