Interview scorecard
Financial Analyst
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
Financial modeling
Builds clear spreadsheet models that link assumptions to outputs and can be tested and updated by others.
Questions
- Tell me about a financial model you built. How did you structure it?
- Walk me through how you tested that your model's results were correct.
- Tell me about a time a model needed major changes. How did you handle it?
1: Below the bar
Describes formulas but not structure. Mixes assumptions with calculations and cannot say how they checked the results.
3: Meets the bar
Describes a logical layout with separate assumptions. Checks totals and key outputs, and can update the model with some effort.
5: Above the bar
Explains a clean structure, tests with scenarios and cross-checks, documents assumptions, and shows how others could update it easily.
Data analysis
Turns raw financial data into clear findings that people can act on.
Questions
- Tell me about a time you found an unexpected pattern in a messy dataset. What did you do?
- Describe how you check that data is complete and reliable before drawing conclusions.
- Tell me about an analysis you presented to non-finance colleagues. How did you explain the findings?
1: Below the bar
Reports numbers without checking the source or asking what they mean. Cannot explain how they reached a conclusion.
3: Meets the bar
Cleans and checks data, finds the main drivers, and explains the result clearly. Needs some prompting to dig into surprises.
5: Above the bar
Tests data quality first, digs into surprises unprompted, and ties findings to a specific recommendation others acted on.
Forecasting
Projects future revenue and costs from stated assumptions, then updates the projection as results come in.
Questions
- Tell me about a forecast you built. How did you choose your key assumptions?
- Tell me about a time your forecast was off. What did you learn?
- How do you decide when to revise a forecast, and who do you tell?
1: Below the bar
Gives a single number with no stated assumptions. Blames outside events when the forecast misses and changes nothing afterward.
3: Meets the bar
Names key assumptions and compares results to forecast. Revises when asked, and explains misses with some reasons.
5: Above the bar
Ties each assumption to evidence and gives a range. Tracks misses, revises early, and tells stakeholders what changed and why.
Business understanding
Connects financial numbers to how the company earns money, spends it, and makes decisions.
Questions
- Tell me about a time you explained a change in results using what was happening in the business.
- Describe a time your analysis changed a business decision. What did you learn about the business?
- How does a company you know well make money, and what costs matter most?
1: Below the bar
Describes numbers without the business behind them. Can't say what drives revenue or cost, or who uses the analysis.
3: Meets the bar
Links results to main business drivers and names the decision the work supported. Understanding stays mostly within finance.
5: Above the bar
Ties numbers to customers, operations, and strategy unprompted. Anticipates what leaders will ask and recommends action with clear reasons.
Attention to detail
Catches errors in numbers and documents before others see them, using deliberate checks.
Questions
- Tell me about a time you caught an error in your own work. How?
- Describe the checks you run before sending a financial report to others.
- Tell me about a mistake that reached someone else. What did you change afterward?
1: Below the bar
Relies on rereading or luck to find errors. Can't describe a repeatable check or a lesson from a past mistake.
3: Meets the bar
Describes a few regular checks, like reconciling totals or reviewing formulas. Owns past mistakes and made one clear fix.
5: Above the bar
Describes a layered, repeatable checking routine, tailored to the risk of each report. Shares examples where it caught errors early and prevented repeats.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.