JPMorgan Interview Process: Superday & Code for Good

JPMorgan is a bank, and its software-engineer loop shows it. The algorithm bar is lighter than big tech. It is nothing like the LeetCode hard tier, and the rounds lean on practical Java, a code-review exercise, and pragmatic system design. Clever puzzles barely feature; which loop you sit comes down to how you enter. New grads and interns join through the Software Engineer Program, and on campus that runs through a two-day Code for Good hackathon. Experienced engineers take an online assessment and then a Superday: three back-to-back interviews in one sitting.

One round has no FAANG equivalent. Alongside a standard medium coding problem, you get a pull-request review: real code is handed to you, and you read it, flag what is wrong, and fix it. It rewards the daily work of an engineer, reading and correcting other people's code, over raw speed on a fresh algorithm. The rest of the loop rewards breadth: practical Java, a system design that stays grounded, and a behavioral round that carries real weight, because a bank hires for judgment as much as for code.

The Pipeline

Each stage gates the next, and the Superday is where the offer is won. The online assessment is a filter. The three Superday rounds, run back to back, are the decision. Most candidates hear about a Superday within two to three weeks of the assessment, and a shortlist call usually lands within a few days of the Superday itself. JPMorganChase's own How we hire page keeps it general. The process differs by role, and you meet several people in multiple rounds before the firm reviews your whole application and decides on an offer.

Superday rounds: 3. A coding round with a code review, pragmatic system design, and behavioral, run back to back at about 45 minutes each with short breaks between.
Online assessment: ~1 hr. A HackerRank round of two coding problems, easy-to-medium for grads and up to medium-hard for experienced roles, weighted on speed and correctness.
Business Principles: 4. Client service, operational excellence, integrity, and a winning culture. Behavioral maps loosely to these; there is no numbered scorecard.
Shortlist call: ~3 days. A typical wait to hear back after the Superday, with the offer following shortly after that.

For an experienced or lateral hire, the path runs through five stages.

Offer and Team Matching

01Application

You apply online or come in through a recruiter. A referral or a recruiter reaching out moves faster than the general queue, but the loop itself is the same either way.

02Online Assessment

A HackerRank round of two problems in about an hour. Easy-to-medium for grads, medium to medium-hard for experienced roles, scored on speed and correctness. A clean run moves you toward the Superday, though a strong score is sometimes still passed over.

03The Superday

The centerpiece. Three back-to-back rounds of about 45 minutes each, with short breaks between, in one sitting: coding with a code review, pragmatic system design, and behavioral. This is where the hire is decided, and it is the heart of the guide.

04Decision

The hiring manager and the three Superday interviewers weigh their written feedback together, and a shortlist or decision call usually comes within a few days. There is no cross-org hiring committee of the kind Google or Amazon runs.

05Offer and Team Matching

The offer comes first. Team matching happens after, a lighter conversation with managers about your stack and projects, with no second technical bar. You clear the loop for JPMorgan, then find the team.

Inside the Superday

Three rounds, back to back, each with a distinct job. The coding and code-review round and enterprise Java get their own lessons; the summary here places each round in the day.

The coding round pairs a standard medium problem with the review exercise. The problem itself is arrays, hashing, strings, a two-pointer sweep, the everyday medium tier, well short of a hard puzzle. Then the review: you are handed a short piece of code, often in a shared editor, and asked to find the bug, the race, or the design flaw, comment on it, and fix it. What the round rewards is plain, correct Java a teammate could read at a glance.

The system design round stays pragmatic. A recurring prompt is to pull a monolith into services, or to hold a system together under fifty times the traffic: service decomposition, a cache, an API gateway, load balancing. Grads get a lighter version; from senior up it carries real weight. What earns the round is a sound tradeoff argued in plain terms, the kind you would defend to a skeptical staff engineer.

The behavioral round is standard STAR, with more weight than a pure coding loop gives it. Expect projects you owned, a disagreement you worked through, and an honest answer to why JPMorgan and why you are moving. It maps loosely to the firm's four Business Principles, but there is no numbered value rubric to recite.

The JPMorgan angle

The code review is the round FAANG prep skips. Drill enough medium coding to clear the first half, then practice the second: read unfamiliar code and correct it out loud. Pull up a change you did not write, name the thread-safety bug or the leaked resource, and say how you would fix it. That is the daily work JPMorgan is testing for, and it is the one part of the day a LeetCode grind never touches.

The Campus Route: Code for Good

New grads and interns take a different front door. The Software Engineer Program starts with a HackerRank online test of two easy-to-medium problems. Then comes a HireVue recorded video interview with no coding: about two behavioral questions in ten minutes, answered on your own inside a two-to-three day window. On campus, the final stage is Code for Good, a two-day hackathon on a real problem for a nonprofit, in teams of seven or eight with two assigned mentors.

