Financial Analyst hiring kit

Every step to hire the analyst who finds out why the numbers moved, checks the data underneath them, and tells a manager plainly what to do about it.

About this kit — the 5Ws

A financial analyst turns ledger, billing and operational data into budgets, forecasts and the monthly explanation of why actual results differ from plan. The tools matter less than the habits behind them: tracing a variance to the real driver instead of restating it, noticing when a source changed what it counts, keeping a model that someone else can check, and giving a non-finance manager a clear recommendation along with the limits of what the data can show.

Calibrated for:: Calibrated for an analyst who has already produced monthly reporting, a budget or a forecast for a real business. For a graduate hire, shorten the exercise and drop the definition change; for a senior hire, add a reforecast to the brief.
Timeline:: Set an approval-to-offer target at intake, allowing for panel availability, candidate adjustments, references and any lawful checks.

Who: Finance leaders, hiring managers and recruiters in financial-services firms hiring an analyst to own budgets, forecasts and variance commentary — whether into an established planning team or as the first dedicated analyst.
What: A weighted competency model, a monthly variance work sample with a planted data-definition change, structured technical questions with strong and weak answers, a job description, a 30-60-90 plan and a short review of how the hiring process itself ran.
When: Use it once the same forecasting and variance questions land on someone's desk every month, from the moment the role is proposed until you have logged how the hire moved through each step.
Where: Banks, payments firms, insurers, lenders, wealth managers and other financial-services businesses with a monthly management reporting cycle.
Why: Most analyst CVs list the same spreadsheet and modelling skills. A shared rubric and a realistic variance exercise let you compare what each candidate does with a misleading number, rather than which tools they name.

The competency model · 7

Use these competencies to compare job-related evidence. Review any apparent gap in a must-have before deciding.

Variance analysis and commentaryMust-have · 20
Splits a gap between actual and budget into volume, price or rate, mix and timing; separates one-off effects from lasting ones; and writes commentary that names the driver rather than repeating the number.
Data sourcing and reconciliationMust-have · 15
Knows where each figure comes from, ties report totals back to the ledger or source system, and notices when a source changed its definition before building conclusions on it.
Three-statement and driver-based modellingMust-have · 15
Builds models where outputs flow from a small set of named drivers, and can show how one change moves the income statement, balance sheet and cash-flow statement together.
Budgeting and rolling forecastsMust-have · 15
Runs a budget cycle with budget holders, keeps the approved budget as a fixed reference, and updates a rolling forecast from drivers rather than extending last month's run-rate.
Presenting numbers and a recommendationMust-have · 15
Leads with a recommendation a non-finance manager can act on, backs it with two or three figures, states what the data cannot show, and holds a position under pushback unless new evidence arrives.
Unit economics and margin analysisCan learn · 10
Works out revenue, cost and contribution per customer, account or transaction, and is explicit about which shared costs are allocated and on what basis.
Spreadsheet hygiene and model reviewCan learn · 10
Keeps inputs, calculations and outputs apart, avoids hard-coded figures inside formulas, adds check cells, and can review someone else's workbook quickly in a sensible order.

What's required and what's optional

Your hiring journey for Financial Analyst. Select a stage to jump to it.

Required for every hire
Optional — use when it adds evidence
AI boost — a big drafting win
Colour = phase

Phase 1
Plan
1. 01Plan the roleRequired
2. 02Agree successRequiredAI boost
Phase 2
Attract
1. 03Write the jobRequiredAI boost
2. 04Find candidatesOptionalAI boost
Phase 3
Select
Phase 4
Decide
Phase 5
Onboard & learn
1. 12Help them settle inRequired
2. 13Measure time to hireRequiredAI boost

AI drafts, people decide: Use AI to draft, rewrite and summarise your own material — never to rank, score, screen out or decide on candidates, and never with a candidate's personal data.

Plan

Attract

Select

Decide

Onboard & learn

Solid = required · dashed = optional · arrow keys move between steps

Stage 1 of 13Required

0 of 3 done

Plan the role

Workforce planning and requisition approval

Who runs it: Hiring manager + finance / HR business partner
Done when: An approved requisition with a written business case, budget and a named decision-maker.

Key tool

Answer these before the role is approved

1Which recurring decisions will this analyst's numbers support — budget approvals, pricing, product investment, cost reviews?
2Who explains variances to budget holders today, and how long does the monthly pack take to produce?
3Is the source data reconciled and owned, or would this person start by fixing it?

AI as an advantage4D framework

Delegate: Hand AI the first draft of the business case and the build / borrow / buy comparison. The decision, the budget and the sign-off stay with people.

Show the prompt and the checks

Describe: You are helping a hiring manager write a business case for a Financial Analyst role. Context: I will paste the problem the hire solves, the work it involves, the capacity we already have and the time we have. Produce: (1) a one-sentence problem statement in business terms; (2) a build / borrow / buy comparison with the strongest argument for each; (3) the questions a finance partner would ask; and (4) a short recommendation with the evidence it rests on. Use British English and plain language. Do not invent figures — leave [brackets] where I need to supply numbers. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check every number and claim against your own notes and strike anything the draft assumed. Make sure 'buy' is argued from ongoing work, not from a job title.
Diligence: The hiring manager owns the final case and the budget request. No candidate information belongs here; AI drafts the case, people decide whether to open the role.

Don't miss: Hiring an analyst when the real gap is the month-end close and bookkeeping — that is accounting work, and an analyst hired into it will spend the year reconciling rather than analysing.

Framework

Build · Borrow · Buy

Before opening a role, decide whether to build the capability in your current team, borrow it (contractor, agency, partner), or buy it (a permanent hire).

Write the problem the hire solves in one sentence, in business terms — not the job title.
Test Build: could an existing person grow into this within the time you have?
Test Borrow: is the need time-boxed, or does it end once a system is shipped?
Choose Buy only when the work is ongoing, core to the product and nobody inside can absorb it.
Record the decision, the budget and the one person who signs off the final hire.

Why it works: Writing the build, borrow or buy decision down exposes a vague or temporary need before it becomes a permanent requisition — and gives every later stage an anchor to check against.

• Name the decision-maker, usually the finance director or head of planning the analyst will report to.

Is this a dedicated role?

Decide whether the work is sustained and substantial enough for a dedicated owner by writing down the workload, the risk, the capacity you already have and the outcomes you expect.

Answer these before the role is approved

1.Which recurring decisions will this analyst's numbers support — budget approvals, pricing, product investment, cost reviews?
Listen for: Named decisions that come round every month or quarter.
Red flag: 'We need better visibility' with no decision attached.
2.Who explains variances to budget holders today, and how long does the monthly pack take to produce?
Listen for: A specific person stretched across the work, or a pack that goes out late or without commentary.
3.Is the source data reconciled and owned, or would this person start by fixing it?
Listen for: An honest view of data quality — it decides whether you need an analyst, a data engineer or a finance systems project first.
4.Could an accountant or an operations analyst already on the team take this on with training?
Listen for: A named person and a realistic path, or a clear reason the work needs a dedicated analyst.
5.What happens each month the role stays empty?
Listen for: A concrete cost: late packs, unchallenged overspends, a budget cycle without an owner.

Build, borrow or buy?

Build: train an accountant or operations analyst in forecasting and variance work, with a senior analyst reviewing their first cycles.
Borrow: use a contract or fractional analyst for a single budget cycle or funding model, with a written hand-over of the model and its assumptions.
Buy: hire a permanent analyst once the monthly pack, the forecast and budget-holder questions recur and need one owner.

