RepostedJP Morgan Chase logo

JP Morgan Chase · OA → Onsite

In process

JPMorgan Code for Good India: 10 Experiences (Part 4 of 5)

Technology and software internships · InternshipReported Sep 17, 2020
Shared byjanebeingjane

JP Morgan Chase Code for Good in India, 2024–2026: a two-problem HackerRank OA, a two-answer HireVue, then a team NGO build that decides the internship.

At a glance

  • Process: HackerRank OA with two problems (all 10 reports), given 45 minutes (30), one hour (31, 35, 36) or two hours (29, 32) → HireVue with two behavioral answers, usually 30 seconds to prepare and two minutes to speak (29, 31, 36) → Code for Good, a team build for an NGO with mentors → offers about a month later (31, 32, 34).
  • Asked recently: greedy and scheduling tasks in 4 of the 10 reports (28, 30, 31, 36) and string or array tasks in 4 (28, 31, 36, 37); HireVue prompts on teamwork, ethics, persuasion and communication (29, 31, 36).
  • Difficulty: candidates called the OA medium (29, 30), easy to medium (33) or one easy and one medium (37).
  • Practise first: Minimum Servers for an Exact Load, Minimum Flips for Even Binary Runs, Tracks in Hackathon and Minimum Meeting Rooms.

Coverage: 10 JP Morgan Chase software engineering intern candidates who took the Code for Good route in India (reports 28–37): Mumbai, Bengaluru, Hyderabad and campus applicants. Events from June 2024 to the 2025 cycle; reports from May 2024 to June 2026. Superday and other live interviews are in Parts 1–3.

In this series

  • Part 1: live finals and campus interviews, reports 1–12.
  • Part 2: campus interviews, reports 13–16.
  • Part 3: earlier rounds, reports 17–27.
  • Part 4 (current): Code for Good in India, 2024–2026, reports 28–37.
  • Part 5: a 2024 CRY dashboard build, plus older Code for Good reports, 38–43.

Related JP Morgan Chase roundups: Quant intern · Data & AI intern

What came up

Every report describes the same funnel, but the OA tasks change each year. Counts are out of the 10 reports in this part; one candidate can sit in several rows.

Topic Reports Last seen
Two-task coding OA 10 of 10 Apr 2026 (report date)
NGO project build at Code for Good 8 of 10 2025 cycle
Greedy, DP and scheduling 4 of 10 Apr 2026 (report date)
Strings, arrays and stacks 4 of 10 Apr 2026 (report date)
Behavioral prompts with wording shared 4 of 10 2025 cycle

Questions we found

Coding (OA)

Question Reports Last seen
Minimum Servers for an Exact Load 1 Apr 2026 (report date)
Minimum Flips for Even Binary Runs 1 Apr 2026 (report date)
Tracks in Hackathon 1 2024 cycle
Odd/even vowel substring game 1 2024 cycle
Minimum Meeting Rooms 1 May 2024 (report date)
Maximise Pair Count (condition not shared) 1 May 2024 (report date)

Project coding (Code for Good briefs)

Question Reports Last seen
VOPA reading assessment build 1 Dec 2024 (report date)
Indus Action benefit applications (assigned) 1 Jul 2024
DOTS intervention workflow (alternative brief) 1 Jul 2024
U & I multilingual tutoring (alternative brief) 1 Jul 2024
Aspire and Glee donation and clothing workflow (alternative brief) 1 Jul 2024

Behavioral (HireVue and mentors)

Question Reports Last seen
Working with several people on a project: your steps 1 2025 cycle
An ethical challenge at work or school 1 2025 cycle
Past experience, learning new tech, career goals (mentor) 1 Jun 2024
Your contributions, challenges, fixes and achievements (mentor) 1 Jun 2024
Convince an unwilling customer to buy a product 1 2024 cycle
Learn a new technology, lead a team, hit a strict deadline 1 2024 cycle
Changing how you communicate with a customer or teammate 1 May 2024 (report date)
A recent successful presentation or project and why it mattered 1 May 2024 (report date)

10 Code for Good candidate reports

Newest first. The numbers continue from Part 3.

28: Two photographed OA tasks from 2026

