Skip to content

JP Morgan Interview Experiences

How JP Morgan fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat 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) - Behavioral and offer discussion. Total duration: 3-4 weeks from application to offer.

Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.

Fresher package ballpark (from student reports): Analyst: ₹25-35 LPA. Confirm on your offer letter.

Round Duration What they test
Online Assessment 90-120 min Aptitude + coding / technical MCQs
Technical Round 1 45-60 min DSA, OOPs, SQL, Java/C++
Technical Round 2 45-60 min Projects + domain / puzzles (varies)
HR 20-30 min Motivation, location, background verification

JPMC runs two distinct fresher funnels in India and public write-ups split cleanly between them: the Code for Good (CFG) hackathon route, and a direct on-campus SDE route. They are not interchangeable - CFG has no conventional technical interview at all. Both accounts below are rewritten from public student posts.

Experience 1: Software Engineer via Code for Good

Section titled “Experience 1: Software Engineer via Code for Good”

Reported round 1 - online coding

  • HackerRank, 2 coding questions, roughly 60-90 minutes depending on the cycle. No MCQ section.
  • Difficulty reported as easy-to-medium; the recurring topics were hashing / unordered maps and linked lists.
  • In one drive about 30 candidates cleared this stage.

Reported round 2 - HireVue video interview

  • Pre-recorded, not live. Two attempts per question, each answer capped at roughly 2 minutes.
  • This is described as the biggest cut in the funnel - 30 down to 17 in the account above - and it is behavioural, not technical. People underestimate it because there is no interviewer.

Reported round 3 - the 24-hour hackathon

  • In person at a JPMC office (Mumbai in this account). Teams of 6-7 are assigned by the company, mixing students from different colleges.
  • Real non-profit problem statements; teams build a full-stack solution and present to judges.
  • Offers are few: this write-up reports 3 offers made overall, and the candidate was not selected despite writing most of the team’s code and getting good judge feedback.

Reported outcome: Not selected. Worth naming plainly - at CFG, individual coding output is not the scoring unit. Team behaviour, collaboration and the demo are.

Reported flow: HackerRank coding test → 3 interview rounds.

  • Coding test: 1 hour, 2 questions at easy-medium. This candidate finished both with all test cases passing well inside the time.
  • Technical round 1: HashMap internals (what it is, how it works under the hood), priority queue operations and their time complexity, code a sorting algorithm and state its time and space complexity. Then a long dig into the resume - an IoT / wireless sensor network project and a Samsung internship - ending in an open design question: manage parking allocation across a 5-floor parking lot using IoT.
  • Technical + HR round 2: Django and how it compares with alternatives, what the candidate knew about JPMC and why they wanted to join, interest in finance-meets-technology, and long-term aspirations (quant research came up).
  • HR round 3: family background, location preference among Bangalore / Mumbai / Hyderabad, and a general chat about how the day had gone.
  • Reported outcome: Verbally confirmed by HR, then waitlisted, and no final offer. A reminder that a clean interview day does not always survive headcount.

What the pattern suggests

  • The OA is a filter, not the fight - two easy-medium questions. Losing here is usually nerves or setup, not skill.
  • Interview DSA stays at fundamentals depth: hashmap internals, heaps, sorting complexity. Being able to explain how a HashMap resolves collisions matters more than solving a hard problem.
  • The resume is interrogated hard, and the open design question is typically framed around the candidate’s own project domain, not a generic system-design template.
  • “Why finance / why JPMC” is asked in a technical round, not just HR. Have a real answer.

Sources: GeeksforGeeks - JPMC SDE full-time on-campus · GeeksforGeeks - JP Morgan SDE on-campus 2023 · GeeksforGeeks - Code for Good, Software Engineer FTE · GeeksforGeeks - Code for Good internship

  1. Valid parentheses / expression checks. Usually expects stack
  2. Find duplicates in a stream. Usually expects hashing
  3. SQL + coding hybrid (nth highest / joins). Usually expects window functions / careful queries
  4. Discussion on trade booking and low-latency, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change
  1. Why banking technology?
  2. Comfort with background verification timelines
  3. Location preference
  4. Strengths and weaknesses
  • Clear the screening round first. Timed practice beats last-minute topic hopping.
  • For domain questions, explain trade booking in plain language, inputs, outputs, what breaks at scale.
  • OOPs and SQL still open a lot of JP Morgan panels. Do not skip fundamentals.
  • HR answers should be concrete. One story with a result beats five slogans.
  • If you do not know something, say so and outline how you would find out.

After technical rounds, JP Morgan usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

Goldman Sachs · Morgan Stanley · Bank of America · Deutsche Bank · Wells Fargo · HSBC