Jp Morgan Chase Interviews

I'm a SDE-1 at a FinTech company with 3.5 years of experience. After solving two DSA problems on HackerRank, I received an interview call. The process consisted of three rounds scheduled back-to-back on the same day with only 5-minute gaps.

First, I had a coding round with a code review and a DSA problem involving a circular array. Then, I tackled a system design task for an API rate limiter, which involved deep technical discussions and some disagreements on design choices. Finally, I faced a managerial/behavioral round focusing on communication, leadership, and real project experiences.

Despite the intensity, I received positive feedback from the recruiter and a 15-minute hiring manager round. After about 10 days, I was offered an SDE-3 position, with the system design and behavioral rounds playing a key role in the offer upgrade.

I received an interview call from HR after successfully completing a HackerRank assessment. My Super Day was scheduled for the first week of November, 2025. Two days after the Super Day, HR contacted me for the next steps, which involved verifying a few documents, followed by an HR discussion.

Round 1: System Design
This round focused on designing a Movie Ticket Booking system. The interviewer expected a detailed discussion covering various aspects:
1. Defining system requirements.
2. Proposing a suitable database schema.
3. Presenting both High-Level Design (HLD) and Low-Level Design (LLD), including class diagrams and snippets of code.
4. Discussing potential scaling strategies for the system.
Throughout the discussion, the interviewer also interjected with a few medium-level technical questions.

Round 2: Managerial Round
This was a standard managerial round where the questions were mostly behavioral and project-based. Key discussions included:
1. How I would handle conflicts with colleagues.
2. In-depth questions about my previous projects.

Round 3: DSA
The final technical round was centered around Data Structures and Algorithms.
1. I was given a medium-level problem based on trees, for which I had to propose two different approaches.
2. There was also a code review exercise.

1st Round (Coding)

This round focused on breadth of knowledge rather than depth, as I was asked multiple LeetCode medium-type questions within an hour. I was able to answer most of these since they were quite popular. The interviewer was also helpful, providing hints when needed. While I coded the first question fully, for others, I mainly wrote down the core logic in 2-3 lines. There was also some discussion regarding the work I had highlighted on my resume.

2nd Round (LLD)

Although this round was designated for Low-Level Design, it delved heavily into Java fundamentals and its unique aspects compared to other languages. I was asked about the advantages of new features in Java 21, and to compare Java with languages like Scala (which I have experience with). Concurrency control in Java and its extension to distributed systems was also a major topic. I was given a piece of code to review for issues and another to debug and fix. There was an in-depth discussion about the technologies I've worked with, the design choices I made, and the rationale behind those decisions. This was one of the harder rounds I've experienced, as I was grilled rigorously on every point I brought up.

3rd Round (HLD + Behavioral)

This round was conducted by the Head of the department I was interviewing for. It began with a discussion about the new business initiatives they are building. Following this, behavioral questions were asked about my motivation for joining JPMC and the kind of work I was looking for.

The High-Level Design question involved designing a website capable of taking files/folders (like Aadhar documents) from a user, validating them through a third-party software (which takes 2-3 seconds), storing them in our system, and then providing a tracking link back to the user. Key discussion points revolved around storage strategies (e.g., file metadata in a database, file bytes in S3), managing the validation delay while ensuring a positive user experience (I suggested an asynchronous worker fleet and temporary storage), API design, and scaling considerations for the system.

Ultimately, I was selected for the role but with a downlevel to an SDE-2 position. The primary reasons given were that my overall experience (4.5 YOE) was less than most SDE-3s in their organization (who typically had >6 years), and my performance in the second round specifically did not meet the SDE-3 bar. I chose to decline the offer, despite the compensation being quite good and almost matching an SDE-3 salary to align with my current compensation.

I recently participated in the JP Morgan cohort hiring event. The interview process was quite structured, consisting of three distinct rounds, all conducted on the same day, each lasting approximately 45 minutes.

DSA & Code Review Round

The first round was focused on Data Structures & Algorithms and included a code review component. The interviewer, a developer with six years of experience, assessed my problem-solving skills, primarily with LeetCode medium-level questions. Beyond pure DSA, they also delved into my practical coding experience, specifically asking about my proficiency with API calls, file handling, exception management, and how I handle HTTP responses in real-world scenarios.

System Design Round

The second round was a System Design interview, led by a Senior Engineer with twelve years of experience. This was a comprehensive case study centered around designing the TicketMaster system. My task was multifaceted: I had to propose a robust database schema, clearly identify all the essential functional components, prepare a High-Level Design (HLD) diagram illustrating the architecture, and explain my deployment strategy for the system on major cloud platforms like Azure, AWS, or GCP.

