JPMC

I went through the JPMorgan Chase Software Engineering Program hiring process, and the overall experience was quite different from a conventional internship interview. The selection was built around Code for Good, so clearing the coding test was only the beginning. The first stage was the online assessment on HackerRank. I got two coding problems, and both were around the easy-to-medium range. My questions were mainly based on standard DSA patterns rather than anything extremely advanced. I focused on getting a correct solution first and then checked the complexity and edge cases. Recent JPMC internship reports also describe two-question HackerRank assessments, with arrays and strings being common topics, while some candidates received graph or DP problems. After the OA, I received the HireVue interview. This was a recorded behavioral assessment rather than a live technical interview. I was given questions related to teamwork, leadership, handling difficult situations and explaining technical concepts to other people. I had limited preparation time before recording each answer, so I tried to structure my responses around actual situations instead of giving generic answers. The format also allowed limited retakes, which made it important to organize my thoughts quickly. The next stage was Code for Good, and this was easily the most important and interesting part for me. I was placed into a team with other shortlisted candidates and given a problem statement from an NGO. We first understood the requirements and then divided the work among ourselves. I worked mainly on the development side. We had to turn the problem statement into something functional within a limited amount of time, so there was a lot of discussion about what features were actually necessary. I worked on my assigned modules while also helping the team integrate different parts of the application. Mentors from JPMC periodically checked our progress and asked questions about our design and implementation. Near the end, we prepared the final presentation. We had to demonstrate what we had built and explain our technical decisions. I also had to clearly describe my individual contribution rather than simply saying what the entire team had developed. Earlier JPMC Code for Good reports similarly describe teams working with NGO problem statements, mentors, development and a final presentation. After the hackathon, I waited for the final result and eventually received the selection confirmation for the SEP internship. What I liked about this process was that DSA was not the only thing being evaluated. The OA checked problem-solving, HireVue checked communication, and Code for Good tested whether I could actually work with a team and build something under a deadline. For me, the hackathon was the stage that required the most preparation because knowing how to code individually was very different from building a working solution with several people.