JPMorgan
Free first round · 20 min · no credit card
Risk-discipline + DSA rigor. Code for Good campus program at IITs.
How JPMorgan Chase actually interviews
JPMorgan India interviews are rigorous on fundamentals — DSA at medium-hard difficulty, distributed-systems design, and a deep code-review/project round where the interviewer probes for risk-thinking. Compared to FAANG, the bar on raw algorithmic novelty is slightly lower, but the bar on production-grade defensiveness (idempotency, audit logging, security review, regulatory awareness) is higher. Most loops include a HackerRank online assessment followed by 3–4 elimination rounds, all structured.
The behavioral component is heavily integrity-loaded. Interviewers are trained to probe for past situations where the candidate was pressured to skip controls, mishandle data, or accept incomplete information — and to listen for whether the candidate escalated. Discomfort with rigor or a track record of "shipping fast and apologizing later" is a near-automatic decline at JPMC.
Campus hiring is largely funneled through the Code-for-Good 24-hour hackathon held in Bangalore, Mumbai, and Hyderabad each summer; this replaces most of the technical loop with a team-performance evaluation. Lateral hires go through the standard online assessment plus interview loop described below.
A "hire" at JPMC India is an engineer who can ship production-grade, regulator-defensible systems with minimal supervision and who demonstrates integrity instincts under pressure. Raw IQ alone does not clear the bar.
What they're measuring you on, beyond the right answer
The values interviewers probe for. Each pillar is what they ask about, plus how they ask it.
Integrity First
Acting with honesty and ethics is non-negotiable; the firm is heavily regulated and trust failure is a career-ending event.
How they probe · Behavioral STAR scenarios on conflicts of interest, dealing with bad data, or pressure to cut corners — the answer must show you escalated, not absorbed.
Risk Discipline
Engineers are expected to think about edge cases, failure modes, blast radius, and regulatory impact before shipping — not after.
How they probe · Code review rounds where bugs are seeded; system design rounds that probe failover, idempotency, and audit trails.
Scale and Rigor
The firm processes trillions of dollars daily; solutions must hold up at extreme throughput and under audit. Hand-waving fails.
How they probe · DSA at medium-to-hard difficulty with optimal complexity expected; system design grilled on throughput, latency SLAs, and consistency models.
Customer Focus (Internal + External)
Even back-office engineering teams have direct internal clients (traders, analysts, compliance). Engineers must understand who consumes what they ship.
How they probe · Project deep-dives where they ask 'who used this and how did they tell you it worked?'
Collaborative Intensity
Cross-LOB (line-of-business) collaboration is constant; lone-wolf brilliance is undervalued versus people who unblock teams.
How they probe · Behavioral questions on conflict with manager or peers, leading without authority, working with non-technical stakeholders.
Round-by-round, in the order they actually run
Reported pattern from candidate write-ups. Eliminating rounds are the ones where a single bad signal ends the loop.
- 01Recruiter screen30 minNon-eliminating
career story, why JPMC, comp expectations, team-fit signals
- 02Online assessment60 minEliminating
2 HackerRank coding problems — typically one HashMap/array, one DP or graph
- 03Dsa Technical60 minEliminating
live DSA with interviewer; medium-hard LeetCode style; optimal complexity probed
- 04System design60 minEliminating
distributed-systems design, often financial domain (payments, market data, fraud); failover, idempotency, audit trails are scored hard
- 05Project Deep Dive Code Review45 minEliminating
candidate's past project + a seeded-bug Java/Python code review on HackerRank
- 06Hiring manager60 minEliminating
behavioral, conflict scenarios, why-JPMC, leadership signals, integrity probes
- 07Hr Offer30 minNon-eliminating
comp negotiation, notice period, references
What candidates were actually asked
Curated from interview reports and company write-ups. Practise against any of these in a live mock.
SDE · Senior
Coding
- Find missing letters in a string given a dictionary
- Determine if any 3 integers in an array sum to target K
- Clone a directed graph (deep copy with random pointers)
- Minimum coins to reach a sum (classic DP)
- Detect if integer + reverse(integer) is a palindrome
- LRU cache implementation with thread-safety follow-up
- Find longest substring without repeating characters
- 2D dynamic programming: min path sum with obstacles
- HashMap-based: group anagrams across 10M-string corpus
System design
- Design a fraud detection system for credit-card transactions
- Design a global payment-processing system (idempotency, retries, exactly-once semantics)
- Design a real-time market data feed (FIX protocol awareness valued for trading-tech roles)
- Convert a monolithic order-management service to microservices
- Design a data warehouse for end-of-day P&L reconciliation
- Design a stock-prediction batch pipeline with audit trail for regulators
Behavioral
- Tell me about a time you found a critical bug late in the cycle. What did you do?
- Describe a conflict with your manager. How did you resolve it?
- Why JPMorgan Chase over a product company?
- Walk me through your largest project and the riskiest technical decision in it
- Tell me about a time you had to escalate something uncomfortable
- How do you handle ambiguous requirements from a non-technical stakeholder?
Data Science · Senior
modeling
- How would you build a model for credit-default prediction in a regulated environment?
- How do you handle class imbalance in a fraud-detection dataset?
- Explain bias-variance tradeoff with a fraud-model example
- When would you NOT use deep learning for a financial-services problem?
Case study
- Design an AML (anti-money-laundering) alerting pipeline
- Identify drivers of customer churn in a credit-card portfolio
Behavioral
- Tell me about a model you shipped that performed worse in production than in dev
- How do you explain a complex model to a regulator or auditor?
Product · Senior
Product sense
- How would you redesign Chase mobile onboarding for first-time investors?
- Pitch a feature for the JPM Markets app that improves trader productivity
- How would you approach launching a new product in a regulated market?
Behavioral
- Describe a time you killed your own feature. Why?
- Tell me about a launch where compliance or legal pushed back hard
The two patterns that decide every loop
Red flags
- Cavalier attitude toward edge cases, audit logs, or regulatory impact
- Past examples that hint at integrity shortcuts (over-promising to clients, hiding bugs, etc.)
- Cannot articulate WHY they want financial services vs. product company
- Hand-wavy system designs with no failure-mode reasoning
- Talking down on JPMC's regulatory burden or 'old-school' culture
- Discussing material non-public information from a previous employer
- Surface-level project descriptions — cannot answer 'what would you do differently?'
Advance signals
- Volunteers risk + failure analysis without being prompted
- Demonstrates clear understanding of why financial-services engineering is harder than CRUD
- Comfortable with ambiguity but defaults to escalating, not absorbing
- Code-review round: spots subtle bugs (off-by-one, race conditions, missing nullchecks, missing audit logging)
- Strong communication with non-technical stakeholders evidenced in past stories
- Cites specific compliance / data-handling considerations in design rounds
Don't do
- Discuss material non-public information or proprietary systems from a current/past financial-services employer
- Bad-mouth previous regulators, auditors, or compliance partners
- Claim you 'just want to learn finance' — they read this as low conviction
- Skip edge-cases in coding rounds because 'it works for the happy path'
- Negotiate aggressively before clearing the loop; HR factors this into final calibration
- Show up to system design without asking about scale, latency SLA, or consistency requirements
Base salary bands by level
Junior
₹14–22L
Annual base
Mid
₹22–38L
Annual base
Senior
₹35–65L
Annual base
Staff+
₹65–130L
Annual base
Levels.fyi India median TC: Analyst ~17L, Associate ~27L, Senior Associate ~36L, VP ~57L. Greater Bengaluru median TC ~30L overall. VPs in CIB / Markets tech can hit 80–130L TC with bonus (cash bonus 10–25% of base, paid Jan-Feb, can stretch top end materially). No public-market RSU grants below VP level — comp is base + cash bonus heavy at the lower levels. Annual bonus is the single biggest variable.
What to expect after each round
Typical timeline
~5 weeks
Recruiter-screen → offer
Reapply window
6 months
After a final-round rejection
Feedback practice
Recruiter shares pass/fail per round; detailed feedback rare unless explicitly requested. Specific scoring breakdown is never shared.
“Thanks for your time today — your recruiter will share the next-round update within 5 business days.”
Verified profile
Last verified Mon Apr 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time) · 10 sources
View sources
- Levels.fyi — JPMorgan Chase India SWE: https://www.levels.fyi/companies/jpmorgan-chase/salaries/software-engineer/locations/india
- Levels.fyi — JPMorgan Chase Greater Bengaluru SWE: https://www.levels.fyi/companies/jpmorgan-chase/salaries/software-engineer/locations/greater-bengaluru
- Glassdoor JPMorganChase Software Engineer reviews (522 reviews, 2024-2026): https://www.glassdoor.com/Interview/JPMorganChase-Software-Engineer-Interview-Questions-EI_IE5224839.0,13_KO14,31.htm
- LeetCode discuss — JPMC SDE-2 Hyderabad offer: https://leetcode.com/discuss/interview-experience/4584155/JP-Morgan-Chase-and-Co.-or-SDE-2-or-Hyderabad-or-Offer
- Jointaro — JPMC SDE II Bengaluru, May 2025: https://www.jointaro.com/interviews/companies/jpmorgan-chase/experiences/software-engineer-ii-bengaluru-karnataka-may-1-2025-no-offer-positive-37a28422/
- InterviewQuery JP Morgan SWE Guide 2025: https://www.interviewquery.com/interview-guides/jp-morgan-chase-software-engineer
- JPMorganChase official 'How We Do Business' principles: https://www.jpmorganchase.com/about/business-principles
- JPMorgan Code-for-Good 2025 official rules: https://careers.jpmorgan.com/content/dam/careers/documents/social-good-hackathons/2025-CFG-Candidate-Agreement.pdf
- GeeksforGeeks JPMC FTE interview experience (India): https://www.geeksforgeeks.org/jp-morgan-chase-co-jpmc-interview-experience-full-time-software-engineer/
- Educative — JP Morgan System Design questions: https://www.educative.io/blog/jp-morgan-system-design-interview-questions