Real, anonymous reports from people who interviewed for Software Engineer at Chase, newest first and distilled into what to expect across the loop.
It started with a phone screening and then, about a week later, I had an online assessment that took roughly two hours. After that, I spoke with four senior software engineers across technical and behavioral questions. The whole thing felt fairly easy and paced in a way that didn’t feel overly stressful.
I got pulled into the process pretty quickly, but the recruiter call caught me off guard because it came out of the blue—I wasn’t prepared for the timing. Still, it ended up feeling more like an informative conversation than a high-pressure screening. After that, I moved into a technical round centered on higher performance computing.
The interview process typically begins with a recruiter call, followed by a mix of technical assessments and behavioral interviews, often spanning several weeks to months. Candidates noted a bureaucratic feel and varying timelines, with some experiencing ghosting or delayed responses post-interview.
Candidates faced a range of technical assessments, including coding challenges that often emphasized data structures and algorithms, as well as system design questions. The difficulty varied, with some candidates finding the assessments manageable while others felt overwhelmed by the expectations.
Behavioral interviews often included questions about past experiences and conflict resolution, with a focus on how candidates handled team dynamics. Some candidates felt the behavioral questions were less aligned with their backgrounds, leading to confusion during the interviews.
Candidates reported mixed experiences regarding communication from the recruiters and interviewers, with some feeling well-informed while others experienced a lack of follow-up or constructive feedback after interviews. This inconsistency contributed to a sense of frustration for many.
The overall difficulty of interviews varied significantly, with some candidates describing intense pressure during technical rounds, particularly in system design discussions. Others found the process to be straightforward but noted that clarity of questions was sometimes lacking.
Candidates expressed that they wished they had focused more tightly on relevant technologies and experiences during their interviews, particularly in technical discussions. Emphasizing clear communication and reasoning during problem-solving was also highlighted as crucial.
