JPMorgan Chase Data Scientist interviews, as three candidates describe them, lean heavily on walking through your own projects and defending your choices. Expect behavioral depth, possibly some early coding or ML questions, and possible scheduling delays.
$150K
Avg. Base Comp
$180K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
The three candidates here describe a JPMorgan Chase Data Scientist interview that rewards clear, end-to-end storytelling about your own projects more than puzzle-solving. One candidate was asked to explain a time they implemented an ML model from start to finish, and felt the focus was on walking through the full lifecycle rather than tricky algorithms. Another reported a recruiter screen, a hiring manager interview, and an in-person panel. That candidate said the questions were mostly behavioral but pushed deep: your specific contribution, the biggest challenge, how you measured impact, and what you would do differently. They reported no coding, technical case, or take-home.
Not every report matches. A third candidate, after a first round, said they were asked about the models they built at their current employer. They were also asked how they would choose ML techniques across scenarios the interviewer gave, and about gradient descent and linear versus nonlinear optimization. That candidate was surprised to be asked about coding skills so early. So prepare a polished project narrative, and also be ready to explain core ML and optimization ideas conversationally.
One candidate was told the loop would end after round three, then was asked to schedule an additional in-person round. After sending availability, that candidate heard nothing despite several follow-ups. Treat the schedule as flexible and keep your recruiter contact organized. Of these three candidates, one did not receive an offer and two were still waiting to hear back, so none reported an offer.
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 | |
| Xgboost vs Random Forest | |
| Hurdles In Data Projects | |
| Forecasting New Year Revenue | |
| Replace Words with Stems | |
| Lasso vs Ridge | |
| HHT or HTT | |
| Coin Dispenser | |
| 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 reports the process opened with a recruiter screen before any interviews with the team. It is a good moment to ask about the number of rounds and expected timeline, since scheduling was a pain point for one candidate.
One candidate reports a first round covering their current employer's work and the models they developed. They were asked how they would pick ML techniques across scenarios, and about gradient descent and linear versus nonlinear optimization. That person was surprised by coding-skill questions this early, so you may want to review fundamentals.
A candidate reports a hiring manager interview that was mostly behavioral but detailed. Questions covered the project they were proudest of, their own contribution, the biggest challenge, how impact was measured, and what they would change. They described the tone as conversational yet probing, and reported no coding or take-home.
One candidate reports a final in-person panel. Another was told the loop ended after round three, then asked to schedule an additional in-person round and never heard back after sending availability. Because the final stage may shift, confirm next steps in writing and follow up persistently but patiently.
