← Back to Directory

JPMorgan Chase interview notes, page 3 of 7

Large Enterprises

Most of these JPMorgan Chase write-ups come from Software Engineers (56), then Product Managers (8) and Machine Learning Engineers (2). The most reported rounds are the technical phone screen (33), the system design round (13), the hiring manager screen (8) and the behavioral / leadership round (5).

69 interview notes · updated Sep 2026

JPMorgan Chase·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at JP Morgan with an engineering manager who'd clearly been around a while. Mostly a conversation about past projects and how you think through tradeoffs, not a gotcha session, but you need to have your stories tight.
  • Walk me through a past project in depth, including the decisions you made and why.
  • How would you handle a situation where you disagree with a technical direction your team has already committed to?
  • How do you approach the tradeoff between moving fast and maintaining code quality?

“This is the kind of question that sounds easy until you're actually in it and realize you've been talking for four minutes and haven't gotten to the point yet.”

View Post

JPMorgan Chase·Software Engineer·Technical Phone Screen

May 2026
Interviewed at JP Morgan Chase for a cloud/infrastructure role and got asked the classic Azure vs. AWS comparison. Short and focused, not a lot of fluff.
  • When would you recommend using Azure over AWS, and vice versa?

“This is the kind of question that seems easy until you're actually saying words out loud.”

View Post

JPMorgan Chase·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a Software Engineer role at J.P. Morgan and got a graph problem about detecting cycles in a course prerequisite dependency. Pretty classic but still stressful when you're on the spot.
  • Given a number of courses and a list of prerequisite pairs, determine whether it's possible to complete all courses without hitting a circular dependency.

“This is basically cycle detection on a directed graph, which I knew going in, but I fumbled the implementation a bit.”

View Post

JPMorgan Chase·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Product analyst interview at JP Morgan Chase with a metrics/analytics question about drop-off in an application flow. Pretty lean on details but the question itself was meaty enough to chew on for a while.
  • 55% of users drop off somewhere between the application start page and the submission page. What do you think is causing this?

“My first instinct was to just list UX problems but that felt too shallow.”

View Post

JPMorgan Chase·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at J.P. Morgan for a software engineer role. The whole session was centered on designing an e-commerce backend, and it went deeper than I expected, especially around concurrency and order correctness.
  • Design the backend system for an e-commerce shopping platform. Walk through the high-level architecture, the major services, the data stores, and how requests flow on both the read path (browsing, product pages, cart) and the write path (adding to cart, placing an order).
  • How would you design the order submission path to be idempotent, so that network retries or double-clicks never result in duplicate orders or double charges?
  • Two customers simultaneously try to buy the last unit of a product. How do you prevent overselling, and how do you handle reservations that are abandoned mid-checkout?
  • During a flash sale, a single popular SKU becomes a write hotspot. How do you prevent that inventory row from becoming a bottleneck without allowing oversells?
  • A payment goes through successfully but the order confirmation write fails, or the reverse. How do you keep money and order state consistent, and how do you recover from that split?
  • If the business is willing to accept a small, reconcilable oversell in exchange for much higher checkout throughput, how would your inventory design change and how would you reconcile afterward?
  • How would you extend a single global inventory count per SKU to a multi-warehouse model where stock and reservations are tracked per fulfillment location?

“I started by splitting things into domains: catalog, cart, inventory, order, payment, fulfillment.”

View Post

JPMorgan Chase·Software Engineer·Technical Phone Screen

May 2026
JP Morgan Chase SWE interview with a classic array problem. Nothing too wild but the question has a few edge cases that can trip you up if you're not careful.
  • Given an array of distinct integers, find all pairs with the minimum absolute difference.

“I went straight for sorting the array first, which is the right move, but I fumbled explaining why for a second.”

View Post

JPMorgan Chase·Software Engineer·Technical Phone Screen

May 2026
Quant engineer interview at JP Morgan with a combinatorics/dynamic programming problem that felt more like a math olympiad warmup than anything I expected from a finance role. The question had real depth once you got past the setup.
  • How many distinct ways can you tile a 3xN rectangle using 1x2 and 2x1 dominoes? Derive a recurrence relation and generalize to arbitrary N.

“I'd seen domino tiling problems before but always on 2xN grids, so the 3xN version threw me more than I expected.”

View Post

JPMorgan Chase·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at JP Morgan for a software engineer role, centered entirely on designing a shopping cart service. Pretty deep dive, they wanted both read and write paths covered in detail which I wasn't fully expecting.
  • Design a shopping cart service for a large e-commerce platform. Walk through the write path (adding, removing, and updating items including quantity and variants), how you'd handle persistence across sessions and devices, and idempotency. Then cover the read path including retrieving the cart, computing totals, applying coupons and discounts, and surfacing fresh stock and pricing data. Also discuss your data model, storage choices, caching strategy, consistency between cart and inventory or pricing systems, and how you'd scale for high-traffic users and seasonal spikes.

“This one sprawled fast.”

View Post

JPMorgan Chase·Software Engineer·Onsite - System Design / Architecture

May 2026
Systems design round at J.P. Morgan for a software engineer role, centered entirely on architecture and database scaling trade-offs. Two big topics: microservices vs. monolith, and sharding vs. replication. The follow-ups were where things got interesting.
  • Compare microservices and monolithic architectures. When would you choose one over the other?
  • What is the difference between database sharding and replication, and what specific problem does each one solve?
  • A team adopted microservices but every new feature still requires changing three services simultaneously and they always deploy together. What went wrong and what would you fix?
  • Your read replicas are lagging and users are seeing data they just saved disappear on refresh. What's causing it and how do you fix it?
  • How do you choose a shard key, and what breaks if you pick a bad one like sharding a user table by country?
  • When would you deliberately stay with a monolith and a single vertically scaled database even as the product grows?

“I went in thinking I'd just list pros and cons and that would be enough.”

View Post

JPMorgan Chase·Software Engineer·Technical Phone Screen

May 2026
Coding round at JP Morgan for a software engineer role. One algorithmic question, pretty focused, nothing behavioral. The problem itself was clean but I spent more time than I'd like to admit second-guessing my frequency counting logic.
  • Given a digit string of even length, find the minimum number of single-character changes needed so that the left half and right half are anagrams of each other.

“My first instinct was to sort both halves and compare, which works but I fumbled explaining the complexity.”

View Post