RepostedJP Morgan Chase logo

JP Morgan Chase · OA → Onsite

In process

JPMorgan Code for Good India 2024: 6 Experiences (Part 5 of 5)

Technology and software internships · InternshipReported Aug 25, 2020
Shared byjanebeingjane

JP Morgan Chase Code for Good 2024 in India: a two-problem OA, HireVue and a CRY dashboard build that led to an offer, plus five 2020–2022 reports.

At a glance

  • Process: HackerRank OA with two problems and a three-day window → HireVue with two prompts and two attempts → Code for Good team build for the NGO CRY → offer about two months later (38).
  • Asked recently: a simulation-style cost problem and a pairs problem solved with sorting and two pointers; HireVue on a teammate conflict and future goals (38).
  • Difficulty: the candidate called the cost task a straightforward simulation with loops (38).
  • Practise first: Min Total Cost and Pairs.

Coverage: 6 JP Morgan Chase software engineering intern candidates on the Code for Good route (reports 38–43). One is current: a 2024 India candidate who received a six-month internship and full-time offer. Five reports from 2020 to 2022 (India campus and virtual events, and Plano in the U.S.) sit in History.

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: Code for Good in India, 2024–2026, reports 28–37.
  • Part 5 (current): a 2024 CRY dashboard build (38), plus older Code for Good reports with OA tasks and mentor interviews (H39–H43).

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

What came up

The one current report covers the whole route: two coding tasks, two HireVue prompts and a web build for an NGO (38). For more recent Code for Good reports, see Part 4.

Questions we found

Coding (OA)

Question Reports Last seen
Min Total Cost 1 2024
Pairs 1 2024

Project coding (Code for Good brief)

Question Reports Last seen
CRY internal document review dashboard 1 2024

Behavioral (HireVue)

Question Reports Last seen
Resolving an ongoing project conflict with a teammate 1 2024
Your future goals 1 2024

The current report

38: CRY dashboards, then a six-month internship and full-time offer

Interview year: 2024 (report September 10, 2024) · Role: Software engineer, six-month intern plus full-time offer · Location: India · Result: Offer

  1. HackerRank gave a three-day window for two problems.
  2. Min Total Cost: the candidate called it a straightforward math simulation with loops.
  3. Pairs: solved with sorting, two pointers and condition checks. The full statement was not shared.
  4. HireVue: two prompts, two attempts (the author was unsure of the timing). They asked how the candidate resolved an ongoing project conflict with a teammate, and about future goals.
  5. Code for Good brief: an internal document review flow between CRY and self-help groups, with dashboards. The team of seven or eight used Vite/React, Tailwind CSS, ShadCN, SQL and Django.
  6. Demos had to fit in seven minutes, and the top two teams per NGO advanced. This team did not.
  7. About two months later, four teammates, the author included, got a full-time offer with a six-month internship.

Common questions

What does the JP Morgan Chase Code for Good OA look like?

In report 38 it was two HackerRank problems with a three-day window to start. Part 4 has ten more recent OA reports.

Can you get a JP Morgan Chase offer without winning Code for Good?

Yes. Report 38's team did not reach the final, yet four of its members got offers.

History (before Nov 2023)

These five reports are older than three years. They count toward this part but stay out of the summary and tables above.

H39: An overnight nonprofit build in Plano

Interview month: October 2022 (year inferred; report July 2023) · Role: Software engineer intern · Location: Plano, U.S. · Result: Offer

  1. Applied in September, took the OA and got an invite in late September or early October.
  2. The Plano event was in late October: an overnight nonprofit build, with travel support. The author found it stressful. The NGO problem was not shared.
  3. The offer arrived in mid-November.

H40: Merge costs, an overtaking problem and a MERN build

Cycle: March 2022 (report September 13, 2022) · Role: Software engineer, six-month internship plus full-time offer · Location: India, on campus · Result: Offer

  1. HackerRank had two 50-point problems.
  2. Minimum total merge cost: repeatedly merge two numbers, pay their sum and put the sum back; minimize the total cost to reach one number.
  3. Days to Overtake Another Coder: given two coders' daily problem counts and a starting gap, find the fewest days until the first strictly passes the second, or −1.
  4. HireVue: two questions, about ten minutes in all. A project with strong learning and real-world use; and career goals.
  5. Code for Good: teams of seven or eight, two days to prepare, two mentors. The team built a MERN app (domain not shared) and was runner-up.
  6. Mentor 1 (about 30 minutes): SQL versus MongoDB, Node.js middleware, REST APIs and generating schemas in Node.js and MongoDB.
  7. Mentor 2 (about 20 minutes): show your personal contribution, walk through a resume project, then standard HR questions.
  8. Selection came about 45 days after the hackathon.

H41: Two OA tasks, then nine mentor questions

Report date: August 4, 2021 · Role: Software engineer intern, class of 2022 · Location: India · Result: Selected

  1. February HackerRank: two problems in 75 minutes. Minimum movement around a circular tool array (walk either direction to reach a target) and Binary Linked List to Decimal.
  2. March HireVue: two answers, 30 seconds to prepare, two minutes each, two attempts. A project mistake and what you learned; going above and beyond on a project.
  3. July's 24-hour virtual hackathon had more than 650 students in about 100 teams of six or seven, choosing among ten or eleven NGOs with two mentors. Teams recorded a seven-minute demo before technical judging; the top two per NGO reached the final.
  4. Two personal mentor interviews asked: your approach to the NGO problem and where the project stood; your own contribution; tech stack choices and why; how you heard about Code for Good; your hackathon experience and what could improve; why JP Morgan, and is it your dream company; higher-study plans; teamwork; and implementation difficulties and fixes.
  5. Nine students from the college were selected about three weeks later.

H42: A circular tool array and a binary linked list

Interview date: February 20, 2021 (report August 5, 2021) · Role: Software engineering intern, second year · Location: India, virtual · Result: Selected

  1. HackerRank: 75 minutes for two 50-mark questions; the author finished in 14 minutes.
  2. Minimum Circular Tool Distance: the fewest left or right steps around a circular list of tool names to a target, with repeated names allowed. With saw, hammer, mallet, file, saw, ladder, scissor and a start at index 6, the nearest saw is one step away.
  3. Binary Linked List to Decimal: 1→0→1→1→0 returns 22.
  4. HireVue on March 10: two behavioral answers, 30 seconds to prepare, one retake each. Going beyond the assigned task at school or work; learning from a recent mistake.
  5. A May 1 invite led to a virtual 24-hour hackathon: teams of six or seven, five NGO choices, two or three mentors, code and demos submitted online. The NGO task was not shared. Selection came July 31.

H43: A small egg dataset and a site that did not fully work

Report date: September 19, 2020 · Role: Software and technology intern · Location: VJTI, India · Result: Selected

  1. 72 applicants were shortlisted on resumes. A two-hour test had ten C-output MCQs and two coding problems; 18 moved on.
  2. One coding task: Divisibility by Three and Five, saying whether a number divides by 3, by 5 or by both.
  3. HireVue: 60 seconds to prepare and 90 to answer each of two prompts, which the author did not remember.
  4. The virtual programme ran over several August dates, with the build on one 12-hour Sunday: about 550 participants, nine NGOs, two mentors per team.
  5. Build: an egg supply-and-demand analysis website, with forecasts and current-state plots from a few years of data. It stayed incomplete and partly unresponsive, and the team was not a finalist.
  6. A mentor asked about plans after college. Three teammates, the author included, were selected. The post's timeline is inconsistent, so the date above is the report date.

Keep practicing

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

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.