Behavioral Round

Finally, the third round was a Behavioral interview. This round strictly followed the STAR (Situation, Task, Action, Result) methodology. The focus was on evaluating my communication skills, ability to work effectively in a team, problem-solving approach in non-technical scenarios, and my sense of ownership in past projects or situations.

The role specified a requirement of 3+ years of experience, and depending on my background, I was being considered for either a SWE 2 or SWE 3 position.

I applied on the JPMC careers website for various SWE 2/3 job roles and subsequently received an online assessment for one of them.

Round 1: Online Assessment

Round 2: Data Structures & Algorithms (DSA)

Round 3: High-Level Design (HLD)

Round 4: Hiring Manager (HM) Round

I recently had the opportunity to interview for an SDE3 position at JPMC (J.P. Morgan & Chase) in Bengaluru. I applied via LinkedIn and received an email to complete an online assessment within two days.

Round 1: Online Assessment

The online assessment consisted of two LeetCode Medium questions, which I had to complete within 60 minutes.

1. Minimum number of platforms needed for a railway station.
2. Counting valid substrings with no repeating adjacent characters and a length within a specified range (minLen, maxLen).

I managed to complete both questions within the given time limit.

After almost a month, I received a call from HR inquiring about my availability for interviews. The interview format was a "Superday," meaning all rounds would happen on the same day with 15-minute breaks, and each round would occur independently of the previous rounds' outcomes.

Round 2: Code Pair

This round was divided into two sections:

PR Review (10 mins)

I was presented with a Pull Request and its description. The focus was primarily on my understanding of Design Principles, Security Concerns, Logging, Clean Code practices, identifying potential SQL Injections, Middleman Attacks, and Concurrency/Multi-threading issues.

DSA Problem

I was given a matrix of size m*n containing 1s and 0s. The task was to count the number of connections that could be made from one level to the next feasible level. A node represented by 1 could connect to a 1 on the next level. If any level had no 1s, I needed to check for the next possible level that did. For example, given int[][] graph = [[1,0,0,1], [1,1,0,1], [0,0,0,0], [1,0,0,0]], the count would be 2 * 3 + 3 * 1 = 9.

Round 3: System Design

For this round, I had to design a News Aggregator System on a HackerRank Whiteboard. The system needed to present real-time updates from multiple news sources to a UI, where users could log in and set their preferences.

My approach for this round involved:

• Defining Functional Requirements
• Defining Non-Functional Requirements
• Creating a High-Level Design Diagram
• Discussing Database Schema (Tables, Columns)
• Outlining necessary APIs

Round 4: Behavioral Round

This round began with discussions about my resume and the projects I had worked on. Following that, I answered behavioral questions based on my project experiences and some generic situational questions.

1. How do you keep up with the latest technologies?
2. How do you handle pushback on a solution from higher management?

My interview journey for the SDE-2 role at JPMC began with an Online Assessment that lasted one hour. It consisted of two medium-level coding problems, one involving String manipulation and the other a Shortest path problem in graphs. I managed to solve both within the allotted time.

Following this, I advanced to the Data Structures & Algorithms + Code Review round, which took about 45-50 minutes. Here, I faced a code review task where I had to suggest improvements and ensure the given code passed all test cases; I focused on optimization and clean code practices. Subsequently, I tackled a medium-hard coding problem on HackerRank that utilized the sliding window technique, achieving an optimal O(N) time and O(1) space complexity, which impressed the interviewer.

The third round was dedicated to System Design, also lasting 45 minutes. I used HackerRank's platform tools to design a scalable parking lot system. My discussion revolved around scalability, essential system components, and architectural choices, engaging in a Q&A with the interviewer who was satisfied with my approach.

Next was a 45-minute Behavioral Round. I was asked to discuss my current project, particularly how I handled complex problems within it. This round also included situational and HR-type questions. I made sure to ask thoughtful questions, demonstrating my interest in the company and the role, which helped build a good rapport.

Finally, the HR Discussion covered my past work experience, salary expectations, and general questions to assess my mindset and fit for the role. This was a straightforward conversation, culminating in the discussion of my job offer details.

I recently appeared for a Software Engineer 2 role at JPMorgan Chase. There were a total of two interview rounds for me.

First Round

This was a one-hour round with a Project Manager. She was very friendly, and the round went well. She asked basic Java, Spring Boot, and project-related questions.

Questions I remember:

