What a finance interview is actually testing

The mistake almost everyone makes

Candidates prepare a list of likely questions and rehearse an answer for each one. It feels like diligent preparation. It usually produces a candidate who performs well for about ninety seconds and then falls apart.

The reason is simple: interviewers do not grade the first answer. They grade what happens after they ask "why?"

What the technical question is really for

Take a standard opener — how the three financial statements connect. A memorised answer recites the links. It sounds fine.

Then comes: "So if depreciation goes up by 10, walk me through it."

Now the memorised answer is useless, because the question is not testing whether you know the definition. It is testing whether you understand the mechanism well enough to run it forward on a case you haven't rehearsed.

That is the whole game. Technical questions in finance interviews are almost never knowledge checks. They are reasoning checks wearing a knowledge check's clothes. The interviewer wants to see whether there is a model in your head or a script.

Three things they are actually assessing

Can you reason under mild pressure? Not "do you know the answer" but "can you construct one while someone watches". These are different skills, and only the second one is the job.

Do you know what you don't know? A candidate who says "I'm not certain, but here is how I'd work it out" outperforms one who bluffs confidently and is wrong. In audit and finance, a person who bluffs is a liability — that instinct is exactly what the interview is screening for.

Would you be tolerable at 9pm on a deadline? Unspoken, always assessed. Much of this work happens in small teams under time pressure. "Pleasant to be around when tired" is a real criterion, and interviewers form that judgement whether or not they admit it.

How to prepare so it holds up

Learn mechanisms, not answers. For each core concept, be able to explain why it works that way, not just what it does. The test: can you explain it two different ways? If only one phrasing works, you memorised a sentence rather than learning an idea.

Rehearse the follow-up, not the answer. After preparing any answer, ask yourself what the obvious "why" is — then answer that too. Go two levels deep. That is where interviews are actually won.

Have three real stories, properly built. One where you found a problem, one where you got something wrong, and one where you worked with someone difficult. Real situations, with specifics. Every behavioural question is a variation on these three.

Be honest about the gap. If you don't know something, say so and then show how you'd approach it. This reads as maturity, not weakness. Bluffing reads as risk.

The questions you ask

The end of the interview is not a formality. Asking "what does someone need to get right in their first six months here?" tells them you are thinking about doing the job, not just getting it. Asking "what's the training like?" tells them you are thinking about being trained.

Ask about the work.

The point

Preparation that consists of memorising answers optimises for the wrong ninety seconds. Preparation that builds real mechanisms — and then stress-tests them with your own follow-up questions — holds up for the whole conversation. That is the difference between sounding prepared and being prepared.