Watch out for

Opening the role for a single project, such as one funding model, when a contractor would cover it.

Stage 2 of 13Required

0 of 2 done

Agree success

Intake meeting and competency model

Who runs it: Recruiter + hiring manager
Done when: A signed-off competency model: 5–7 competencies, each marked must-have or trainable, with weights.

Key tool

Ask the hiring manager

1Which of the systems or areas this person will own worries you most, and why?
2When something there went wrong recently, how did you find out?
3In 12 months, what will be shipped, fixed or running for you to call this hire a success? Agree two or three measurable outcomes.
4Who will they work with most closely?
5What could a strong candidate learn in their first three months? Those capabilities are 'trainable' — never use them to filter applications.

AI as an advantageAI boost4D framework

Delegate: Hand AI your raw intake notes to turn into a draft competency model. Choosing the must-haves and the weights stays with the hiring manager and recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter and a hiring manager build a competency model for a Financial Analyst role. Context: I will paste the notes from our intake meeting, including the 12-month outcomes and what the hiring manager worries about most. Produce a table of 5–7 observable competencies with, for each: a one-line definition; whether it is a must-have or trainable, with the reason; what evidence of it looks like in real work; and a suggested weight so the weights total 100. Use British English and inclusive wording, avoid years-of-experience or named employers as evidence, and keep every competency job-related. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each competency is observable and job-related, that nothing describes a type of person rather than the work, and that trainable items haven't been marked must-have.
Diligence: The hiring manager signs off the final model and weights before anyone meets a candidate. No candidate data goes into the prompt; AI drafts, people decide.

Don't miss: Writing a must-have for one spreadsheet add-in or planning system. Experience with a specific tool may be trainable, depending on the system and the role; judgement about drivers is harder to teach.

Framework

Competency model (must-have vs trainable)

A short list of the observable capabilities the job needs, split into what the hire must bring on day one and what you will teach.

Start from the 12-month outcomes, then ask which capabilities produce them.
Keep 5–7 competencies. With more, interviewers struggle to score each one separately.
Mark each must-have or trainable. Only must-haves can count against a candidate.
Give each a weight so they sum to 100, agreed before anyone meets a candidate.
Write what evidence of each looks like, so interviewers know what they are listening for.

Why it works: Agreeing the criteria before meeting candidates stops the bar moving from one candidate to the next, and makes it harder for 'I'll know it when I see it' to decide the hire.

Core intake questions (ask for every role)

Book 45 minutes with the hiring manager before anything is advertised, and write the answers down.
Which of the systems or areas this person will own worries you most, and why?
When something there went wrong recently, how did you find out?
In 12 months, what will be shipped, fixed or running for you to call this hire a success? Agree two or three measurable outcomes.
Who will they work with most closely?
What could a strong candidate learn in their first three months? Those capabilities are 'trainable' — never use them to filter applications.
Who is on the interview panel, and is their time held for the next four to six weeks?

Questions specific to this role

1.Which decisions will this analyst's numbers feed in the first year — the annual budget, the monthly management pack, pricing reviews, product cases?
Listen for: Which outputs matter most; this sets the competency weights and the shape of the work sample.
2.Where do the source figures come from — ledger, billing system, customer database, data warehouse — and who owns each definition?
Listen for: How much reconciliation and data chasing the role involves, and whether definition changes are announced or discovered.
3.Will someone senior review this person's models and commentary, or will they be the only analyst?
Listen for: Whether model-review skill is a nice-to-have or something the hire must bring from day one.

What success looks like in 12 months

The monthly pack goes out on the agreed date with commentary that names the driver behind each material variance.
Budget holders can say what their latest forecast assumes and who agreed it.
The main forecast model has a documented set of drivers, check cells and a version log someone else could pick up.
At least one recommendation from the analyst led to a decision that was tracked against what actually happened.

Watch out for

Requiring a professional finance qualification by default when the work does not need one — it narrows the pool without testing the skill.

Stage 3 of 13Required

0 of 3 done

Write the job

Job description and pay band

Who runs it: Hiring manager (content) + recruiter (publishing)
Done when: A published job description that states outcomes, the must-haves, how AI tools are used and the pay information the law requires.

Key tool

Financial Analyst

We're looking for a financial analyst to own the monthly variance commentary, the rolling forecast and the budget cycle for [business area]. You'll work out why results differ from plan, keep the models that support decisions clean and checkable, and explain the numbers to managers across [teams] in plain language — reporting to [role].

What you'll do

•Produce the monthly management pack and write commentary that explains the drivers behind each material variance.
•Run the annual budget with budget holders and maintain a rolling forecast built on agreed drivers.
•Build and maintain driver-based and three-statement models, with clear inputs, check cells and version control.
•Source data from the ledger and operational systems, reconcile it, and flag changes in how figures are defined.
•Analyse unit economics and margins by product, customer group or channel.
•Present findings and recommendations to non-finance managers and follow up on the decisions made.

What you need

•You have produced recurring financial reporting, a budget or a forecast for a real business.
•You can explain a variance you investigated, what drove it and what changed as a result.
•You build spreadsheet models that someone else can follow and check.
•You can explain a financial result to a manager outside finance without jargon.

Nice to have

•Experience in banking, payments, insurance, lending or another financial-services business.
•An accounting or finance qualification, either held or in progress.
•Experience with a planning system, a reporting tool or SQL for pulling source data.
•Experience preparing cost or margin analysis by product or customer group.

How we use AI tools

•Where company policy permits, you may use approved AI tools to draft formulas, queries or a first version of commentary — and you check every figure back to its source before it is shared.
•Confidential, customer or unpublished financial data goes only into tools your organisation has approved for it.
•You stay accountable for the numbers and the recommendation; an AI draft does not sign off a variance or a forecast.

Pay

Salary range: [currency, minimum–maximum], plus [equity/bonus/benefits]. The range reflects [location/working pattern]. We place every offer within it using the same pre-set, job-related, gender-neutral factors — level, scope of reporting and budget-holder ownership, depth of modelling and forecasting experience — never previous salary or negotiating style.

AI as an advantageAI boost4D framework

Delegate: Hand AI the first draft of the job description from your signed-off competency model. The must-haves, the pay range and the final wording stay with people.

Show the prompt and the checks

Describe: You are helping write an outcome-based job description for a Financial Analyst role. Context: I will paste the competency model (must-have and trainable, with evidence), the 12-month outcomes, how the team uses AI tools, the location and working pattern, and the pay range. Produce: a summary paragraph that leads with the problem and what the hire will own; 'What you'll do' as outcomes, not tasks; 'What you need' containing only the must-haves; 'Nice to have' for the trainable items; 'How we use AI tools'; and a pay section that states the range. Use British English and inclusive, gender-neutral wording, avoid hype, and replace any 'X years' with the capability it stands for. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that 'What you need' contains only the must-haves, that no degree, employer or years requirement crept in, and that the pay range and location are exactly what was approved.
Diligence: The hiring manager owns the content and the recruiter owns publishing, including the pay information the law requires for each location. AI drafts the advert; people decide what it says.

Don't miss: A responsibilities list that reads like the whole finance department — tax, treasury, audit and payroll — which attracts generalists and puts off analysts.

Stage 4 of 13Optional

0 of 3 done

Find candidates

Sourcing strategy

