Financial Analyst Interview Questions and Scorecard
Financial analyst interview questions for employers: 34 questions across 5 sets with why to ask and what a strong answer sounds like, plus a scorecard.
Financial Analyst Interview Questions and Scorecard
34 employer-side questions across five sets, each with the reason it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard and a short modeling exercise. Built for small businesses without an HR department. Download as DOCX.
The first financial analyst a small company hires is usually hired by someone who cannot personally check the answers. I have sat on that side of the table, nodding along to a fluent explanation of a discounted cash flow model with no way to tell whether the candidate had ever built one. The fix is not to learn finance before the interview. It is to ask questions that produce answers you can judge.
At FirstHR, we build for owners and managers who hire without an HR department, where the founder runs the interview alone between everything else. This page gives you 34 employer-side questions across five sets, each with the reason it is worth asking and what a strong answer sounds like, plus a scorecard and a short modeling exercise. If you still need the posting, start with the financial analyst job description.
TL;DR
Interview a financial analyst across five areas: technical foundations, modeling and spreadsheet craft, forecasting and variance, business partnering, and behavioral evidence. The highest-signal opener is asking them to link the three financial statements. Add a 45 to 60 minute modeling exercise and score the structure, not the number. Federal data puts the median wage at $102,740 a year. Download 34 questions and a scorecard as DOCX.
What to Assess in a Financial Analyst
Assess five things: whether they understand the numbers, whether they can build a model another person can audit, whether they can run a forecasting and variance cycle, whether they can explain any of it to people who do not think in numbers, and whether they will tell you an answer you do not want. The last two are where small-company analyst hires most often go wrong.
The role itself is broader than the title suggests at your size. The federal occupation, financial and investment analysts, covers people who evaluate investments and business performance and make recommendations. Inside a large company that work is specialized and the data arrives clean. Inside a small one the same person pulls the data, cleans it, models it, presents it, and then defends it to a department head. Interview for that reality, not for a job description borrowed from a bank.
Write Down Your Three Questions First
Before you build the question list, write down the three questions you most want answered every month: whether to add a shift, which product line actually makes money, how long the cash lasts at the current burn. Those three questions tell you which sets below to weight and what the modeling exercise should look like. They also make the interview concrete, because you can ask each candidate how they would answer them here.
The Five Question Sets and the Scorecard
The 34 questions are grouped into five sets plus a scorecard. Each set targets a different part of the role, and a strong candidate performs across all of them rather than only on the technical questions they have rehearsed. Take two or three from each set and use the same core list for every candidate.
Technical Foundations
Do they know the numbers?
Statements and how they link, profit versus cash, working capital, and metric judgment. Each question ships with what a strong answer sounds like, so a non-finance interviewer can score it.
Modeling and Spreadsheets
Where the job happens
Model structure, auditability, lookups, scenarios, error checks, and automation judgment. Weight this set heavily for any analyst hire.
Forecasting and Variance
The recurring cycle
Budget process, driver-based revenue forecasting, month-end variance analysis, forecast accuracy, and the reporting pack for the first 90 days.
Business Partnering
Can they be understood?
Explaining finance in plain language, changing a decision with analysis, delivering unwelcome findings, and collecting assumptions from non-finance people.
Behavioral and Integrity
Past behavior, real evidence
STAR questions on errors owned, disagreement with seniors, data validation, prioritization, and handling confidential salary and results data.
Scorecard and Exercise
Decide on evidence
A six-area 1-to-5 rubric, a red-flag checklist, and a short modeling exercise brief with its own scoring criteria. The part most question lists leave out.
Weight the sets to your situation. If the analyst will own the monthly pack and the budget, the forecasting set matters most. If they are joining to answer one big investment question, weight modeling and partnering. Every candidate should still face the integrity questions in the behavioral set, because this role sees payroll totals and margins before anyone else does.
34 Questions and a Scorecard to Download
Download all six files as a single Word document, or copy individual sets. Each set lists when to use it, the questions with the reason to ask and what a strong answer sounds like, what to listen for, and space for notes. The final file is the scorecard, the red-flag checklist, and the modeling exercise brief.
Download All 34 Questions and the Scorecard
Five question sets by competency plus a 1-to-5 scoring rubric, red flags, and a modeling exercise brief. All in one DOCX.
Set 1: Technical Foundations
Statement mechanics, profit versus cash, working capital, and metric judgment. Every question ships with what a strong answer sounds like, so you can score it without a finance background. Start here.
This set tests whether the candidate understands the numbers or only formats
them. Ask 4 to 6 of these. You do not need a finance background to score them:
each question lists why it is worth asking and what a strong answer sounds like.
Listen for a candidate who explains the mechanics in plain language.
QUESTIONS
1. Walk me through the three financial statements and how they connect.
Why ask: the fastest test of real accounting understanding.
Strong answer: net income flows into retained earnings on the balance sheet
and to the top of the cash flow statement; non-cash items and working capital
changes reconcile profit to cash; the ending cash balance ties back to the
balance sheet. Explained calmly, without notes.
Weak answer: names the three statements but cannot link them.
2. If depreciation goes up by $100, what happens across all three statements?
Why ask: it separates memorized definitions from working knowledge.
Strong answer: pre-tax income falls $100, net income falls by $100 times one
minus the tax rate; the cash flow statement adds depreciation back so cash
rises by the tax saving; on the balance sheet fixed assets fall $100, cash
rises by the tax saving, retained earnings fall by the after-tax amount, and
the balance sheet still balances.
3. Which three metrics would you track for a business like ours, and why?
Why ask: tests judgment, not recall.
Strong answer: picks metrics tied to how we actually make money (gross margin,
days sales outstanding, revenue per employee, customer payback) and names the
decision each one drives.
Weak answer: recites a generic ratio list with no link to our business.
4. What is the difference between profit and cash, and why does it matter here?
Why ask: the single most useful thing an analyst explains to an owner.
Strong answer: profit is earned, cash is collected; a growing company can be
profitable and still run out of cash through receivables and inventory.
5. How do you calculate free cash flow, and what does it tell you?
Strong answer: operating cash flow less capital expenditure, with a comment on
what it means for funding growth without outside money.
6. What is working capital, and how would you improve ours?
Strong answer: current assets less current liabilities, then practical levers:
collections discipline, payment terms, inventory turns. Asks about our cycle
before proposing anything.
7. Explain a variance to me as if I have never seen a budget.
Why ask: an analyst who cannot translate will not be used.
Strong answer: plain language, a concrete example, no jargon, and a clear
statement of what should happen next.
WHAT TO LISTEN FOR
•Mechanics explained in plain English, not memorized definitions
•Metrics chosen for our business, not a textbook list
•Comfort saying "I would need to check that" instead of bluffing
•Curiosity about how our revenue and costs actually work
NOTES
__
__
Set 2: Financial Modeling and Excel
Model structure and auditability, lookups, scenarios, error checking, and automation judgment. This is where most of the job happens, so weight it heavily and pair it with the exercise.
Financial Modeling and Excel Questions
FINANCIAL ANALYST INTERVIEW: MODELING AND SPREADSHEET SKILL
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Spreadsheet work is where most of the job happens, so this is the set to weight
heavily. The goal is not to hear tool names, it is to hear how the candidate
builds something another person can check. Pair this set with the short modeling
exercise in the scorecard file.
QUESTIONS
1. Describe a model you built from scratch. What decision did it drive?
Why ask: separates building from maintaining someone else’s file.
Strong answer: names the business question, the structure, the assumptions,
and the decision that changed. Owns the outcome, good or bad.
Weak answer: describes updating a template with no decision attached.
2. How do you structure a model so someone else can audit it?
Why ask: an unauditable model is a liability, not an asset.
Strong answer: inputs, calculations, and outputs separated; a consistent color
convention for hard-coded inputs; no numbers typed inside formulas; a
documented assumptions tab; check rows that flag when something breaks.
3. Which spreadsheet functions do you rely on, and when do you use INDEX and
MATCH or XLOOKUP rather than VLOOKUP?
Strong answer: explains the fragility of column-position lookups and gives a
real case where it mattered. Mentions pivot tables and named ranges naturally.
4. How do you build scenarios or run a sensitivity analysis?
Why ask: single-point forecasts are the most common analyst failure.
Strong answer: a scenario switch driven from one input cell, two or three
named cases, and a sensitivity table on the two assumptions that actually
move the answer.
5. How do you check a model for errors before anyone relies on it?
Strong answer: a real routine: balance checks, tracing precedents, sanity
testing against known totals, a second pair of eyes, and stress-testing
extreme inputs. Assumes their own work contains mistakes.
6. What have you automated, and what do you deliberately keep manual?
Why ask: judgment about where automation pays off.
Strong answer: automates repetitive pulls and refreshes, keeps judgment steps
manual, and can explain the tradeoff.
7. What is your experience with SQL, Power Query, or a BI tool?
Strong answer: honest about depth. A candidate who can pull their own data is
worth more at a small company than one who files requests.
WHAT TO LISTEN FOR
•Structure and documentation habits, not just formula names
•Scenarios and ranges rather than one confident number
•A real error-checking routine
•Honesty about the edge of their skill
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
The budget process, driver-based revenue forecasting, month-end variance analysis, forecast accuracy, and the reporting pack they would build in the first 90 days.
Use this set when the role owns the budget cycle, the rolling forecast, or the
monthly reporting pack. These are the questions that reveal whether a candidate
has run a real planning cycle or only contributed a tab to one.
QUESTIONS
1. Walk me through how you would build an annual budget for a company our size.
Why ask: shows whether they can run a process, not just a spreadsheet.
Strong answer: a timeline, a driver-based approach, department inputs
collected on a schedule, a review loop, and a version that gets locked.
Weak answer: last year plus a percentage, with no drivers.
2. How would you forecast revenue when we have limited history?
Strong answer: builds from drivers (units, price, pipeline, capacity) rather
than trend lines, states the assumptions openly, and gives a range.
3. Describe your month-end variance analysis process.
Why ask: variance work is the recurring core of the job.
Strong answer: a materiality threshold so small variances are ignored, the
split between volume and rate, a written explanation for each large item, and
a follow-up with the budget owner rather than a spreadsheet dropped in email.
4. Actuals miss the forecast badly. What do you do first?
Strong answer: verify the data before raising an alarm, isolate the driver,
then tell the person who owns the number before it appears in a report.
5. A department head wants a budget number you cannot support. How do you handle
it?
Why ask: an analyst with no spine produces numbers nobody should trust.
Strong answer: shows the calculation, asks what changed in their assumptions,
offers a documented scenario, and escalates with facts rather than arguing.
6. How accurate were your forecasts, and how did you measure that?
Why ask: analysts who track their own error rate are rare and valuable.
Strong answer: a specific method and a specific number, plus what they changed
after a bad quarter.
7. What reporting pack would you produce in your first 90 days here?
Strong answer: a short list tied to decisions we need to make, delivered on a
fixed calendar, not a 40-page book nobody reads.
WHAT TO LISTEN FOR
•A repeatable process with dates, owners, and a lock point
•Driver-based thinking instead of percentage growth
•Ranges and stated assumptions
•Willingness to defend a number with evidence
NOTES
__
Set 4: Business Partnering and Communication
Explaining finance in plain language, changing a decision with analysis, delivering findings nobody wants, and collecting assumptions from people who do not think in numbers.
Business Partnering and Communication Questions
FINANCIAL ANALYST INTERVIEW: BUSINESS PARTNERING
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
At a small company the analyst sits close to the owner and to every department
head, so the ability to explain and to influence matters as much as the modeling.
Use this set for every candidate. Ask them to explain something to you directly
and watch what happens.
QUESTIONS
1. Explain a financial concept of your choice to me as if I have no finance
background.
Why ask: the cleanest live test of translation skill.
Strong answer: picks something relevant, uses a concrete example, checks
whether you followed, and skips the jargon entirely.
Weak answer: lectures in acronyms and never checks understanding.
2. Tell me about a time your analysis changed a decision.
Why ask: analysis nobody acts on is expensive decoration.
Strong answer: the question asked, what the analysis found, who they persuaded
and how, and what the business did differently afterward.
3. How do you present a recommendation the leadership team will not want to hear?
Strong answer: leads with the finding, shows the working, offers options
rather than only a verdict, and separates fact from opinion.
4. How do you gather assumptions from people who do not think in numbers?
Why ask: at a small company nobody hands the analyst clean inputs.
Strong answer: interviews operators, translates their language into drivers,
confirms the number back to them in writing, and dates the assumption.
5. Someone asks you for a number that supports a decision they already made. What
do you do?
Why ask: this happens, and the response reveals the candidate’s integrity.
Strong answer: provides the honest number, presents the case for and against,
and does not quietly rework assumptions to reach a preferred answer.
6. What questions would you ask us in your first week?
Strong answer: asks about how we make money, where the data lives, who owns
which budget, and what decision is pending. Curiosity here predicts speed.
WHAT TO LISTEN FOR
•Plain language and checking for understanding
•Evidence that analysis led to action
•Comfort delivering unwelcome findings
•Refusal to bend numbers to a preferred conclusion
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
STAR questions on errors owned, disagreement with senior people, data validation, prioritizing competing requests, and handling confidential salary and results data.
Behavioral, Judgment, and Data Integrity Questions
FINANCIAL ANALYST INTERVIEW: BEHAVIORAL AND DATA INTEGRITY
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Past behavior predicts future behavior better than a hypothetical, so ask these
as real examples and press for the result. Score answers on the STAR pattern:
Situation, Task, Action, Result. An analyst handles confidential numbers, so
integrity questions belong in every interview for this role.
QUESTIONS
1. Tell me about a time you found a mistake in your own work after it had been
shared.
Why ask: everyone makes modeling errors; what matters is what happens next.
Strong answer: raised it immediately, quantified the impact, corrected the
record, and added a check to prevent a repeat. No blame shifting.
Weak answer: claims never to have made one.
2. Describe a time you disagreed with a senior person about the numbers.
Strong answer: brought evidence, stayed calm, sought the source of the
difference, and accepted the decision once it was made on full information.
3. Tell me about the largest or messiest dataset you have worked with. How did
you validate it?
Why ask: bad data quietly ruins good analysis.
Strong answer: reconciled to a trusted total, checked for duplicates and
date gaps, spot-checked source records, and documented what they cleaned.
4. Three people need analysis from you the same afternoon. How do you decide?
Strong answer: asks what decision each output feeds and by when, negotiates
explicitly, and communicates the tradeoff rather than going quiet.
5. What is the biggest error you have made in a model, and what changed after?
Strong answer: a specific story with a specific process change.
6. How do you handle confidential financial and payroll information?
Why ask: this role sees salary data and results before anyone else.
Strong answer: treats access as a duty, keeps files controlled, does not
discuss numbers outside the people who need them.
7. Why this role at a company our size, rather than a larger finance team?
Why ask: tests fit and reduces early attrition.
Strong answer: wants breadth, proximity to decisions, and ownership. A
candidate who only wants a title should worry you.
WHAT TO LISTEN FOR
•Specific examples with measurable results, not generalities
•Ownership of mistakes and a process change that followed
•Data validation habits described without prompting
•A real reason to want a small-company role
NOTES
__
Set 6: Scorecard, Red Flags, and Modeling Exercise
A six-area 1-to-5 rubric with space for evidence, an eight-item red-flag checklist, and a modeling exercise brief with its own scoring criteria. Use it with any set above.
Scorecard, Red Flags, and Modeling Exercise
FINANCIAL ANALYST SCORECARD, RED FLAGS, AND MODELING EXERCISE
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO SCORE
Score every area from 1 to 5 immediately after the interview, while it is fresh,
and anchor each score to something the candidate actually said. If more than one
person interviews, each scores independently before anyone talks. Use the same
rubric for every candidate for the same role.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Technical foundations: statements, cash vs profit, metric judgment
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Modeling and spreadsheet craft: structure, auditability, scenarios, checks
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Forecasting and variance: driver-based process, accuracy, follow-through
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Communication and partnering: plain language, influence, unwelcome findings
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Judgment and integrity: owns errors, validates data, will not bend numbers
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Fit for a small team: breadth, self-service data, ownership
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
RED FLAGS (WEIGH CAREFULLY)
[ ] Cannot link the three financial statements
[ ] Gives one confident number and no range or assumptions
[ ] Describes models with no checks and no documentation
[ ] Blames data, tools, or colleagues for every past problem
[ ] Claims never to have made a modeling error
[ ] Will not explain anything without jargon
[ ] Vague about what they personally built versus inherited
[ ] Hints they would adjust assumptions to reach a wanted answer
SHORT MODELING EXERCISE (45 TO 60 MINUTES, PAID IF EXTENDED)
Give the candidate a small, clean brief and a blank sheet. Judge the structure
more than the answer.
Brief: "Here is 24 months of revenue by product line and a simple cost list.
Build a 12-month forecast with a base case and a downside case. Tell us the two
assumptions the answer is most sensitive to, and what you would want to know
that we did not give you."
Score the exercise on:
[ ] Inputs separated from calculations and outputs
[ ] Assumptions written down and labelled
[ ] A working scenario switch
[ ] At least one check or balance row
[ ] A clear one-paragraph summary of what the model says
[ ] The questions they asked about the missing information
Keep the completed scorecards with the rest of the hiring record rather than in a personal notebook, so the decision is documented and consistent if you ever need to explain it. Once you hire, FirstHR stores the signed offer and onboarding documents on the employee profile alongside those records. Applicant tracking is coming soon to FirstHR.
What a Strong Answer Sounds Like
You do not need to grade the finance yourself, you need to tell a strong answer from a weak one, and the pattern is consistent across every set. Strong answers are specific, structured, and honest. Weak answers are confident but vague, or arrive as a single number with no range and no stated assumptions.
Walk me through the three financial statements and how they connect.
Why ask it: It is the fastest way to tell whether a candidate understands the numbers or only formats them, and it works even if you have no finance background yourself.
Strong answer: Net income flows into retained earnings on the balance sheet and to the top of the cash flow statement, non-cash items and working capital changes reconcile profit to cash, and the ending cash balance ties back to the balance sheet. Delivered calmly, in plain language, without notes.
Weak answer: Names the three statements, describes each one in isolation, and cannot say how a change in one moves the others.
How do you structure a model so someone else can audit it?
Why ask it: A model nobody else can check is a liability. At a small company you will be the one relying on it, so the structure matters more than the cleverness.
Strong answer: Inputs, calculations, and outputs kept separate, a consistent color convention for hard-coded inputs, no numbers typed inside formulas, an assumptions tab that is dated, and check rows that flag when something stops balancing.
Weak answer: Talks only about advanced functions, has no documentation habit, and treats the file as personal rather than as a company asset.
How accurate were your forecasts, and how did you measure that?
Why ask it: Analysts who track their own error rate are rare, and the habit is the strongest single predictor that the forecasts you get will improve over time.
Strong answer: A specific method, a specific number, and a concrete change they made to the model or the process after a quarter that missed. Comfortable naming a bad result.
Weak answer: Never measured it, or answers that the forecast was accurate without any way of knowing whether that is true.
Someone asks you for a number that supports a decision already made.
Why ask it: This will happen at a small company, and the answer tells you whether the analysis you commission will be worth trusting.
Strong answer: Gives the honest number, lays out the case for and against, and offers a documented scenario rather than quietly reworking assumptions to reach the preferred answer.
Weak answer: Treats it as a service request, or signals that assumptions are negotiable depending on who is asking.
Two follow-ups do most of the work. What was the result forces a number instead of a story, and what would make this wrong forces the candidate to name their own weak assumptions. An analyst who cannot name them has not thought hard enough about the model. One who names them immediately is telling you how they work.
What to Probe For (and Red Flags)
The listed questions get you started, and the follow-ups are where you learn the most. Push for the specific number, the actual decision, the part they personally built. Watch for false certainty, which in this role is more dangerous than a gap in knowledge.
Push for the specific
What was the number, before and after?
What did you build versus inherit?
Who acted on it, and what changed?
Test the assumptions
Which two inputs move the answer most?
What would make this forecast wrong?
How did you check the source data?
Watch for false certainty
One number with no range is a warning
A model with no checks is another
Never made an error is the loudest
Fit for a small team
Can they pull their own data?
Will they talk to operations directly?
Do they want breadth or a narrow lane?
Red flag
Why it matters
Follow-up to ask
Cannot link the three statements
Suggests reporting experience, not analysis
How does a change in inventory hit cash?
One number, no range
Single-point forecasts hide the real risk
What is the downside case, and why?
No checks in the model
Errors reach a decision before anyone notices
How would you know if this broke?
Never made a modeling error
Either untrue or never owned the output
What is the closest you came to one?
Cannot explain without jargon
The analysis will not be used
Say that again for someone in operations
Vague about what they built
May have inherited someone else’s work
Which tabs did you create yourself?
None of these is disqualifying on its own, and a nervous candidate can stumble on a statement question and still be excellent. Treat each one as a prompt to probe rather than a verdict, and let the pattern across the whole scorecard decide, not a single bad moment.
The Short Modeling Exercise
A short modeling exercise is the highest-signal step in the whole process, because modeling ability is easy to describe and hard to fake in a spreadsheet. Keep it to 45 to 60 minutes on a small, clean brief, and judge the structure rather than the final number.
Give the candidate 24 months of revenue by product line and a simple cost list, then ask for a 12-month forecast with a base case and a downside case, the two assumptions the answer is most sensitive to, and what they would want to know that you did not provide. That last part matters: good analysts ask before they assume. Score the exercise on the criteria below, using the same sheet for every candidate.
What you are scoring
Strong submission
Weak submission
Inputs separated from calculations
Assumptions written down and labelled
A working scenario switch
At least one check or balance row
Plain-language summary of the result
Asked about the missing information
If you extend the exercise beyond an hour, or ask a candidate to work on your real data, pay them for the time. A paid short exercise gets better candidates to say yes, and it keeps the process defensible. The same brief for every candidate is what makes the comparison worth anything.
Fair, Legal, and Structured Interviewing
A good interview is fair, legal, and structured, and the three reinforce each other. Asking the same job-related questions of everyone keeps you compliant, reduces bias, and produces better hires at the same time. This is the part generic question lists skip.
Ask about the job, not the person
Federal anti-discrimination law prohibits basing a hiring decision on protected characteristics, and questions that probe them create risk even when they are asked as small talk. For a financial analyst interview the traps are ordinary conversation: do not ask how old the candidate is, whether they have or plan to have children, where they are originally from, or about religious observance. You may ask whether they can perform the essential functions of the role and whether they are authorized to work in the United States. Every question in the sets on this page is written to stay on the job. This is general information, not legal advice.
Use the same core questions for everyone
Asking each candidate the same core questions is both fairer and more accurate. A structured interview, where every candidate faces the same questions scored against the same rubric, predicts on-the-job performance far better than a free-flowing conversation, and it keeps a hiring decision from resting on rapport. For an analyst hire this matters more than usual, because a confident presenter can talk about modeling far better than they can model. Write the questions in advance, ask them consistently, and score them the same way.
Score independently, then discuss
When more than one person interviews, have each interviewer complete the scorecard alone before the group talks. This stops the most senior voice in the room from anchoring everyone else, which is the usual way a weak candidate gets talked into and a quiet strong one gets talked out of. Compare the written evidence first, then discuss the gaps. For an owner who is also the hiring manager, the scorecard is the discipline that keeps one strong impression from deciding the hire.
Be careful with salary history and pay questions
A growing number of states and cities restrict asking candidates about their salary history, and several require you to disclose a pay range at some point in the process. The rules vary by jurisdiction and change, so check your own state and city before you build the question list, and default to asking about the candidate’s pay expectations for this role rather than what they earned previously. Applying the same practice to every candidate is the safest habit. This is general information, not legal advice.
Same Questions, Scored on a Rubric
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an unstructured conversation, and asking the same job-related questions of everyone also keeps you within the EEOC rules against basing decisions on protected characteristics. Structure is the fairer and the more effective approach at the same time.
Two more habits are worth building in. Keep every question tied to the job and avoid the small-talk traps about age, family, origin, or religion, which are covered in more depth in our guide to illegal interview questions. And check your own state and city rules on salary history before you ask about pay. This is general information, not legal advice.
What Financial Analysts Are Paid
Financial analyst pay varies widely by industry, location, and seniority, so use federal data as the baseline and adjust for your market. The spread matters more than the median for a small business, because the top of the range reflects specialists inside large financial institutions rather than a first analyst at an operating company.
Median $102,740 a Year (BLS OEWS, May 2025)
Financial and investment analysts had a median annual wage of $102,740, about $49.40 an hour, according to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025). The lowest 10 percent earned under $63,720 and the 25th percentile was $79,290, while the 75th percentile reached $133,340 and the top 10 percent exceeded $180,860 (U.S. Bureau of Labor Statistics).
A first analyst hire at a small operating company usually lands between the 10th percentile and the median, and the full cost adds payroll taxes, benefits, and software seats on top of base pay. If the budget does not stretch, a junior analyst with strong spreadsheet craft and a senior reviewer is often the better trade than stretching for a title.
Classification is a separate question from pay level. Under the Fair Labor Standards Act, an analyst can qualify for the administrative exemption only if they are paid on a salary basis of at least $684 per week and their primary duty involves independent judgment on significant matters. The job title does not decide it, the duties do, and some states set stricter rules. This is general information, not legal advice.
Interviewing an Analyst Without an HR Department
At a large company an analyst candidate runs through coordinated panels with recruiters managing scorecards and a finance leader grading the technical rounds. At a small business the owner usually runs the interview alone, without a finance background, and a bad hire in this seat quietly produces numbers nobody should have trusted.
You are hiring an analyst without being one yourself
Most owners hiring a first analyst cannot personally grade a three-statement walkthrough, which is why the question sets here pair every question with the reason it is worth asking and what a strong answer sounds like. You are not judging the accounting, you are judging whether the answer is specific, structured, and honest. A candidate who explains cash versus profit in plain language and asks how our revenue actually works is showing you the two things the role needs most. One who retreats into jargon is showing you something too.
One analyst at a small company is a generalist, not a specialist
At a large company an analyst sits inside a planning team with clean data handed to them. At a small company the same title means pulling the data, cleaning it, building the model, presenting it, and then explaining it again to a department head who disagrees. Interview for that reality: ask whether they can get their own data, whether they will talk to operations directly, and why they want breadth rather than a narrow lane. A candidate who has only ever worked inside a big finance function may be excellent and still be a poor fit for a team of one.
The interview is step one; the offer and onboarding are where it gets real
Once you choose someone, the work shifts from evaluating to hiring well: a written offer, a confidentiality agreement because this role will see salary and results data early, the standard new hire paperwork, and system access granted deliberately. FirstHR fits that people side for a small business: send the offer for e-signature, run the onboarding workflow and task list, and store the signed documents and interview records on the employee profile. FirstHR is an onboarding and HR platform, not accounting, planning, or business intelligence software, so pair it with those. Applicant tracking is coming soon to FirstHR.
The practical version is short. Use the same questions for everyone, run the exercise, score the rubric immediately, and treat the reference call as a real step rather than a formality. Ask a former manager specifically whether the candidate ever told them something they did not want to hear, because that answer predicts more about this role than any technical detail. Our guide to reference checks covers the rest of the call.
From Interview to Onboarding
The interview is step one. Once you choose someone, the job shifts to hiring well: a written offer, a signed confidentiality agreement, the standard new hire paperwork, and system access granted deliberately rather than all at once on day one.
Prepare the same question set
Pick the sets that match the role, and ask the same core questions of every candidate so the comparison is fair and defensible.
Score the rubric and the exercise
Rate the six areas from 1 to 5 with written evidence, and score the modeling exercise on structure rather than on the final number.
Send the offer and the NDA
Confirm role, pay, and start date in writing, and have the analyst sign a confidentiality agreement before they see salary or results data.
Onboard for the first 90 days
Give the analyst a defined reporting pack, named data owners, and system access, so the first useful output arrives in weeks.
An analyst hire has a few onboarding steps most roles do not, because this person will see payroll totals and margins in their first month. Handle the new hire paperwork and the I-9 as usual, then add the access and data-ownership steps below before the first close.
Sign the confidentiality agreement first
An analyst sees payroll totals, margins, and results before anyone else. Get the NDA signed before access is granted, not after the first report.
Grant data access deliberately
Decide which systems the analyst reads and which they can write to. Read access to accounting data is usually enough to start.
Name the data owners
Write down who owns each source system and each budget line, so the analyst is not guessing where a number came from.
Agree the reporting calendar
Fix the dates for the monthly pack and the variance review in week one, so the cadence exists before the first close.
FirstHR connects the offer, the confidentiality agreement, e-signatures, and the onboarding workflow in one place, and keeps the signed documents and interview records on the employee profile, so a small business can run hiring through onboarding from one system. FirstHR is an onboarding and HR platform, not accounting, planning, or business intelligence software, so connect those separately. Applicant tracking is coming soon to FirstHR.
If you are still shaping the role, the rest of the hiring templates cover the posting and the evaluation paperwork, and the controller interview questions are the closest neighbor if the job is really about owning the books rather than analyzing them.
Key Takeaways
Assess a financial analyst on five areas: technical foundations, modeling craft, forecasting and variance, partnering, and behavioral evidence.
Open with the three-statement walkthrough; it is the fastest test of whether a candidate understands the numbers or only formats them.
Judge answers on specificity, structure, and honesty rather than on finance knowledge you do not have.
Run a 45 to 60 minute modeling exercise and score the structure, not the final number.
Treat false certainty as a red flag: one number with no range, and a model with no checks, are both warnings.
Use BLS data as the baseline: financial and investment analysts reported a median of $102,740 a year in May 2025.
Frequently Asked Questions
What questions should I ask a financial analyst candidate?
Ask across five areas: technical foundations, modeling and spreadsheet craft, forecasting and variance, business partnering, and behavioral evidence. The strongest single opener is to have them walk you through the three financial statements and how they connect, because it separates real understanding from formatting work. Follow with how they structure a model so someone else can audit it, how they would build a budget for a company your size, how they explain a financial concept to a non-finance listener, and a time their analysis changed a decision. Close with an integrity question about being asked for a number that supports a decision already made. Ask the same core questions of every candidate and score them on a rubric. The sets on this page give you 34 questions, each with the reason to ask it and what a strong answer sounds like.
How do I evaluate a financial analyst if I am not a finance person?
You do not need to grade the finance yourself, you need to tell a strong answer from a weak one, and the pattern is consistent. Strong answers are specific, structured, and honest: a named number, a named decision, an admitted mistake with a process change that followed. Weak answers are confident but vague, arrive as a single figure with no range or assumptions, or hide behind jargon. Two questions do most of the work for a non-finance interviewer. Ask the candidate to explain a financial concept as if you have no background, then watch whether they check that you followed. Ask what would make their forecast wrong, because an analyst who cannot name their own weak assumptions has not thought hard about them. Pair the interview with the short modeling exercise and score the structure of what they build.
Should I give a financial analyst candidate a modeling test?
Yes, a short one is the highest-signal step in the process, because modeling ability is easy to describe and hard to fake in a spreadsheet. Keep it to 45 to 60 minutes, give a small clean brief with real-shaped data, and ask for a 12-month forecast with a base case and a downside case, plus the two assumptions the answer is most sensitive to. Judge the structure more than the number: inputs separated from calculations, assumptions written down, a working scenario switch, at least one check row, and a plain-language summary of what the model says. Also note the questions they ask about the information you deliberately left out, because good analysts ask before they assume. If you extend the exercise beyond an hour or ask candidates to work on your real data, pay them for the time.
What is the difference between a financial analyst and an accountant?
An accountant records and reports what already happened, while a financial analyst uses that record to explain what it means and what to do next. Accounting work is the close, the ledger, reconciliations, statements, and compliance. Analyst work is budgeting, forecasting, modeling, variance analysis, pricing and margin work, and the recommendations that come out of it. The federal occupation for the analyst role is financial and investment analysts, distinct from accountants and auditors. At a small business the two often overlap, and a first finance hire may do both, so decide which side you actually need before you write the questions. If you mostly need clean books and a smooth tax season, hire for accounting. If you need to know whether to add a product line or a shift, hire for analysis.
How much does a financial analyst cost to hire?
Pay varies widely by industry, location, and seniority. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), financial and investment analysts had a median annual wage of $102,740, about $49.40 an hour. The spread is the useful part for a small business: the lowest 10 percent earned under $63,720 and the 25th percentile was $79,290, while the 75th percentile reached $133,340 and the top 10 percent exceeded $180,860. The upper end reflects senior specialists inside large financial institutions rather than a first analyst at an operating company, so a small business hire usually lands between the 10th percentile and the median. Add payroll taxes, benefits, and software seats on top of base pay when you budget. This is general information, not compensation advice.
Is a financial analyst exempt from overtime?
Often, but not automatically, and the classification depends on duties and salary rather than on the job title. Under the Fair Labor Standards Act, an employee can qualify for the administrative exemption only if they are paid on a salary basis of at least $684 per week, or $35,568 a year, and their primary duty is office work directly related to management or general business operations that includes the exercise of independent judgment on significant matters. An analyst who genuinely builds forecasts and makes recommendations usually meets the duties test; someone whose real job is data entry into a fixed template may not. Note that the higher salary threshold from the 2024 Department of Labor rule was vacated in court and formally rescinded, so the $684 figure applies. State rules can be stricter than the federal floor. This is general information, not legal advice.
What questions are illegal to ask in a financial analyst interview?
Avoid anything that probes a characteristic protected under federal law: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, or genetic information. In practice that means not asking how old someone is, whether they have or plan to have children, where they are originally from, what their religion is, or about health conditions, even as friendly small talk before the real questions start. You may ask whether the candidate can perform the essential functions of the job and whether they are legally authorized to work in the United States. Separately, many states and cities restrict asking about salary history and some require you to share a pay range, so check your own jurisdiction and ask about pay expectations for this role instead. Asking the same job-related questions of everyone is the simplest safeguard. This is general information, not legal advice.
How long should a financial analyst interview be?
Plan 45 to 60 minutes for the main interview, plus a separate 45 to 60 minute modeling exercise. That is enough to take two or three questions from each of the five sets, ask real follow-ups, and leave room for the candidate to ask their own questions, which tells you a lot about how they think. Depth beats breadth here: three questions with genuine follow-ups reveal more than fifteen asked as a checklist. The single most useful follow-up is what was the result, because a strong candidate has the number ready and a weaker one retreats into generalities. Most small businesses run two rounds plus the exercise: a first conversation, the exercise, and a final round with whoever else the analyst will work with. Score immediately after each conversation while the answers are still fresh.
