Financial Analyst interview scorecard template
A structured scorecard for interviewing a Financial Analyst: six weighted competencies, what a 1 and a 5 actually look like, and questions that surface evidence instead of opinions. Print it, or copy it into your ATS.
The Financial Analyst scorecard
| Competency | Weight | Score 1 — what it looks like | Score 5 — what it looks like |
|---|---|---|---|
| Forecast construction and driver logic Whether a forecast is built from operating drivers the business can act on, rather than from last year plus a growth percentage. | 22% | Grows every line by a single rate and cannot say which assumption, if wrong, would move the bottom line the most. | Names the three or four drivers the model actually turns on, where each number came from, and which one they got wrong last cycle. |
| Variance analysis that explains causes Whether the candidate can trace a gap between plan and actual back to a business event, instead of restating the difference in currency. | 18% | Reports that revenue came in under plan by a percentage and stops there, or attributes every gap to timing without checking. | Splits a variance into volume, price and mix, points to the operating event behind the largest piece, and says who confirmed that reading. |
| Model construction and auditability Whether a model can be opened by someone else and traced: separated inputs, no hardcoded numbers inside formulas, checks that catch breaks. | 16% | Describes their models as complex and cannot say where the assumptions live or how someone else would find a broken link. | Separates inputs from calculations, keeps a check row that must tie to zero, and describes an error a check caught before the model went out. |
| Business partnering and decision influence Whether analysis reaches the person who decides in a form they can act on, which determines if the work changes anything at all. | 16% | Describes the deliverable they produced but cannot say who read it or what decision it changed afterward. | Names the decision, the recommendation they made, who pushed back and on what grounds, and what the business chose in the end. |
| Scenario and sensitivity judgment Whether scenarios are built around what could actually break the plan, or reduced to an optimistic and a pessimistic column beside the base case. | 16% | Produces best, base and worst cases defined by moving every input up or down by the same arbitrary percentage. | Builds scenarios around a named risk with a trigger attached, and states the level at which the business would need to act. |
| Data sourcing and reconciliation to the books Whether analysis numbers tie back to the accounting system, which decides if a finding survives its first challenge from finance leadership. | 12% | Pulls figures from a dashboard or a shared file without knowing how they were built or when the source was last refreshed. | States where each figure came from, ties the total back to the reported result, and explains any reconciling difference before being asked. |
Weights sum to 100. Agree them before the first interview, not after — adjusting weights once you have scores is how a panel rationalises a favourite.
Questions that surface evidence
Each one asks for something that already happened, in enough detail to verify. Hypotheticals reward rehearsal, not track record.
- Take a forecast you owned. Which three assumptions did the result actually turn on, where did each number come from, and which one turned out wrong?
- Describe the largest variance to plan you had to explain. How did you split it, and what was the business event behind the biggest piece?
- Tell me about an analysis of yours that changed a decision. Who decided, what did you recommend, and who argued against it and why?
- What error has a model of yours produced that reached someone else? How was it found, and what check did you add so it could not repeat?
- Walk me through how you reconciled a number in your analysis to the reported financials. What difference remained, and how did you explain it?
Red flags
- Every forecast is described as accurate, with no cycle where the number missed and no explanation of why.
- Explains variances only as timing differences, without ever having verified that reading against operations.
- Cannot name a single recommendation of theirs that leadership rejected or overruled.
- Lists modeling tools fluently but goes vague when asked where the assumptions in a model lived.
How to use this scorecard
- Agree the weights with the panel before anyone interviews, and write them down.
- Every interviewer scores every competency independently, adding a note that quotes what the candidate actually said.
- Compare scores before discussing them. Discussing first anchors the panel on whoever speaks loudest.
Build a custom scorecard → · Boolean string to source a Financial Analyst →
Frequently asked questions
What should a financial analyst interview scorecard include?
Weighted competencies that match how the role creates value: forecast construction and driver logic, variance analysis, model auditability, business partnering, scenario judgment, and reconciliation to the books. Weight forecasting and variance work highest, since that is what the role produces every month. Anchors matter here because almost every candidate will say they are strong in Excel, and the anchor is what turns that claim into an observable difference.
Should a financial analyst interview include a modeling test?
A short exercise beats a long one. Give a small dataset and ask the candidate to build a forecast and explain the drivers out loud, or hand them a model with a planted error and ask them to find it. Both take under an hour and reveal structure, checks and reasoning. A multi-day case study mostly measures who had a free weekend.
How do you compare a financial analyst from a large corporate to one from a startup?
The two build forecasts under different constraints, so compare the reasoning rather than the polish. A corporate analyst may own one line with strong controls, while a startup analyst may own the whole model with none. Ask both for the assumption that drove the result and what happened when it was wrong, and score them on the same competencies with the evidence cited next to each rating.
When the stakes are a real hire, use evidence
These tools are quick heuristics. Verdict reads the CV against your job description and scores six dimensions with verbatim quotes as evidence — a hiring document you can defend.