JPMorgan Chase Data Analyst candidates report HireVue motivation questions, resume-based manager conversations, and practical Excel, Python and data reconciliation topics. One superday included a group business problem.
$85K
Avg. Base Comp
$100K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Reports from JPMorgan Chase Data Analyst candidates point to a process where motivation and clear communication carry as much weight as technical skill. Candidates describe starting with a HireVue video screen, and the "why JPMorgan" question came up in more than one account. One candidate was also asked why they wanted the division, while another was surprised by an opening prompt about investment banking for a middle-market role, so tailor your answer to the team you are actually targeting.
The technical side is practical. A candidate who accepted an offer described basic Python questions alongside Excel formulas, data automation, reconciling mismatched data across different reports and software, and thinking about how to build databases. They said the questions were not especially hard but expected depth in the basics. Another candidate, whose conversation centered on their CV, heard SQL, Excel, Python/R and data visualization mentioned as areas the team cares about, though the discussion stayed mostly on projects and background.
Behavioral questions covered weaknesses, strengths, proudest achievement, handling pressure and competing priorities, and influencing a stakeholder. One candidate faced a group business problem with other applicants at a superday, which seemed to test communication and teamwork. Candidates also mention slow communication between steps, and one said it was hard to tell what each next interviewer would focus on, so ask your recruiter what to expect.
Synthesized from 21 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.
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 | |
| Department Expenses | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Get Top N Frequent Words | |
| Normalize Grades | |
| Profit-Maximizing Dice Game | |
| New Partner Card | |
| Sort Strings | |
| Valid Anagram | |
| Bucket Test Scores | |
| Xgboost vs Random Forest | |
| Hurdles In Data Projects | |
| Replace Words with Stems | |
| Forecasting New Year Revenue | |
| Lasso vs Ridge | |
| HHT or HTT | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Data Preparation for Imbalanced Data | |
| Stick Break | |
| Loan Model | |
| Diagnosing Query Speed Degradation | |
| Deciding Between Solutions | |
| Pipeline Transformation Failures | |
| Decision Tree Evaluation | |
| Client Solution Pushback | |
| Explaining Linear Regression to Different Audiences |
Synthesized from candidate reports. Individual experiences may vary.
Three candidates describe starting with a HireVue. One reported three questions with two minutes each: why JPMorgan, why the division, and tell me about yourself, plus a personality-style prompt. Another could re-record answers and was asked to walk through their resume, why JPMorgan, and behavioral prompts on using data to decide, handling competing priorities, and influencing stakeholders.
One candidate who did not receive an offer met a manager and one other team member after the HireVue. The conversation focused on their CV: a university or prior-work project, three strengths and weaknesses, why JPMorgan Chase, hobbies and five-year goals. The candidate felt it also checked English communication. SQL, Excel, Python/R and visualization were mentioned but came up less.
The candidate who accepted an offer described technical questions that were practical rather than deeply technical: basic Python, data automation, Excel formulas, reconciling data across different reports and software, and thinking about building databases. They said the questions were not especially hard but expected depth in the basics, and that interviewer preferences seemed to vary by department.
One candidate reported a superday of three rounds mixing technical and behavioral questions, including Python coding, general problem solving and a proudest-achievement question. They also had a roughly 45-minute one-on-one with a VP, which opened with why JPMorgan, and a group business problem with other candidates that seemed aimed at communication and collaboration. This candidate did not receive an offer.
