Jpmorgan Chase

I applied for the JPMorgan Chase SEP internship through the campus hiring process. The selection journey was different from the usual internship process because there was no traditional sequence of two or three technical interviews. Instead, the main stages were the coding assessment, a recorded behavioral interview, and finally Code for Good. The first stage was the online assessment on HackerRank. I had two coding questions, and the difficulty was mostly around easy to medium. The questions were based on standard DSA patterns, so I concentrated on solving them efficiently rather than trying to use complicated techniques. I finished both and spent the remaining time checking boundary cases and complexity. Recent JPMC reports confirm that two coding questions are common in this stage, with arrays and strings appearing frequently and some candidates receiving DP or graph questions. After clearing the OA, I received the HireVue assessment. This was completely different from the coding round. Instead of speaking to an interviewer live, I was shown behavioral questions and had limited time to prepare each response before recording it. One question was about teamwork, while another focused on explaining a technical concept or dealing with a difficult situation. I tried to keep my answers structured and based on things I had actually experienced rather than giving generic statements. Candidate reports describe two recorded questions with limited preparation and attempts for each response. The next email I received was the invitation to Code for Good. This was the stage I was most excited about because we had to actually build something rather than just solve isolated coding problems. I was assigned to a team and given a problem statement from an NGO. We first spent time understanding the requirements and deciding which features were realistic to complete within the available time. I took responsibility for part of the development and also helped connect my work with the modules being built by the other members. The biggest challenge was coordination. Everyone had different ideas about implementation, so we had to agree on priorities quickly. We also had mentors available during the event, and I found their feedback useful when we were unsure about our architecture or feature scope. JPMC Code for Good reports describe the same combination of NGO problem statements, team development, mentor interaction and final presentation. Near the end, we prepared the demonstration and presentation. I explained the part I had implemented, the technical decisions behind it, and the problems we encountered during development. I also had to answer questions about how the application could be improved beyond the hackathon. After the event, I received the selection confirmation for the SEP internship. Looking back, the process tested three very different skills: DSA in the OA, communication in HireVue, and practical software development and teamwork during Code for Good. That combination made the process feel much broader than a conventional coding interview.