The twist is who decides. Hackathon standing barely matters; the mentors' one-on-one conversations with you across the two days are the actual interview, and a team can place runner-up and still get offers. Off-campus and some US new-grad candidates get a Super Day, a single final interview day, in place of the hackathon.

The JPMorgan angle

In Code for Good, the mentors are interviewing you the whole time. Winning the hackathon is not the goal. The mentors watch how you break the problem down and work with a team you met two days ago. They watch you carry a piece of the build to the end. Their feedback is what converts to an offer. Treat every mentor check-in as the round it is: show your reasoning, ask for input, and own a real slice of the work.

After the Superday

JPMorgan's decision is hiring-manager and panel driven, weighed against the interviewers' written feedback, and there is no published pass rate worth trusting. One thing to settle before you read an offer letter: a JPMorgan Vice President is a senior engineer, a lead individual contributor a rung below the executive titles the name suggests. The bank overlays corporate titles, Analyst then Associate then VP, on internal engineering grades, and the title inflation trips up everyone new to finance. How that ladder maps to scope, and how it sets your offer, is the next lesson.

The code review is a real, first-class round

Alongside a medium coding problem you read code you are handed, find the bug or the race, and fix it. It rewards correcting other people's code, which a fresh-algorithm grind never practices.

A JPMorgan "VP" is a senior engineer

The bank overlays corporate titles (Analyst, Associate, Vice President) on engineering grades. A VP here is a lead individual contributor, so read any title through its engineering grade rather than its finance connotation.

The bar rewards practical Java over algorithms

Streams, equals and hashCode, Spring Boot, sometimes exposing your code as a REST endpoint and calling it. The bar rewards breadth and code that runs, and it is nothing like the LeetCode hard tier.

Team matching comes after the offer

You clear the Superday for JPMorgan first and match to a team second. Matching is a lighter post-offer chat about your stack, so a pass carries across open roles.

What This Guide Covers

The rest of the guide takes the loop apart round by round and turns each one into concrete preparation. Start wherever your own day looks weakest.

Coding and the Code Review Round

The HackerRank assessment, the everyday medium patterns JPMorgan reuses, and the pull-request review where you read, critique, and fix code you are handed.

Enterprise Java Fundamentals

The practical Java the loop leans on: streams, equals and hashCode, Spring Boot, and exposing a service as a REST endpoint. The stack the bank runs on.

System Design

The pragmatic design round, worked the JPMorgan way: pulling a monolith into services and holding a system together under fifty times the traffic, argued in plain tradeoffs.

Behavioral

STAR stories built for a bank that weights judgment: ownership, collaboration, and an honest why-JPMorgan, mapped to the four Business Principles without a numbered rubric.

Leveling and the Offer

How Analyst, Associate, and VP map to engineering grades and scope, and why JPMorgan's cash-heavy, bonus-driven pay makes the right level the real negotiation.

Common questions

How many rounds of interviews does JPMorgan have?

For an experienced software engineer, usually three to four stages: a HackerRank online assessment, then a Superday of three back-to-back rounds, a coding round with a code review, pragmatic system design, and behavioral. New grads take the Software Engineer Program instead: an online test, a HireVue video interview, and a Code for Good hackathon or a Super Day.

How long does the JPMorgan interview process take?

Most candidates get a Superday invite about two to three weeks after the online assessment. A shortlist or decision call usually follows within a few days of the Superday. The full loop commonly runs three to six weeks.

Is the JPMorgan interview hard?

The algorithm bar is lighter than big tech, closer to the everyday medium tier than the LeetCode hards. The difficulty is breadth: practical Java, a code-review round, and pragmatic system design, plus a behavioral round that genuinely counts. Prepare all of it and the loop is very beatable.

What are the stages of the JPMorgan software engineer interview?

In order: an application, a HackerRank online assessment, and a Superday of three back-to-back rounds, followed by a hiring decision and a post-offer team match. New grads follow the Software Engineer Program: an online test, a HireVue video interview, and Code for Good or a Super Day.

Key Takeaways

✓JPMorgan runs two front doors. Experienced engineers take a HackerRank online assessment and a Superday of three back-to-back rounds; new grads join the Software Engineer Program through a video interview and a Code for Good hackathon.
✓The round that sets JPMorgan apart is the code review: alongside a medium coding problem, you read code you are handed, find what is wrong, and fix it. A LeetCode-only plan never practices it.
✓The bar is breadth over depth. The algorithm tier is lighter than big tech, the emphasis falls on practical Java and pragmatic system design, and the behavioral round carries real weight.
✓A JPMorgan Vice President is a senior individual contributor despite the executive-sounding title, and team matching happens after the offer. The decision is hiring-manager and panel driven, with no cross-org committee.

Next up:How JPMorgan Makes Hiring Decisions