Financial analyst phone screen questions: FP&A, forecasts, models and business partnering
On this page
- Which financial analyst: FP A, business unit, investment or reporting
- Budgets and forecasts: what they owned
- Variance analysis: the explanation test
- Models: built, maintained or used
- Business partnering: who listened to them
- Excel, SQL and systems without a test
- Credentials: CFA, FPAC, CPA and the MBA
- Logistics, knockout checklist and scorecard
- Questions people ask
A financial analyst phone screen should find out what the candidate forecast, what they explained, and who acted on it. Ask which budget or forecast they owned, how they built the numbers, the last variance they had to explain to a manager, and a model they built from a blank sheet. Analysts who did the work name drivers, cadences and the decision their analysis changed. Inflated resumes say "financial modeling" and "strategic insights" and never say for whom.
This guide is for corporate FP&A and business-unit analyst roles. It is not the staff accountant screen, which tests the close and reconciliations; that one is in staff accountant phone screen questions. If the role is mostly SQL and dashboards with "finance" in the team name, the data analyst phone screen fits better.
Which financial analyst: FP&A, business unit, investment or reporting
The title covers very different jobs. Place the candidate in the first two minutes and compare it with what your client described at intake.
| Background | What the work usually is | Facts to ask for | Common overstatement |
|---|---|---|---|
| Corporate FP&A | Annual budget, monthly or quarterly reforecast, consolidated variance analysis, board deck support | Company revenue range, forecast cadence, which lines they owned, who presented the numbers | "Owned the budget" when they consolidated submissions from others |
| Business unit or commercial finance | Partnering with a sales, operations or product leader; pricing, headcount and spend tracking | Which leader they supported, the size of that budget, one decision they influenced | "Business partner" meaning they sent a monthly report nobody replied to |
| Investment or corporate development | Valuation, acquisition models, investment memos | Deal count and size, their part in each, which model sections they built | "Led M&A analysis" for a team of five on one deal |
| Financial reporting analyst | Management reporting, KPIs, often close-adjacent | Which reports, what system, whether they explained results or only produced them | "Forecasting" for a role that only reported actuals |
| Banking or equity research | Three-statement models, comps, pitch books | Industry coverage, model types, hours, why they want corporate work | Strong modeling mistaken for experience running a budget process |
A banker moving into FP&A can be an excellent hire, but they have usually never lived with a forecast for twelve months and been asked why it missed. Say that plainly in the submittal.
Budgets and forecasts: what they owned
Open with: "Walk me through the last budget or reforecast cycle, from the first request to the final numbers." People who ran it describe templates, deadlines, pushback and revisions. People near it describe the calendar.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| How often did you reforecast, and which lines were yours? | "Monthly rolling forecast, 18 months out. I owned operating expenses for three departments and headcount for all of them." | "I did the forecast," with no cadence or lines. |
| What were the main drivers in your forecast? | Names drivers tied to the business: headcount and loaded cost per head, units times price, pipeline times close rate, churn. | "Last year plus 5 percent" for everything, and no awareness that this is a shortcut. |
| How did you get inputs from department heads, and what did you do when they were late or padded? | A process and a story: "Marketing asked for 20 percent more every year. I showed spend against pipeline for the last four quarters and we settled at 8." | Accepted every submission as sent. |
| How accurate was your forecast, and how did you measure it? | Compares forecast to actual by line or quarter and names what drove the misses. | Has never checked. "It was pretty close." |
| Which planning tool did you work in: Excel, Adaptive, Anaplan, Pigment, Planful, or something built in-house? | Names it and what they did in it: loaded actuals, built versions, maintained driver logic, or only entered numbers. | A long list of tools with no task for any of them. |
Variance analysis: the explanation test
The single most useful question on this screen is: "Tell me about the last time actual results were well off plan. What was the difference, how did you find the reason, and who did you tell?" You do not need to know the business to judge the answer. Listen for a size, a cause below the account level, and a consequence.
- Strong: "Cost of goods was about 300K over plan for the quarter. Volume was on plan, so I split it into price and mix. Freight rates were most of it. I showed the ops VP, and we reforecast freight for the rest of the year."
- Weak but honest: "Revenue was under plan. I pulled the report by region and sent it to my manager, who took it from there." That is a junior answer; fine for a junior role.
- Red flag: "Timing." Timing is a real cause, but an analyst who explains every variance as timing has not looked.
Follow-ups that separate depth from reporting:
- "What threshold made a variance worth explaining?" A number and a percent, such as "over 50K and 10 percent."
- "Did you break revenue variance into price, volume and mix?" Candidates who have done it explain it in a sentence.
- "What happened because of your explanation?" A changed forecast, a hiring freeze, a pricing review. "Nothing" is honest and tells you the role was reporting.
Models: built, maintained or used
"Financial modeling" is on almost every resume. Place each claim on this ladder and write down the rung, not the phrase.
| Rung | What it means | Question that places them | What you hear at this rung |
|---|---|---|---|
| Used | Updated inputs in someone else's model | "Who built the model, and what did you change each month?" | "My manager built it; I dropped in actuals." |
| Maintained | Fixed and extended an existing model | "What did you add or fix, and what broke?" | "I added a new product line and had to rebuild the revenue tab's lookups." |
| Built | Designed a model from a blank sheet | "Walk me through the tabs: inputs, calculations, outputs. Who used it?" | Clear structure, named drivers, a user and a decision. |
| Owned a system | Designed the planning model the company runs on | "How did other people submit into it, and how did you control changes?" | Versioning, locked inputs, review steps, a planning tool or a disciplined workbook. |
Five model questions a non-analyst can judge
- "Did your three statements link, and how did you check the balance sheet balanced?" Strong: a check row, and a story about finding why it didn't. Red flag: a "three-statement model" with no balance sheet.
- "How did you separate inputs from calculations?" Strong: a dedicated assumptions tab, color coding, no hard-coded numbers in formulas. Red flag: never thought about it.
- "What was the most important assumption, and how sensitive was the answer to it?" Strong: names it and a sensitivity or scenario table. Red flag: every assumption was equally important.
- "Tell me about an error someone found in your model." Strong: the error, how it got there, what they changed so it wouldn't happen again. Red flag: "My models don't have errors."
- "What did the model decide?" Strong: a price, a hire, a lease, a go or no-go. Red flag: nobody remembers.
Business partnering: who listened to them
Hiring managers in FP&A often say they want an analyst who can "push back." Ask for the evidence directly, because it rarely shows up on a resume.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| Who was the most senior person who used your analysis regularly? | A title and a rhythm: "The COO, in a monthly ops review. I presented the cost slide." | Only their direct manager saw their work, for a role that partners with leaders. |
| Tell me about a time a budget owner disagreed with your numbers. | A specific disagreement, the data they brought, and an outcome, including when the owner was right. | Either always won or always deferred. |
| How did you explain a finance concept to someone outside finance? | A plain example: "I stopped saying 'accrual' and said 'we owe it, we just haven't been billed.'" | Jargon when describing how they avoid jargon. |
| What recurring report did you kill or change, and why? | Shows they asked who used it. | Produced the same reports for years without asking. |
Excel, SQL and systems without a test
Most FP&A teams still live in spreadsheets, and more of them now pull actuals with SQL or a BI tool. Ask what they did, not what they know.
- Excel: "What is the largest workbook you maintained, and what held it together?" Strong answers name INDEX/MATCH or XLOOKUP, SUMIFS, data tables for scenarios, pivot tables, and sometimes Power Query. "Advanced Excel" with no function named is a red flag.
- Actuals: "Where did actuals come from: an ERP export, a data warehouse, or accounting sending a file?" This tells you how much data wrangling the candidate has done and whether they know which ERP (NetSuite, SAP, Oracle, Dynamics) fed the model.
- SQL or BI: "Did you write queries yourself, or edit ones someone gave you?" Both are useful; only one is "SQL experience."
- Planning tools: "Were you an admin, a model builder, or a contributor in it?" Admin and builder experience in Anaplan or Adaptive is scarce and worth stating separately in a submittal.
Credentials: CFA, FPAC, CPA and the MBA
No credential is required to work as a financial analyst, so the question is what each one proves and whether the candidate describes theirs accurately.
| Credential | Issuer and what it involves (as of September 2026) | Question to ask | How to check |
|---|---|---|---|
| CFA charter | CFA Institute. Three exam levels, plus 4,000 hours of qualifying experience over at least 36 months and membership, per the charter requirements page. Experience must relate to the investment decision-making process. | "Are you a charterholder, or which level have you passed?" | The CFA Institute member directory lists current members and charterholders |
| "CFA Level II candidate" | Passed Level I, working on Level II. Not a designation. | "When did you pass Level I, and when do you sit for Level II?" | Take as stated; the resume should not show "CFA" alone |
| FPAC (Certified Corporate FP&A Professional) | Association for Financial Professionals. Two exam parts (financial acumen and financial analysis) plus two to three years of full-time FP&A experience depending on education, per AFP's eligibility page. Recertification every three years. | "Did you complete the experience requirement, or pass the exams only?" | Ask for the certificate; confirm with AFP if the role requires it |
| CPA | State boards of accountancy. Relevant for FP&A candidates coming from accounting. | "Which state, and is it active?" | Covered in the staff accountant guide |
| MBA | A degree, not a license. Program and concentration vary widely. | "What did you do before and during it, and what changed after?" | Degree verification in the client's background process |
The CFA is built around investment analysis. For a corporate budgeting role it signals discipline and valuation knowledge, not forecasting experience, so do not let it stand in for the budget questions above.
Logistics, knockout checklist and scorecard
FP&A calendars have crunch points: budget season, quarter-end reporting, board meetings. Tell the candidate when those are and ask how hours ran in their last role. Ask salary expectations rather than current pay (see salary expectation questions), ask every candidate the same work authorization and sponsorship questions, and ask where else they are interviewing.
Must-ask on every financial analyst screen
- Which kind of analyst: FP&A, business unit, investment, reporting or banking.
- The forecast lines they owned, the cadence and the main drivers.
- One variance they explained, with size, cause and consequence.
- One model placed on the used, maintained, built, owned ladder.
- The most senior person who used their work, and one disagreement.
- Planning tool and data sources, with their role in each.
- Credentials stated accurately, and checked where the role requires one.
Knock out, or flag to the client before submitting, if:
- The role owns a forecast and the candidate has never produced one, only reported actuals.
- The candidate cannot describe a single variance they explained or a model they worked in.
- A claimed credential is misstated, such as "CFA" for a candidate who has passed one level.
- Budget-season hours, on-site days or salary are a clear mismatch with the intake.
| Area | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Forecast ownership | Describes the team's process | Entered inputs for a few lines | Owned lines with named drivers | Designed the process or the driver logic |
| Variance explanation | "Timing," no detail | Pulled the report, someone else explained | Size, cause and who they told | Cause, consequence and a changed forecast or decision |
| Modeling | Used | Maintained | Built, with a user and a decision | Owned a model others submit into |
| Business partnering | Manager only | Sent reports to leaders | Presented to a leader regularly | Changed a leader's decision with evidence |
| Logistics fit | Deal-breaker | Two open questions | One open question | All aligned |
Beside each score, write the evidence in the candidate's words: "Owned opex forecast for 3 departments, monthly, 18 months out; explained a 300K freight overrun to the ops VP." Interview Signal pulls quotes like that into the scorecard from the call, so the evidence is exact rather than remembered. For senior finance leaders who run the whole function, use the controller screening questions instead.
Questions people ask
What is the difference between screening a financial analyst and a staff accountant?
A staff accountant records what happened and proves the balances are right. A financial analyst explains why results moved and predicts what happens next. So the accountant screen is about the close and reconciliations, and the analyst screen is about forecasts, variance explanations, models and the people the analyst advised.
Should a recruiter ask a financial analyst to build a model on the phone?
No. Ask them to describe a model they built: its inputs, the drivers, the outputs and who used it. A modeling test belongs with the hiring team, who can judge the result and ask about the choices.
Is the CFA useful for a corporate FP&A role?
It shows commitment and valuation knowledge, but the CFA Program is built around investment analysis, not budgeting and forecasting. For FP&A roles, treat it as a plus, not a substitute for having owned a forecast. AFP's FPAC credential is aimed at FP&A work specifically.
How do I check whether a candidate is a CFA charterholder?
Search the CFA Institute member directory. It lists current members and charterholders; lapsed or suspended members do not appear, so a missing name is a question to ask, not proof of a false claim.