JPMC Code For Good Interview Experience 2024
Interview Experience
Hey everyone,I am excited to share my journey with JPMC Code for Good 2024 so far. This experience has been thrilling and enriching tested my skills, and pushed my limits ...
Full Details
Hey everyone, I am excited to share my journey with JPMC Code for Good 2024 so far. This experience has been thrilling and enriching tested my skills, and pushed my limits and I can’t wait to see what the final round holds. Here’s a detailed look at my journey through the rounds up to this point.
Round 1 The Coding Test After the Resume Shortlisting Process, the first step in this journey was the coding test, conducted on HackerRank Platform. We were given two questions to solve within 60 minutes. These questions tested our understanding of basic data structures and algorithms, challenging us to apply our knowledge practically. Platform: HackerRank Duration: 60 minutes Question 1: Pairs Question 2: Swap Parity The questions were of medium difficulty, and having a solid grasp of DSA concepts was crucial. After an intense hour of coding, I submitted my solutions, feeling both nervous and excited.
Round 2 The HireVue Interview Clearing the coding test led me to the next stage: the HireVue interview. The selected candidates get a mail regarding HireVue Interview on their registered mail address. In this round, usually, two behavioural questions are asked. The questions flash on your screen and you are supposed to record yourself. You get a maximum of 2 attempts for each question. Make sure you are fluent and confident in this round. Use the STAR Approach to answer the questions carefully. Normally it takes 15-20 minutes to complete. This online video interview was unique. I had to answer two behavioural questions: Q.1. Tell us about the situation in which you felt that you have communicated wrong, and you need to correct it. Q.2. Tell me about a time when you had to explain something you knew well to someone who had difficulty understanding the subject. Describe the situation, the steps you took and the outcome. Preparing for this round involved structuring my responses using the STAR (Situation, Task, Action, Result) method. The HireVue platform allowed me to record my answers twice, which helped in present my thoughts clearly and confidently. This round required a blend of self-reflection and clear communication, and I felt a great sense of accomplishment upon completing it.
Round 3 The Awaited Code for Good Hackathon! The most exciting part of this journey is yet to come: the Code for Good Hackathon , scheduled for June 15-16, 2024 . This 24-hour hackathon is the climax of the selection process and promises to be an intense, collaborative, and rewarding experience. Preparation and Anticipation: We have been informed about the format and logistics of the hackathon. Our team, consisting of 6-7 students from different colleges, will be formed a day before the event. This gives us a short window to get acquainted with each other, discuss our strengths, and decide on our tech stack. Effective Communication will be a key to coordinating our efforts. The Hackathon: On June 15, we will receive problem statements from various Non-Governmental Organizations (NGOs). Our task will be to select a problem, brainstorm solutions, and develop a website or app to address it. We will have two mentors to guide us throughout the process, ensuring we stay on track and overcome any technical challenges. Subject Matter Experts (SMEs) will also be available to assist us whenever we need help. Looking Forward: I am eagerly looking forward to this final round. It’s an opportunity to apply my skills in a real-world scenario, collaborate with talented peers, and make a meaningful impact through technology. The Hackathon will be a test of endurance, creativity, and teamwork. I am prepared to give it my all and learn as much as I can from this incredible experience. Reflections So Far: Participating in JPMC Code for Good 2024 has been a transformative experience. It has challenged me to sharpen my coding skills, reflect on my career goals, and prepare for intense collaboration. The upcoming hackathon is not just a competition but a chance to grow and contribute to meaningful solutions. I am grateful for the journey so far and am excited about what lies ahead. Stay tuned for updates after the hackathon, where I’ll share more about the experience and the outcomes. Thank you for reading about my journey. Best of luck to everyone participating, and let’s make the most of this fantastic opportunity!
About This Question
This is a candidate experience report from a jpmorgan interview for a swe role during the oa round reported in 2024.
It covers the following topics: Sql, Oop, Stack, Stack Queue .
Difficulty rating: Easy
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.