Who runs it: Recruiter / sourcer
Done when: A shortlist-ready pipeline from at least three channels, with outreach tracked.

Use when:: Inbound applications won't give you enough qualified candidates.
Skip when:: Your shortlist already comes from inbound applications or referrals.

Key tool

Search query

("financial analyst" OR "FP&A" OR "finance analyst" OR "business finance" OR "commercial finance") AND ("variance" OR "forecast" OR "budget" OR "management accounts") AND ("model" OR "modelling" OR "Excel") NOT ("intern" OR "recruiter")

First outreach message

AI as an advantageAI boost4D framework

Delegate: Hand AI the search queries and the first draft of the outreach template. Choosing channels, personalising to a candidate's public work and sending stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter source candidates for a Financial Analyst role. Context: I will paste the must-have competencies, the kind of work we want evidence of, the channels we are using and the pay range. Produce: (1) one search query per channel, using OR for alternatives, AND for things that must all appear and NOT to exclude, with a one-line note on what each query looks for; and (2) a first-outreach template of under 120 words that opens with a [placeholder for something the candidate built], states the problem we are hiring to solve and the pay range, and ends with a low-pressure question. Use British English and inclusive wording. Do not refer to any specific person. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the queries search for evidence of the work rather than job titles alone, and that the template claims nothing about the role or the pay you can't back up.
Diligence: The recruiter personalises every message to something the candidate actually built, and sends it. No names or profile data go into the prompt; AI drafts, people decide whom to contact.

Don't miss: Searching only for the exact title 'Financial Analyst' and missing FP&A, business finance and commercial finance profiles doing the same work.

Framework

Channel mix + evidence-first outreach

Spread sourcing across channels where the work is visible, and open outreach with the problem, not the perks.

Pick channels where candidates show their work, not only where they list job titles.
Write one search query per channel. OR joins alternatives, AND joins things that must all appear, NOT excludes. Keep the version that works best.
Personalise the first line to something the candidate actually built or wrote.
Lead with the problem and the pay range. Save the perks for later.
Track reply rates by channel each week and drop the channel that isn't working.

Why it works: Searching for evidence of the work can surface candidates whose current title differs from the vacancy, or whose CV undersells what they have done.

Sourcing basics

Adapt the search query for each platform — the same words behave differently on each site.
Candidates with adjacent titles may have relevant evidence. Search for the work and outcomes the role needs, not the current title.
Channel activity is a lead, not evidence. Review linked work and examples against the written competencies.

Where to look

Finance teams at comparable financial-services firms

People already producing monthly packs and forecasts in a similar reporting cycle can show the work directly.

Audit and advisory alumni networks

Former auditors and advisory staff often bring reconciliation discipline and want to move into forward-looking analysis.

Professional accounting and finance bodies' job boards and member events

Members studying for or holding a qualification are already working on budgeting and reporting.

Internal operations, data and accounting teams

An internal candidate who already knows your products and data can be assessed with the same work sample.

LinkedIn and similar networks, searched by the reports and forecasts a person owned

Titles vary widely across firms; the work described in a profile is a better guide than the title.

Boolean search string

("financial analyst" OR "FP&A" OR "finance analyst" OR "business finance" OR "commercial finance") AND ("variance" OR "forecast" OR "budget" OR "management accounts") AND ("model" OR "modelling" OR "Excel") NOT ("intern" OR "recruiter")

First outreach message

Hi [name] — your work on [specific report, forecast or project] stood out. At [company] we need someone to own the monthly variance commentary and rolling forecast for [business area], working directly with the managers who use it. The range is [range]. Would you be open to a 20-minute call about what the role involves month to month?

Stage 5 of 13Required

0 of 3 done

Check applications

Application screening

Who runs it: Recruiter
Done when: Every application reviewed against the same written knockouts within five working days.

Key tool

Reject only if one of these is missing

•Can meet the role's work-authorisation requirements by the start date, with sponsorship where the employer offers it. Don't ask for documents at this stage.
•Has produced recurring financial reporting, a budget or a forecast for a business, in any sector.
•Has built or maintained spreadsheet models used by other people.

AI as an advantage4D framework

Delegate: Hand AI the job of turning your written knockouts into a consistent checklist with reason codes. Reviewing each application stays with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter prepare an application-screening checklist for a Financial Analyst role. Context: I will paste the must-have competencies and our written knockout criteria. Produce: (1) each knockout as a yes/no question answerable from an application alone; (2) a short list of reason codes for a 'no'; and (3) a note of any criterion that looks like a proxy — a degree, employer brand or employment gap — rather than a job-related requirement, with a suggested rewrite. Use British English. Do not evaluate any applicant and do not ask for applicant details. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each question is binary and job-related, and that every flagged proxy has been removed or justified in writing.
Diligence: A person reviews every application against the checklist and records the reason. Never paste CVs or applicant details into an AI tool, and never let a tool screen anyone out — in New York City and the EU that can bring automated-decision rules into play.

Don't miss: Treating a professional qualification listed on a CV as verified. Where the role or your local rules require a qualification, registration or approval, it is checked with the issuing body or applicable regulator at the references and checks stage — no assessment or interview replaces that check.

Framework

Knockout criteria

A small set of yes/no requirements, written in advance, applied to every applicant the same way.

Derive knockouts only from must-have competencies and genuine legal requirements.
Keep them binary and answerable from the application itself.
Apply them in the same order to every application and log the reason for each rejection.
Do not use proxies such as university, employer brand or employment gaps as knockouts.
Anything ambiguous gets a second review or moves forward to the skills stage.

Why it works: Early screening rejects people before richer evidence exists, so its criteria need the most care. Written criteria make decisions reviewable — but each one must also be job-related, applied consistently and checked for unjustified adverse impact.

Screening rules

Do not use degrees, employment gaps or certifications as filters unless they are demonstrably job-related and justified for this role.
Judge the claims in a CV, not how polished it is — a well-written CV may or may not have had AI help, and either way it is the evidence that matters.

Knockout criteria

Can meet the role's work-authorisation requirements by the start date, with sponsorship where the employer offers it. Don't ask for documents at this stage.
Has produced recurring financial reporting, a budget or a forecast for a business, in any sector.
Has built or maintained spreadsheet models used by other people.

Green flags

Names a specific variance or forecast miss they investigated and what they found.
Mentions reconciling figures between systems, or finding a data problem before it reached a report.
Describes presenting numbers to managers or budget holders outside finance.

Red flags

Lists modelling skills and tools but no output that anyone relied on.
Describes reporting only as 'updating the monthly template' with no mention of explaining results.
Broad claims of 'driving savings' with no figure, product or decision the candidate can name.

Watch out for

Rejecting candidates from outside financial services who have strong budgeting and variance work in another sector; the domain context can be learned.

Compliance checkpointNew York CityEU

For a New York City employment decision, work out whether a tool is an 'automated employment decision tool' (AEDT) under Local Law 144 — one that uses covered techniques to substantially assist or replace a discretionary decision. Before using a covered tool, make sure an independent bias audit was completed no more than a year earlier, publish the required summary, and give covered candidates or employees the required notice at least ten business days before use. In the EU, the AI Act (Annex III) lists AI used to recruit, filter applications or evaluate candidates as high-risk, subject to the Article 6(3) exception; the related obligations apply from 2 December 2027 under the amended timetable. A manual screen does not exempt an AI tool used elsewhere in the process.

