Quant Behavioral Interview Questions: Explain Your Decisions

Preparing for a quant behavioral interview means finding real examples of how you make decisions, work with other people and improve after mistakes. A polished answer is useful only if you can defend the details when someone asks what happened next.

You do not need a trading internship for every story. Coursework, research, software, sport and other team activities can provide evidence, provided you describe their actual scope and your own contribution. Start with work you know well enough to discuss without inventing a better ending.

Official guidance supports this emphasis. Jane Street's trading interview overview describes collaborative problem solving and values openness to feedback and correcting mistakes. Optiver's software engineering interview guidance explicitly recommends reflecting on past experiences, structuring answers with STAR, practicing aloud and being authentic. The latter advice concerns engineering interviews; it does not establish a universal behavioral round for every trading role.

The prompts and examples below are original practice material. All people, projects and situations in the example answers are fictional. They illustrate how to explain evidence, rather than reporting student outcomes or actual employer questions.

Build an evidence inventory before scripting answers

Choose four or five situations you remember clearly. Include a mistake, a disagreement, a hard decision with incomplete information and an example of changing your approach after feedback. One situation may support several prompts, but avoid forcing every answer into the same project.

For each, complete this table:

STAR means situation, task, action and result. Use it to organize material, then give more attention to the decision than to the background. A result does not have to be a dramatic success. Discovering that your approach was invalid can be a useful story if you explain how you recognized it and changed course.

1. Why do you want this quant role?

A useful answer connects what the role involves to something you have already explored. “I enjoy maths and want a challenging career” leaves the connection largely unexplained. Differentiate trading, research and development before deciding which experience best supports your interest.

Consider this fictional trading applicant:

In a student decision game, I liked updating a probability after new information and then deciding whether the price still justified taking the trade. I initially focused on the final profit, but reviewing my decisions showed that some winning rounds had weak reasoning. That made me want to explore work where decisions under uncertainty are central. I'm applying for trading roles, and I'm practicing probability and explaining my choices aloud.

This gives the interviewer something concrete to examine: the game, the probability update and the review. It does not claim that a classroom game is equivalent to professional trading.

For a particular firm, add a detail you have verified from its official role description or materials and explain why it matters to you. Avoid listing prestigious names, repeating a firm's homepage or claiming inside knowledge of its culture.

Practice follow-up: what have you learned about the role that makes it less attractive, and why are you still interested? An honest tradeoff is more informative than treating every feature as a benefit.

2. Tell me about a mistake

Choose a mistake with a decision you owned. Describe how it was detected, what it affected and what you did after discovering it. Avoid disguising a strength as a weakness or shifting responsibility to a teammate.

Weak fictional answer:

I'm a perfectionist, so I spent too much time improving our project, but the result was excellent.

A more useful fictional answer:

I changed a data-cleaning rule and checked only the aggregate row count. A teammate noticed that one category had almost disappeared from our summary. I traced it to how I handled missing labels, told the team which results were affected and reran the analysis. I then added category-level checks to the notebook. We submitted later than planned, and I learned that a stable total can hide a substantial change inside the data.

The second answer identifies the inadequate check and the corrective action. It also preserves the cost. If that did not happen to you, use your own example; do not borrow the fictional checks as accomplishments.

Practice follow-up: what would have detected the problem earlier? Be ready to distinguish your later improvement from what you actually knew at the time.

3. Describe a disagreement with a teammate

A disagreement story should reveal how you handled competing ideas. “I explained my solution and everyone agreed” says little about whether you listened or whether the other person's concern was reasonable.

In a fictional scheduling project, one person wants a more accurate but slower optimization routine, while another wants a simpler heuristic. A useful explanation might say:

I preferred the optimizer because its results were better on the cases I had tested. My teammate pointed out that our demonstration had a strict response-time requirement. We agreed to compare both methods against that requirement before choosing. The heuristic met it reliably on our test cases; the optimizer did not. We used the heuristic for the demonstration and documented where it produced worse schedules.

The insight is the shared decision criterion, not that one person won. Explain how the team chose the test and what the evidence could not establish. If there was no resolution, say so and describe your next step.

Practice follow-up: what was the strongest argument against your original position? If you cannot answer, revisit whether you understood the disagreement.

4. How do you respond to feedback?

Pick feedback that changed an observable behavior. “I'm always open to constructive criticism” is a claim; a before-and-after example provides evidence.

A fictional applicant might explain that a supervisor found their presentations hard to follow because they introduced methods before the research question. The applicant then started with the question and baseline, put detailed derivations later and asked a colleague to summarize the main point after a rehearsal. That shows an attempt to check whether the change helped.

Keep the result proportional to the evidence. One clearer rehearsal does not prove you became an excellent communicator. You can say what the colleague understood and what still needed work.

Practice follow-up: was there any feedback you did not act on? Explain your reasoning respectfully and distinguish disagreement from simply ignoring it.

5. Tell me about deciding with incomplete information

Choose a decision where waiting had a cost and the available evidence had limits. Explain the objective, the uncertainty and why your chosen action was reasonable at the time.

A useful practice structure is:

“I needed to decide X by Y. I knew A and did not know B. I compared these alternatives, chose this action for these reasons and planned to revisit it if this information arrived.”

Use the structure with your own facts. Do not add probabilities retrospectively if you never estimated them. You can explain a qualitative judgment honestly and then discuss how you would make the decision more explicit now.

The trading decision games offer a separate way to practice distinguishing what was known before a choice from what became clear afterward. Their hypothetical results should not become stories about your professional experience.

6. What would you change about a project?

Choose one important limitation and explain its consequence. A long list of advanced methods you could add may obscure whether you understand the work you already did.

For a research project, identify the question, your contribution, the evidence and the largest limitation before discussing extensions. The research-project review checklist develops that technical preparation. For an engineering project, explain the constraint you would investigate next and what test would help you decide.

A good revision follows from a diagnosed problem. “I would try a larger model” needs a reason; “I would test whether the apparent gain survives a later evaluation period” names a specific uncertainty.

Rehearse follow-ups, not a memorized monologue

Record one answer, then listen for long background sections, vague “we” statements and results you cannot substantiate. As a practice target, try giving the essential story in around a minute or two and leave room for questions. This is a rehearsal suggestion, not an employer time limit.

Have a partner interrupt with “Why?”, “What did you personally do?” and “How do you know?” Those questions expose gaps that reading a script silently can miss. Keep technical details accurate when shortening an answer. Use the quant resume examples to check that the story and the written application describe the same contribution.

If your examples feel thin, the useful next step may be to do and document more work. If you have strong experience but struggle to explain it, practice selection and delivery. A quant consultation can help you discuss your background, target role and the preparation support that fits those gaps.