Ey Quantitative Analyst Interview Guide

We've seen EY treat this Quantitative Analyst process less like a quiz and more like a stress test of judgment. Multiple candidates reported that the interviewers kept pushing past definitions into how a model behaves in the real world: backtesting, robustness, overfitting, and what the metrics actually say about performance. One candidate described the hardest moment as defending a strategy evaluation, while another was pressed on whether X, Y, Z could have negative correlation — a good sign that EY cares about whether you can reason from first principles, not just recite formulas.

A recurring theme is how often the conversation returns to your own work. Candidates were asked to walk through resume projects in detail, explain why they chose specific models, what coefficients meant, and how they would validate results. Even when the questions shifted into Python, SQL, or option pricing, the expectation was the same: explain your thinking clearly under pressure. We also noticed that EY’s interviews reward people who can connect technical choices to business context, whether that’s a live business case, a process optimization example, or a discussion of how you’d handle a difficult scenario.

The non-obvious takeaway is that EY seems to value breadth only when it’s anchored in practical interpretation. Candidates who did well were able to move comfortably between probability, statistics, modeling, and implementation details without sounding scripted. The ones who struggled usually knew the topic, but couldn’t defend it when the interviewer kept asking “why this model, why this metric, why this conclusion?”