In this article
Before you start
Why interviewers ask this
A vague answer to a behavioural prompt costs you the one thing a résumé cannot show: evidence of how you act when a forecast misses, data conflicts or a stakeholder disagrees. The interviewer cannot see that from a list of tools, so they ask for a story. The wider set of finance rounds is in the financial analyst interview questions guide.
The role gives the reason. The U.S. Bureau of Labor Statistics describes the role as evaluating financial data, forecasting trends and preparing written reports and presentations that support recommendations (page read 26 October 2026). Corporate Finance Institute, a training provider, lists communication, critical thinking, problem-solving, attention to detail, teamwork and adaptability as soft skills of the role. A behavioural prompt tests those through one real event.
Schmidt and Hunter (1998) describe a behavioural-consistency method: applicants describe past achievements that show job-relevant skills, scored against anchored scales. A weak answer is general ("I am a team player"). A strong answer shows one event, your own actions and a result.
Financial analyst behavioural questions from first principles
- Behavioural question
- A behavioural question is an interview prompt that asks you to describe something you actually did in the past, usually opening with "tell me about a time when", so that the interviewer can judge how you act in situations like those of the job rather than how you say you would act.
- Structured interview
- A structured interview is an interview whose questions are fixed in advance from an analysis of the job and whose answers are scored by a set procedure rather than by one overall impression.
In plain words
Think of a driving test. Asking "are you a good driver?" gets a confident yes from everyone. Putting the person in a car shows what they do at a junction. A behavioural question is the junction. The analogy breaks in one place: you choose the junction yourself, from your own past, so you can prepare it.
In one precise sentence, a behavioural question asks for evidence of past behaviour, and the STAR method organises that evidence so the interviewer hears your actions and the outcome.
Note what STAR is not. The Interview Guys, a coaching site, put it plainly: "STAR" is the answer format, not a special category of questions. The same story can answer "tell me about a time you disagreed with a manager" and "describe a decision with incomplete data". Only the emphasis changes.
Step 1: Choose a story from a story bank
Choose a story from a story bank before the interview, not during it. Searching your memory under pressure produces the first event that comes to mind, which is rarely the best one.
OwlApply, a secondary coaching source used only for this idea, suggests about eight stories, each flexible enough to answer several questions with a different emphasis. Its themes include a difficult person, a deadline crunch, a failure with a fix and a decision without full information.
For analyst work, a strong bank usually includes a forecast that missed, an error you found in a model or a report, a number that two teams disagreed on, and a time you explained a result to someone who is not in finance. Write each story as bullet notes, not a script. The financial analyst interview guide places this preparation among the other rounds. What you now know: where the material comes from. Next, how to open the answer.
Step 2: Set the scene: Situation and Task in two sentences
Set the scene in two sentences. The first gives the Situation: where you were, when, and what was at stake. The second gives the Task: the part that was yours.
Keep the numbers that matter and drop the rest. "In my second quarter on the planning team, the monthly revenue forecast was off and the budget review was a week away. I owned the forecast." That is enough. The interviewer does not need the company's history or the name of every colleague.
Numbers matter in setup too, as in budgeting methods questions and how to answer them. A test: if you can delete a sentence of the setup and the Action still makes sense, delete it. Setup exists only so the Action has a reason. Writing the Task as "I owned" or "my job was" also makes it clear which part of the story is you rather than the team. What you now know: how to start fast. Next, the part that carries the answer.
Step 3: Spend most of the answer on Action
Spend most of the answer on Action. Action is the part where the interviewer learns what you personally did, and it is the one part they cannot guess from the question.
The Interview Guys suggest a split of Situation 20%, Task 10%, Action 60% and Result 10%. OwlApply reports the same split from the career advising office at the Massachusetts Institute of Technology (MIT), for a two-minute answer. These are coaching rules of thumb, not a research standard. For a 90-second answer the split means 18, 9, 54 and 9 seconds.1
What goes into the Action: say "I" for what you did and name the team's part separately, state each decision you made, and say why you chose it over the alternative. A common error, which coaches such as OwlApply warn about, is the reverse: three sentences of background, one of action, none of result. What you now know: where the time goes. Next, how to end.
Step 4: Close with a quantified Result
Close with a quantified Result. A Result says what changed because of your Action, in a number where one exists, and ends the answer cleanly.
The Interview Guys advise: Whenever possible, quantify your results with specific numbers, percentages, or measurable improvements. For an analyst the natural numbers are forecast error, hours saved, a variance explained or a decision changed. If you have no number, say what direction the measure moved and say it is an estimate; never invent one.
Add one sentence of what you would do differently. That shows judgement, and it is the part interviewers can probe with a follow-up. Then stop talking. Stories that run past the Result tend to drift into new, unprepared material. What you now know: all four moves, which the figure below shows in order.
Step-by-step description
- Choose from a story bank.
- Two sentences of context.
- Action gets most of the time.
- End on what changed.
- Choose a story from a story bank.
- Set the scene in two sentences.
- Spend most of the answer on Action.
- Close with a quantified Result.
Common financial analyst behavioural questions
Financial analyst behavioural questions cluster around a handful of situations: a model error, a forecast, a stakeholder, a deadline. The prompts below are reported by candidates in finance interviews and reworded here; none is claimed to be asked by a particular firm. Each one draws on a story-bank theme from Step 1 and tests a skill from the soft-skills list in the first section. Pick the theme that fits your own history and prepare one story for it. Then check that the same story can serve a second prompt with a different emphasis, because one well-built story usually covers two or three of the prompts in the table.
| Prompt (reported by candidates) | Story-bank theme | Signal it tests |
|---|---|---|
| Tell me about an error you found in a model or report. | Error found and fixed | Attention to detail, honesty |
| Describe explaining numbers to someone outside finance. | Explaining a result to a non-finance colleague | Communication |
| Tell me about a tight close or reporting deadline. | Deadline crunch | Prioritising under pressure |
| Tell me about disagreeing with a manager over an assumption. | Disagreement on an assumption | Judgement, teamwork |
| Describe a decision you made with incomplete data. | Decision without full information | Critical thinking, risk handling |
| Tell me about a forecast that missed. | Forecast that missed | Ownership, problem-solving |
| Describe a process you automated or improved. | Process improvement | Initiative, problem-solving |
| Tell me about juggling competing requests. | Competing requests | Prioritising, adaptability |
| Two teams disagreed on a number; how did you settle it? | Conflicting numbers | Teamwork, attention to detail |
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →Worked example
The first table shows the suggested 90-second split as seconds. The second shows what the research says about interview methods, with a derived figure of our own.
| Part | Suggested share (coaching guidance) | Seconds of 90 |
|---|---|---|
| Situation | 20% | 18 |
| Task | 10% | 9 |
| Action | 60% | 54 |
| Result | 10% | 9 |
Text description of the diagram
- The suggested split gives Action 54 of 90 seconds.
- The suggested split gives Situation 18 seconds, Task 9 seconds and Result 9 seconds.
Now an illustrative pair of answers to "tell me about a time a forecast you owned was wrong". These are invented, not a real person's story. The weak version: "We had a forecast problem in a busy quarter, the team worked hard and it worked out." It has no owner, no action and no result. The strong version: the monthly forecast was 500,000 and the actual was 440,000, a miss of 12% (illustrative numbers).1 The analyst traced it to stale deal data, replaced it with a weekly check against the sales team's list, and over the next quarter the error fell to 4% (illustrative).1
Validity is the correlation between a hiring method's score and later job performance, written r; 0 means no link and 1 a perfect one. Squaring r shows the share of variation in performance a method accounts for, which is our calculation and not a figure from any source.1 Variance explained understates the practical value of a predictor, and Schmidt and Hunter argue from r, not r squared.
| Method | Validity r | Share of variation (our calculation) |
|---|---|---|
| Structured interview, Schmidt and Hunter 1998 | 0.51 | 26% |
| Unstructured interview, 1998 | 0.38 | 14% |
| Years of job experience, 1998 | 0.18 | 3% |
| Years of education, 1998 | 0.10 | 1% |
| Structured interview, revised (Master International table of Sackett et al. 2021/2022) | 0.42 | 18% |
| Unstructured interview, revised (same Master International table) | 0.19 | 4% |
Text description of the diagram
- Structured interview validity is 0.51 against 0.38 for the unstructured interview.
- Years of experience scores 0.18 and years of education 0.10.
The 1998 paper reports a structured interview validity of 0.51 against 0.38 for the unstructured interview.1 It also reports that years of experience scores 0.18 and years of education 0.10.
Trade-offs and edge cases
The headline figure moved. The 1998 estimate of 0.51 for the structured interview was later revised down: Master International's table of Sackett et al. (2021/2022) gives 0.42 for the structured interview and 0.19 for the unstructured one, down from 0.38. The ranking held, with the structured form still ahead. Quote both figures with their dates, and treat the revised ones as read through a summary table, not the original paper.
An average is not a promise. Validity is an average across many jobs and employers, so it says nothing certain about one candidate or one interviewer. Schmidt and Hunter also note that structured interviews cost more and in some forms contain job-knowledge components, so they may not suit inexperienced entry-level applicants.
The interview you sit may not be structured. Many are conversations, so prepare a story bank that works for both. Combining methods helps: the same paper gives a structured interview plus a general mental ability (GMA) test a combined validity of 0.63 (Schmidt and Hunter, 1998).1 Experience alone is weak: 0.18, so a short résumé is not a verdict.
Treat any percentage on how often finance employers run behavioural rounds with suspicion unless it names a dated source. The numbers-focused rounds are covered in budgeting methods questions. For a wider set of finance prompts, see finance behavioral interview questions, and for the same skills across other jobs, behavioral interview questions by competency. Technical rounds are in financial modeling interview questions.
How to answer it in an interview
Tell me about a time a forecast you owned turned out to be wrong.
My monthly revenue forecast missed by 12% because two large deals slipped. I owned the number, so I traced the miss to stale pipeline data, rebuilt the input as a weekly check with the sales team, and told my manager the cause and the fix before the review. Over the next quarter the forecast error fell to about 4%. The trade-off was a few extra hours of work each week, and I would now flag deal risk earlier.
The figures in the answer are the illustrative ones computed above.1 The spoken structure: two sentences of setup, most of the time on what you did, one result with a number, then one thing you would change.
Common mistakes
- "Behavioural questions are just chat, so I will wing it." (wrong) An unprepared answer wastes your one chance to show evidence; the research on structure is about how interviewers design and score interviews, not about how you answer. (right) "I prepare a story bank and a fixed answer shape."
- "STAR is the kind of question they ask." (wrong) STAR is the answer format, not a question type. (right) "I use STAR to organise any 'tell me about a time' answer."
- "We built the model and we fixed the error." (wrong) The interviewer cannot tell what you did. (right) "The team shared the work; I wrote the check that found the error."
- A long Situation, no Result. (wrong) The answer ends where the story gets useful. (right) "Two sentences of context, the Action, then a measured Result."
Follow-up questions
What is the STAR method, and is it a type of question?
STAR is an answer format with four parts: Situation, Task, Action, Result. It is not a type of question; any behavioural prompt can be answered with it. The financial analyst interview guide places it among the other answer formats.
How long should a behavioural interview answer be?
There is no standard. The worked example uses 90 seconds, a length within the 90-second to two-minute range that OwlApply mentions; shorter is fine if Action and Result are covered.
How many stories should I prepare for behavioural questions?
OwlApply, a secondary coaching source, suggests about eight, each flexible enough to answer several questions. What matters is that each is real and that you can tell it in the shape of Step 3 and Step 4.
Do behavioural interviews predict job performance?
Structured ones do better than unstructured ones: 0.51 against 0.38 in the 1998 estimates, and 0.42 in a later revision for the structured form. Neither number settles the outcome for one candidate.
What if I am applying for an entry-level analyst role with little experience?
Choose stories from coursework, internships, society roles or personal projects that involved data and a decision.
- Behavioural questions ask for a real past example, and STAR is the answer format, not a question type.
- Spend most of the answer on your own Action and end with a quantified Result.
- Prepare a story bank of about eight real events and reuse each one.
- Structured interviews predicted job performance better than unstructured ones, but the figures were revised down.
- Validity is an average across jobs, so it does not predict one candidate.
Sources
- The Validity and Utility of Selection Methods in Personnel Psychology (Psychological Bulletin 124(2), 262-274) — American Psychological Association (Schmidt and Hunter), 1 Jan 1998
- New study providing updated validity estimates — Master International (summary of Sackett et al. 2021/2022), 14 Mar 2022
- Financial Analysts: Occupational Outlook Handbook — U.S. Bureau of Labor Statistics, 20 Oct 2026
- What Does a Financial Analyst Do? Role, Skills and Path — Corporate Finance Institute (secondary), 3 Feb 2026
- STAR Interview Questions: The Top 10 Questions and Sample Answers — The Interview Guys (secondary), 1 Aug 2026
- 40 Behavioral Interview Questions and STAR Answers — OwlApply (secondary), 1 Sep 2026
