Cibc Software Engineer interview typically runs 1-2 rounds: recruiter screen, technical interview, and HR/behavioral screening. The process usually takes a few days to a few weeks and can feel rushed or unstructured.
$80K
Avg. Base Comp
$105K
Avg. Total Comp
2-3
Typical Rounds
1-3 weeks
Process Length
Our candidates report that CIBC is less interested in flashy algorithms than in whether you can explain technical decisions cleanly under pressure. Across experiences, the strongest signal was clear communication tied to real engineering judgment: one interviewer kept pulling from the resume and asked how past presentation skills would translate to CIBC, while another focused on walking through a CV, adding something not on it, and explaining basic concepts like object-oriented programming. Even when the technical bar felt light, candidates still had to sound organized, precise, and comfortable talking through their thinking.
A recurring theme is that the technical questions often center on practical stack familiarity and system thinking rather than deep theory. Multiple candidates mentioned Go, API design, and security coming up prominently, and one person noted that even a simple coding task was treated strictly in execution. We’ve also seen oddly specific questions surface, like Java reflection or setup/version-check details, which suggests the team may be testing whether you’ve actually worked in the environment you describe. The non-obvious trap here is not complexity — it’s inconsistency. The interviews can feel unstructured or rushed, so candidates who stay composed and keep answers grounded in concrete experience tend to do better than those who over-explain or drift into abstractions.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Cibc process.
I applied through a referral, and the whole thing felt a little rushed from the start. The recruiter pushed me to come in for a technical interview the next day or within a couple of days, which was odd because I never really had a proper recruiter chat beforehand. The first round was about an hour and was done with the hiring manager, recruiter, a senior developer, and an HR person all together. They barely touched my resume and went straight into technical questions. Since the role seemed to lean heavily toward Go, I got a lot of Go-related questions, and they spent even more time on API design and security. I was able to answer the Go questions reasonably well, but the technical focus was definitely the main thing they cared about. I also got the sense that if you struggled on the coding part, there wasn’t much room to recover. One review I saw mentioned a whiteboard coding exercise with a simple problem like sorting socks by color in Python, and that matches the overall vibe I had: straightforward on paper, but they were strict about execution. Another round I heard about was more standard, with an online application, behavioral assessment, and HR screening before the interview, plus some basic behavioral and tech questions. In my case, there wasn’t much behavioral discussion at all. After that interview, I followed up a few times and never got a response, so it ended with no closure.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Cibc
Describing a data project and its challenges
| Question | |
|---|---|
| Text Editor With OOP | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Maximum Profit | |
| Like Tracker | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Monthly Customer Report | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Top 3 Users | |
| Size of Joins | |
| Total Spent on Products |
Synthesized from candidate reports. Individual experiences may vary.
Candidates either apply online or come in through a referral. In some cases, the process moves quickly from application to interview, with little time spent on early screening.
Some candidates reported a recruiter or HR screening before the technical round, while others said this step was minimal or skipped entirely. When it happens, it appears to cover basic fit, availability, and an initial check of background.
This is the main round and can be fairly formal or unstructured depending on the interviewer. Expect questions on your resume, basic software engineering concepts like object-oriented programming, and role-specific technical topics such as Go, Java reflection, API design, and security. Some candidates also described a simple whiteboard-style coding exercise.
Behavioral questions are often mixed into the technical interview rather than handled as a separate round. Candidates were asked about challenges, how they communicate with stakeholders, what matters most to them in a project, and how peers would describe them.
After the interview, candidates may hear back with an offer or no offer, though some reported delayed or no follow-up. The process can end without much closure if the company does not move forward.