The thirty-second answer

There is a specific way that competent people fail finance interviews in Nairobi.

They are asked something like "what do you make of the CBK holding rates?" — a question they genuinely have views on — and they produce ninety seconds of accurate, unstructured material that arrives nowhere. The interviewer nods, writes something short, and moves on.

The knowledge was there. The delivery was not. That is a fixable problem, and it is almost entirely a matter of structure.

The shape

Every good answer to a markets or business question has four moves. In this order.

1. The claim. One sentence. State your position immediately. Not background, not throat-clearing, not "well, it's complicated." The interviewer needs to know within five seconds whether you have a view.

"It has been defensible so far, but it's getting harder to justify."

2. The mechanism. Two or three sentences. This is where the marks are. Explain how one thing causes another. Not what happened — why it follows.

"Holding at 8.75% while inflation went from 4.4% to 6.6% means the real policy rate has roughly halved. So policy has actually loosened without CBK ever voting to cut."

3. The evidence. One or two numbers. Specific, sourced, and used to support the mechanism rather than decorate it. Two well-chosen figures beat six recited ones every time.

"Private sector credit growth was 8.1% in March, up from 7.4% in February."

4. The condition. One sentence. What would change your mind. This is the move most candidates skip and it is the one that separates a student from an analyst — because it demonstrates you know your view is contingent on something.

"I'd want to see the core inflation figure in the next print. If core starts moving, this stops being a supply story."

Claim, mechanism, evidence, condition. About thirty seconds.

Why thirty seconds

Long enough to demonstrate you can think. Short enough that the interviewer stays engaged and can follow up — and the follow-up is where you actually get assessed.

An answer that runs two minutes does not sound thorough. It sounds like someone who cannot prioritise, which is a real and disqualifying observation about how you would work.

The three failure modes

The data dump. Reciting figures without a mechanism connecting them. Sounds prepared, reads as memorised. If you cannot explain why a number matters, it is not helping you.

The fence-sitter. "There are arguments on both sides." Interviewers hire people who can commit to a view and then update it. No view is harder to hire than a defensible wrong one.

The overreach. Claiming certainty you do not have, or citing a number you are not sure of. A confident wrong figure is far more damaging than an honest "I'd want to check the exact number, but directionally it was rising." Interviewers remember bluffing. They do not mind not-knowing.

How to practise this without a partner

Pick any story in the Brief. Give yourself two minutes to read it and thirty seconds to answer it out loud, using the four moves in order.

Out loud. Not in your head. The gap between knowing something and being able to say it is almost entirely a mouth problem, and it only closes with reps.

Record yourself once. You will hate it, and you will fix three things immediately that you would never have noticed otherwise.

Do it twice a week for a term and you will be visibly better than people who know more than you.