Sources: NYC DCWP — Automated employment decision tools · EU AI Act — consolidated Regulation (EU) 2024/1689 · checked 2026-09-25

Stage 6 of 13Optional

0 of 3 done

Recruiter call

Recruiter screen

Who runs it: Recruiter
Done when: A 20–30 minute call that confirms logistics, motivation and one or two must-have signals.

Use when:: You are hiring at volume, or pay and logistics need confirming early.
Skip when:: You have only a handful of applicants — fold the pay and logistics questions into application screening instead.

Key tool

Ask every candidate, in this order

1Tell me about a regular report or forecast you owned. Who used it, and what did they decide with it?
2Tell me about a number in one of your reports that turned out to be wrong or misleading. How did you find out?
3What has made you want to move from your current finance work to this role?
4Our range for this role is [range]. Does that work for you?

AI as an advantage4D framework

Delegate: Hand AI the first draft of the screening-call script and its evidence anchors. Running the call and taking the notes stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter write a 20–30 minute structured screening call for a Financial Analyst role. Context: I will paste the must-have competencies, the logistics we need to confirm (location, working pattern, notice period) and the pay range. Produce: an opening that explains the process, the timeline and the pay range; 4–6 questions in a fixed order, each with one line on what a strong answer contains; and a closing that asks whether the published range works. Use British English and inclusive wording. Do not include questions about salary history, age, family, health or any other protected characteristic. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that every question is job-related and lawful, that the pay question asks whether the range works rather than for history, and that the anchors describe evidence, not impressions.
Diligence: The recruiter asks the same questions of everyone and writes the notes. No candidate details go into the prompt; AI drafts the script, people run the call and decide.

Don't miss: Asking the recruiter to test modelling technique. The recruiter checks motivation, logistics and whether the candidate can describe their own work clearly; the panel tests the craft.

Framework

Structured screening call

The same short set of questions for every candidate, with notes taken against what a strong answer contains.

Open by explaining the process, timeline and pay range. No surprises later.
Confirm logistics: location, working pattern, notice period and whether the range works for them.
Ask the same 4–6 questions in the same order, and note evidence, not impressions.
Leave time for the candidate's questions. Don't score their questions unless they test a written, job-related competency.
Decide within 48 hours and tell the candidate either way.

Why it works: Using the same questions and written evidence anchors makes answers easier to compare, and a short, predictable call respects the candidate's time.

Screening call basics

Set the decision timetable before sourcing and tell candidates when to expect each update.
Ask every candidate what draws them to this particular role, and listen for interest in the work described rather than the title.
Confirm notice period and whether they are in other processes, so you can plan the timetable.
End every call by asking whether the published pay range works — never ask for salary history.

Recruiter screen questions

1.Tell me about a regular report or forecast you owned. Who used it, and what did they decide with it?
Listen for: A specific output, a named audience and a decision it fed, with the candidate's own part clear.
Red flag: Describes the team's reporting cycle without saying what they personally produced.
2.Tell me about a number in one of your reports that turned out to be wrong or misleading. How did you find out?
Listen for: A concrete check — a reconciliation, a comparison with another source, a question from a manager — and what they changed afterwards.
Red flag: Says they have never had a number questioned, or that errors were someone else's to find.
3.What has made you want to move from your current finance work to this role?
Listen for: Interest in explaining and forecasting results, and a realistic view of month-end pressure.
Red flag: Expects mainly strategic projects with no interest in the monthly cycle.
4.Our range for this role is [range]. Does that work for you?
Listen for: A clear answer on whether the published range works. Don't ask for salary history — this process sets pay from the published band and pre-set, job-related factors.

Compliance checkpointUS (state and city)EU

Don't ask for salary history. In the EU, national laws implementing Article 5(2) of Directive (EU) 2023/970 must prohibit the question. US rules vary, but jurisdictions including California and New York prohibit employers from seeking salary history. Ask whether the published range works instead.

Sources: EU Pay Transparency Directive 2023/970, Article 5 · California Labor Commissioner — salary history · New York State DOL — salary history ban · checked 2026-09-25

Stage 7 of 13Required

0 of 3 done

Work sample

Skills assessment / work sample

Who runs it: Hiring manager (design) + recruiter (logistics)
Done when: Every shortlisted candidate completes the same job-shaped task, marked against criteria written in advance.

Key tool

Explain a September cost overspend and answer a budget request

Plan on 75 minutes; any spreadsheet tool is allowed. You may use AI tools if you wish: list in your submission each tool you used, what you used it for, and how you checked its output. All names, figures and events below are fictional. You are the analyst at a small consumer payments business. September operating costs, budget vs actual in thousands: Card, processing fees 408.0 vs 462.5; Card, fraud and chargeback losses 75.0 vs 70.0; Card, support contacts 60.0 vs 64.0; Current account, support contacts 90.0 vs 140.0; Savings, support contacts 30.0 vs 32.0; Shared, staff costs 520.0 vs 528.0; Shared, marketing 150.0 vs 112.0. Totals 1,333.0 vs 1,408.5. Card transactions, budget vs actual: domestic 7.6m vs 7.1m, cross-border 0.6m vs 1.3m; the processor's contract fee per transaction is 0.045 domestic and 0.110 cross-border, unchanged this year. Support is outsourced at a contract price of 10.00 per contact, unchanged. Contacts by reason, August then September: sign-in and access 2,100 then 7,400; card disputes 3,900 then 4,100; payments and transfers 6,000 then 6,200; other 5,700 then 5,900. App release 3.2 on 4 September changed the sign-in screen. The autumn marketing campaign moved from 15 September to 6 October. Active customers from the customer database: June 61,000, July 70,500, August 72,000, September 74,000. A note from the data team says that from 1 July 'active' means logged in within the last 90 days; until June it meant made a transaction in the last 30 days. On the old basis, September is 62,500; July and August have not been restated. The head of customer operations writes: 'Support is over budget because our customer base has grown — active customers are up by 13,000 since June. Please add 60k a month to my support budget from October.' Find the real drivers of the overspend, decide how to answer the request, and say what you cannot conclude from this data.

Planned for up to three hours (adjustments available on request). At the agreed stopping time, write a short note on what you would examine next, and what you deliberately left out.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the work-sample brief and its marking sheet. Choosing the task, setting the timebox and marking stay with the hiring manager.

Show the prompt and the checks

Describe: You are helping a hiring manager design a work sample for a Financial Analyst role. Context: I will paste the competency model, a real problem the team solved recently with anything confidential removed, the timebox, and our AI-tool policy for candidates. Produce: a candidate-facing brief (what to do, what to hand in, the time cap, how to request an adjustment, which AI tools are allowed and how to report their use); and a marking sheet with 4–6 criteria tied to named competencies, each with what a 1, a 3 and a 5 look like. Use British English and plain, inclusive wording. Do not design anything that needs more than the stated time. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the task fits the timebox, that every criterion maps to a competency, and that the brief gives all candidates the same starting materials.
Diligence: The hiring manager owns the task and the criteria, and people mark every submission. Do not paste candidate submissions into an AI tool for scoring; AI drafts the brief, people mark and decide.

H-EvaluateH-Evaluate can generate a job-specific assessment from your job description, so you don't have to build the task by hand.How H-Evaluate helps →

Don't miss: Using real company figures, even disguised. Fictional data avoids confidentiality problems and stops candidates with inside knowledge from having an advantage.

Framework

Work-sample test

