Skip to content

JP Morgan Interview Questions

JP Morgan’s technology hiring funnels through an OA, a HireVue video screen, and two technical interviews, with a parallel Code for Good hackathon track that can fast-track strong performers straight to an offer.

Round Duration What they test
Online Assessment 90-120 min Aptitude + coding problems (HackerRank)
HireVue Video Interview 3-5 questions Recorded behavioral answers, 2-3 min each
Technical Round 1 45-60 min DSA, OOPs, SQL, Java/C++
Technical Round 2 45-60 min Projects, domain topics (trade booking, low-latency)
HR / Managerial 20-30 min Motivation, location, background verification

A timed HackerRank test mixing 2-3 coding problems with mathematical and logical aptitude. Clean, fully-passing solutions are valued over partial cleverness - shortlist mail typically arrives within a few days of the test.

Common questions

  • Array/string coding problems at easy-medium difficulty
  • Quantitative and logical reasoning MCQs
  • Basic SQL query questions

A recorded, one-way interview with 3-5 pre-set questions - 30 seconds to prepare, then 2-3 minutes to record each answer, with exactly one re-record allowed per question. It screens for communication and motivation before any live technical round.

Common questions

  • Why do you want to work in banking technology?
  • Tell me about a time you solved a difficult problem
  • Describe a situation where you worked well in a team
  • Why JP Morgan specifically?

Focuses on core DSA and CS fundamentals with live coding, plus OOPs and SQL questions.

Common questions

  • Valid parentheses / balanced-expression checks (stack-based)
  • Find duplicates in a stream of data (hashing)
  • SQL + coding hybrid - nth-highest-salary style queries using window functions
  • OOPs concepts - inheritance, polymorphism, interfaces vs abstract classes

Goes deeper into your resume project and domain systems relevant to JP Morgan - trade booking, low-latency processing, and risk systems - at a fresher-appropriate depth.

Common questions

  • Explain trade booking in plain language - inputs, outputs, what breaks at scale
  • Discuss low-latency system design - bottlenecks and failure modes
  • Detailed project walkthrough - architecture, hardest bug, what you’d rebuild
  • API and data-model design questions for a simple risk or trading system

Full round-by-round narratives are on the JP Morgan interview experience page.

A closing conversation on motivation, location preference, and comfort with background-verification timelines. Concrete, situation-based answers land better than rehearsed slogans.

Common questions

  • Why banking technology, and why JP Morgan?
  • Tell me about a time you showed leadership while resolving a conflict in a team
  • Tell me about a time you received tough feedback - how did you respond?
  • Are you comfortable with the background-verification process and timelines?

Sample answer frameworks for each of these are on the JP Morgan HR interview questions page.

Code for Good: JP Morgan’s hackathon fast-track

Section titled “Code for Good: JP Morgan’s hackathon fast-track”

Unlike most bank recruiting funnels, JP Morgan runs Code for Good - a weekend hackathon where shortlisted students form teams and build real software for non-profit organizations, mentored directly by JP Morgan engineers. It runs alongside the standard interview process at many campuses rather than replacing it, and strong performers can be fast-tracked into summer analyst or full-time software engineering offers without completing the full standard technical-interview loop. If your campus runs a Code for Good drive, it’s worth treating as a parallel - and sometimes faster - path to an offer.

Frequently asked questions about JP Morgan interviews

Section titled “Frequently asked questions about JP Morgan interviews”
What is the JP Morgan interview process for freshers?

JP Morgan’s technology loop typically runs: 1. Application (on-campus via college placement cell, off-campus via the JP Morgan Careers portal, or through referrals). 2. Online Assessment (90-120 minutes) - 2-3 coding problems on HackerRank plus mathematical/logical aptitude. 3. A HireVue recorded video interview - 3-5 pre-set questions, 30 seconds to prepare and 2-3 minutes to record each, with one re-record allowed per question. 4. Two technical interviews (45-60 min each) covering DSA, OOPs, SQL, and domain topics like trade booking and low-latency systems. 5. A closing HR/managerial round (20-30 min) on motivation and background verification. Total duration: roughly 3-4 weeks from application to offer.

What questions are asked in JP Morgan interviews?

Technical rounds commonly ask stack-based problems like valid parentheses/expression checks, hashing problems like finding duplicates in a stream, and SQL-plus-coding hybrids (nth-highest-salary style queries, window functions). Expect domain conversation around trade booking, low-latency system design, and risk systems explained in plain language, plus a detailed walkthrough of your resume project - architecture, hardest bug, what you’d change. Behavioural rounds check ownership, teamwork, and why JP Morgan.

How many rounds are there in the JP Morgan interview?

JP Morgan typically runs 4-5 touchpoints: an Online Assessment (90-120 min), a HireVue video interview, two technical interviews (45-60 min each), and a closing HR round (20-30 min). Some drives skip the standalone HireVue or merge HR with the managerial round - check that cycle’s college placement email or offer communication.

What is JP Morgan’s Code for Good hackathon?

Code for Good is JP Morgan’s weekend hackathon where shortlisted candidates and students form teams to build software for non-profit organizations, mentored by JP Morgan engineers. It runs alongside the standard recruiting funnel at many campuses, and strong performers in the hackathon can get fast-tracked into summer analyst or full-time software engineering offers without going through the full standard interview loop.

How should I prepare for JP Morgan interviews?

Practise timed DSA on stacks, hashing, and graphs, revise OOPs and SQL (especially window functions and joins), and prepare one crisp, detailed project narrative you can defend under follow-up questions. Read up on trade booking and low-latency systems so you can explain them in plain language rather than buzzwords, and rehearse the HireVue format - short, structured answers recorded in a single take. Use STAR for behavioural answers.

Does JP Morgan interview differently for technology vs other analyst roles?

Yes. Technology Analyst / Software Engineer candidates are evaluated on coding, CS fundamentals, and domain systems knowledge (trade booking, low-latency, risk). Business/operations analyst tracks lean more on aptitude, case-style reasoning, and finance fundamentals with little to no coding. Confirm which track your req falls under before you start prepping - the technical bar and question style differ substantially.

Looking for placement papers, OA practice, or coding questions?

Section titled “Looking for placement papers, OA practice, or coding questions?”