Academic requirements
Marks: ~7.0 CGPA / 70% across 10th, 12th, graduation
Degree: Full-time B.Tech / B.E. / M.Tech
Year: Final year or recent grads within ~1 year
Backlogs: None active through OA and interviews
JP Morgan Placement Papers 2026
JPMorgan Chase is one of the world’s largest financial services firms, spanning consumer banking, investment banking, and asset management. In India campus tech hiring, JP Morgan, J.P. Morgan, and JPMorgan Chase refer to the same employer brand. Technology teams in Mumbai, Bengaluru, and related hubs build trading, risk, and banking platforms.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
JP Morgan eligibility & CGPA (2026)
Who this hub is for
- For: Students targeting Technology Analyst / software roles in JP Morgan India tech (trading, risk, banking platforms) - mainly Mumbai and Bangalore.
- Not the same track: Pure investment-banking analyst case loops with DCF-heavy interview days (those appear mixed into some year pages - tech candidates should not over-prep IB valuation at the cost of DSA).
- Career switchers: IT/ECE profiles with strong projects clear when OA is clean - see Experience 2 below.
Good fit: You like timed DSA, you can talk about latency and failure modes without buzzword soup, and you will complete HireVue within a few days of the link. Internships help; they do not replace passing OA test cases.
Harder path: You only grind LeetCode and ignore HireVue; you recite “blockchain” without a bottleneck story; you refuse Mumbai/Bangalore relocation. JP Morgan’s late-stage drops are often behavioral clarity and domain storytelling - not only a missing DP solution.
On-campus vs off-campus vs code for good
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list | Coding bar, interview depth |
| Careers portal / referral | Resume volume; year-round | Still expect OA + tech loop |
| Code for Good | Hackathon weekend after OA/HireVue | DSA OA still first |
Off-campus does not mean easier coding. It often means more applicants fighting the same HackerRank filter. If your CGPA sits near 7.0, spend energy on mocks - not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 7.0 enough?”
Yes for eligibility on many drives. No as a substitute for OA. JP Morgan’s quiet filter is passing test cases + clear narration before anyone cares about your CGPA story. Put one honest project on the resume with metrics and be ready to connect it to trade booking, risk, or reliability in plain language.
Naming note: JP Morgan, J.P. Morgan, and JPMorgan Chase refer to the same employer brand in this hub.
Gap years and backlogs: active backlogs at application/OA/interview are a common hard stop. Cleared historical backlogs are often fine. Education gaps are frequently acceptable when you can explain academic or skill-development time without sounding defensive. Full-time degrees only for the TA campus route described here.
Branch myth: ECE/EE and Maths & Computing students clear JP Morgan when DSA is real. Branch does not replace OA correctness; it also does not auto-reject you if coding and narration are strong.
Certifications: cloud/quant certs are optional extras after fundamentals. For campus SWE/TA, DSA + OA mocks + one strong project beat certificate stacks. See certifications.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0 / 70% at 10th, 12th, and graduation | 8.0+ / 80%+ helps shortlists; CGPA is not the sole filter |
| Degree | Full-time B.Tech / B.E. / M.Tech | Distance/correspondence rarely accepted for TA campus roles |
| Branch | CS, IT, ECE, EE, Maths & Computing, related | Strong DSA helps adjacent branches on some drives |
| Year | Final year or recent grad (~1 year) | 0-1 year experience for entry TA |
| Backlogs | No active at application / OA / interview | Cleared historical often OK |
| Gaps | Often acceptable if justified | Academic/skill story ready |
| Skills | Strong coding in C++/Java/Python + OA performance | Invite list wins |
Selection chances by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| ~7.0-7.4 | Eligible | You need strong OA + clear explanations |
| 7.5-8.4 | Solid | Matches many selected stories |
| 8.5+ | Stronger shortlist odds | Still loses if HireVue / design talk collapses |
Branch & programming
Branches: CS, IT, ECE, EE, Maths & Computing, related
Languages: C, C++, Java, Python (C++/Java preferred by many)
Experience: Freshers and ~0-1 year for entry TA
JP Morgan CGPA criteria
Minimum CGPA required (candidate-reported): ~7.0 CGPA / 70% across 10th, 12th, and graduation. That is the usual Technology Analyst floor students cite - not a promise that 7.0 alone gets you past HackerRank. Always verify the drive notice or careers posting.
JP Morgan does not publish one universal India cutoff for every campus, Code for Good, and off-campus TA drive. Numbers below synthesize campus notices, candidate write-ups, and careers chatter as of August 2026. Your placement email wins.
What that means day to day: a 8.2 CGPA who freezes on a 60-minute two-problem OA usually loses to a 7.1 who passes all test cases and can explain a trade-booking story in plain words. JP Morgan’s “banking tech” story matches how drives feel - product-like DSA bar with domain vocabulary, not a store-operations quiz.
JP Morgan previous year paper PDFs
Download 2026 JP Morgan placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What JP Morgan previous year papers actually train
JP Morgan papers are simulators for OA stamina and interview themes, not leaked live exams. Themes repeat more than exact clones. If you can finish a 2024 pack under time, a 2026 OA still feels familiar even when the second coding prompt is new.
| Round (typical) | What to practice |
|---|---|
| Online Assessment | 2-3 DSA + math aptitude |
| HireVue / behavioral | Short video answers, Why JP Morgan |
| Technicals | DSA + trade booking / low-latency / risk |
| Managerial / HR | Ownership, relocation, BG timelines |
Themes that keep repeating (2024-2026)
- 2024: OA with 2-3 coding + math aptitude; coding themes like Two Sum, Linked List Cycle, Longest Common Prefix; aptitude on probability/statistics plus classic quant/LR/verbal banks; HireVue after OA on many paths; interview themes include leadership/resilience and (on finance-leaning pages) market awareness.
- 2025: Same OA shell with stricter emphasis on optimal solutions; coding themes like Palindrome, Two Sum, Rotate Array; more HireVue; more financial-awareness chatter on some loops.
- 2026: Continuity + polish; stricter timed execution; cleaner communication; banking-tech vocabulary (reliability/controls) helps; OA remains the volume filter.
Duration shape conflicts to preserve: hub tables often say ~90 min combined; year pages sometimes split 60 coding + 30 math; LinkedIn/Code for Good stories often cite 60 min / 2 DSA. Trust your invite.
OA clear-rate chatter: hub aggregates ~25-35%; year pages sometimes cite ~15-20%. Treat both as “steep first filter.”
How to use a paper: time the OA exactly as your invite says; mark every coding miss as speed vs concept; rewrite solutions that fail hidden tests; then spend 15 minutes listing which pattern you missed. Three reviewed papers beat ten skimmed PDFs.
Sample mental model for OA triage
- Skim both (or all three) coding prompts in the first 3-4 minutes
- Lock the “sure” problem first and pass all samples
- Harden edge cases before opening the harder problem
- Keep math aptitude from stealing the last 20 minutes if coding is unfinished
- Never submit a clever partial when a brute-force AC was available
Related coding problems to practice
| Theme that shows up | What to drill next |
|---|---|
| Arrays / hashing | Two Sum, duplicates in stream, frequency maps |
| Strings / stacks | Valid parentheses, palindrome checks |
| Trees / graphs | Traversals, BFS/DFS templates |
| DP / intervals | Classic medium DPs; rotate/merge patterns |
| SQL-flavored logic | nth highest, joins, window-function intuition |
JP Morgan placement process, round by round
JP Morgan runs campus, off-campus (careers.jpmorgan.com), referral, and Code for Good paths. Technical bar is the same idea: pass OA, then defend DSA and banking-tech judgment in interviews.
How to apply
Campus recruitment
Placement cell lists → PPT → batch OA → interviews (virtual or onsite). Season-aligned with college calendars.
Off-campus / careers
Apply via careers.jpmorgan.com year-round. Resume screen → OA invite → same interview ladder. Referrals help volume, not the coding bar.
Code for good
Hackathon hiring path after DSA OA and often HireVue. Real FTE signal when you ship under weekend pressure.
Round-by-round walkthrough
-
Application / eligibility screen (1-2 weeks)
Campus lists or portal resume screen. Rough filter on CGPA/branch when printed. Put projects with metrics and Java/C++/Python signal on top.
-
Online Assessment - often ~90 minutes (HackerRank or Codility)
Section Questions Time notes Difficulty Focus Coding 2-3 Full window or ~60 min in some splits Medium-Hard Arrays, strings, trees, graphs, DP Mathematical Aptitude 5-10 (or 5-7) Included or ~30 min split Medium Probability, statistics, quant Languages: C, C++, Java, Python. Usually no negative marking. All test cases must pass for full credit. Candidate-reported clear rates sit around ~25-35% (hub) or ~15-20% (year pages).
Time boxing: skim all coding prompts first; bank one full AC; then attack the harder problem; do not let aptitude wipe coding.
Platform tip: read the invite for duration. A LinkedIn 2025 SDE write-up described a 60-min HackerRank with two DSA problems - shorter than the hub’s 90-minute combined table.
Why OA feels product-hard: JP Morgan wants engineers who ship correct code under time, then talk about reliability. Candidates who only ever practiced untimed Easy problems feel the hidden-test wall hardest. Treat timed mocks as non-negotiable for two weeks before any drive.
Build order under the clock: (1) skim all prompts, (2) implement the sure AC, (3) harden edge cases and complexity if time remains, (4) open the harder problem, (5) leave a brute force that passes samples rather than an empty clever idea. Name variables clearly; later interviews may reopen your approach.
-
HireVue (on many paths) - video screen
Especially common after OA on Code for Good and some campus loops. CFG 2024: about two ~3-minute HR videos, 2-3 attempts, complete within 2-3 days. Biggest reported prep mistake: ignoring HireVue after coding-only prep.
-
Technical Interview 1 - ~45 minutes (sometimes 45-60)
DSA/live coding; talk approach before typing; interviewer may evolve constraints (“infinite input stream,” “billions of records”). Roughly ~50-60% advance in hub funnel notes.
-
Technical Interview 2 - ~45 minutes
System design / projects / domain: trade booking, low-latency, risk systems, APIs, failure modes at fresher depth. Roughly ~60-70% advance.
Expect “how would you book a trade end to end?”, “what breaks if the matching engine slows?”, and “walk me through your project’s hardest bug.” If you only recite microservices buzzwords without a bottleneck, that is a red flag. Bring the same calm OA triage into spoken form: constraints first, then data, then failure modes.
-
Managerial - ~45 minutes
Behavioral + technical depth; ownership; Why banking technology? Roughly ~70-80% advance. STAR stories with metrics beat vague “I am a team player” lines. Expect follow-ups like “what would you do differently?”
-
HR - ~30 minutes (sometimes 20-30; sometimes merged)
Offer discussion, relocation (Mumbai/Bangalore), background verification timelines. Around ~80-90% of late-stage survivors get offers when logistics are clean.
Prepare a specific Why JP Morgan (markets tech, scale, India hubs - pick what is true for you). Vague “I like finance” answers underperform if you cannot connect to engineering work. If you need time before relocating, say so clearly rather than bluffing.
Code for good 2024 campus colour
- Campus registration opened 28 March 2024
- 60-minute two-question DSA OA early April
- HireVue 19 April - two ~3-minute videos
- Hackathon shortlist 30 May; event 15-16 June used React/FastAPI
- FTE results 27 August 2024
(GeeksforGeeks write-up.) Budget months of patience after the hackathon weekend.
Alternate process shapes
Year pages describe HireVue → phone screen → longer onsite/virtual loops (4-6 rounds) for some finance-leaning paths. Certifications tables show OA 60-120 → technical/case 30-60 → HR/values 20-40. Interview-experience FAQs sometimes count 4 stages (OA + 2 tech + HR). Superday is not mentioned in current JP Morgan hub/nested docs - do not invent it.
Timeline from application to offer
| Phase | Duration | What happens |
|---|---|---|
| Application | 1-2 weeks | Screen / shortlist |
| OA | ~1 week phase | Coding + aptitude |
| Tech interviews | 1-2 weeks | DSA + design/domain |
| Managerial | 3-5 days | Behavioral depth |
| HR / result | 2-3 days / 1-2 days | Offer letter |
Total: usually 3-4 weeks end to end (faster for strong referrals). Code for Good stretches across months from OA to FTE mail.
Campus path (typical): college registers → PPT → OA on campus schedule → HireVue if listed → tech + managerial + HR → offer. Advantages: familiar process support and batch energy.
Off-campus path (typical): careers.jpmorgan.com application → resume screen → OA invite → same interview ladder. Advantages: year-round attempts; denser applicant mix. Your OA still decides whether humans see you.
Phone screen colour (year pages): some 2024/2025 finance-leaning paths list a technical phone screen (45-60 min) before longer onsite/virtual loops. If your invite includes it, treat it as a real DSA filter, not a soft chat.
What each early round actually asks
- OA coding: medium DSA with full test-case pressure; correctness first, then complexity.
- OA math: probability/statistics and quant speed - do not ignore if present.
- Tech 1: talk before code; adapt when constraints change.
- Tech 2: trade booking / low-latency / risk in plain language.
- Managerial/HR: Why JP Morgan tech?, relocation, BG verification comfort.
If you only remember three numbers: ~90-minute OA filter, ~5-stage TA loop, fresher TA band ₹25-35 LPA (candidate-reported).
Preparation resources for JP Morgan
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How to train for JPMorgan Chase & Co. this season
If a JPMorgan Chase & Co. invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for JPMorgan Chase & Co. sits around ₹25-35 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): JP Morgan eligibility for freshers 2026 is candidate-reported, not one official published cutoff. Common Technology Analyst baseline: about 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT, ECE, or related fields; final-year students and recent graduates within about 1 year; no active backlogs; C++/Java/Python preferred. Always verify careers.jpmorgan.com or your drive notice.
What you are training for: Technology Analyst fresher loops commonly run: Application (campus / careers portal / referral) → Online Assessment (~90 min, 2-3 coding + math aptitude on HackerRank or Codility) → Technical Interview 1 (~45 min) → Technical Interview 2 (~45 min) → Managerial (~45 min) → HR (~30 min). Some paths add HireVue after OA or use Code for Good. Total often 3-4 weeks.
Short version of the prep split: Split time roughly: 40% DSA, 25% system design / banking-tech scenarios, 20% timed coding mocks (200+ problems), 10% quantitative aptitude, 5% behavioral/HireVue. Do not skip behavioral screens after coding-only prep. Languages: C, C++, Java, Python.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the JPMorgan Chase & Co. previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most JPMorgan Chase & Co. drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at JPMorgan Chase & Co. usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why JPMorgan Chase & Co.?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a JPMorgan Chase & Co.-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the JPMorgan Chase & Co. story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 JPMorgan Chase & Co. PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed JPMorgan Chase & Co. papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many JPMorgan Chase & Co. papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in JPMorgan Chase & Co.-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed JPMorgan Chase & Co. paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why JPMorgan Chase & Co. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For JPMorgan Chase & Co., interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three JPMorgan Chase & Co. mistakes, you are collecting content, not preparing.
Extra drill block (2)
Sit one more mixed JPMorgan Chase & Co. set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Extra drill block (1)
Sit one more mixed JPMorgan Chase & Co. set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
What JP Morgan pays freshers
Figures below are candidate-reported as of August 2026. Treat them as ranges - offer letters win.
Technology analyst / India software bands
| Level | Experience | Base (approx.) | Total package |
|---|---|---|---|
| Technology Analyst | Fresher | ₹18-22 LPA | ₹25-35 LPA |
| Associate | 2-4 years | ₹28-35 LPA | ₹40-55 LPA |
| Vice President | 5-8 years | ₹50-80 LPA | ₹70-110 LPA |
| Executive Director | 8+ years | ₹1 Cr+ | ₹1.3 Cr+ |
Other bands students mention
| Role / source | Band |
|---|---|
| Certifications Analyst FAQ | ₹16-26 LPA (preserve as alternate reported band) |
| Exceptional top-college chatter | Toward ₹35-45 LPA |
| Quant Analyst | ₹30-50 LPA |
| Risk Analyst | ₹25-40 LPA |
| DevOps | ₹35-60 LPA |
Locations students cite most: Mumbai, Bangalore. Bonuses often discussed around 15-30% of base.
Peer comparison (FAQ chatter): Goldman Sachs TA ~₹28-38 LPA; Morgan Stanley TA ~₹25-35 LPA.
Benefits students care about
Health coverage, retirement/ESPP-style benefits depending on entity, performance bonuses, L&D, hybrid norms, and relocation support when moving cities - ask HR, do not assume.
How to read the TA band: ₹25-35 LPA total with base often ₹18-22 LPA is the fresher Technology Analyst range students most often cite on hub and interview-experience pages. Certifications pages quoting ₹16-26 LPA are a wider/alternate band - preserve both as candidate-reported, not a fight to “correct” the internet. Exact splits vary by year, college tier, and letter.
Growth students ask about: Technology Analyst → Associate → VP → ED is the common ladder people describe. Internal learning surfaces and cert sponsorship after joining appear in career pages - useful later, not a substitute for OA prep now.
How to talk CTC in HR without sounding lost
Know the ₹25-35 LPA fresher TA context (and that some guides cite ₹16-26), ask how the package splits (base vs bonus), and clarify joining vs finals. One calm clarifying question beats aggressive negotiation with no market anchor. Do not negotiate from vibes without a market anchor, and do not treat blog midpoints as guarantees.
Recent JP Morgan placement trends
- Digital / HackerRank-Codility OAs remain the volume filter alongside campus drives.
- HireVue stays common - complete it fast when the link arrives.
- Code for Good remains a real FTE path when you can ship under weekend pressure.
- Domain vocabulary (trade booking, low-latency, risk, controls) shows up more than in pure services aptitude mills.
- India hub expansion chatter continues for Mumbai/Bangalore tech centers.
- AI/ML, cloud (AWS/Azure), microservices appear on hiring-trend cards - still secondary to DSA for fresher OA.
- Treat ₹25-35 LPA as a reported fresher TA band, not a promise for every role or college.
Net for 2026: do not wait for a “new pattern” rumor. Double down on timed OA correctness, one plain-language domain story, and HireVue discipline.
Also expect virtual interviews to remain common and India tech hiring to stay hub-centric (Mumbai/Bangalore). If your college finally gets a JP Morgan PPT, treat it as a real shot - the OA bar does not drop because the venue is familiar. Referrals can shorten resume wait times; they do not skip HackerRank.
Online-assessment caveat: nested OA pages note limited verified public reports. Use this hub’s tables as a map, then trust the invite for exact duration, section list, and language dropdown.
Prep calendars students actually use range from 6-8 weeks (prep-guide FAQ) to 2-3 months intensive or 4-6 months extended when DSA is weak. Certifications pages sometimes say 2-6 months. Pick the shortest plan you can execute with timed mocks - unread PDFs do not count as prep. When the OA link arrives, block a half-day: coding plus aptitude often takes longer than students expect once you include setup and buffer.
Common questions about JP Morgan hiring
Process & papers
What is the JP Morgan placement process?
Typical Technology Analyst path: Application → OA (~90 min coding + math aptitude) → Technical ×2 → Managerial → HR. Some paths insert HireVue after OA or use Code for Good. Campus loops often finish in about 3-4 weeks; CFG can stretch months.
How many rounds are there in JP Morgan interview?
Most fresher TA loops report about five stages (OA + two technicals + managerial + HR). Some drives merge HR or add HireVue/phone screens. Count the mailer.
Can I download JP Morgan placement papers PDF for free?
Yes. Free JP Morgan placement papers PDF and 2024-2026 style practice are on this site - trainers with solutions, not leaked live papers. Start with the 2026 PDF or the archive.
What does the JP Morgan Online Assessment look like?
Candidate-reported OA is often ~90 minutes with 2-3 coding problems and math aptitude on HackerRank or Codility. Some invites are 60 minutes / 2 DSA. Languages: C, C++, Java, Python. Verify yours.
Eligibility & offer
What is JP Morgan eligibility criteria for freshers 2026?
Candidate-reported: ~7.0 CGPA / 70% across 10th, 12th, graduation; B.Tech/B.E./M.Tech in CS/IT/ECE/related; final year or recent grads within ~1 year; no active backlogs. Not one official published cutoff - verify careers.jpmorgan.com or your drive notice.
What is JP Morgan salary for freshers?
Technology Analyst fresher CTC commonly cited around ₹25-35 LPA total (base often ₹18-22 LPA) as of August 2026. Some certifications pages cite ₹16-26 LPA. Offer letter wins.
Do I have to relocate to Mumbai or Bangalore?
Those are the main India tech hubs candidates report. HR usually checks relocation willingness and joining logistics. Be honest about constraints early.
Prep & JP Morgan-specific
How to prepare for JP Morgan placement?
Split ~40% DSA, 25% system design/domain, 20% timed coding, 10% quant, 5%+ behavioral/HireVue. Details: preparation guide.
Which programming languages are allowed?
C, C++, Java, Python. C++/Java are common among selected candidates. Confirm the invite. Do not switch languages the week of the drive.
What is Code for Good?
JP Morgan’s hackathon hiring path. A 2024 campus story ran DSA OA → HireVue → React/FastAPI hackathon → FTE months later. Still expect OA-quality DSA first.
What is HireVue and why do people fail it?
A video behavioral/technical screen after OA on many paths. CFG write-ups: ~3-minute videos, a few attempts, complete within 2-3 days. People fail it by treating coding-only prep as enough and delaying the video link.
What banking-tech topics should I revise for interviews?
Trade booking, low-latency, risk systems, payment flows, reliability/controls at fresher depth: APIs, data choices, bottlenecks, failure modes in plain language. Practice sketches beat memorised IB valuation formulas for TA roles.
JP Morgan vs Goldman Sachs vs Morgan Stanley - which fits better?
All three are competitive finance-tech bars. Candidate-reported fresher TA bands often sit in the mid-high ₹20L+ ranges (JP Morgan ~₹25-35, GS ~₹28-38, MS ~₹25-35 in FAQ chatter). Prep DSA for all; customise domain stories per firm.
Is 7.0 CGPA good enough for JP Morgan?
It meets the commonly reported minimum. Weight sits on OA, problem-solving, and interviews. Exceptional coding can offset borderline CGPA; weak OA cannot be saved by 9.0.
Any pro tip that actually changes outcomes?
Bank solvable OA problems first, keep an error log, rehearse one trade-booking or low-latency explanation out loud, and complete HireVue within days of the link. Correctness under time beats a half-finished clever solution.
Where can I read real interview experiences?
Start with JP Morgan interview experience on this site, then cross-check recent LinkedIn/GfG write-ups for your path (campus vs Code for Good). Patterns shift by year - use them as maps, not scripts.
How long does JP Morgan hiring take end to end?
Typical TA loops land in about 3-4 weeks from application to offer once OA starts. Referrals can move faster. Code for Good often stretches from spring OA to late-summer FTE results - budget patience.
Do I need finance knowledge for Technology Analyst roles?
You need engineering judgment about trading/risk/payment systems at fresher depth, not memorised DCF models. Fake IB jargon without a bottleneck story hurts more than honest “here’s the data flow.” Finance-track interview pages exist - do not let them derail DSA prep for tech roles.
What certifications help before joining?
For campus TA, DSA + OA mocks + one strong project beat certificate stacks. Cloud or quant certs are optional extras after fundamentals. See certifications.
JP Morgan - recent candidate experiences
2025 SDE Linkedin write-up
Funnel: OA HackerRank 60 min, two DSA problems. Then a 60-min pair-programming technical where the interviewer evolved constraints (“infinite input stream,” “billions of records”), plus system design and behavioral. Tip candidates repeated: explain trade-offs aloud; panels watch adaptation as much as the first AC.
Code for good 2024 → fte
Registration 28 March 2024 → 60-min two-question DSA OA → HireVue 19 April → hackathon shortlist 30 May → event 15-16 June (React/FastAPI) → FTE results 27 August 2024. Complete HireVue within 2-3 days of the link.
Experience 1 - TA/HR 2025
Profile: B.Tech CSE, ~8.0 CGPA, tier-2, one internship, steady DSA. OA: timed HackerRank-style; shortlist in a few days. Coding: valid parentheses (stack); find duplicates in stream (hashing). Domain: trade booking, low-latency; project deep-dive. HR/managerial: Why banking technology?; background verification timelines. What helped: talk approach before coding; connect project to trade booking.
Experience 2 - TA/HR 2024-2025
Profile: B.Tech IT/ECE, ~7.2 CGPA, strong projects, average contest rating. Tighter timed screening; optimized pass needed. Later: risk systems (APIs, data choices, failure modes). Warm-up: SQL + coding hybrid (nth highest / joins), window functions. Takeaway: clear DSA + coherent trade-booking story beats high CGPA with weak explanation.
What hurt other candidates in the same cycles: coding before clarifying constraints; treating HR as a formality; jargon without a bottleneck story; optimising one hard OA item while leaving an easy problem incomplete; delaying HireVue until the link expires in your head.
Common question families candidates keep listing:
- Coding: valid parentheses; stream duplicates; SQL nth highest/joins; arrays/hashing mediums
- Domain: trade booking, low-latency, risk systems, project deep-dive
- HR: Why banking tech?, BG verification comfort, location, strengths/weaknesses
Profile patterns that got selected: roughly 7.2-8.0 CGPA, tier-2 and tier-1 mix, one internship or strong project, steady DSA rather than last-week panic.
What to steal: pass tests first; narrate trade-offs; finish HireVue fast; keep one domain story ready in plain words. Do not treat one LinkedIn/GfG post as a fixed paper template - use it as a vibe check, then return to timed mocks. More fresher narratives: interview experience.
Emotional budget: OA week is a timed correctness problem; Code for Good is a multi-month patience problem after the hackathon weekend. Do not confuse them. If you only have six weeks, lock OA mocks and HireVue first, then decide whether a hackathon path fits your calendar.
One last OA reminder: limited public write-ups mean your invite is the source of truth for clocks and sections. When blogs disagree on 60 vs 90 minutes, prepare for both triage styles - skim-first coding with a protected AC - so neither duration surprises you.
If you’re also targeting…
Goldman Sachs · Morgan Stanley · Bank of America · Deutsche Bank · Wells Fargo · HSBC