RepostedJP Morgan Chase logo

JP Morgan Chase · OA → Onsite

In process

JPMorgan Tech Intern HackerRank OA: 11 Experiences (Part 3 of 5)

Technology and software internships · InternshipReported Sep 13, 2022
Shared byjanebeingjane

JPMorgan Chase tech intern assessments in 2024 were a one-hour HackerRank with two problems, then a HireVue video; older campus reports are in History.

At a glance

Coverage: 2 current assessment reports (April 2024; technology and software summer intern, India where stated) and 9 older reports in History: three 2017 campus interview loops in India and six 2019–2023 assessment-only accounts, including a London six-month route.

In this series

  • Part 1: live finals and campus, entries 1–12, with the current question tables.
  • Part 2: four 2019 campus accounts, entries 13–16.
  • Part 3 (current): assessments and earlier rounds, entries 17–27.
  • Part 4: Code for Good, entries 28–37.
  • Part 5: Code for Good, entries 38–43.

What came up

Both current reports describe the same two-step assessment: two coding problems in an hour, then recorded HireVue answers about teamwork and communication.

Topic Reports Last seen
Two-problem HackerRank coding test 2 of 2 Apr 2024 (report date)
HireVue behavioral video 2 of 2 Apr 2024 (report date)

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Array reduction 1 Apr 2024 (report date)
Job scheduling (variant not stated) 1 Apr 2024 (report date)
Server Selection 1 Apr 2024 (report date)
Swap Parity 1 Apr 2024 (report date)

Behavioral (BQ)

Question Reports Last seen
Team management and conflict 1 Apr 2024 (report date)
Technical and management problems in your projects 1 Apr 2024 (report date)
How would you fix ineffective communication? 1 Apr 2024 (report date)
Help a friend understand a difficult subject 1 Apr 2024 (report date)

2 detailed candidate timelines

20: array reduction, job scheduling and two-minute videos

Report date: April 30, 2024 · Role: Technology intern · Result: Not reported

Coding test (one hour, two questions)

  1. Array reduction; the candidate used basic data structures and nested loops.
  2. Job scheduling: the candidate named a familiar practice exercise, but the variant, input and output were not given.

HireVue

  1. Team management and conflict; technical and management problems in past projects; how you would handle certain team situations.
  2. Each answer could run two minutes, with two attempts.

21: every Server Selection test, six of ten Swap Parity tests

Interview date: April 7 (year not stated; report date April 29, 2024) · Role: Software summer intern · Location: India · Result: Awaiting a decision

HackerRank (one hour, two problems, ten tests each)

  1. Server Selection: all ten tests passed. The full capacity and load rules were not reproduced.
  2. Swap Parity: six of ten tests passed. The full statement was not reproduced.

HireVue (two weeks later, about 20 minutes)

  1. How would you correct ineffective communication?
  2. How would you help a friend understand a difficult subject, and how would you teach it?
  3. Each prompt gave 30 seconds to read and at least 90 seconds to answer.

Common questions

How long is the JPMorgan Chase intern HackerRank test?

One hour for two coding problems in both current reports (entries 20, 21).

What is the JPMorgan Chase intern HireVue like?

Recorded behavioral answers about teamwork, conflict and communication: two minutes with two attempts in one report (entry 20), and about 20 minutes with 30 seconds to read and at least 90 seconds to answer in the other (entry 21).

What coding questions are on the JPMorgan Chase intern OA?

Array reduction and job scheduling (entry 20); Server Selection and Swap Parity (entry 21). Older reports add 0/1 knapsack, Decode Ways and bracket matching (History).

History (before 2024)

These reports are more than three years old. They stay out of the counts and tables above.

H22: a valid-parentheses task

Report date: July 27, 2023 · Role: not stated (a software internship discussion) · Result: Not reported

  1. The candidate's HackerRank had Validate Matching Brackets, which they recognized and completed.

H23: explaining a DP bug after one of four tests passed

