JP Morgan Interview Experience Through Code For Good(CFG)
Question Details
For Full-Time 2021Round 1(Online Coding Test):The Online Test was conducted on Hackerrank, 2 questions were askedI don't remember the exact questions,The first question wa...
Full Details
For Full-Time 2021 Round 1(Online Coding Test): The Online Test was conducted on Hackerrank, 2 questions were asked I don't remember the exact questions, The first question was, 2 strings are given as input and we have to check if those strings are almost equivalent or not and output as YES or NO. It was similar to this https://www.geeksforgeeks.org/dsa/check-whether-two-strings-are-equivalent-or-not-according-to-given-condition/ The second question was, give no of projects(n), an array of projects (proj), an array of costs to complete those projects (cost) as input and we have to calculate minimum Price, it can be achieved through Dictionary (in Python)/ Maps (in C++) (This is the Underlying Data structure). Round 2(Video Interview): This is the online video interview with the robot. It basically has 2 questions, a question pops up and 30 secs time is given to prepare and given a maximum of 2 mins to speak on that particular question. The first question was, Describe a situation where you felt you didn't have proper communication and had to solve it? The second question was, What are your specific goals for your future? Tips: Make sure you have proper lighting, you are clearly visible and no disturbance around!! From our college 55 were selected for Code for Good Hackathon Round 3(Code for Good Hackathon): This year hackathon was conducted virtually all over the country(India). All the selected candidates are divided into a team of 6 members by the company (Mix of different students of different colleges). On the day of the hackathon, there would be 6 problem statements given by different NGOs connected to the company. Around 10 mins are given to all the teams to order their interesting statements (It is like Fastest Finger First). Once the time is over they will let you know the problem statement you are allotted with. It's a 24-hour hackathon you are given time till next day morning and 2 mentors also allotted to each team and SME's also be available in case if you need any technical help. Make sure you commit your changes to the Github time to time so that you won't miss any code. After the hackathon time, we have to upload the project on to the portal. And reviews are done by the technical team and the respective NGO. After all, the reviews at the end of the event Winners would be announced!! Tips: Have some basics on Git and Github After around a month Results were announced and I was not Selected. But after 2 months I got a mail that I need to face an additional interview(This may not happen to everyone). Round 4(Face-Face Interview): The interviewer asked Self-Introduction. Next went on to my resume and asked about my favourite project and asked me to explain that. Based on that he further asked me questions related to my project. Tips: Make sure you have read and checked your resume carefully, Be Confident enough while giving your self-introduction. And Finally , I got SELECTED for JPMC Full Time Software Engineer- 2021 :) :)
About This Question
This is a reported interview question from a jpmorgan interview for a swe role during the oa round reported in 2025.
It covers the following topics: Arrays, Strings, Hash Table .
Topics
More JPMorgan Interview Questions
About JPMorgan Interview Reports
This question was reported by a candidate who interviewed at JPMorgan. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at JPMorgan are the higher-signal extractions to take from this report.
For broader preparation context, the JPMorgan interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in JPMorgan reports consistently are the ones worth investing in; one-off niche problems are not.
During Your JPMorgan Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in JPMorgan reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.