The finance and accounting interview prep guide that covers all three rounds

Finance interviews mix two very different skills in one loop: the technical ability to actually reason through numbers, and the judgment to explain a decision to someone who isn't an accountant. Candidates who drill technical questions in isolation often freeze the moment a question wraps a real tradeoff around the math. Here's how a typical loop breaks down and how to prepare for each part of it.

The three rounds you'll actually face

Most finance and accounting loops collapse into three buckets: a technical round (walk through a financial statement, reconcile a discrepancy, build or interpret a model, or explain a standard like revenue recognition), a case or scenario round (a budget is over, a forecast is off, a close is late — how do you handle it), and a behavioral round (how you've handled pressure, an error, or a disagreement with a stakeholder about the numbers). Roles closer to FP&A or corporate finance lean harder on the case round; roles closer to audit or controllership lean harder on the technical one, but nearly every loop touches all three.

A framework for working a case question live

1. State the goal before the math. Clarify what the number actually needs to support — a board decision, a hiring freeze, a pricing change — before building toward it. The same numbers answer different questions differently.
2. Show the structure, not just the answer. Narrate how you're breaking the problem down (revenue drivers, cost buckets, the assumption you're making) before you land on a figure. Interviewers are scoring the reasoning, not just the final number.
3. Flag your assumptions explicitly. Every real-world number rests on an assumption — a growth rate, a churn figure, a one-time item you're excluding. Naming it shows you know where the number could be wrong.
4. Connect the number back to a decision. Finish by stating what the number implies for the actual business question, not just the calculation itself.

The common failure mode isn't arithmetic error — it's silence. A candidate who gets the number right but never explains the reasoning out loud is much harder to trust with judgment calls than one who talks through an imperfect but well-reasoned approach.

A worked example: explaining a budget variance

"Before I explain the variance, I'd confirm what decision this is feeding — if it's about next quarter's headcount plan, that changes what matters versus if it's just a close-the-books explanation. Assuming it's the former: the overage is mostly in marketing spend, and I'd split it into the part that's a timing shift — a campaign that was planned for next quarter and got pulled forward — versus the part that's a real overrun. The timing piece isn't a problem; it nets out next quarter. The real overrun I'd flag honestly rather than bury in the explanation, and I'd tie it back to whether it drove incremental revenue, because that's what actually matters for the headcount decision, not the variance number by itself."

Notice the clarified goal, the explicit breakdown (timing versus real), and the connection back to the actual decision — all stated out loud rather than left for the interviewer to piece together from a number alone.

Preparing for the technical and behavioral rounds

Technical questions reward fluency you can only get from practice under time pressure — walking through a statement or a reconciliation at the speed of conversation is a different skill than doing it alone with no clock running, so rehearse out loud, not just on paper. For the behavioral round, build a small bank of 6-8 real stories in advance covering a time you caught an error, a disagreement about a number with a stakeholder, and a deadline you nearly missed — see behavioral interviews and the STAR method for how to structure each one so you're not improvising the timeline live. For case-heavy loops, understanding the company's actual business model and recent numbers — not just generic finance theory — pays off directly in how grounded your assumptions sound; see how to research a company before an interview.

Common mistakes to avoid

• Going silent while calculating. Interviewers can't score reasoning they can't hear; narrate your structure as you work, not just the final number.
• Hiding or burying a real problem. Spinning a genuine overrun as a non-issue reads as evasive, not polished — flag it honestly and explain the plan.
• Skipping the "so what." A correct number with no link back to the actual business decision leaves the interviewer to guess why it matters.
• Memorizing formulas without the underlying logic. A question that tweaks a standard case exposes memorization fast; understand why the formula works, not just its shape.
• Generic behavioral stories. Vague answers about "attention to detail" without a concrete error, catch, or outcome don't differentiate you.

Bottom line

Finance interviews test reasoning under pressure, not just arithmetic. State the goal before the math, narrate your structure, flag your assumptions, and connect every number back to a decision — doing that consistently across technical, case, and behavioral rounds matters more than speed alone.

Related: Behavioral interviews and the STAR method · Data analyst / scientist interview prep · How to research a company before an interview