A small, realistic slice of the job, marked against criteria written in advance. Give candidates equivalent materials and arrange reasonable adjustments where required.

Take a real problem the team solved recently and shrink it to fit the timebox.
Write the marking criteria first, tied to the competency model.
Timebox honestly — for take-home work, a few hours at most — and say so in the brief.
State the AI-tool policy in writing. Where the job permits these tools, use equivalent conditions in the assessment and evaluate how candidates verify their output.
Mark without CV details where you can, and have two people mark borderline submissions.

Why it works: A well-designed work sample gives direct evidence of job-relevant skill rather than a proxy for it, and gives candidates a realistic preview of the work.

Assessment rules for every candidate

State the planned time cap and how to request an adjustment. At the agreed stopping time, ask candidates to note what they would examine next and what they left out — never reward unpaid overtime.
Give every candidate the same starting materials, and use a second marker for borderline submissions.
Say in writing which AI tools are allowed and ask candidates to tell you how they used them.
Invite every candidate to ask for adjustments, and answer each request promptly.
Pay for anything the task costs the candidate to run, such as model or cloud usage.

The work sample

Explain a September cost overspend and answer a budget request

Timebox: Planned for up to three hours (adjustments available on request). At the agreed stopping time, write a short note on what you would examine next, and what you deliberately left out.

What the candidate hands in

A short breakdown of the main variances into volume, mix, rate and timing, with your workings in the spreadsheet.
A one-page commentary for the head of customer operations and the finance director: the drivers, your recommended response to the budget request, and the action you propose.
A short list of what this data cannot tell you, and what you would ask for to close each gap.

Marking criteria (write these first)

Splits the processing-fee overspend of 54.5 into a volume effect and a cross-border mix effect, shows the workings, and states that the contract fee per transaction did not change.
Attributes the support overspend to the rise of 5,300 sign-in and access contacts after the 4 September release, checked against the contract price of 10.00 per contact.
States that the active-customer definition changed on 1 July, does not use the 13,000 growth figure, and either compares September's restated 62,500 with June's 61,000 or explains why the series cannot be compared.
Labels the marketing underspend of 38.0 as timing that reverses in October, not as a saving.
Gives a yes, no or conditional answer to the 60k request, ties it to at least one figure from the brief, and names who should act on the sign-in problem.
Lists at least two limits of the data, such as no revenue figures to set against the extra cross-border fees and no restated active-customer figures for July and August.

Adjustments: Candidates can ask for extra time, the table in another file format, a screen-reader-friendly version, or to talk through the exercise live with an interviewer instead of writing it up. No finance software beyond a spreadsheet is needed.

Watch out for

Rewarding the most polished-looking workbook over the commentary that found the definition change.

Compliance checkpointUSGreat BritainEU

In the US, covered employers must provide a reasonable accommodation to a qualified applicant with a disability unless it would cause undue hardship (ADA). In Great Britain, the Equality Act 2010 requires reasonable adjustments in recruitment. In the EU, the duty comes from national equality law. Don't ask for more medical information than the law allows.

Sources: EEOC — prohibited practices · Equality Act 2010 · checked 2026-09-25

Stage 8 of 13Required

0 of 3 done

Structured interviews

Structured interview loop

Who runs it: Interview panel (named in advance)
Done when: Every competency has a lead interviewer and at least one second source of evidence, with the same questions for every candidate.

Key tool

Interview questions by pillar

Free in this kit: Domain questions for every round. The other three pillars and the AI-fluency check are measured by H-Evaluate.

Free in this kit

The finance manager who scored the variance exercise · Variance analysis and commentary · Data sourcing and reconciliation

1.Walk us through how you split the card processing-fee overspend. Which parts would you put in front of the card product owner, and what would you leave out?
Variance analysis and commentary
Good answerSeparates a small volume effect from the larger mix shift towards cross-border transactions, confirms the contract rate did not change, leads with the mix driver and notes that cross-border income is not in the data.
Weak answerReports the overspend as 'higher volumes', or restates the gap without saying what caused it.
2.When active customers jumped between June and July, what did you check before using the figure, and how would you build a series you could trust from here?
Data sourcing and reconciliation
Good answerRead the data team's note, compared the restated September figure with June, would ask for July and August on the old basis, and would label the break in any chart or table going forward.
Weak answerUses the 74,000 figure as given, or drops the measure without proposing a consistent replacement.
3.Support costs rose sharply in September. What evidence in October and later months would show whether that increase persists or fades, and how would it change your answer to the budget request?
Variance analysis and commentary
Good answerNames the sign-in contact count against its August level after the fix, contacts per transacting customer on one definition, and the point at which they would change the recommendation.
Weak answerIs certain the problem has gone, or has no test that would change their mind.

Optional follow-ups (1)

4.The ledger shows September support costs of 236k, but the outsourcer's invoice report totals 229k. How would you reconcile the two before the pack goes out?
Data sourcing and reconciliation
Good answerChecks accruals and invoice timing, credit notes, indirect tax treatment and cost-centre mapping; lists each reconciling item; and decides whether any remaining gap is material enough to delay the pack.
Weak answerPicks one figure without explaining the difference, or posts a balancing figure to make the totals agree.

AI as an advantageAI boost4D framework

Delegate: Hand AI the drafting of probe questions and strong / weak anchors for one competency. Asking, listening and scoring stay with the interviewer.

Show the prompt and the checks

Describe: You are helping an interviewer prepare a structured technical interview for a Financial Analyst role. Context: I will paste one competency, its evidence description and the core question we ask every candidate. Produce: four probes in this fixed order — what would you do, why that choice, what else did you consider, how would you know it worked — tailored to the question; a one-line description of a strong answer and of a weak answer; and two follow-ups to use only if time allows. Use British English and inclusive wording. Keep everything about the work, nothing about the person. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the probes test the named competency rather than trivia, that the anchors describe observable evidence, and that no question touches a protected characteristic.
Diligence: Interviewers ask the same core questions of every candidate and score alone against the rubric. Interview notes and candidate names never go into an AI tool; AI drafts the questions, people interview and decide.

H-EvaluateH-Evaluate can add evidence on Cognitive, Situational judgement, Behavioural and AI fluency for your panel to review alongside these interviews.How H-Evaluate helps →

Don't miss: Turning the modelling round into a test of keyboard shortcuts or function names instead of how the candidate structures and checks a model.

Framework

Structured technical interview

Every candidate gets the same job-specific questions, each interviewer leads on specific competencies, and every answer is probed with the same four follow-ups: what would you do, why, what else did you consider, and how would you know it worked.

Give each competency a lead interviewer, plus a second source of evidence — the work sample, another round or an independent marker. Avoid asking the same thing twice, but never let one person's view be the only evidence for a critical competency.
Ask the three core questions for your round, in order, for every candidate. Use an optional follow-up only if there is time.
Probe each answer: why that choice, what else they considered, and how they would know it worked — until you hear the candidate's own technical decision.
Take notes on evidence during the interview. Don't rate until it's over.
Fill in your interviewer sheet and submit it before you talk to any other interviewer.

Why it works: Structured interviews make answers comparable: every candidate faces the same job-related questions and is scored against the same anchors.

Interview rules

Use the same core questions in the same order for every candidate.
In the work-sample review, understand the candidate's decisions against the rubric — don't turn it into a debate about your preferred solution.
Avoid trivia disconnected from a real job decision. Use a realistic debugging, design or evaluation problem instead.

Watch out for

