JPMorgan Chase's Quantitative Analyst interviews combine HireVue or HR screens with technical rounds on statistics, forecasting, and basic coding, then a panel and final round that mix behavioral scenarios with deeper technical follow-up, typically across two to four stages.
$130K
Avg. Base Comp
$180K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
JPMorgan Chase's Quantitative Analyst interviews turn out to be less about rapid-fire math and more about demonstrating steady technical fundamentals alongside clear communication. Several candidates describe an opening stage built around a HireVue-style recorded interview or a short HR or recruiter screen. The early questions tend to be predictable: why JPMorgan, why this role, and a recent financial news story you're following. At least one candidate noted the firm wanted real substance behind those answers, not just a polished delivery.
Once candidates move into live technical rounds, the content can skew toward fundamentals rather than advanced theory. One report described a first technical interview built around forecasting experience, a simple Python for-loop exercise, basic date and time manipulation, and fundamental forecasting concepts. Knowing your own projects well enough to defend the reasoning behind them, not just the result, appears to matter as much as the technical answer itself. Another candidate's interviewers asked follow-up questions about their research and how they approached implementation.
Later rounds tend to mix panels and a hiring-manager-led final stage. In one process, a panel split responsibilities. One interviewer probed how the candidate explained a bad forecast to stakeholders, and the other drilled into hypothesis testing and a logical reasoning problem. A separate candidate's superday panel was far more conversational, asking about a time data was used to solve a problem and what financial news they'd been following. Another candidate's superday included a technical question that veered into macroeconomics when they expected risk.
In one final round, a hiring manager asked almost entirely behavioral questions about past forecasting work. A second interviewer in that round wanted the specific names of statistical tests rather than just the underlying logic, a gap the candidate said contributed to their rejection. Another candidate's later in-person round instead produced a university-level math problem they hadn't prepared for. Across these reports, technical fundamentals open doors, but communicating them clearly and specifically closes the loop.
Synthesized from 23 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Jpmorgan Chase & Co. process.
Asked about my resume and went deep into Models I implemented. 3 rounds, two technical and one behavioural. Mostly about Python coding, Machine Learning and Quant Finance topics. About portfolio optimization and Risk modeling.
Questions asked: What are the assumptions of Linear Regression? Go through Unsupervised Machine learning models you implemented?
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Jpmorgan Chase & Co.
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Slacking Employees Salaries | |
| Merge Sorted Lists | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Department Expenses | |
| Profit-Maximizing Dice Game | |
| New Partner Card | |
| Find the Missing Number | |
| Bucket Test Scores | |
| Hurdles In Data Projects | |
| Forecasting New Year Revenue | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| Get Top N Frequent Words | |
| HHT or HTT | |
| Normalize Grades | |
| Sort Strings | |
| Valid Anagram | |
| Xgboost vs Random Forest | |
| Offer Matching API Design | |
| Stick Break | |
| Data Preparation for Imbalanced Data | |
| Replace Words with Stems | |
| Lasso vs Ridge | |
| Loan Model | |
| Coin Dispenser | |
| Count Transactions | |
| Deciding Between Solutions | |
| Implementing the Fibonacci Sequence in Three Different Methods |
Synthesized from candidate reports. Individual experiences may vary.
Most Quantitative Analyst candidates start with either a short HR or recruiter screening call or a HireVue-style recorded interview, and sometimes both. One candidate described submitting a cover letter before a HireVue round. Another said JPMorgan expected real background knowledge about the firm and a current event, not just polished general answers. Across these reports, expect to be asked why JPMorgan, why this role, and about a recent financial news story you can discuss with some depth.
One candidate's first technical interview centered on forecasting experience, a simple Python for-loop exercise, and basic date and time manipulation questions. It stayed at a fundamentals level rather than advanced theory. This is a single report, so the depth of early technical screens may vary by team.
Several candidates described a panel or superday stage with multiple interviewers. In one, a panelist asked situational questions about explaining a forecast that went wrong and communicating with stakeholders, while a second panelist focused on hypothesis testing, statistical concepts, and a logical reasoning problem. Another candidate's superday panel was more conversational, asking about a time data was used to solve a problem and recent financial news. A third candidate's superday included a technical question that shifted into macroeconomics when a risk-focused question was expected.
In the final stage reported by one candidate, the hiring manager's questions were almost entirely behavioral. They covered past forecasting projects, decision-making, and scenarios about handling a failed forecast or stakeholder pushback. A second interviewer in that same final round pushed further into forecasting methodology, including how to detect trends in time series data. That interviewer was listening for the names of statistical tests rather than just the reasoning behind an answer, and missing those names was cited as a factor in the rejection. Another candidate's later in-person round instead included a university-level math problem that diverged from what they had prepared for.