• What is finally block and when it is called?
• Exception propagation in Java?
• How HashMap works?
• Difference between flatMap and map?
• What is a functional interface?
• Difference between @RestController and @Controller?
• Advantages of Spring over Spring MVC?

Second Round

This was another one-hour round. The interviewer had 20 years of experience. It started with an introduction and a discussion about my projects. Since JPMC is in the finance domain and I also work in finance, he asked very key questions from my project. I even answered a few project questions with some doubt.

He then moved on to Java, Spring Boot, and database-related questions, ranging from basic to advanced topics. I was not satisfied with my performance, especially regarding the design pattern code he asked for.

Questions I remember:

• Can a Java class be static?
• Can a Java class be final?
• Can a Java class be private?
• Can we override static, private, or final methods?
• Transaction propagation in Spring Boot?
• Given Employee and department classes, without modifying these classes, how can we establish a relationship between these two so that a department can hold all of its employees and we can return all of its employees given a department object?
• He asked an SQL query to return a list of all departments with zero employees.

The second round did not go well for me. I answered a few project questions with doubt and could not answer some of the advanced Java and Spring Boot questions.

I did not hear anything back, and I didn't even follow up because I felt I hadn't performed to my average. However, overall, these rounds were good for learning.

I recently applied for the J.P. Morgan cohort SWE Bengaluru 2024 and wanted to share my interview journey.

Online Assessment (OA)

Shortly after applying, I received a link to the online assessment. It consisted of two questions of easy-medium difficulty. One question was Minimum String Length After Removing Substrings; I don't recall the exact second question, but it was of similar difficulty.

Three days after completing the OA, a recruiter called me to inform me that I had progressed to the next stage and that they would schedule my Superday. About 15-20 days later, they contacted me again to confirm the schedule for my Superday.

Superday

My Superday consisted of three rounds, all conducted on the same day.

Round 1: Design Pair Round

I was asked to design a high-level system for a parking lot. An AI service was already present, which automatically captured the photo of a vehicle's number plate and its entry timestamp. My task was to design the rest of the services and components, considering this existing AI service.

Round 2: Behavioral Round

This round involved general situation-based questions designed to understand my behavioral traits and how I handle different scenarios.

Round 3: Code Pair Round

This round had two parts. First, I was given a piece of working code and asked to provide review comments on it, similar to how one would review a pull request (PR). Second, I was asked to solve a problem: count the number of substrings with non-repeating characters.

All three rounds went well. Two days later, I received an email confirming that I was one of the selected candidates. They requested a few details like my current CTC, expected CTC, and notice period. Two days after providing the required information, HR scheduled a call with me to discuss the details of the position and the CTC they were offering, as the cohort was for both SE2 and SE3. The very next day, I received my offer letter for SE3.

I recently applied to the J.P. Morgan cohort SWE program for 2024 in Bengaluru and wanted to share my interview journey.

Online Assessment (OA)

1. One question was Minimum String Length After Removing Substrings.
2. The second question's exact details I don't recall, but it was of similar difficulty.

Superday

Round 1: Design Pair Round

Round 2: Behavioral Round

Round 3: CoderPad Round

1. I was given a piece of working code and asked to provide review comments on it, similar to performing a pull request (PR) review.
2. I had to write a function to count the number of substrings with non-repeating characters.

I interviewed for the Software Development Engineer (SEP) role at JPMC through an on-campus drive at IIT (BHU) Varanasi. The profile was open to students from CSE, MnC, EE, and EC branches. With a B.Tech in CSE from a Tier 1 college and 0 years of experience, complemented by a research project and a 2-month internship at Samsung Bangalore, I proceeded through the selection process.

Coding Test

The process began with a 1-hour coding test on HackerRank, consisting of two easy-to-medium level questions. I managed to solve both within 5 minutes, passing all test cases, and was subsequently shortlisted for the interview rounds.

Round 1: Technical Interview (60 minutes)

This round had two interviewers and started with my introduction and a deep dive into my resume. We discussed Data Structures and Algorithms, specifically hash maps. I was asked about their definition, working mechanism, and structure. Unfortunately, I couldn't answer these accurately as I hadn't reviewed the concepts recently.

The discussion then shifted to priority queues, their functionality, and time complexity. Following this, the second interviewer focused on my research project on IoT and WSNs, and my published paper. They were very curious about the novelty of my work and how I executed it. My internship experience at Samsung Research Institute was also thoroughly discussed, with one interviewer even asking me to visually explain my work on paper due to its complexity.

