Assessment tips
- Confirm the current JP Morgan pattern from the drive mail before practising old papers
- Finish one problem or section fully before starting the next
- Revise the fundamentals listed in the round table on this page
JP Morgan Interview Experience 2026
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-wise process
| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 60-120 min | 2-3 coding problems + aptitude / MCQs (HackerRank or CodeVue) |
| HireVue (many campus paths) | ~30 min | 2-5 recorded behavioural answers; some cycles add coding + reflection |
| Technical Round 1 | 45-60 min | DSA, OOPs, SQL, Java/C++ |
| Technical Round 2 | 45-60 min | Projects + domain / puzzles (varies) |
| Managerial (some drives) | 45 min | Technical depth + why finance / why JPMC |
| HR | 20-30 min | Motivation, location, background verification |
Real interview experiences
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
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.
Takeaways
- What decided it: At Code for Good, collaboration and the team demo score more than individual coding heroics - this account cleared coding and still missed the offer
- Common fail: Underestimating HireVue timing, or optimizing only for personal code output in the hackathon
- How to practise: Timed HireVue answers (2 minutes); rehearse teamwork and demo stories, not only solo DSA
Experience 2: SDE, on-campus (2023)
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.
Takeaways
- What decided it: HashMap/heap fundamentals plus a resume-tied IoT design question cleared the day verbally - headcount still blocked the final offer
- Common fail: Treating the OA as the hard part, or having no real “why finance / why JPMC” answer in a technical round
- How to practise: Explain HashMap collision handling aloud; prepare a project-domain design sketch; write a specific why-JPMC answer
Experience 3: Campus 2022–23 - OA → HireVue → Code for Good
Reported flow: HackerRank coding (March) → HireVue behavioural (March) → CFG hackathon (~40–45 days later for shortlists).
- Coding round: Two questions, 60 minutes, easy-to-medium; strong DSA fundamentals sufficient to clear.
- HireVue: ~30 minutes, two behavioural questions recorded on screen; up to two attempts per answer plus a practice question. Reported prompts: team conflict on a project and five-year career plan.
- Code for Good: 24-hour hackathon on Zoom/Slack; ~35 students shortlisted after HireVue in one account; optional 1:1 check-in (~30 min) on progress and implementation logic during the event.
- Reported outcome: Selected (author of the GFG write-up). HireVue tips from the same post: dress formally, quiet room, speak naturally - treat it like conversation, not monologue.
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 · GeeksforGeeks - JP Morgan Chase on-campus 2022-23 · GeeksforGeeks - JPMC full-time SWE HireVue coding
Takeaways
- What decided it: Clearing HireVue behavioural prompts and showing teamwork during the 24-hour CFG hackathon, not only finishing the OA
- Common fail: Monotone HireVue answers or disappearing during hackathon collaboration check-ins
- How to practise: Record two-attempt HireVue drills; practise explaining implementation choices to a teammate in under two minutes
Questions that come up often
Coding / technical
- Valid parentheses / expression checks. Usually expects stack
- Find duplicates in a stream. Usually expects hashing
- SQL + coding hybrid (nth highest / joins). Usually expects window functions / careful queries
- Discussion on trade booking and low-latency, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
- Why banking technology?
- Comfort with background verification timelines
- Location preference (Bangalore / Mumbai / Hyderabad common)
- Strengths and weaknesses
- HireVue: conflict with a teammate; five-year plan; successful team project
- CFG HireVue: presentation success; adapting communication for a struggling teammate
Pre-interview checklist (JP Morgan)
- Confirm whether your path includes standalone HireVue or merged CodeVue coding + video
- Two easy-medium timed coding sits (arrays, hashing, stacks, basic DP)
- One SQL window-function answer spoken aloud (nth salary, running total)
- Three STAR stories recorded on phone under 2:30 each
- Plain-language trade booking paragraph (30 seconds)
- Location and background-check timeline answer ready
- Resume project you can defend for 15+ minutes including design trade-offs
Practical tips for JP Morgan
- 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.
HR interview
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.
Sample answers for high-frequency questions
Use these as frames, not scripts - interviewers probe follow-ups.
Q. Explain trade booking in plain language - what actually happens end to end?
A. Booking is the step where an agreed trade is recorded in the bank’s systems as an official position. An order is placed and routed to a venue; when it executes, the fill comes back with the economics - instrument, quantity, price, counterparty, trade date and settlement date. Booking writes that into the trade capture system, which then feeds three downstream consumers: risk, which needs the new position to recompute exposure; settlement, which arranges the exchange of cash and securities on the value date; and the general ledger for accounting. The parts that break at scale are duplicate bookings when a confirmation is replayed, which is why every trade carries a unique ID and the booking API must be idempotent, and amendments or cancellations after the fact, which is why bookings are usually stored as an append-only event history rather than an updatable row. Static data errors - a wrong counterparty or instrument reference - are the other common source of breaks.
Q. What makes a system low-latency, and where are the usual bottlenecks?
A. Low latency is about the tail, not the average - the number that matters is the 99th percentile, because in trading a slow one-in-a-hundred response is a real loss. The usual bottlenecks are garbage collection pauses in managed runtimes, which is why latency-sensitive Java code is written to allocate almost nothing in the hot path and to reuse object pools and primitive arrays; network hops and serialisation, addressed by co-locating services and using compact binary formats instead of JSON; disk and database access, moved off the critical path by keeping state in memory and writing to a log asynchronously; and lock contention, avoided with lock-free ring buffers and single-writer designs. Cache locality matters concretely too - an array of primitives traverses far faster than a linked structure of objects scattered across the heap. The framing interviewers reward is measuring first and naming the specific percentile you improved.
Q. Write a SQL query for a running total of trade notional per day.
A. Use a window function with an ordered frame: SELECT trade_date, notional, SUM(notional) OVER (ORDER BY trade_date ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) AS running_total FROM trades ORDER BY trade_date; If you need the running total restarted per book or desk, add PARTITION BY book_id before the ORDER BY. The reason a window function is right here rather than GROUP BY is that GROUP BY collapses the detail rows, whereas the requirement is to keep every trade row and attach a cumulative figure to it. The alternative self-join, joining trades to all trades with an earlier or equal date and aggregating, is O(n squared) and is exactly the answer interviewers are hoping you improve on.
Q. What is the difference between HashMap, Hashtable, and ConcurrentHashMap in Java?
A. HashMap is unsynchronised, allows one null key and null values, and is the right default for single-threaded or externally synchronised use; used concurrently it can corrupt its internal structure or lose updates. Hashtable is the legacy synchronised version, which locks the entire map on every operation, so throughput collapses under contention, and it forbids nulls. ConcurrentHashMap is the modern concurrent option: reads proceed without locking, and writes lock only the individual bin rather than the whole table, so many threads write in parallel. It also forbids nulls, deliberately, because a null return would be ambiguous between absent and present-with-null in a concurrent setting. It adds atomic compound operations such as putIfAbsent, computeIfAbsent, and merge, which are what you need to avoid the check-then-act race that a plain get followed by put would create.
Q. How would you evaluate a postfix expression?
A. Scan the tokens left to right with a single stack. Push every operand. On an operator, pop the top two values, apply the operator with the second-popped value as the left operand - order matters for subtraction and division - and push the result back. When the scan finishes, the single value left on the stack is the answer. This is O(n) time and O(n) space. Postfix, or reverse Polish notation, needs no parentheses and no precedence rules, which is precisely why compilers and calculators convert infix to postfix first, using the shunting-yard algorithm. The edge cases to raise unprompted are division by zero and a malformed expression, where either the stack underflows on an operator or more than one value remains at the end.
Tips from successful candidates
Interview tips
- Narrate trade-offs; expect “why” after every answer
- Only list projects you can defend under follow-ups
- Prepare 3-4 STAR stories for behavioural prompts
HR tips
- Know why JP Morgan, not just why the industry
- Be clear on location / notice period / higher studies
- Practise answers on the dedicated HR page
Sources
These links are research inputs we used to map round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for JP Morgan.
Cross-check the current drive mail or careers posting for timings and pattern changes.
For the company overview and FAQs, see the JP Morgan hub. For behavioural STAR prompts, use the JP Morgan HR page. For OA drills, use JP Morgan on placementpapers.app.
Related resources
Similar companies
Goldman Sachs · Morgan Stanley · Bank of America · Deutsche Bank · Wells Fargo · HSBC