Report date: April 20, 2026 · Role: Software engineering summer intern · Location: India, NIT campus

  1. The programme timetable listed a March 9 presentation, applications March 9–12, assessments March 25–26 and HireVue March 25–29. The author's own test day was not stated.
  2. Minimum Servers for an Exact Load: choose the fewest servers whose capacities add up exactly to expected_load. Each server is used at most once and every capacity is a power of two; return −1 if impossible. With capacities [1,1,2,4] and load 3 the answer is two servers; [1,1,1] cannot reach 4. Up to 10^5 servers; capacities and load up to 10^9.
  3. Minimum Flips for Even Binary Runs: flip the fewest bits in an even-length binary password so it splits into even-length runs of one character. Grouped in pairs, 11 10 01 10 00 needs three flips to become 11 11 11 11 00: eight ones, then two zeros. Length 2 to 10^5, always even.
  4. The timetable gave several June and July Code for Good dates; which one the author attended, the HireVue prompts and the NGO task were not shared.

29: Two coding tasks and no separate mentor interview

Report date: March 15, 2026 · Cycle: 2025 campus · Role: Software engineering intern · Location: India · Result: Selected

  1. OA: two medium DSA problems in two hours; neither was named.
  2. HireVue: 30 seconds to prepare and two minutes to answer, with two recordings, the second counting as final. The prompts: how the candidate works with several people on a project, step by step; and an ethical challenge at work or school, with the situation, actions and outcome.
  3. Teams were assigned two days before Code for Good, with two or three mentors. This candidate's mentor did not hold a separate interview.
  4. Two of seven teammates were selected, and four of seven participants from the college, including the author. The NGO task was not named.

30: The VOPA education build and a late selection

Report date: December 31, 2024 · Role: Software engineer intern · Location: Mumbai · Result: Selected

  1. HackerRank arrived April 8: two medium problems in 45 minutes, done in about 40. One was dynamic programming and one a greedy maximum-benefit task; their exact goals were not shared.
  2. HireVue invite on April 19, hackathon invite on May 30, event on June 15–16. The event year is not consistent across the post.
  3. Build: VOPA rural-education support. The team chose reading assessment, AI-generated personalized tests and teacher insights; this was their pick, not a fixed NGO feature list.
  4. The team did not win. The author was missing from the August 27 selection list, then added on August 30, and said two of the college's 450 CS students were selected. HireVue prompts were not shared.

31: An Indus Action build, broken integration and a winning pitch

Event date: July 27–28, 2024 (report March 13, 2025) · Role: Software engineer summer intern · Location: Bengaluru · Result: Offer

  1. A second-year student got a three-day window to take a 60-minute, two-problem OA.
  2. Tracks in Hackathon: split p participants into teams of size a or b with the fewest teams, or return −1 if no exact split exists.
  3. System and Strings, the vowel game: Alex removes a substring with an odd number of vowels, Chris one with an even number, taking turns until someone cannot move. The full winning rule was not given.
  4. HireVue (30 seconds to prepare, two minutes, two attempts), as remembered: how would you convince an unwilling customer to buy a product, software or technology; and you must learn a new technology, lead a team and deliver under a strict deadline: what challenges would you face and how would you respond?
  5. At kickoff, four NGOs presented briefs. Three were alternatives: DOTS Foundation, digitizing intervention for child-marriage cases; U & I Trust, multilingual one-to-one tutoring with volunteers; and Aspire and Glee, field data, donations, donor contact and a clothing bank.
  6. The team was assigned Indus Action: automate frontline workers' citizen-benefit applications, identity checks and tracking.
  7. The app never fully integrated, so they demoed from several laptops. They still advanced and won, and offers came about a month later.

32: Bengaluru after an April OA, then a full-time conversion

Event date: July 27, 2024 (report June 21, 2026) · Role: Software engineer intern, second-year route · Location: Bengaluru · Result: Offer, later full time

  1. Applications closed March 30, 2024. HackerRank came April 4: two DSA problems in two hours.
  2. HireVue: two situational answers, one minute each, no retakes, as this author remembered it.
  3. The May 30 invite was for the July 27–28 event. Teams of seven or eight picked from four NGOs; mentors ran ten-minute standups.
  4. Demos lasted five to ten minutes and the top two teams per problem advanced. This team was not a finalist.
  5. The author still got an internship offer on August 28 and later converted to full time. Coding problems and the NGO task were not shared.

33: Five months of process and no offer

