jpmorgan chase logo
JPMorgan Chase· Analyst

Title: JPMorgan Chase | Analyst | Mumbai | Feb 2026 [Rejected after 4 Rounds]

Location
Mumbai
Experience
1.7 years
Posted
4 Feb 2026
367 reads

Summary

I interviewed for an Analyst position at JPMorgan Chase in Mumbai. The process involved 4 rounds covering resume discussion, system design, DSA, behavioral, and a high-pressure ambiguity problem, which ultimately led to my rejection due to missing an edge case.

How it went

Status: SDE 1 at Barclays (1.7 YOE) IIT BG

Position: Analyst Location: Mumbai (onsite 5 days office) Salary Offered/Target: 25 LPA Date: Feb 2026

Overview:

The process consisted of 4 rounds in total, moving from basic project discussions to high-pressure ambiguity tests with Executive Directors (EDs).

Round 1: VP Round (Resume & Design)

Focus: Deep dive into my work at Barclays (Java 21, Kafka, React).

Questions:

  • Detailed discussion on my specific projects.
  • System Design/Observability: How would you debug a sudden increase in page loading time? (Discussed latency, DB bottlenecks, and network issues).
  • Concurrency: Real-world scenarios around record-level concurrency.
  • DB: Indexing and optimization questions.
  • Behavioral: Why do you want to switch from Barclays?

Round 2 (Associate): DSA (Problem Solving)

  • Question 1: Container With Most Water. Started with $O(n^2)$ and moved to the optimal two-pointer $O(n)$ approach.
  • Question 2: Find the second largest number in an array. Variations included handling duplicates vs. non-duplicates. Final expectation was a single-pass $O(n)$ solution.

Round 3: ED (Executive Director) Round 1 (Behavioral & Tech)

  • Behavioral: Standard questions (Strengths, Weaknesses, etc.).
  • Tech: Resume-related deep dives and a heavy focus on Kafka (likely due to my work with Kafka optimization at Barclays).

Round 4: ED(Executive Director) Round 2 (Ambiguity & Edge Cases)

This was the "Elimination" round. It started with my Full Stack experience and moved into a high-pressure coding scenario.

Full Stack Discussion:

  • Why use Redux for state management?

Frontend vs. Backend: Why not store all validations on the frontend?

Architectural choices: Why Spring Boot? Why a specific DB?

The "Ambiguity" Problem:

  • Task: Parse a date from a string of length 10. The format is unknown (could be yyyy_mm_dd, mm/dd/yyyy, etc.). The separator can be anything.
  • Requirement: Identify the separator and extract the date components correctly.

My Experience: I solved for the standard valid cases with assumptions. I missed one edge case with more than 2 separator.

Result: Rejected on the basis of not handling that final edge case under pressure.

Key Takeaways for Candidates:

  1. Expect Ambiguity: In senior/analyst rounds at JPMC, they often give problems with 50% missing info. Ask questions before coding.
  2. Stress Test: The interviewer might act hurried or confused to see if you stay calm.
  3. Full Stack means Full Stack: Even as a Backend-heavy dev, expect deep questions on React state (Redux) and frontend architecture.
  4. Don't ignore the "Why": Be ready to defend every tool in your stack (e.g., "Why not just use Context API instead of Redux?").

Final Note: Despite being a LeetCode Guardian, sometimes these "Managerial/ED" rounds come down to how you handle a specific edge case they have in mind. Don't let a rejection stop your momentum!

Happy Coding....!!

Questions asked (9)

  1. 01

    Debug Page Loading Time Increase

    System Design

    How would you debug a sudden increase in page loading time? (Discussed latency, DB bottlenecks, and network issues).

  2. 02

    Record-level Concurrency Scenarios

    System Design

    Discuss real-world scenarios around record-level concurrency.

  3. 03

    Why Switch Companies?

    Behavioral

    Why do you want to switch from Barclays?

  4. 04

    Container With Most Water

    Data Structures & Algorithms · Medium

    Find two lines that together with the x-axis form a container, such that the container contains the most water.

    Open the problem
  5. 05

    Find Second Largest Number in Array

    Data Structures & Algorithms · Easy

    Find the second largest number in an array, considering variations for handling duplicates vs. non-duplicates. The final expectation was a single-pass $O(n)$ solution.

  6. 06

    Why Use Redux?

    Other

    Why use Redux for state management?

  7. 07

    Frontend vs. Backend Validations

    System Design

    Why not store all validations on the frontend?

  8. 08

    Why Spring Boot? Why Specific DB?

    System Design

    Discuss architectural choices: Why Spring Boot? Why a specific DB?

  9. 09

    Parse Date from Ambiguous String

    Data Structures & Algorithms · Hard

    Task: Parse a date from a string of length 10. The format is unknown (could be yyyy_mm_dd, mm/dd/yyyy, etc.). The separator can be anything. Requirement: Identify the separator and extract the date components correctly.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at JPMorgan Chase recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!