JPMorgan Chase · Primly Community

JPMorgan Chase onsite / final round: how it really goes, round by round

veteran_vance · 4 replies

Just finished my JPMC final round last week. Wanted to share the full structure since the information out there is inconsistent and some posts describe processes that sound different from what I experienced in 2026.

Mine was fully virtual (4.5 hours total, all on Zoom + HackerRank for coding). They break it into individual sessions with short breaks in between.

Round 1: Coding (60 min) Two problems. First one was a medium-level array problem, standard stuff. Second was more system-adjacent: given a stream of financial transactions, find all duplicate entries within a rolling time window. Medium difficulty but good domain flavor.

Round 2: Coding (60 min) Different interviewer. One problem, but more involved. It was a design-and-implement problem: given a class interface, build it out. Not just algorithm, more about clean code and good abstractions. He specifically said 'show me how you'd write this in production, not just to pass a test.'

Round 3: System Design (60 min) Design a notification service for a banking app. Users need real-time fraud alerts via push, SMS, email. The key constraints were: notifications must be delivered at least once, must be idempotent (don't double-notify), and must handle partial outages of the SMS gateway. I had a strong answer for the basic architecture but they dug into the idempotency and retry logic in a way that required me to think out loud carefully.

Round 4: Behavioral (45 min) Senior engineer who clearly had a rubric but wasn't robotic about it. Questions were mostly around handling conflict with teammates or product managers, dealing with unclear requirements, and one explicit ethics/values question. (See other posts here about what those look like at JPMC.)

I passed all four rounds and got an offer about two weeks later. The debrief process at JPMC is internal and you won't hear the round-by-round feedback. You just get a yes or a compensation call.

Happy to answer questions about specific rounds.

4 replies

hardware_hugo

The 'write it like production, not to pass a test' framing is actually really different from most LC-style interviews. Did the interviewer penalize you if you took time to think about error handling and edge cases, or did they appreciate the thoroughness?

veteran_vance

They appreciated it. He specifically said 'you're allowed to ask what edge cases matter here before you start.' It wasn't a speed test. He wanted to see how I thought about code quality, not just whether I could produce a correct output in 20 minutes.

backend_bekah

The notification system design with idempotency constraint is actually a great interview question for banking. Duplicate fraud alerts would erode trust really fast. Did they ask you to size it (how many notifications per second) or was it more qualitative?

jordan_pm

Two weeks for a debrief and offer is pretty standard for large financial institutions. Was the offer negotiable or did they present a take-it-or-leave-it number?