Towards the end, an out-of-the-box system design question was posed, based on my IoT background. I was asked to design an IoT system for a 5-floor parking lot to efficiently utilize space, ensuring cars don't move to the next floor until the current one is sufficiently occupied. I spent a few minutes thinking and provided a convincing answer, which seemed to leave a very good impression and led to my invitation for Round 2.

Finally, I was asked to write code to sort an array and explain its time and space complexity, which I found quite straightforward. The round concluded positively after I asked them a question.

Round 2: Tech + HR Interview (25 minutes)

This round was a blend of technical and HR questions, primarily assessing my soft skills and communication. We discussed my Django project, focusing on what Django is, how it works, and why I chose it over other frameworks. The conversation then moved to my understanding of JPMC and my motivation to join the company. I expressed my interest in finance and how JPMC combines finance and technology, aligning with my career goals. I also mentioned my aspiration to switch to a Quantitative Researcher role in the future, acknowledging that this might not be immediately available in the current profile. I affirmed my comfort with a Software Developer role for now, open to any team allotment. This round also ended with a warm handshake after I asked a question.

Round 3: HR Interview (10 minutes)

This was a very brief and relaxed round, with no serious HR questions. We discussed my family background, living location, and my preferences for Bangalore, Mumbai, or Hyderabad. The interviewer also inquired about my day, leading to a discussion about other interviews I had given recently. The interview concluded with the interviewer's encouraging words, "So, Yash, your hunt will hunt today...and we will see you on the other side," followed by a warm handshake.

P.S.: Despite the positive interactions, I unfortunately did not receive an offer. There were complications, and I was waitlisted after an initial confirmation from HR. It was a matter of hard luck, and a long story for another time.

My hiring process at JPMC, conducted via the Code for Good hackathon, was divided into three steps: an Online Coding Test, a HireVue Interview, and the Code for Good Hackathon itself.

The first round was an online coding test on HackerRank, featuring two programming questions worth 50 points each. Next, I had a 10-minute HireVue interview which consisted of two questions.

The final round was the Code for Good Hackathon. My team, consisting of 7-8 students, had two days to develop a solution for an NGO's problem statement. We chose a MERN stack-based web application and ended up as runners-up. During the hackathon, I also had 1-on-1 interviews with two mentors, which I believe were crucial for selection.

My first mentor interview lasted about 30 minutes. Since I was working with MongoDB, the discussion revolved around databases, comparing SQL and MongoDB, and specific SQL queries. We also covered Middleware in Node.js, REST APIs, and schema generation with Node.js and MongoDB. The second mentor interview was about 20 minutes. I demonstrated my contributions to the hackathon project and discussed one of my resume projects. He concluded with some typical HR questions.

Approximately 45 days later, I received an email with an offer for a 6-month internship followed by full-time employment at JPMC.

Round 1 - 60 minutes phone call

My first round was a 60-minute phone call. We had a detailed discussion on several core OOPs concepts including special pointers, virtual tables, const functions, private constructors, and the Singleton pattern. Following this, I was given one coding question and one behavioral question.

Round 2 - 60 minutes screen sharing

The second round involved 60 minutes of screen sharing. We continued our discussion on OOPs concepts, delving into special pointers, the const keyword, inline functions, how virtual functions are implemented (vtable), how the vtable of base and derived classes would look for a function override, and virtual destructors. After the discussion, I was given another coding question.

Round 3 - 60 minutes screen sharing

My third round, also 60 minutes with screen sharing, started with a discussion on OOPs concepts in the context of a trade system, specifically inheritance. I was then asked a design question about creating a stack class by inheriting from an array class, its pros/cons, and alternative implementations. Further OOPs concepts like metaclasses, composition, encapsulation, and inheritance were discussed. This round concluded with two coding questions.

Round 4 - 30 minutes screen sharing

The final round was a 30-minute screen sharing session. I was presented with one coding question, followed by two behavioral questions, one of which was a repeat from the first round.

I recently interviewed for a Senior Lead Engineer position at JPMC in April 2020. My interview experience was divided into several rounds, touching upon various technical aspects. The initial rounds focused heavily on fundamental data structures and algorithms, where I was challenged with a classic tree construction problem and implementing a generic stack from scratch. Subsequently, the interview delved into core Java concepts, including the characteristics and optimal use cases for different collections, their thread-safety properties, and specifics regarding ConcurrentHashMap and HashSet. Finally, there were questions about advanced testing methodologies using JUnit, particularly concerning how to test private methods and count method invocations for monitoring or verification.