Real, anonymous reports from people who interviewed for Software Engineer at CIBC, newest first and distilled into what to expect across the loop.
I started with a recruiter call, and the whole process felt unusually lean—there wasn’t much fluff, and the technical rounds weren’t treated like generic leetcode practice. After the recruiter touchpoint, about a week later I moved into a technical screen online. That round was focused and to the point, and it already felt like they were looking for how I think rather than me reciting memorized solutions.
My interview journey kicked off with an online session on Microsoft Teams with the recruiter and a senior manager. That part felt straightforward enough, and then I went into an in-person round in downtown Toronto. The in-person interview included some whiteboard work, where I walked through basic logic using simple if statements to reason out how to approach the problems.
The interview process typically begins with a recruiter call that focuses on background and fit, often feeling straightforward and organized. Candidates noted that the initial conversations were generally human and aimed at understanding their experience rather than being overly scripted.
Candidates experienced a mix of technical assessments, including online coding challenges and in-person problem-solving discussions, often focusing on practical skills rather than intense algorithmic challenges. The emphasis was on evaluating fundamentals and real-world problem-solving abilities.
Later rounds often included behavioral interviews that assessed cultural fit and communication skills, with questions tied to personal experiences and teamwork. Candidates felt these discussions were aimed at understanding how they would integrate into the team.
The overall atmosphere during interviews was described as professional and respectful, with many candidates appreciating the collaborative nature of discussions. However, some reported experiences that felt more hostile or aggressive, particularly during technical assessments.
Candidates noted that the timeline for the interview process was generally quick, with many steps occurring within a month. However, there were instances of inconsistent communication and follow-up, leading to uncertainty for some candidates.
Technical interviews covered a range of topics, including SQL, UNIX, and specific programming languages, but candidates expressed that some questions felt disconnected from the job description. This led to confusion about expectations and the relevance of certain assessments.