
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.
$90K
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.
Synthetized from 3 candidates 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.
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
How would you answer when an Interviewer asks why you applied to their company?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Find the Missing Number | |
| Rolling Bank Transactions | |
| Prime to N | |
| String Shift | |
| Comments Histogram | |
| Employee Salaries | |
| Maximum Profit | |
| Closest SAT Scores | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Monthly Customer Report | |
| Hurdles In Data Projects | |
| Slacking Employees Salaries | |
| Over-Budget Projects | |
| Top 3 Users | |
| Size of Joins | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change | |
| Cumulative Distribution | |
| Level Of Rain Water In 2D Terrain | |
| Google Maps Improvement |
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.