A financial analyst interview tests three things in sequence: whether you know the technical mechanics (modeling, accounting, valuation), whether you can reason through a business problem out loud, and whether you communicate numbers clearly to people who will act on them. Most candidates over-prepare the trivia and under-prepare the reasoning. The fix is to drill the core technicals until they're reflexive, then practice walking through a case and a behavioral story the way you'd brief a manager — structured, quantified, and concise. Below are the questions you'll actually face, grouped into technical, case, and behavioral, with how interviewers grade your answers.
The three layers interviewers grade
Finance interviews move from mechanics to judgment to communication. You can be perfect on the technicals and still lose on a case if you can't structure your thinking out loud, or on behavioral if your stories have no numbers. Prepare all three deliberately.
Technical questions
These are the mechanics. They should be reflexive, because hesitation here reads as a gap. Common ones:
- Walk me through the three statements. Income statement (profitability over a period), balance sheet (snapshot of assets, liabilities, equity), cash flow (reconciles net income to cash). Be ready for "how does a $10 increase in depreciation flow through all three?" — the canonical follow-up.
- What's the difference between accrual and cash accounting? Accrual recognizes revenue and expenses when earned or incurred; cash recognizes them when money moves. Tie it to the matching principle.
- How do you build a DCF? Project free cash flows, discount at WACC, add a terminal value, sum to enterprise value, bridge to equity value. Know what moves the output most (growth, margin, discount rate, terminal assumptions).
- How do you analyze a budget variance? Split it into price and volume, isolate the drivers, separate one-time from structural, and translate it into an action. This is the bread-and-butter FP&A question.
- What makes a clean model? Separated inputs, no hardcoded numbers inside formulas, consistent signing, clear labeling, and a checks row that flags when the balance sheet doesn't balance.
Case questions
Here they hand you a business situation and watch how you think. There's rarely one correct answer; they grade structure, the data you'd reach for, and whether you land on a defensible recommendation. Typical prompts:
- A product line is running 15% under its revenue budget. How do you find out why?
- Should the company build a capability in-house or buy it? How would you frame the analysis?
- Our forecast keeps missing high. What would you check, and how would you fix the process?
- A department wants to add five headcount. Walk me through how you'd evaluate the request.
Answer in four beats: state your approach, name the data you'd pull, do the rough math out loud, then give a recommendation with its caveats. For practical framing on the role's day-to-day reasoning, Indeed's career guides on financial analyst interview questions walk through common case and technical prompts with sample structures.
How interviewers grade technical vs. case answers
| Dimension | Technical question | Case question |
|---|---|---|
| What they test | Whether you know the mechanics cold. | Whether you can structure ambiguity and reason to a decision. |
| A strong answer | Correct, fast, with assumptions stated. | Structured approach, rough math out loud, clear recommendation with caveats. |
| A weak answer | Hesitation, hand-waving, or a memorized line you can't extend. | Jumping to a conclusion with no framework, or freezing on the ambiguity. |
| How to prep | Drill until reflexive — flashcards, repetition. | Practice talking through 5 to 10 cases out loud, end to end. |
Behavioral questions
Finance behavioral questions reward the same thing the resume does: quantified, concise stories. Lead with the result, keep it structured, and don't ramble. Common prompts:
- Tell me about a time your analysis changed a decision.
- Describe a time you found an error in someone's numbers. How did you handle it?
- Walk me through a deadline you hit under pressure during close or planning.
- Tell me about a time you had to explain a financial result to a non-finance audience.
Structure each answer as situation, what you did, and the quantified result — "the variance was $2.4M, I traced it to two vendors, and we recovered the spend within the quarter." The number is what makes a finance behavioral answer credible. The BLS Occupational Outlook for financial analysts is a useful reference for the responsibilities your stories should illustrate.
The honest summary
Financial analyst interviews reward reflexive technicals, structured case reasoning, and quantified behavioral stories. Drill the three statements and core valuation until they're automatic, practice talking through five to ten cases end to end, and rehearse two or three behavioral stories that each land on a number. Match the depth to the track the role sits in, state your assumptions out loud, and you'll read as someone who can do the job — which is the only thing they're trying to find out.
Common questions
- What technicals must I know cold for a financial analyst interview?
- The three financial statements and how they connect, how a change flows through all three (the classic "walk me through what depreciation does"), the basics of valuation (DCF, comps, precedent transactions), working capital, and core Excel and accounting concepts like accrual versus cash and the matching principle. For FP&A specifically, be fluent in variance analysis, budgeting, and forecasting methods.
- How do I answer "walk me through the three statements"?
- Briefly and in order. The income statement shows profitability over a period; the balance sheet is a snapshot of assets, liabilities, and equity at a point in time; the cash flow statement reconciles net income to actual cash and ties them together. Then be ready for the follow-up: how a $10 increase in depreciation flows through all three.
- What does a financial analyst case interview look like?
- You're given a business situation — a product line missing budget, a make-versus-buy decision, a forecast that's drifting — and asked how you'd analyze it. They're grading structure and judgment, not a single right answer. State your approach, name the data you'd pull, do the rough math out loud, and land on a recommendation with the caveats.
- How technical is the Excel portion?
- Expect to discuss or demonstrate lookups (INDEX/MATCH or XLOOKUP), pivot tables, building a clean three-statement or scenario model, and good modeling hygiene — no hardcoded numbers inside formulas, clear input cells, consistent signing. Some firms run a timed live modeling test; for those, speed and structure both count.
Sources
Keep reading
How to answer "tell me about yourself"
Answer "tell me about yourself" with a 60-90 second present-past-future pitch tailored to the role. The structure, a before/after example, and what not to do.
What questions should I ask the interviewer?
The best questions to ask an interviewer, organized by who you are talking to. Questions that signal seriousness, surface red flags, and the ones to avoid.
How do I prepare for a behavioral interview?
Prepare for a behavioral interview with the STAR method, a bank of 6-8 stories mapped to common competencies, and practicing out loud. Examples included.
Software engineer interview questions
The real software engineer interview loop — phone screen, coding, system design, behavioral — with representative questions per stage and how to prep.