
Candidates describe a JPMorgan Chase software engineer process that often starts with a HackerRank or HireVue screen and moves to a coding, system design and behavioral Superday. Reported rounds range from 3 to 8.
$120K
Avg. Base Comp
$150K
Avg. Total Comp
3-8 rounds
Typical Rounds
Not reported
Process Length
Candidates describe a JPMorgan Chase software engineer interview that usually opens with an online screen, either a HackerRank assessment or a HireVue, and then moves to a multi-interview Superday or "Power Day". Several reports describe a final stage of a code pair, a design round and a behavioral round, and one candidate said the combined result decided whether they were leveled as SDE2 or SDE3.
Coding questions are mostly LeetCode-style and easy to medium. Reported examples include valid parentheses, Trapping Rain Water, run-length compression of alert codes, permutations, and a greedy sorting problem. Two candidates were also asked to review code or a pull request out loud, so practice narrating what you would question and whether you would approve. One candidate who ran out of time on a medium problem said they kept talking through their reasoning throughout.
Design prompts were practical: a video streaming app with efficient watch history, a global file storage system, an Airbnb-style booking system, a CloudWatch-like monitoring service, and a payment layer with idempotency and Kafka. Java-heavy candidates also reported questions on Spring Boot, singletons, immutability and a Java CircuitBreaker with unit tests.
Expect behavioral questions on teamwork, conflict and past projects. Some candidates also reported team matching after the interviews, and experiences vary by team, level and location.
Synthesized from 40 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 | |
| Find the Missing Number | |
| Get Top N Frequent Words | |
| Slacking Employees Salaries | |
| Maximum Profit | |
| Department Expenses | |
| Bagging vs Boosting | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| International e-Commerce Warehouse | |
| Normalize Grades | |
| Decision Tree Evaluation | |
| Sort Strings | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Replace Words with Stems | |
| Coin Dispenser | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Client Solution Pushback | |
| Offer Matching API Design | |
| Loan Model | |
| Diagnosing Query Speed Degradation | |
| Deciding Between Solutions | |
| Pipeline Transformation Failures | |
| Swipe Payment API | |
| Your Strengths and Weaknesses | |
| Ugly Powers | |
| LRU Cache 1 |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online first step that varies: a 60-minute HackerRank with two or three problems, a five-question HireVue mixing behavioral and technical prompts, or a video submission followed by a timed assessment. Problems are typically easy to medium array and string work, and one candidate heard back within about a week.
Some candidates describe an initial recruiter or phone conversation about background, programming experience, framework experience and timeline. This does not appear in every report, so it may depend on the route in, such as a referral, a LinkedIn contact or a program application.
Candidates report a live coding round where the interviewer shares a HackerRank link. Some were also asked to review code or a pull request aloud. Reported problems include valid parentheses, Trapping Rain Water and a sorted-array problem. Explaining your approach as you go appears to matter as much as the final code.
Candidates report practical design prompts such as a video streaming watch history, global file storage, an Airbnb-style booking system, a monitoring service and a payment layer. Interviewers may probe trade-offs and follow-ups rather than expect a perfect design. Java, Spring Boot, API design and project deep dives also came up for some.
Candidates describe behavioral rounds on challenges, collaboration, conflict with a manager and project contributions. Some reports include hiring manager or senior leader conversations focused on resume projects and fit. Behavioral content was reported as roughly half of one Superday, so prepare examples alongside coding.
Outcomes in the reports are mixed. Some candidates received offers, some were rejected, and one said the role was filled internally after eight rounds. One reported passing Power Day and then waiting for team matching, so candidates may need to ask about the team's actual work and stack.