Marking down a candidate who reached a different but well-evidenced split of a variance than the marker did.

Compliance checkpointUSUKEU

Don't ask about protected characteristics — such as age, disability, pregnancy or family plans, religion, race or nationality — unless applicable law permits the question for a specific, necessary, job-related purpose, and HR or counsel has confirmed that basis beforehand. Ask only whether the candidate can meet the role's work-authorisation requirements. If a candidate volunteers protected information, don't probe; record only what is lawfully needed, keep it separate and restrict access.

Sources: EEOC — prohibited practices · Equality Act 2010 · checked 2026-09-25

Where to find more interview questions

Use web question banks for inspiration only: ask every candidate the same job-related questions, check each one against this kit's competencies, and never ask about protected characteristics. Don't reuse this kit's work sample from a public bank — candidates can find questions that circulate online, so a widely posted question tests preparation more than skill.

Show 4 sites

US OPM — Structured interviews(opens in a new tab)
US federal guidance on building structured interviews, with a guide, training material and sample questions with rating scales.
FreeFor interviewers
Acas — Interviewing job applicants(opens in a new tab)
UK public guidance on preparing fair interviews, asking applicants the same questions and avoiding discriminatory ones.
FreeFor interviewers
Workable — Interview questions library(opens in a new tab)
Sample interview questions for employers, listed by job role, including machine learning, data and engineering roles.
FreeFor interviewers
Indeed for Employers — Interview questions(opens in a new tab)
Sample interview questions for employers by job title and skill, with notes on what to look for in answers.
FreeFor interviewers

Links checked 2026-10-05. External sites; we don't control their content.

Stage 9 of 13Required

0 of 2 done

Compare evidence

Scoring, calibration and debrief

Who runs it: Hiring manager (chairs) + panel
Done when: A documented hire / no-hire decision traceable to scored evidence against the competency model.

Key tool

Interactive scorecard

Score one candidate against the rubric. Everything stays in your browser. Download it as a spreadsheet for your records.

Variance analysis and commentary Must-have

Weight

What do 1, 3 and 5 look like?

1: Restates the gap between actual and budget without saying what caused it.
3: Finds the main driver with some prompting; commentary is accurate but mixes one-off and lasting effects.
5: Splits each material variance into its parts unprompted, separates timing from lasting effects, and writes commentary that ends in an action.

Data sourcing and reconciliation Must-have

Weight

What do 1, 3 and 5 look like?

1: Uses figures as given without checking where they came from.
3: Reconciles totals when asked and notices obvious breaks in a series.
5: Checks sources and definitions before building on them, reconciles to the ledger, and labels any break so others are not misled.

Three-statement and driver-based modelling Must-have

Weight

What do 1, 3 and 5 look like?

1: Builds outputs from typed-in figures; cannot say how a change flows between statements.
3: Builds a working driver-based model; links between statements need checking.
5: Builds models from a few clear drivers that tie across all three statements, and knows which drivers the answer is most sensitive to.

Budgeting and rolling forecasts Must-have

Weight

What do 1, 3 and 5 look like?

1: Treats the budget as the forecast, or extends last month's run-rate.
3: Updates a forecast regularly; driver ownership and the link to the budget are partly clear.
5: Keeps the budget fixed for reference, reforecasts from owned drivers on a set cycle, and explains every movement between versions.

Presenting numbers and a recommendation Must-have

Weight

What do 1, 3 and 5 look like?

1: Presents data without a recommendation, or uses language a non-finance manager cannot follow.
3: Gives a clear recommendation when asked; struggles to hold it under pushback.
5: Leads with a recommendation, states its limits, and changes position only when new evidence is offered.

Unit economics and margin analysis Can learn

Weight

What do 1, 3 and 5 look like?

1: Compares products on revenue or direct cost alone.
3: Calculates contribution per unit; allocation of shared costs is unexplained.
5: Builds per-unit economics with a stated allocation basis and uses them to support a specific decision.

Spreadsheet hygiene and model review Can learn

Weight

What do 1, 3 and 5 look like?

1: Hard-codes figures, has no checks, and reviews by reading formulas at random.
3: Separates inputs from calculations and adds some checks; reviews thoroughly but slowly.
5: Keeps workbooks others can audit, with checks and a version log, and reviews a model in a risk-first order.

Weighted score– / 5

AI as an advantage4D framework

Delegate: Hand AI the drafting of a blank debrief worksheet and agenda from the competency rubric alone. People add the evidence locally; the scores and the decision stay with the panel.

Show the prompt and the checks

Describe: You are helping a hiring manager prepare a debrief for a Financial Analyst role. Context: I will paste the competency rubric only — the competencies, their weights and their 1, 3 and 5 anchors. Produce: (1) a blank debrief worksheet with one row per competency and empty columns for each interviewer's independent score, the evidence they cite, the spread of scores and an 'evidence gap?' box; (2) a 45-minute agenda: confirm every scorecard is in and reveal all scores at once, discuss the widest spreads using evidence only, review any must-have scored 1, then look at the weighted total and decide (hire, no hire or one targeted follow-up), and record the reasons; and (3) neutral questions the chair can ask to draw out evidence rather than adjectives. Leave every evidence and score cell empty. Do not suggest a score, a rating or a recommendation. Use British English. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the worksheet follows your rubric exactly — same competencies, weights and anchors — and that the agenda keeps independent scores hidden until the reveal.
Diligence: Interviewers fill in the evidence and scores locally, alone, before the debrief, and the panel decides together. Candidate notes and personal data never go into an AI tool; AI never scores, ranks or compares candidates.

H-EvaluateH-Evaluate gives you a report on each candidate's assessment evidence to bring into this debrief.How H-Evaluate helps →

Don't miss: Letting a fluent presentation cover for a candidate who missed the definition change in the exercise.

Stage 10 of 13Optional

0 of 2 done

Check references

References and background checks

Who runs it: Recruiter (references) + HR (checks)
Done when: At least two references that test specific competencies, plus only the checks that are lawful and relevant to the role.

Use when:: It is lawful where you hire, and specific evidence from a referee would change the decision.
Skip when:: Local law or company policy rules it out.

Key tool

Ask each referee

1Can you describe a variance or forecast miss [candidate] explained to you? How useful was the explanation?
2When someone else had to pick up one of their models, how easy was it to follow and check?
3How did they handle a manager who disagreed with their numbers?

AI as an advantage4D framework

Delegate: Hand AI the drafting of reference questions aimed at the competency the panel was least sure about. Choosing referees, making the calls and interpreting the answers stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter write competency-based reference questions for a Financial Analyst role. Context: I will paste the competency model and the one or two competencies where our evidence is thinnest — no candidate details. Produce: 3–4 questions per competency that ask for specific examples ('tell me about a time…') rather than ratings; an opening question about how the referee worked with the person and for how long; and a closing question about what their next manager could do to help them do their best work. Use British English and inclusive wording. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the questions ask for examples rather than opinions, that they stay on job-related competencies, and that none asks about health, family or other protected matters.
Diligence: References are taken with the candidate's consent and interpreted by people. Referee answers and candidate details never go into an AI tool; AI drafts the questions, people decide.

Don't miss: Accepting a reference that confirms dates and title but says nothing about the quality of the person's numbers.

Framework

Competency-based referencing

Treat references as a last structured conversation about the candidate's work, aimed at the competencies where your evidence is thinnest.