Interview date: August 14, 2021 · Role: Software engineer summer intern (summer 2022) · Result: Awaiting a result

  1. HireVue coding: a 30-minute string task with a three-minute video explanation, then a 45-minute DP task with another three-minute video. Neither objective was shared.
  2. All tests passed on the first task and one of four on the second; in the video the candidate named the remaining bug and the fix.

H24: two solved questions, then a rejection

Interview date: December 2020 (inferred; report date February 4, 2021) · Role: Six-month software internship (exact title not stated) · Result: Rejected

  1. Both assessment questions solved; the tasks were not named.

H25: London six-month route with coding videos

Interview date: October 13, 2020 · Role: Software developer six-month intern · Location: London, UK · Result: Not reported

  1. Applied the day before and reused an earlier Pymetrics result; the HireVue invitation arrived about 20 minutes later.
  2. Two 35-minute coding problems, each followed by a video on the approach and possible improvements: Capitalize Each Word Initial and Decode Ways. Only two sample tests, no custom tests, and no HR prompts.

H26: two sample tests and a recording after each solution

Interview date: August 28, 2020 · Role: Software engineer summer intern · Result: Awaiting an update

  1. Applied August 21, got Pymetrics on August 24, and received the coding/video invitation about ten minutes after finishing the games on August 25.
  2. An easy and a medium task (not named), each with a recorded explanation and only two sample tests.

H27: two easy tasks that did not advance

Interview date: 2019 · Role: Software engineering intern applicant · Result: Did not advance

  1. Two easy coding tasks with video explanations; the candidate felt they did well.

H17: balls between towers, ML theory and a SQL question

Report date: October 7, 2017 · Role: Summer technology analyst intern (summer 2018) · Location: India · Result: Selected (10 of about 30)

  1. Assessment: ten aptitude/technical MCQs and two coding tasks worth 15 and 55 marks. Count Trapped Unit Balls, a trapping-rainwater variant with balls as wide as a tower; and Count Training Programs in a Maximum-Value Schedule, where P1=[14,15,200], P2=[18,19,200], P3=[16,19,100], P4=[15,18,100] gives 3 (P1, P4, P2). About 30 of 90 advanced.
  2. Two technical interviewers: four resume projects (IoT/PHP, two Django apps, an ML project); what ML is; Naive Bayes, KNN and SVM; AI versus ML versus deep learning; how voice assistants work; NLP versus voice recognition; why C++ and Python. Then SQL: delete duplicate rows from a table.
  3. Lighter questions: where you see yourself in three to five years, why JPMorgan, and when you had breakfast and dinner.
  4. HR: background, choosing a job over the family business, responsibilities and future goals.

H18: knapsack and constructor questions

Report date: September 5, 2017 · Role: Technology intern · Location: India · Result: Not stated

  1. Assessment: 0/1 Knapsack (completed) and an array/hash problem whose operation was not shared (about half the tests passed).
  2. Technical: encapsulation; reaching private class data; why Java when C++ existed; whether multiple inheritance is good; handling an exception thrown in a constructor; what happens when a class has only a one-argument constructor and you create an object with no argument. Also DBMS.
  3. HR: grades, coding contests and a campus ambassador role.

H19: a full binary tree that needed a longer explanation

Interview date: September 1, 2017 (year inferred) · Role: Technology intern · Location: India · Result: Selected (13 students)

  1. Assessment: 90-minute HackerRank with ten aptitude questions and two coding questions, including 0/1 Knapsack; 46 of about 100 advanced.
  2. Technical: favorite subject (operating systems); check whether a binary tree is full (every node has zero or two children), solved recursively, with an extended walkthrough even though the examples passed; semaphores, processes and threads.
  3. HR: introduce yourself, why hire you, weaknesses and how you fix them, and evidence that you learn fast.

Keep practicing

In this series

Related JPMorgan Chase roundups: quant interns · Data & AI interns

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.