Report date: April 9, 2025 · Cycle: Code for Good 2024 for summer 2025 · Location: RVCE, India · Result: Not selected

  1. Registered in March, took the OA in early April and HireVue in the third week of April, and got a hackathon invite in May.
  2. The OA had two easy-to-medium tasks: sorting with pointers helped on one; small limits let brute force pass the other. Neither was named.
  3. HireVue had two behavioral prompts, two tries each; the wording was not shared.
  4. The late-July hackathon ran 24 hours with two mentors. The team was not a finalist, and the author was not picked when offers came in late August.

34: Hyderabad workshops, a 24-hour build and an offer

Event date: June 22–23, 2024 (report August 16, 2024) · Role: Software engineer summer intern · Location: Hyderabad · Result: Offer

  1. Announcement March 18, HackerRank April 8, HireVue April 19. The OA had two DSA questions of different difficulty; HireVue had two behavioral questions with two attempts (wording not shared).
  2. A May 30 invite, then workshops on June 4, 11 and 12.
  3. At the event: assigned teams of seven, a Q&A with the NGOs, first-come choice of problem and two judging rounds.
  4. A summer 2025 offer came about a month later. Coding prompts and the project goal were not shared.

35: A Mumbai team that did not win, an internship and a PPO

Event date: June 15–16, 2024 (report January 13, 2026) · Role: Software engineer intern · Location: Mumbai · Result: Selected, later PPO

  1. A second-year student (class of 2026) applied in March 2024 for summer 2025.
  2. HackerRank: two problems in one hour. HireVue: two HR answers, two minutes each, one retry; only themes were shared.
  3. The hackathon had assigned teams, three NGO choices and two mentors, each with a separate conversation. One asked about past experience, learning new technologies, related technical questions and career goals. The other asked about personal contributions, challenges, how they were fixed and achievements.
  4. The team did not win, but the author was selected. The eight-week internship had reviews in weeks four and seven, and a PPO followed. The project goal was not shared.

36: Meeting rooms and a pair-count task

Report date: May 13, 2024 · Role: Code for Good software intern · Location: India · Result: Waiting for the hackathon

  1. After pool-campus resume screening, two HackerRank problems in one hour, finished in about 50 minutes. The author noticed most of that shortlist had CGPAs above 8.5.
  2. Minimum Meeting Rooms, the minimum-halls scheduling problem.
  3. Maximise Pair Count. The candidate named it but did not restate the pairing condition.
  4. HireVue in the second-last week of April: 30 seconds to prepare, two minutes, at most two attempts. Prompts: how you changed your way of communicating with a customer or teammate; and a recent successful presentation or project and why it mattered.

37: Mumbai prototype, summer internship and a PPO

Report date: December 18, 2025 · Cycle: Code for Good 2024 → summer 2025 → 2026 · Location: Mumbai · Result: Selected, then PPO

  1. In second year, the candidate solved an easy stack task and a medium string task in about 45 minutes; neither was described. HireVue followed; prompts not shared.
  2. Nine or ten students from the college advanced, with a local shortlist cutoff of 9.46 CGPA.
  3. The team built a working prototype but was not a finalist.
  4. The author interned in summer 2025 and got a PPO on August 6, 2025, which included a six-month internship from February 2026.

Patterns across the reports

  1. The team result does not decide the individual offer. Reports 30, 32, 35 and 37 got offers after a team that did not win or reach the final; 33 was on a non-finalist team and got no offer; 31's team won.
  2. Two OA tasks, varied clocks. All 10 reports had two problems, but the time limit ranged from 45 minutes (30) to two hours (29, 32).
  3. HireVue format. Reports 29, 31 and 36 describe 30 seconds to prepare and two minutes per answer; 32 remembered one minute and no retakes.
  4. About a month to hear back. Offers came about a month after the event in 31, 32 and 34.

Common questions

What is on the JP Morgan Chase Code for Good OA?

Two coding problems on HackerRank in every report, from 45 minutes to two hours. Named tasks include exact-load server selection and binary-run flips (28), team splitting and a vowel game (31), and meeting rooms (36).

What does JP Morgan Chase HireVue ask for Code for Good?

Two behavioral prompts: teamwork and ethics (29), persuading a customer and a deadline challenge (31), changing communication style and a successful project (36).

Do you need to win Code for Good to get a JP Morgan Chase offer?

No. Four candidates got offers from teams that did not win or reach the final (30, 32, 35, 37).

When do Code for Good offers come out?

About a month after the event in 31, 32 and 34; report 30 heard on August 30 after a June event.

Keep practicing

In this series: Part 1 · Part 2 · Part 3 · Part 4 (current) · Part 5

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.