JPMorgan Chase & Co. Data Scientist interview typically runs 4 rounds: recruiter screen, technical interviews, behavioral interview, and an in-person round. Timeline is unclear, and the process can involve unexpected extra rounds and poor follow-up.
$125K
Avg. Base Comp
$168K
Avg. Total Comp
3-4
Typical Rounds
3-6 weeks
Process Length
Our candidates report that JPMorgan Chase cares less about flashy theory and more about whether you can connect the model to the business problem. The standout prompt was a full walkthrough of an ML model implemented end to end, which tells us the bar is really about ownership: problem framing, data choices, modeling tradeoffs, and how the work landed in practice. Even the technical questions leaned practical rather than academic, with prompts like loan modeling and comparing XGBoost, random forest, bagging, and boosting.
A recurring theme is that the interviewers want clear, audience-aware communication. We saw a question about explaining linear regression to different audiences, which is a strong signal that they’re testing whether you can translate technical work for stakeholders, not just recite definitions. The “bucket test scores” and “hurdles in data projects” prompts also suggest they’re listening for judgment and implementation realism — where things break, how you handled constraints, and what you learned when the project got messy.
The non-obvious make-or-break here is not technical difficulty; it’s whether your examples sound credible, complete, and grounded in actual delivery. Our candidates’ experiences suggest a process that can feel uneven on the recruiting side, so the people who do best are the ones who stay precise in their storytelling and can show they’ve shipped models with real-world constraints, especially in a regulated setting like finance.
Synthesized from 1 candidate report 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.
I only had one round of interview with their group member. I was not given the topic of the interview. Based on the job description, it is also not clear the job responsibilities. The interview told me it will be a code question, a case study, machine learning questions. i was rejected after that round.
Questions asked: First it is a question about gradient descent. How to use this algorithm to solve squared error loss. Write the code. Next it is a case study about pricing elasticity. Suppose for auto loans, how to check the elasticity of mortgage rates. How to set up the experiments? machine learning questions about xgboost, logistic regression
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.
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Slacking Employees Salaries | |
| Find the Missing Number | |
| Maximum Profit | |
| Bucket Test Scores | |
| Bagging vs Boosting | |
| Department Expenses | |
| The Brackets Problem | |
| Get Top N Frequent Words | |
| Level Of Rain Water In 2D Terrain | |
| Profit-Maximizing Dice Game | |
| Normalize Grades | |
| New Partner Card | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Valid Anagram | |
| Replace Words with Stems | |
| Lasso vs Ridge | |
| Forecasting New Year Revenue | |
| HHT or HTT | |
| Coin Dispenser | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Data Preparation for Imbalanced Data | |
| Stick Break | |
| Loan Model | |
| Offer Matching API Design | |
| Decision Tree Evaluation | |
| Deciding Between Solutions | |
| Explaining Linear Regression to Different Audiences |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with the recruiter to discuss your background, the Data Scientist role, and the expected interview loop. In this case, the candidate was told the process would end after three rounds, setting expectations for the rest of the interviews.
The interview focused on a behavioral and experience-based discussion rather than heavy algorithmic questions. A key prompt asked the candidate to explain a time they implemented an ML model end to end, with emphasis on clearly walking through the full lifecycle of the project.
After the third round, the candidate was unexpectedly asked to schedule another in-person interview. The content was described as fair and average in difficulty, but the process was less clear than originally communicated.
After the extra round, the candidate sent availability and followed up multiple times with the recruiter but did not receive a response. The process ended without an offer, and the main issue was poor recruiting coordination rather than interview difficulty.