With the candidate's consent, ask for two people who saw their relevant work directly — ideally a former manager and a peer.
Accept suitable alternatives if a manager or peer isn't available, and never penalise a candidate for a former employer's no-reference policy.
Aim your questions at the one or two competencies the debrief was least sure about.
Ask for examples, not ratings. 'Tell me about a time they…' works here too.
Set the timing of each background check by the law and policy that apply.

Why it works: Generic reference questions tend to produce little job-related evidence. Asking for specific examples tied to the role's competencies turns referencing into something you can use.

Core reference questions and checks

Open with: 'How did you work together, and for how long?' — it tells you how much weight the rest can carry.
Ask: 'Tell me about a time something they owned went wrong. What did they do?'
Close every reference with: 'What should their next manager do to help them do their best work?'
Verify only claims that were material to the decision — don't verify a degree the role never required.
Run criminal-record checks only where the role justifies them and local law allows; many roles don't need one.
Schedule formal work-authorisation checks at the legally required time: before employment starts in the UK; for US Form I-9, Section 1 by the first day of paid work and Section 2 within three business days.

Reference questions specific to this role

1.Can you describe a variance or forecast miss [candidate] explained to you? How useful was the explanation?
Listen for: A specific example where the referee understood the driver and acted on it.
2.When someone else had to pick up one of their models, how easy was it to follow and check?
Listen for: Evidence of clear structure and documentation, not only that the model worked.
3.How did they handle a manager who disagreed with their numbers?
Listen for: Holding a position with evidence and changing it when the manager had a point.

Compliance checkpointUS

If a consumer reporting agency provides a background report, the Fair Credit Reporting Act requires a clear, stand-alone written disclosure and the candidate's written authorisation before you order it. Before rejecting someone because of the report, give them a copy and the FCRA summary of rights and a reasonable opportunity to review and dispute it before any adverse action; if you still reject, send a final adverse-action notice. State and local 'fair chance' laws may delay criminal-history questions or checks until after a conditional offer.

Sources: FTC — Background checks: what employers need to know · FTC — Using consumer reports: what employers need to know · checked 2026-09-25

Stage 11 of 13Required

0 of 2 done

Agree the offer

Offer, negotiation and close

Who runs it: Hiring manager + recruiter
Done when: An accepted written offer within the approved band, with a start date.

Key tool

Build the offer around

•Direct contact with the budget holders and managers who use the analysis, not only the finance team.
•A named owner for review of their models, so they can learn quickly and are not working unchecked.
•Support towards a professional finance qualification where the organisation offers it.
•A clear explanation of the level and what the next step up would look like.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the offer message built around what the candidate said matters to them. The figure, the approval and the conversation stay with the hiring manager.

Show the prompt and the checks

Describe: You are helping a hiring manager draft an offer message for a Financial Analyst role. Context: I will paste three general priority categories (for example: learning, flexibility, scope) — not the candidate's words, notes or personal details; the parts of the offer; and the start-date options — without the salary figure. Produce: a warm, plain-English message that links each part of the offer to one of their priorities, says what happens next and when the written offer follows, and invites questions. Use British English and inclusive wording, and leave [brackets] for figures and names. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that nothing promised is outside policy or the approved band, that every claim about the role is true, and that the message reads as personal rather than templated.
Diligence: The hiring manager places the offer in the band using the same pre-set factors for everyone and makes the verbal offer personally. Figures and personal details are filled in by people, never pasted into AI.

Don't miss: Promising strategic project work in the offer when most of the first year will be the monthly cycle.

Framework

Close plan (motivators → offer → objections)

Build the offer around what the candidate told you they care about, anticipate their objections, and make sure the verbal and written offers match.

List the candidate's top three motivators from your notes at every stage.
Make the verbal offer personally, and link each part of it to a motivator.
Ask what else they are weighing and when they have to decide.
Place the offer in the band using the same pre-set, job-related factors for everyone, and record why.
Send the written offer promptly after the verbal one.

Why it works: A close plan ties the offer to the candidate's stated priorities and makes approvals explicit before the final interview.

Offer checklist and negotiation

Stay inside the approved band. If the candidate is worth more, re-level them with evidence rather than stretching the band.
Trade in things that cost less than salary where policy allows: start date, learning budget, working pattern.
Before the written offer, ask: 'What would make this an easy yes?'
Agree approval and the pay band before the final interview, so the offer isn't held up.
The hiring manager makes the verbal offer; the written offer follows within a working day.
Record which pre-set factors placed the offer where it is in the band.
Tell unsuccessful finalists personally, without avoidable delay, with brief feedback.

What will close this candidate

Direct contact with the budget holders and managers who use the analysis, not only the finance team.
A named owner for review of their models, so they can learn quickly and are not working unchecked.
Support towards a professional finance qualification where the organisation offers it.
A clear explanation of the level and what the next step up would look like.

Compliance checkpointEUUS

Use objective, gender-neutral, pre-agreed factors to place candidates within the band, apply them consistently and record the decision as an internal pay-equity control. Check the national law implementing Directive (EU) 2023/970 and any local record-keeping rules; this recommendation is good practice, not a universal statutory documentation rule.

Sources: EU Pay Transparency Directive 2023/970 · checked 2026-09-25

Stage 12 of 13Required

0 of 2 done

Help them settle in

Pre-boarding and 30-60-90 onboarding

Who runs it: Hiring manager + buddy + HR
Done when: A new hire who has worked through a written 30-60-90 plan tied to the 12-month outcomes, with a check-in at each milestone.

Key tool

Before day one
Access to the ledger, reporting tools and data warehouse requested, with approvals in place.
Days 1–30: learn
Meets each budget holder they support and learns what drives their costs or revenue.
Days 31–60: contribute
Owns the commentary for their full area of the monthly pack.
Days 61–90: own
Presents the variance commentary to budget holders without a finance manager leading.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the 30-60-90 plan from the 12-month outcomes. Agreeing the plan with the new hire stays with the manager.

Show the prompt and the checks

Describe: You are helping a hiring manager draft a 30-60-90 day onboarding plan for a new Financial Analyst. Context: I will paste the 12-month outcomes from the intake meeting, the systems and people the hire will work with, and anything they will need before day one. Produce: a pre-boarding checklist (equipment, access, a named buddy, a first-week schedule); then three sections — days 1–30 learn, days 31–60 contribute, days 61–90 own — each with 3–4 concrete, checkable expectations and one milestone check-in question. Use British English and plain wording. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each expectation is realistic for a new starter, ties back to a 12-month outcome, and offers the hire support rather than a test.
Diligence: The manager agrees the plan with the new hire in week one and owns the check-ins. The new hire's personal details stay out of the prompt.

Don't miss: Handing over the forecast model on day one with no walkthrough of its assumptions or known weak spots.

Framework

30-60-90 day plan

Three phases — learn, contribute, own — with written expectations for each, agreed with the new hire in week one.

Before day one: equipment, access, a named buddy and a first-week schedule.
Days 1–30, learn: systems, people and the current state of the work.
Days 31–60, contribute: a first scoped piece of work shipped with support.
Days 61–90, own: an area of responsibility with clear outcomes.
Hold a check-in at each milestone against the written plan.

Why it works: Hiring doesn't end at the signature. A written onboarding plan makes expectations and support visible to the new hire and their manager.

