# JPMorgan Interview Experience 2026: Code for Good to Offer

> At 2:30 AM, halfway through a 24-hour hackathon, our team's app was broken, our NGO mentor had just changed a key requirement, and two of my teammates were argu

Canonical: https://devsunite.com/blog/jpmorgan-interview-experience-2026
Last updated: 2026-11-19

- Author: Aditi Chauhan
- Published: 2026-11-19
- Read time: 7 min
- Tags: Interview Experience, Hackathons, Interview Preparation, First Job

At 2:30 AM, halfway through a 24-hour hackathon, our team's app was broken, our NGO mentor had just changed a key requirement, and two of my teammates were arguing about whether to start over. I didn't know it then, but how I handled the next hour mattered more for my JPMorgan offer than any code I wrote that night.

Here's my complete JPMorgan interview experience for 2026: how I applied, the online assessment, the video interview, the Code for Good hackathon, the final interview, and what I learned about how JPMorgan actually evaluates freshers.

*This story is based on patterns commonly reported by recent JPMorgan fresher candidates. Rounds and formats can vary by program, location and hiring cycle.*

## What Is JPMorgan Code for Good?

Code for Good is JPMorgan Chase's hackathon where students work in teams to build technology solutions for non-profit organisations, guided by JPMorgan mentors. For many students, it's also a route into JPMorgan's hiring process, because mentors observe how participants code, communicate and work as a team.

## JPMorgan Interview Process 2026 at a Glance

| Stage | What happens |
| --- | --- |
| Application | Apply through JPMorgan's careers site for the software engineering program or Code for Good |
| Online assessment | Coding problems on an online platform |
| Video interview | Recorded answers to behavioural questions |
| Code for Good hackathon | Team project for a non-profit, observed by mentors |
| Final interview | Technical and behavioural questions |

## Step 1: The Online Assessment

The OA had two coding problems:

- **Problem 1 (easy-medium):** Given a list of transactions, find accounts whose total spending exceeds a limit within any 7-day window (sorting plus a sliding window).
- **Problem 2 (medium):** Find the minimum number of coins needed to make an amount, or return -1 if it's impossible (dynamic programming).

I solved both, but the first took longer than expected because of edge cases with dates. **Tip:** Read the input format carefully. Many hidden test cases target edge cases like empty lists and boundary values.

## Step 2: The Video Interview

This was a recorded interview with no live interviewer. A question appeared on screen, I got a short time to think, and then I recorded my answer. Questions included:

- Why do you want to work at JPMorgan?
- Tell us about a time you worked in a team to solve a problem.
- Describe a time you had to learn something new quickly.
- How do you handle feedback?

I prepared STAR stories in advance and practised recording myself. If you've never done a recorded interview, read [How to Crack AI Interviews in 2026](https://devsunite.com/blog/how-to-crack-ai-interviews-2026) before yours.

## Step 3: Code for Good (The Real Test)

My team had six students from different colleges, most of whom I'd never met. Our non-profit worked with volunteers for community education programmes, and they needed a way to match volunteers to sessions based on skills, location and availability.

**What we built:** A web app where the NGO could post sessions and volunteers could sign up. The system suggested the best-fit volunteers for each session. We used React for the frontend, Node.js and Express for the backend, and a hosted database. I owned the backend: the data model and the matching logic.

**The 2:30 AM moment:** Our NGO mentor told us that volunteers often cancelled last minute, and asked whether we could add a waitlist. Two teammates wanted to rebuild the data model from scratch. I suggested we keep the current design and add a small waitlist table, so we could still finish on time. We agreed on a 15-minute plan, split the work, and had it running by 5 AM.

**The presentation:** We demoed the app to the NGO and JPMorgan mentors, explaining the problem, our solution, what we'd cut and what we'd build next.

## What the Mentors Were Really Watching

Afterwards, a mentor shared some feedback that changed how I see hackathons. They weren't just judging the final app. They noticed:

