
JPMorgan Chase Data Scientist candidates report project-heavy behavioral interviews, with some early machine-learning, optimization, and coding discussion. Prepare a clear account of your decisions, trade-offs, and impact.
$137K
Avg. Base Comp
$165K
Avg. Total Comp
3-4 rounds
Typical Rounds
3-6 weeks
Process Length
JPMorgan Chase Data Scientist interviews reported here center on whether you can explain real work with specificity. One candidate described a three-stage path—recruiter screen, hiring-manager interview, and in-person panel—where questions were largely behavioral but probed project ownership, business context, analysis, impact, and the choices behind the work. Be ready for follow-ups such as why you selected an approach, what trade-offs you made, and what you would change.
A separate candidate was asked to describe implementing an ML model end to end. That makes a concise, credible project narrative especially valuable: state the problem, your individual contribution, the approach you chose, how you evaluated impact, and the limitations or revisions you would make. Specific ownership and defensible decisions matter more in these accounts than reciting a generic workflow.
Technical emphasis is not identical across reports. One candidate encountered no coding or technical case questions, while another reported first-round questions about coding skills, gradient descent, linear versus nonlinear optimization, and selecting ML techniques for multiple project scenarios. Prepare to connect those concepts to practical modeling choices, while avoiding assumptions that every team uses the same format. The available accounts do not provide an explicit end-to-end timeline.
Synthesized from 3 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.
I have had one round so far. They asked about my past experience with my current employer and the models I developed there. There were also questions about machine-learning techniques and how I would consider them for a project across multiple scenarios given by the interviewer. I was surprised that they asked about coding skills in the first-round interview.
Questions asked: gradient descent, linear vs. nonlinear optimization
Prep tip from this candidate
Prepare to discuss models you developed, explain how you would choose approaches across project scenarios, and expect questions about coding skills in an early conversation.
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 | |
|---|---|
| Merge Sorted Lists | |
| Slacking Employees Salaries | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Bucket Test Scores | |
| Department Expenses | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| Get Top N Frequent Words | |
| Profit-Maximizing Dice Game | |
| Normalize Grades | |
| New Partner Card | |
| Sort Strings | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Xgboost vs Random Forest | |
| Forecasting New Year Revenue | |
| Replace Words with Stems | |
| Lasso vs Ridge | |
| Coin Dispenser | |
| HHT or HTT | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Offer Matching API Design | |
| Stick Break | |
| Data Preparation for Imbalanced Data | |
| Loan Model | |
| Deciding Between Solutions |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported an initial recruiter screen before later conversations. The available account does not specify questions from this stage, so candidates may use it to confirm their background, role fit, and interest without assuming a fixed script.
Candidates report detailed discussion of projects, individual contributions, business problems, analysis, impact, decisions, and trade-offs. Another candidate reported early questions on coding skills, ML techniques, gradient descent, and optimization, so technical follow-ups may appear even when the conversation begins with experience.
One candidate reported an in-person panel as the third stage. Another was told the process would end after a third round and was then asked to schedule an additional in-person round. Prepare to restate and defend your project choices consistently across interviewers.