Real, anonymous reports from people who interviewed for Software Engineer at Jpmorgan Chase &, newest first and distilled into what to expect across the loop.
Get your personalized Jpmorgan Chase & Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with a recruiter phone screen, and soon after I took a HackerRank assessment that was described as easy leetcode-style questions. That kicked off a longer online Super Day on Zoom that lasted around three hours and split into behavioral, coding, and system design segments.
I ended up with a verbal offer after a few days, but the salary wasn’t where I wanted it to be. After that, the process moved into team matching, where I was supposed to speak with at least three teams before being assigned. One of those calls was difficult in a different way—I didn’t feel like the team was very interested in talking or excited to go into what they were building.
3 months ago
Easy Positive Bengaluru
I started with a recruiter touchpoint where I walked through my background at a high level, and then I moved into HackerRank. The assessment felt manageable and leaned on Java and coding practice—more “code it out” than trick questions.
A few days later I did a long Super Day that ran about three hours. It was a mix of behavioral, coding, and system design, with the coding portion including a couple HackerRank-style questions and the technical interviews alternating between formats rather than staying purely algorithmic. The system design discussion stayed practical and anchored to what I’d build and how I’d break it into components, and the behavioral segment focused on past experience.
4 months ago
Difficult Negative Bengaluru
I ran into a more difficult, coding-heavy path. The process started with an online coding assessment, and once I got past that, I came back for a supe…
4 months ago
Difficult Positive Mumbai
My process felt like it had a lot of moving parts and a longer runway than I expected. It was competitive from the start, with resume shortlisting fol…
4 months ago
Average Negative New York, NY
My experience swung between “people are trying to engage” and “this feels mishandled.” In one interview, I was asked questions via a word document aro…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Screening & Assessment
The interview process typically begins with a recruiter phone screen followed by an online coding assessment on HackerRank, focusing on easy to medium LeetCode-style questions. Candidates should be prepared for both coding and behavioral questions early on.
Recruiter callHackerRankLeetCode
Super Day Structure
Candidates participate in a Super Day that lasts around three hours, consisting of back-to-back rounds including coding, system design, and behavioral interviews. The structure is generally well-organized, but pacing can be crucial to manage time effectively across segments.
Super DayBehavioralSystem design
Technical Expectations
The technical rounds often include coding problems that require clear communication of thought processes, as well as system design discussions focusing on practical applications and scalability. Familiarity with Java and core data structures is essential.
CodingSystem designJava
Behavioral Interviews
Behavioral interviews emphasize structured responses, often using the STAR method to convey past experiences and problem-solving approaches. Candidates should prepare for scenario-based questions that assess fit with the company's values.
BehavioralSTARValues
Team Matching & Follow-Up
After the interview rounds, candidates may enter a team matching phase where they interact with potential teams. However, communication can stall during this phase, so proactive follow-up may be necessary to maintain engagement.
Team matchingFollow-upCommunication
Interview Dynamics & Culture Fit
The overall experience can vary significantly based on interviewer demeanor and organizational culture, impacting candidate performance and comfort. Candidates should be prepared for different styles of interaction and adapt accordingly.