The HireVue link arrives on a Thursday and expires Sunday. You get thirty seconds to think and two minutes to answer, into a webcam, with no human on the other end and a countdown bar draining in your peripheral vision. Candidates who interview well in person routinely fall apart here, and the reason is simple: talking to nobody is a separate skill, and almost nobody practises it.
JPMorgan Chase is one of the largest technology employers in banking — tens of thousands of engineers, and a hiring process that screens as hard for motivation as for algorithms. Here are the JPMorgan interview questions with real answers.
The JPMorgan interview process
Stages vary between the Software Engineer Program for graduates and experienced hires, and between lines of business. The sequence below is the common shape; confirm yours with the recruiter rather than assuming.
Round 1 — online coding assessment
HackerRank-style, typically easy to medium. A filter, not a differentiator.
Round 2 — the recorded video interview
Pre-recorded behavioural questions with a short preparation timer and a fixed answer window, sometimes with a technical question included. Practise this format specifically: record yourself on your phone answering "why JPMorgan" in ninety seconds and watch it back. It is unpleasant and it is the single highest-return thing you can do for this round.
Round 3 — final rounds or superday
Several back-to-back interviews: coding, CS fundamentals, a project deep dive, behavioural, and system design for experienced roles. Stamina matters — the fourth conversation is where prepared answers start coming out flat.
JPMorgan technical questions, with answers
Data structures and algorithms
Arrays, strings, hashing, trees and some dynamic programming, at easy-to-medium difficulty. The bar is lower than a FAANG loop; the expectation of clean, correct, explained code is not. Handle the empty input and state your complexity without being prompted.
Explain the four OOP principles
Standard, and asked more often in finance than in product companies because the codebases are large, long-lived and Java-heavy. Give an example first and let the definition follow. Expect a follow-up on interface versus abstract class: an abstract class can hold state and constructors and a class extends exactly one; an interface defines a contract and a class can implement many. Our OOPs guide covers the rest.
ACID properties, and why a bank cares
Atomicity, consistency, isolation, durability. This is worth more here than almost anywhere else, so connect it to the domain rather than reciting it: a funds transfer is the canonical atomicity example, because a debit that succeeds while its matching credit fails is not a bug, it is missing money. Be ready for isolation levels and what a dirty read or a non-repeatable read would mean on an account balance. Our DBMS guide goes deeper.
The project deep dive
Your role, your technical decisions, and what you would change. Interviewers probe for genuine ownership, so be precise about which parts were yours. If you worked on something with real constraints — latency, correctness, data volume — lead with the constraint, because that is the shape of the work they are hiring for. Our guide on explaining your project has the structure.
System design, for experienced roles
Frequently finance-flavoured: a payment processing flow, a trade capture pipeline, a real-time fraud check. The recurring theme is correctness under failure — idempotency of payment operations, exactly-once versus at-least-once processing, and how you reconcile when a downstream system times out after committing. See our system design guide.
Behavioural and motivation questions
Why JPMorgan, and why technology in finance?
This is the question that decides marginal candidates, and a generic answer is close to disqualifying because the interviewer's real worry is that you are treating the bank as a fallback. Have a specific reason: a line of business you want exposure to, the scale and latency constraints of payments infrastructure, the regulatory rigour, a product you have used. "Stability and good training" is honest and acceptable if you can say why it matters to you. See how to answer "why do you want to work here".
Tell me about a time you solved a difficult problem
STAR, with the technical detail kept proportionate to your audience, and a quantified result. The most common failure is spending ninety seconds on situation and fifteen on what you actually did.
Tell me about a disagreement with a teammate
Pick a real one with a resolution that was not simply you winning. Banks screen hard for people who can disagree without escalating, because the codebases and the teams are both long-lived. Our conflict question guide has worked answers.
How do you handle pressure and deadlines?
Describe a system rather than an attitude. "I stay calm under pressure" is a claim; "I list what must ship versus what can slip, confirm that split with whoever owns the deadline, and flag the slip the day I see it rather than the day it lands" is a method. Our handling pressure guide covers it.
How this compares to the other ways you could prepare
LeetCode handles the coding assessment and there is no shortcut worth taking. Cap the effort though — this is not a loop where a hundred extra hard problems changes the outcome, and that time is better spent on the rounds that actually decide it.
Written STAR answers in a document are where most candidates stop, and it is the wrong stopping point for this process specifically. A recorded video round has no interviewer to nod, no chance to restart, and a hard cutoff. An answer that reads well at 400 words becomes a rushed, unfinished ninety seconds when spoken, and you only discover that by speaking it.
Greenroom runs it out loud with a timer's discipline, and Ari asks the follow-up rather than accepting the first answer — you said you wanted fintech, so what specifically about payments infrastructure? The honest limit: Ari has no view of JPMorgan's internal bar or which team you would land on, and no external resource does. What it fixes is the gap between the answer you have written and the answer you can deliver. Interviewing across banks? Our Goldman Sachs and Barclays guides map the neighbouring loops, and our behavioural questions guide covers the story structures.
Frequently asked questions
What is the JPMorgan software engineer interview process?
Typically an online coding assessment in HackerRank style, a pre-recorded video interview covering behavioural and sometimes technical questions, and then final rounds or a superday with coding, CS fundamentals, a project deep dive, behavioural questions and system design for experienced roles. Stages vary between the graduate Software Engineer Program and experienced hiring, so confirm with your recruiter.
What technical questions does JPMorgan ask?
Easy to medium data structures and algorithms across arrays, strings, hashing, trees and some dynamic programming; CS fundamentals with a strong emphasis on OOP and databases, particularly ACID properties and isolation levels; a deep dive on your project; and for experienced roles a finance-flavoured system design round on payments, trade capture or fraud detection.
How hard is the JPMorgan coding interview?
The algorithmic bar is generally lower than a large product-company loop, sitting around easy to medium difficulty. The expectation of clean, correct, well-explained code is not lower. Candidates more often lose on the behavioural and motivation rounds than on the coding.
How do I prepare for the JPMorgan HireVue video interview?
Practise the format rather than only the content. Record yourself on your phone answering questions like why JPMorgan within a fixed ninety-second window and watch it back. There is no interviewer to react, no restart and a hard cutoff, so answers that read well written often run long or trail off when spoken for the first time.
Why does JPMorgan ask why you want to work in finance?
Because the bank screens for genuine motivation, not just capability, and interviewers are checking that technology in finance is a deliberate choice rather than a fallback. A specific answer about a line of business, the scale and correctness constraints of payments infrastructure, or the regulatory environment carries far more weight than general praise of the firm.
What behavioural questions does JPMorgan ask?
Expect why JPMorgan and why technology in finance, a time you solved a difficult problem, a disagreement with a teammate and how it resolved, an example of teamwork or leadership, and how you handle pressure and deadlines. Answer in STAR with a quantified outcome, and describe a repeatable method rather than asserting a personality trait.