JPMorgan Chase software engineer candidates report a HackerRank-style assessment followed by coding (in one case paired with code review), system design and behavioral interviews. Round counts vary widely.
$126K
Avg. Base Comp
$148K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates most often describe an online coding assessment followed by several interviews covering coding, system design and behavioral questions. One candidate moved from a HackerRank assessment into a pool-hiring super-day of three rounds, while another described eight rounds in total, so the mix and length differ from person to person.
The piece that surprises people is the code-pair round with code review. One candidate was handed a HackerRank link and started coding immediately, then was asked to review code a colleague had supposedly written and point out issues. Coding problems reported across the process include:
One candidate who did not pass the assessment described it as LeetCode medium to hard, with string parsing and manipulation.
System design prompts were practical. They included a video streaming app with efficient watch history and making a high-traffic full-stack application highly efficient. A Software Engineer III candidate also had a 45-minute system design discussion and a pair-programming build from a Figma design.
Technical depth depends on the team. Some candidates were asked about Java HashMap internals, REST API design, dependency injection or basic authentication concepts, while one panel dug into React internals and backend security. Behavioral rounds covered teamwork, challenges, past projects and conflict with a manager. Keep explaining your thinking even when an interviewer gives little back.
Synthesized from 39 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.
The recruiter reached out about a lead or senior lead software engineer role on a team building AI/ML platforms, with the work centered on large-scale model infrastructure, deployment, and platform engineering. She was vague about the structure, saying the first two rounds would be behavioral and coding, with coding and system design coming after that, so I didn't have a clear picture going in.
My first conversation was with the VP of the team, and it was quick. The VP jumped almost straight into my experience rather than starting with a problem. The tone was direct but respectful. Before the interview, I had seen a comment suggesting the style would resemble an Amazon L4-level interview with discussion-heavy questions, but I can only speak to what I actually experienced, which was a conversation focused on my background.
I did not move forward. The team got back to me quickly with the decision, which I appreciated even though the outcome was disappointing.
Prep tip from this candidate
Be ready to walk through your own past work in depth from the very first conversation, since this VP-led screen went straight into experience rather than problems.
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 | |
| Department Expenses | |
| The Brackets Problem | |
| Get Top N Frequent Words | |
| Level Of Rain Water In 2D Terrain | |
| Normalize Grades | |
| Sort Strings | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Replace Words with Stems | |
| Coin Dispenser | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Offer Matching API Design | |
| Loan Model | |
| Diagnosing Query Speed Degradation | |
| Deciding Between Solutions | |
| International e-Commerce Warehouse | |
| Pipeline Transformation Failures | |
| Swipe Payment API | |
| Decision Tree Evaluation | |
| Client Solution Pushback | |
| Ugly Powers | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates describe a timed HackerRank-style assessment. One reports a 60-minute window with two to three problems, and another described aptitude questions alongside basic problem-solving tasks. One candidate who did not pass described it as LeetCode medium to hard with string manipulation.
Some candidates report an initial phone screen about background and programming experience, and a technical screen on past projects. Topics reported by individual candidates include Java HashMap internals, basic authentication concepts, REST API design and dependency injection. One candidate described an abrupt, unstructured screen that jumped from syntax questions to data structures.
One candidate reports live coding on HackerRank with an interviewer watching, paired with reviewing a colleague's code and pointing out issues. The coding resembled a box-and-units greedy problem. A Software Engineer III candidate instead had a 45-minute pair-programming session building from a Figma design. Keep explaining your thinking as you go.
Reported prompts include a video streaming app with efficient watch history and making a high-traffic full-stack application highly efficient. One Software Engineer III candidate had a separate 45-minute system design discussion. Candidates describe the design discussions as practical rather than abstract.
Candidates describe behavioral questions about team dynamics, challenges, teamwork and leadership, and in one report conflict with a manager. One candidate also had a short hiring manager Zoom call about fit, including an unusual question asking them to describe in three words what they are not.