- Who listened to the NGO's actual needs
- Who helped calm the team down under pressure
- Who made practical trade-offs instead of chasing perfection
- Who could explain their technical decisions clearly
- Who contributed real, working code

The 2:30 AM decision, keeping the design and adding a small waitlist instead of starting over, was something they specifically mentioned.

## Step 4: The Final Interview

A few weeks after the hackathon, I had a final interview with two engineers.

**Technical questions:**

- Walk us through the matching logic you built at Code for Good. How would you scale it to 1 lakh volunteers?
- Coding: find the first non-repeating character in a string, then a follow-up for a stream of characters.
- OOP: explain polymorphism with an example from your own code.
- SQL: write a query to find volunteers who signed up for more than three sessions in a month.

**Behavioural questions:**

- Tell us about the hardest moment in the hackathon.
- Describe a time you disagreed with a teammate.
- Why technology at a bank?

For "Why technology at a bank?", I talked about how much engineering goes into payments, fraud detection and systems that can't afford downtime, and how that reliability challenge excites me.

## Result and Timeline

- **Month 1:** Application, online assessment and video interview
- **Month 2:** Code for Good hackathon
- **A few weeks later:** Final interview
- **About 2 weeks after that:** Offer

## How I Prepared

- **DSA:** Around 200 problems, focused on arrays, strings, hashing, sliding window and DP. Use the [DevsUnite DSA Sheets](https://devsunite.com/resources/dsa-sheets) for a structured plan.
- **Full-stack basics:** I'd built two web projects before the hackathon, which meant I could contribute from the first hour. See [12 Resume Projects for Freshers That Stand Out in 2026](https://devsunite.com/blog/best-projects-for-fresher-resume-2026) for ideas.
- **Behavioural stories:** I prepared 6 STAR stories covering teamwork, conflict, failure and learning quickly.
- **Mock interviews:** Practising answers out loud with [DevsUnite Mock Interviews](https://devsunite.com/mock-interview) helped with both the video and final interviews.

## Tips for JPMorgan Code for Good and Interviews

- **Teamwork matters as much as code.** Mentors watch how you collaborate under pressure.
- **Listen to the non-profit's real problem** before building features.
- **Ship something that works.** A simple working demo beats an ambitious broken one.
- **Own a clear part of the project** so you can explain it deeply in your final interview.
- **Prepare for recorded interviews.** Practise answering on camera with a timer.

## Frequently Asked Questions

### What is JPMorgan Code for Good?

Code for Good is JPMorgan Chase's hackathon where student teams build technology solutions for non-profit organisations with guidance from JPMorgan mentors. It's also a well-known route into JPMorgan's hiring process for students.

### What are the rounds in the JPMorgan fresher interview process?

Candidates commonly report an online coding assessment, a recorded video interview, the Code for Good hackathon for some programmes, and a final technical and behavioural interview. The process can vary by programme and location.

### What do JPMorgan mentors look for in Code for Good?

Mentors typically look at teamwork, communication, problem-solving, technical contribution and how well you understand the non-profit's needs, not just the final product.

### What coding questions are asked in the JPMorgan online assessment?

Candidates commonly report easy to medium problems on arrays, strings, hashing, sliding window and dynamic programming. Careful handling of edge cases and input formats is important.

### How do I prepare for the JPMorgan video interview?

Prepare STAR stories for teamwork, challenges and learning, practise recording yourself with a timer, and make sure your setup has good lighting, clear audio and a stable internet connection.

## Final Thoughts

My JPMorgan offer didn't come from one perfect coding round. It came from staying calm at 2:30 AM, making a practical decision and helping my team ship something that worked. If you get a chance at Code for Good, treat it like the job itself: listen, collaborate, contribute and explain your work clearly.

👉 Get your resume ready for applications with the [DevsUnite ATS Resume Checker](https://devsunite.com/analyse), and ask for referrals using [these LinkedIn templates](https://devsunite.com/blog/how-to-ask-for-referral-on-linkedin-templates).

## Related

- [All blog posts](https://devsunite.com/blogs)
