Interview scorecard for financial analysts, with anchors for each competency
On this page
- The six competencies this scorecard covers
- The scorecard at a glance: weights and anchors
- The scorecard template
- Anchors for each competency
- Two work samples to use in the interview
- A filled example
- Adjusting for seat and level
- Mistakes specific to scoring financial analysts
- Where this fits in the hiring process
- Questions people ask
A financial analyst interview scorecard should score six things: forecasting and modeling judgment, accuracy and checking, variance analysis and materiality, explaining numbers to people outside finance, sourcing and handling data in the team's tools, and integrity under pressure. Below is a copy-ready scorecard with example weights, what a 1, 3 and 5 look like on a 1–5 scale, two work samples and a filled example. Credentials such as the CFA charter or a FINRA registration are pass/fail checks when the seat requires them, never points on the scorecard.
The five points follow the 1–5 interview rating scale: 1 is no evidence or evidence of the opposite, 3 is a clear example that meets the bar for the level, 5 is rare. The layout comes from the interview scorecard template. The full FP&A loop, with a budget-versus-actual variance exercise and a decision rule, is in the interview guide for finance roles; this page adds the anchors interviewers score against and a different exercise, a forecast model review. The scorecard builder prints a 1–4 version if your team uses four points.
The six competencies this scorecard covers
- Forecasting and modeling judgment. Do they build forecasts from drivers they can name, know which assumption moves the answer most, and test it?
- Accuracy and checking. Do totals tie to the ledger or source before anything goes out, and do they catch errors in work they inherit?
- Variance analysis and materiality. Can they separate timing from real change, and pick the three variances that matter instead of explaining every line?
- Explaining numbers to non-finance partners. Can a department head act on what they write or say, and do they hold their ground with evidence when challenged?
- Data sourcing and tools. Do they know where each number comes from (ERP, planning system, data warehouse), and can they pull and shape it themselves in the tools the team uses?
- Integrity under pressure. What do they do when someone senior wants the numbers to look better than they are?
The scorecard at a glance: weights and anchors
Weights are an example for a mid-level FP&A analyst. Agree yours with the finance manager at intake and lock them before the first interview.
| Competency | Weight | 1 looks like | 3 looks like | 5 looks like |
|---|---|---|---|---|
| Forecasting and modeling judgment | 20% | Describes forecasts as last year plus a percentage, or only entered inputs into someone else's model. | Owned forecast lines with named drivers, can say which assumption mattered most and how sensitive the result was to it. | Designed the driver logic others submit into, ran scenarios that changed a decision, and can explain where the model was wrong and what they changed. |
| Accuracy and checking | 20% | Misses most planted errors in the work sample, or describes a wrong number reaching leadership with no change afterward. | Finds most planted errors and describes checks they run by habit (totals tie to the ledger, signs make sense, inputs traced to source). | Finds every planted error and describes a control they added to a shared process after catching an error that was not theirs. |
| Variance analysis and materiality | 15% | Explains variances as "timing" with no detail, or walks through every line with equal weight. | Separates timing from real change, picks the variances that matter by size and consequence, and names the cause. | All of a 3, plus a variance that changed the forecast or a business decision, with what they did to confirm the cause. |
| Explaining numbers to non-finance partners | 20% | Explanations use finance jargon with no "so what", or they defended a wrong number when challenged. | Presents regularly to a budget owner, leads with what it means and what to do, and answers a hard question or follows up with evidence. | Changed a leader's decision with evidence, and can describe adjusting the explanation for a skeptical audience. |
| Data sourcing and tools | 15% | Works only from reports others prepare and cannot say where the numbers originate. | Names the systems behind their numbers, pulls the data themselves in the team's tools, and reconciles before using it. | Fixed a broken data feed or rebuilt a manual report so it ties automatically, and documented it for others. |
| Integrity under pressure | 10% | Would change or hide a number because someone senior asked, or sees no problem with it. | Declines, explains why, and takes it to the right person (manager, controller) while offering an honest alternative. | Describes a real instance handled that way, without naming people, and what changed in the process afterward. |
A 1 on integrity is a no whatever the total. If the guide's variance exercise is also in the loop, let it own the variance row and use the model review below for forecasting and accuracy, so no single exercise scores everything. How to set and lock weights is in weighted interview scorecard.
The scorecard template
Candidate: [name] Role: [FP&A / business unit / investment / credit analyst], [level]
Interviewer: [name] Stage: [screen / technical / model review / budget owner]
Pass/fail (checked before scoring)
Required credential or registration, verified with the issuer: [ ] yes [ ] n/a
Close or budget-season hours as stated in the job description: [ ] meets [ ] does not
Forecasting and modeling judgment (20%) Score 1-5: [ ]
Evidence: [lines owned, drivers named, assumption that mattered most]
Accuracy and checking (20%) Score 1-5: [ ]
Evidence: [model review: _ of 3 issues found; checking habits]
Variance analysis and materiality (15%) Score 1-5: [ ]
Evidence: [variance explained, timing vs real, consequence]
Explaining numbers to non-finance (20%) Score 1-5: [ ]
Evidence: [audience, hardest question, how answered]
Data sourcing and tools (15%) Score 1-5: [ ]
Evidence: [systems named, what they pulled and reconciled]
Integrity under pressure (10%) - a 1 is a no Score 1-5: [ ]
Evidence: [response to the accrual scenario]
Weighted score: sum of (weight x score) / sum of weights scored = [ ]
Recommendation: [Strong yes / Yes / No / Strong no]
Anchors for each competency
The table gives the 1, 3 and 5. Here is the question that tests each row and what a 2 and a 4 sound like.
Forecasting and modeling judgment
Ask: "Walk me through a forecast you owned. What drove it, and which assumption would have changed the answer most if it were wrong?"
- 2: Maintained a model someone else designed; can describe the inputs but not why the drivers were chosen.
- 4: Built the driver logic for their lines and ran at least one sensitivity that someone used.
Accuracy and checking
Ask: "Tell me about a number you sent out that turned out to be wrong. How was it caught, and what do you check now?" Then the model review below. More in interview questions for attention to detail.
- 2: Finds one planted issue; the checking habit is general ("I double-check everything").
- 4: Finds all three, or two plus a precise question about the third, and names a check that would have caught their own past error.
Variance analysis and materiality
Ask: "Tell me about a month when actuals missed the forecast badly. What caused it, and what did you change?"
- 2: Found the cause but did not separate a one-time item from a trend, or the forecast was not updated.
- 4: Separated timing from real change, updated the forecast and told the budget owner what it meant for the rest of the year.
Explaining numbers to non-finance partners
Ask: "What is the hardest question a leader has asked you about your numbers, and what did you do?" Better still, let the budget owner run this row.
- 2: Sends reports to leaders but rarely discusses them, or answered the hard question with jargon.
- 4: Presents regularly, answers in the leader's terms, and admits when a follow-up is needed instead of guessing.
Data sourcing and tools
Ask: "Where did the numbers in your last forecast come from, and what did you do when a source was wrong?"
- 2: Knows the report names but relies on someone else to pull and fix the data.
- 4: Pulls and reconciles their own data and has fixed at least one recurring source problem.
Integrity under pressure
Ask: the accrual scenario below. More in interview questions for integrity.
- 2: Would not do it, but would not raise it with anyone either.
- 4: Declines, involves the controller or accounting team, and drafts an honest variance explanation for the department head.
Two work samples to use in the interview
Both are invented and the same for every candidate. Tell candidates in advance whether they may use their own laptop and how to ask for an adjustment; see ADA accommodations in interviews. If you send either as a take-home instead, read how to evaluate a take-home assignment first.
Forecast model review (20 minutes, then 10 minutes of discussion). A one-tab revenue forecast for an invented product line: units times price by quarter, a growth rate and a churn assumption. Plant three issues: a hard-coded number typed over a formula in the third quarter, a growth rate applied twice to the same line, and a churn assumption with no source. Brief: "Your manager wants this in tomorrow's leadership pack. Review it. What would you fix, what would you ask about, and which assumption matters most?"
What to listen for: how many issues they find and how (tracing formulas, checking that quarters sum to the year); whether they ask where the churn rate came from rather than replacing it with their own guess; and whether they test which assumption moves the answer most before saying so. This scores forecasting judgment and accuracy.
Accrual pressure scenario (10 minutes, verbal). "A consultant finished a project for the marketing department in December. The invoice has not arrived yet. The head of marketing asks you not to accrue the cost so the department finishes the year on budget, and says it will 'come through next year anyway'. What do you do?"
What to listen for: that the cost belongs to the period when the work was done under the company's accrual policy; that they would raise it with their manager or the controller rather than decide alone or simply refuse; and that they offer the department head something useful, such as a variance note explaining the overrun. This scores integrity and explaining numbers.
A filled example
A made-up candidate for a mid-level FP&A analyst role supporting operations, scored after the technical interview, the model review and the budget owner conversation:
Forecasting and modeling judgment — 3. Owned the freight and warehousing forecast for two regions, driven by shipped volume and carrier rates; named the carrier rate as the assumption that mattered most.
Accuracy and checking — 4. Found the hard-coded cell and the doubled growth rate within ten minutes, and asked where the churn rate came from.
Variance analysis and materiality — 3. Explained a fuel surcharge overrun as a real change, not timing, and updated the next two quarters.
Explaining numbers to non-finance partners — 2. The budget owner found the explanations accurate but heavy on terms such as "accrual reversal", with the action left unsaid.
Data sourcing and tools — 4. Pulls shipment data with SQL from the warehouse and rebuilt a manual report so it ties to the ledger each month.
Integrity under pressure — 4. Would accrue the cost, tell the controller about the request, and offered to write the variance note for marketing.
Weighted score: 3.25 ((3×20 + 4×20 + 3×15 + 2×20 + 4×15 + 4×10) ÷ 100). Recommendation: Yes, with one concern for references: ask a past budget owner how usable the candidate's explanations were.
Adjusting for seat and level
| Seat or level | Adjustment |
|---|---|
| Business unit or commercial finance | Raise explaining numbers to 25%; the budget owner scores that row. |
| Investment or equity research analyst | Replace variance analysis with a row for the investment thesis (what would prove it wrong), and check any FINRA registration the seat needs on BrokerCheck as pass/fail. |
| Credit analyst | Replace variance analysis with a row for credit judgment scored on a short credit memo: risks named, a rating with a reason, what would change it. |
| New graduate or junior analyst | Score forecasting on the model review alone; accept internship or coursework examples; keep accuracy and integrity at full weight. |
| Senior or lead analyst | Add a row for building the planning process and reviewing others' work; a 3 on forecasting needs driver logic they designed. |
Mistakes specific to scoring financial analysts
| Mistake | Why it fails | Fix |
|---|---|---|
| Scoring spreadsheet speed | Keyboard shortcuts are easy to show and say little about judgment or accuracy | Score what they found and why, not how fast they moved |
| Giving points for a CFA, CPA or MBA | Double-counts a credential and rewards a line on the resume over the work | Pass/fail if required; for the CFA see how to verify a CFA charter |
| Only technical questions | An analyst nobody outside finance can follow has limited value | Have a budget owner score the explaining row |
| Rewarding confidence over accuracy | A fluent wrong answer outscores a careful right one | Score against the anchors; "I'd need to check" is often a 3 or 4 |
| Running a credit check without checking state law | Several states and cities limit credit checks in hiring | Read credit check laws for employers first; it is never a scorecard row |
Where this fits in the hiring process
The financial analyst phone screen places the candidate on the forecast and modeling ladder and checks credentials. The technical interview, the model review and the budget owner conversation fill in the six rows. Keep the rows consistent with the must-haves in the financial analyst job description template, and carry the weakest scored row into the first month of the 30-60-90 day plan for financial analysts.
If you run interviews with Interview Signal, the desktop app we make, these rows can become the scorecard areas in its kit, each weighted 1, 2 or 3 with rubric lines on a 1–10 scale; each score carries the candidate's own quotes, checked word for word against the transcript, and an area with no surviving quote is capped at 5 and marked "Probe further" (see how the scorecard with verified quotes works). Whatever you use, have each interviewer score before reading the others, then compare in a calibration session.
Questions people ask
What should a financial analyst interview scorecard measure?
Six things for most FP&A seats: forecasting and modeling judgment, accuracy and checking, variance analysis and materiality, explaining numbers to people outside finance, sourcing and handling data in the team's tools, and integrity when someone wants the numbers to look better. Weight them for the seat and anchor what a 1, 3 and 5 sound like for each.
Should a CFA charter or an MBA raise a financial analyst's interview score?
No. If the seat requires a credential such as the CFA charter or a FINRA registration, check it with the issuer as a pass/fail line. The scored rows should measure what the candidate does with a forecast, a variance or a difficult question from a budget owner, which a credential does not show on its own.
How do you test a financial analyst's integrity in an interview?
Give a realistic pressure scenario, such as a department head asking the analyst not to accrue a cost so the department finishes on budget, and score what they would do. A strong answer explains why the request is a problem, goes to the controller or accounting team, and offers an honest way to explain the variance instead.
How do you score a new graduate on a financial analyst scorecard?
Use the same anchors with a smaller scope: a short invented model to review instead of their own past forecasts, and examples from internships, case competitions or coursework. Keep accuracy and integrity at full weight, because those habits do not depend on experience.