Skip to content

JP Morgan Interview Experience 2025–2026 — Real Candidate Stories

These write-ups reflect how JP Morgan fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

JP Morgan placement process includes: 1. Application (on-campus via college placement cell, off-campus via JP Morgan Careers portal, or through referrals), 2. Online Assessment (OA) - 90 minutes (2-3 coding problems and mathematical aptitude), 3. Technical Interviews (2 rounds, 45 min each) - DSA, system design, projects, 4. Managerial Round (45 min) - Technical depth and behavioral fit, 5. HR Interview (30 min) -…

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: JP Morgan eligibility criteria for freshers 2026, based on candidate reports: Minimum 70% or 7.0+ CGPA in 10th, 12th, and graduation. Degree required: B.Tech/B.E./M.Tech in Computer Science, IT, ECE, or related fields.…

Fresher offers (candidate-reported) often land around (Technology Analyst role) ranges from ₹25-35 LPA total compensation in India. This includes base salary (₹18. Treat numbers as directional — confirm on your offer letter.

RoundDurationWhat they test
Online Assessment90–120 minAptitude + coding / technical MCQs
Technical Round 145–60 minDSA, OOPs, SQL, Java/C++
Technical Round 245–60 minProjects + domain / puzzles (varies)
HR20–30 minMotivation, location, bond if any

Experience 1: Technology Analyst / SDE (2025)

Section titled “Experience 1: Technology Analyst / SDE (2025)”

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

  • Focus stayed on problem-solving speed and clean code, not trick questions.
  • Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

  • Coding: Second highest salary style SQL + coding hybrid — approach used: SQL window / hash. Interviewer cared about complexity and edge cases.
  • Follow-up coding: Balanced parentheses / expression validation — stack.
  • Domain discussion around trade booking and low-latency — they wanted practical trade-offs, not buzzwords.
  • Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

  • Why banking technology?
  • Are you comfortable with longer background checks?
  • Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to JP Morgan’s domain (trade booking).

Experience 2: Technology Analyst / SDE (2024–2025)

Section titled “Experience 2: Technology Analyst / SDE (2024–2025)”

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

  • OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
  • Second technical leaned more into risk systems and system design basics (APIs, DB choice, failure modes).
  • Coding warm-up: Find duplicates in a large stream — hashing / bitset discussion.

Mistakes to avoid

  • Jumping into code without clarifying constraints
  • Treating HR as a formality — JP Morgan still filters on communication and intent
  • Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For JP Morgan, consistent DSA plus a clear story on trade booking beats a perfect CGPA with weak explanation.

  1. Second highest salary style SQL + coding hybrid — typically expects SQL window / hash
  2. Balanced parentheses / expression validation — typically expects stack
  3. Find duplicates in a large stream — typically expects hashing / bitset discussion
  4. Discussion on trade booking and low-latency — capacity, failure modes, simple APIs
  5. Project deep dive — architecture, hardest bug, what you would change
  1. Why banking technology?
  2. Are you comfortable with longer background checks?
  3. Location preference
  4. Strengths and weaknesses
  • Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
  • For domain rounds, be ready to talk about trade booking in plain language — inputs, outputs, bottlenecks.
  • Revise OOPs and SQL; many JP Morgan panels still open with fundamentals.
  • Keep HR answers concrete. One story with a clear result beats five buzzwords.
  • If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Last updated: August 2026