JPMorgan Chase Software Engineer interviews commonly combine an assessment or video screen with coding, code review, system design, and behavioral discussion. Reported formats vary by team, level, and hiring program.
$90K
Avg. Base Comp
$160K
Avg. Total Comp
2-8 rounds
Typical Rounds
2-5 weeks
Process Length
JPMorgan Chase Software Engineer candidates describe a process that tests more than algorithm speed. Coding, code review, and practical system-design discussion recur across reports, alongside behavioral questions about collaboration, challenges, and past work. Several candidates began with an online assessment or recorded video response; reported assessments included array and string problems, while one HireVue mixed five technical and behavioral prompts.
At later-stage interviews, the technical work can be practical. Candidates report live coding in HackerRank-style environments, array or string exercises, sorting problems, and discussion of fundamentals such as dependency injection and RESTful APIs. One Power Day report grouped a pull-request review with a medium-level coding task, making it worthwhile to practice reading an existing change aloud: identify correctness or maintainability concerns, explain questions you would ask, and propose a clear next step.
Reported system-design prompts include a rate limiter and a video-streaming application. Prepare to establish requirements, describe a workable design, and explain trade-offs rather than memorizing one solution. Behavioral preparation also matters: candidates describe questions on teamwork, leadership, conflict, and challenges. Some candidates who passed Power Day subsequently entered team matching, so be prepared to ask about the team’s work and role alignment. Formats vary substantially by team, level, and hiring program, so treat these examples as preparation themes rather than one fixed sequence.
Synthesized from 18 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.
3 rounds:
Questions asked: LC questions included a list/array handling and one question of sorting. Classic algorithm solution. Be prepared to share your thought process with the interviewer
One question was around: neighbour comparison / run-length counting on lists handling.
Something like: A monitoring system sends alert codes. Compress consecutive equal alerts into pairs of (code, count).
Example:
["A", "A", "B", "B", "B", "A"] -> [("A", 2), ("B", 3), ("A", 1)]
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 | |
| Bagging vs Boosting | |
| Department Expenses | |
| Get Top N Frequent Words | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| Normalize Grades | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Valid Anagram | |
| Replace Words with Stems | |
| Count Transactions | |
| Coin Dispenser | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Loan Model | |
| Offer Matching API Design | |
| Diagnosing Query Speed Degradation | |
| Decision Tree Evaluation | |
| Pipeline Transformation Failures | |
| Deciding Between Solutions | |
| Client Solution Pushback | |
| Ugly Powers | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Statistically Significant Test | |
| Using APIs for Downstream Tasks | |
| Dropbox Database |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either an online assessment or a recorded video screen before later interviews. Examples include easy-to-medium array and string work, aptitude or technical prompts, and a five-question HireVue that mixed behavioral and technical responses.
Candidates report HackerRank-style coding, including array, string, sorting, and functional exercises. Some technical conversations also covered prior projects, Java fundamentals, APIs, databases, or how the candidate approaches problem solving.
In some Power Day and Superday accounts, candidates reviewed a pull request or completed hands-on work in an existing project setup. Be ready to verbalize concerns, implementation choices, and the reasoning behind a proposed change.
Candidates report design discussions such as a rate limiter, file storage, video streaming, and architecture trade-offs. The expected depth may vary, but reports emphasize explaining requirements, design choices, and follow-up trade-offs clearly.
Candidates report behavioral questions on teamwork, leadership, conflict, and challenges. Some successful Power Day candidates then entered team matching, where conversations may clarify the team’s actual work and role alignment.