Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · JPMorgan Chase

JPMorgan Technical Interview Questions India 2026

JPMorgan's software-engineer rounds in India blend core data structures and algorithms with object-oriented design and a finance-domain framing.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds3
Intense3 of 12
FrameworkFundamentals plus oop
Try it · JPMorgan Chase question 1 of 10
Standard

Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

Think of your answer first, then reveal how to structure it.
Practise this out loud

Expect clean-fundamentals problems (reverse a linked list, running max-profit over a trade stream) alongside design questions like modelling order types in a trading system for extensibility and testability. Interviewers reward SOLID design, correctness in money-handling logic, and fluency in Java or Spring. The bar is not exotic algorithms; it is disciplined, testable code and clear reasoning about edge cases in a financial context.

Practice questions

  1. 01

    Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

    Standard
    Practise
  2. 02

    What is the difference between a class and an object? Give an example.

    Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.
    Practise
  3. 03

    Write a SQL query to find the second-highest salary in a department.

    Warm-up
    Practise
  4. 04

    What is normalisation in databases? When would you de-normalise?

    Warm-up
    Practise
  5. 05

    What's the difference between a stack and a queue? Give a real-world use case for each.

    Warm-up
    Practise
  6. 06

    Given a stream of integers, design a data structure that returns the median in O(log n).

    Intense
    Practise
  7. 07

    You have a service that's slow only on Tuesdays. Walk me through how you'd debug.

    StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first.
    Practise
  8. 08

    Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.

    IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.
    Practise
  9. 09

    Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.

    StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas.
    Practise
  10. 10

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    Practise
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes

How to walk in ready.

The typical JPMorgan Chase recruitment process has 4 stages: Online coding assessment (HackerRank or similar) → Technical coding and OOP round → System/OOP design round with finance framing → Hiring-manager and fit round, then offer.

JPMorgan Chase typically conducts 3 interview rounds: Round 1 (60-90 min): online coding assessment; Round 2 (60 min): coding and object-oriented design round; Round 3 (45-60 min): design plus behavioral with a finance-domain framing.

HireStepX recommends the Fundamentals plus oop framework for this type of interview: Solve core DSA cleanly, then show SOLID, testable object-oriented design and careful correctness reasoning for the finance-domain framing.

TCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.

Googleyness: structured debugging, hypothesis-driven, instrumentation-first.

Stripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.

Core data structures and algorithms (linked lists, arrays, streams), object-oriented design with SOLID principles, and Java/Spring fundamentals, often framed around trading or money-handling scenarios.

Standard difficulty. The emphasis is disciplined, testable code and correct edge-case handling rather than exotic algorithms.

More to read

Practice

Rehearse the room before you enter it.

Run a mock JPMorgan Chase interview and get scored feedback on every answer.