Before day one
- Access to the ledger, reporting tools and data warehouse requested, with approvals in place.
- Last three months' packs, the current budget and the forecast model shared in advance.
- A named buddy in the finance team and a list of the budget holders they will support.
- The calendar for month-end, the next forecast update and the budget cycle.
Days 1–30: learn
- Meets each budget holder they support and learns what drives their costs or revenue.
- Produces commentary for one section of the monthly pack, reviewed before it is sent.
- Maps where each figure in the pack comes from and notes any definitions that have changed.
Days 31–60: contribute
- Owns the commentary for their full area of the monthly pack.
- Updates the rolling forecast for their area with drivers agreed with each budget holder.
- Fixes one weakness in the forecast model, such as a missing check or a hard-coded figure.
Days 61–90: own
- Presents the variance commentary to budget holders without a finance manager leading.
- Delivers one piece of margin or unit-cost analysis that supports a specific decision.
- Agrees with their manager the priorities for the next budget cycle.

Compliance checkpointUSUK

US: the employee completes Form I-9 Section 1 no later than their first day of paid work, and the employer completes Section 2 within three business days after that day (on the first day if the job lasts less than three business days). UK: complete the prescribed right-to-work check before employment starts, and apply it the same way to everyone.

Sources: USCIS — Form I-9 instructions · GOV.UK — Check a job applicant's right to work · checked 2026-09-25

Stage 13 of 13Required

0 of 3 done

Measure time to hire

Measure the process: mean time to hire

Who runs it: Recruiter / talent lead + hiring manager
Done when: A stage-by-stage timing record for this hire, the slowest step named, and one change agreed before the next requisition opens.

Key tool

Record when the hire accepts

•Time to hire: days from the successful candidate entering the pipeline (application or first contact) to the accepted offer. Average it across hires for mean time to hire.
•Time to fill, recorded separately: days from requisition approval to the accepted offer.
•Days per stage, from the stage's first action to its last — and whether the time was spent waiting or working.
•Offer-acceptance rate: offers accepted divided by offers made.
•Where candidates dropped out, and the reason you were given.
•Days from first contact to accepted offer for the analyst hired.

Check in at 90 days whether the hire is meeting the outcomes in the job description — that tells you whether the process picked well.

Read: mean time to hire Read: time to hire vs time to fill

AI as an advantageAI boost4D framework

Delegate: Hand AI the job of building a blank timing worksheet and the instructions for reading it. Entering dates, working out the timings and deciding what to change stay with the recruiter and the hiring manager.

Show the prompt and the checks

Describe: You are helping a recruiter and a hiring manager set up a timing review for a Financial Analyst hire. Context: I will list the stage names we used, in order (for example requisition approved, sourcing, screening, recruiter call, work sample, interviews, debrief, references, offer accepted). Produce: (1) a blank worksheet with one row per stage and columns for start date, end date, days in stage, days spent waiting (scheduling, approvals, no reply) and number of candidates who entered and left; (2) step-by-step instructions for us to work out, from our own records, time to hire (the successful candidate's entry to the pipeline, by application or first contact, to the accepted offer; average it across hires for mean time to hire) and, separately, time to fill (requisition approval to the accepted offer); (3) five questions we should ask about the slowest stage, separating waiting from working; (4) a short template for recording one change to make before the next hire. Use British English. Do not include benchmarks or example figures. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the worksheet covers every stage you actually ran, that the two definitions are not mixed up, and that the questions point at the process rather than at any person.
Diligence: People fill in the dates and do the arithmetic from their own records, choose the one thing to fix and write it down. No dates, names or details about any candidate go into the prompt.

Don't miss: Measuring only how fast the role was filled and ignoring whether budget holders found the panel's non-finance round useful.

Framework

Mean time to hire, by stage

Time to hire is the number of days from the successful candidate entering your pipeline (their application or your first contact) to their accepted offer; mean time to hire is that figure averaged across hires. Time to fill — requisition approval to acceptance — is a separate measure. Record both per stage, so you can see where the time went rather than only the total.

When the hire accepts, write down the date each stage started and ended, and the day the successful candidate entered the pipeline.
Work out the days per stage, the time to hire and the time to fill, and mark the slowest stage.
Note the offer-acceptance rate and the stage where most candidates dropped out.
Separate waiting time (scheduling, approvals, silence) from working time, and decide which one to shorten.
Fix one thing before the next hire, and write down what you changed.

Why it works: A single total hides where the delay sits. Per-stage timing points at the one step to fix, and the acceptance rate and drop-out points show whether candidates kept pace with the process.

Record for every hire

Time to hire: days from the successful candidate entering the pipeline (application or first contact) to the accepted offer. Average it across hires for mean time to hire.
Time to fill, recorded separately: days from requisition approval to the accepted offer.
Days per stage, from the stage's first action to its last — and whether the time was spent waiting or working.
Offer-acceptance rate: offers accepted divided by offers made.
Where candidates dropped out, and the reason you were given.
Check in at 90 days whether the hire is meeting the outcomes in the job description — that tells you whether the process picked well.

What to log for this role

Days from first contact to accepted offer for the analyst hired.
Days spent building and checking the fictional variance file before the work sample could be sent.
Whether the non-finance manager on the business-partnering round was available on the planned dates, or the round had to move.
How many candidates completed the variance exercise, and whether drop-outs came before or after opening the file.

Where this role's hiring slows down

Watch for interviews colliding with month-end close, when the finance panel has least time.
Watch for the business-partnering round waiting on a single budget holder's calendar with no named alternate.
Watch for the same variance file being reused until candidates have seen the answer elsewhere.

Compliance checkpointUKEU

Under the EU and UK GDPR, tell candidates how long you will keep their data, or the criteria used to decide. Give that notice when you collect data from them directly, or within the Article 14 time limit when it comes from another source (such as a referral or a sourcing tool). Delete or anonymise data when it is no longer needed, keeping only what a documented lawful purpose still requires.

Sources: GDPR — Regulation (EU) 2016/679, Articles 5, 13 and 14 · ICO — UK GDPR guidance · checked 2026-09-25

General information, not legal advice. Rules depend on the employer, the role and where the work is done — confirm what applies with HR or counsel.

Frequently asked questions

What does a financial analyst do?

They build and maintain budgets and forecasts, explain why actual results differ from plan, keep the models behind those numbers in order, and turn the findings into recommendations for managers. In financial services that often includes cost and margin work by product, such as cards, accounts or lending.

How does a financial analyst differ from an accountant?

An accountant records and reconciles what has happened and usually owns the month-end close. A financial analyst explains results and looks forward, through forecasts, models and commentary. The roles share rigour and often work side by side; hire for the one whose work recurs on your team.

What is a good work sample for a financial analyst?

A short variance exercise with fictional figures: actual against budget by cost line and product, a source whose definition changed partway through the year, and a request from a manager. It shows whether the candidate finds the real drivers, spots the data problem and gives a recommendation with honest limits, within a stated time.

Do we need to check a financial analyst's qualifications or registration?

Only where the role or your local rules require it. If they do, verify current status with the issuing body or applicable regulator at the references and checks stage. No work sample or interview replaces that check, and a qualification listed on a CV is not evidence on its own.

Should candidates be allowed to use AI tools in the exercise?

Yes, where your policy allows them on the job. Ask candidates to note which tools they used and how they checked the output. What matters is whether they catch a wrong or misleading figure, whoever drafted it.

Go deeper

Related hiring kits

Guides

Skills tests

See your first AI-generated assessment in 5 minutes

No credit card. No question library to learn. Paste a job description and watch H-Evaluate build.

Request early access