JPMorgan Chase Interview Questions — Page 7

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

Jul 2026

System design round at JP Morgan for a software engineer role. The whole session was basically one big URL shortener deep dive, which sounds straightforward but they kept pushing on every layer until you ran out of answers.

Design a URL shortening service like bit.ly or TinyURL. Walk through your full system design.
What are the core functional and non-functional requirements for a URL shortener at scale?
How would you design the API surface for this service?
How would you generate short keys, and how do you handle collisions?
What storage solution would you use, and what does the data model look like?
How would you add a caching layer for popular redirects?
How would you implement click analytics and track redirect counts?
How would you prevent abuse, such as malicious URLs or API misuse?

“This was the anchor question for the whole interview.”

View Post

JPMorgan Chase·Product Manager·Hiring Manager Screen

Jul 2026

PM interview at JP Morgan Chase, one question that sounds simple but actually requires you to have built something real. No fluff, just show your work.

Walk me through something you built from start to finish, without leaning on teammates to carry it.

“I picked a project I was proud of but halfway through my answer I realized I kept saying 'we' instead of 'I'.”

View Post

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

Jul 2026

System design round at J.P. Morgan for a software engineer role, focused entirely on designing a large-scale notification platform. The interview went deep on queues, rate limiting, and reliability mechanics across multiple delivery channels.

Design a scalable notification service that lets internal teams send messages across push, email, and SMS via a single API call. How do you architect the send path and keep channels pluggable?
What clarifying questions would you ask before diving into the design? Things like delivery guarantees, user preferences, latency targets, and compliance constraints.
Why are message queues essential in this architecture, and how do you use them to handle bursts, retries, and provider outages?
How do you implement rate limiting at multiple layers: protecting downstream providers, preventing notification spam to users, and guarding against abusive internal callers?
An SMS provider goes down for 30 minutes. Walk through exactly what happens to in-flight and queued SMS notifications, and how the system recovers without losing or duplicating messages.
How do you guarantee a one-time passcode gets delivered within seconds even when a large marketing blast is running on the same platform?
Compare Kafka and RabbitMQ for this use case. Which would you pick for bulk fan-out and which for transactional notifications?
How would you add delivery status tracking and an in-app inbox on top of this send-focused design?

“This is the core question and it's bigger than it sounds.”

View Post

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

Jul 2026

JP Morgan system design round, one big question about a university course registration system that went way deeper than I expected. They kept pushing on every layer, from data modeling to concurrency to scaling, so it ended up being more of a 45-minute gauntlet than a single question.

Design a university course registration system. Walk through the core entities, the APIs students would use, and the constraints the system needs to enforce.
How would you enforce constraints like prerequisite checks, time conflict detection, seat capacity limits, and registration windows that differ by class year or major?
What data store would you choose for this system, and what consistency model makes sense when thousands of students are all hitting register at the same moment?
Walk through how you'd handle concurrency when multiple students try to register for the same section at the same time. Compare row-level locking, optimistic concurrency, and a queue-based approach.
The course catalog is read very heavily. How would you cache it, and what are the tradeoffs?
How do you ensure fairness in waitlist processing, and how does the whole system scale to tens of thousands of concurrent users during registration open?

“I started with entities and drew out students, courses, sections, instructors, schedules, prerequisites.”

View Post

JPMorgan Chase·Machine Learning Engineer·Technical Phone Screen

Jul 2026

ML engineer screen at JP Morgan Chase, basically one question about imbalanced data and that was the whole technical portion.

How do you handle imbalanced datasets in a machine learning context?

“Ran through the usual stuff: resampling, class weights, different evaluation metrics.”

View Post

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

Jul 2026

System design round at J.P. Morgan for a software engineering role. The whole session was basically one big URL shortener question that kept branching into follow-ups, so be ready to go deep on every layer.

Design a URL shortening service like Bitly. Walk through the full system: API design, data model, short-code generation, scalability, caching, reliability, abuse prevention, and the trade-offs you're making.

“This felt manageable at first and then the follow-ups just kept coming.”

View Post

JPMorgan Chase·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026

Behavioral round for a software engineer role at J.P. Morgan. Five questions, all pretty standard for a big bank, but the deadline pressure one took some real thought. No frills, just tell us who you are and prove you can handle conflict and failure.

Walk me through your background and a recent project you're particularly proud of.
Tell me about a time when failing tests were holding up a release close to a deadline. What did you do, what trade-offs did you weigh, and how did it turn out?
Describe a time you disagreed with a teammate and how you worked through it.
Share a significant failure, how you dealt with it in the moment, and what you took away from it.
Why JPMorgan specifically, and why this team?

“I had a story ready but I rambled a bit on the project part.”

View Post

JPMorgan Chase·Software Engineer·Technical Phone Screen

Jul 2026

J.P. Morgan software engineer interview focused heavily on Spring Boot exception handling and API design. The question was deep enough that I kept second-guessing whether they wanted a design walkthrough or actual code, and I never fully figured that out.

Walk through how you'd implement centralized exception handling in a Spring Boot REST API so that every controller returns a consistent error response instead of leaking stack traces or random messages.
How do you surface per-field validation errors when a request body fails bean validation, and what does the response look like to the client?
What's the difference between @ControllerAdvice and @RestControllerAdvice, and when would you restrict an advice class to only certain controllers or packages?
How would you handle authentication and authorization failures without accidentally leaking whether a resource or an account actually exists?
What is RFC 7807 and why might you adopt that format for error responses instead of a custom schema?

“This one took me a minute to scope properly.”

View Post

JPMorgan Chase·Software Engineer·Onsite - Multi Round

Jul 2026

JPMorgan Chase superday for a software engineering role, two back-to-back 40-minute interviews: one technical, one behavioral. The technical skipped coding entirely and leaned heavily on AI and infrastructure concepts. Both interviewers were relaxed and the whole thing felt more like a casual chat than an interrogation.

What are containers, and what do Docker and Kubernetes do?
How do you use AI tools in your day-to-day work as a developer?
What has been your experience working with AI tools, and what's your take on their limitations?

“They flagged this as the toughest technical question and honestly it wasn't bad at all.”

View Post