CIBC software engineer interviews, as candidates describe them, often combine a recruiter or HR screen with a technical conversation and some behavioral questions. Coding difficulty varies widely between reports.
$65K
Avg. Base Comp
$80K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidate reports describe CIBC software interviews as a mix of resume-driven conversation, behavioral questions and technical screening, with a lot of variation by team and level. Several accounts start with a phone or recruiter screen about background, languages, strengths and why CIBC. Technical rounds then range from relaxed to demanding.
On the lighter end, a co-op candidate described a short phone screen and a 30-minute video interview built around behavioral questions and a discussion of coding experience, with no live coding. Another candidate was asked to explain object-oriented programming, walk through their CV and describe a challenge they faced. A third was asked about Java reflection. They were also asked how past presentation experience would translate to explaining solutions to less knowledgeable stakeholders.
Other reports were harder. One candidate described a LeetCode-style array question about how many people each person in a line can see. Another had a 30-minute online assessment with a LeetCode medium, followed by a broad panel covering cloud platforms, databases, ETL and several languages. One account focused on Go, API design and security, so the stack on your resume and in the job posting matters.
Practice a clear OOP explanation, a few stories about challenges and teamwork, and one or two array problems. Come with genuine questions about the team. Expect follow-up timing to vary; one candidate never heard back after several follow-ups.
Synthesized from 11 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.
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 | |
|---|---|
| Line of Sight | |
| Text Editor With OOP | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Google Maps Improvement | |
| Total Spent on Products | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Cumulative Distribution | |
| Top 3 Users |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online application or referral, followed in several cases by a recruiter or HR phone screen; one co-op candidate's screen lasted 15 minutes. Reported topics include background, languages, strengths and why CIBC. One referred candidate says they went straight to a technical interview without a proper recruiter chat.
One senior candidate describes a 30-minute online assessment with a LeetCode-medium array prefix problem. Another report mentions a LeetCode-style line-of-sight array question in a technical interview. Other accounts, including a co-op one, describe no live coding at all. Whether you get a coding test may depend on team and seniority.
Technical rounds are reported at roughly 30-60 minutes with a hiring manager, senior developer or small panel. Candidates report resume walkthroughs, OOP, Java reflection, Go, API design, security, cloud platforms, databases and ETL. Difficulty ranges from basic and conversational to broad and strict, so prepare the tools you list on your resume.
Some candidates report behavioral questions about challenges, motivation and how peers would describe them, either inside the technical interview or in a separate video conversation. One senior candidate's final round was a technical assessment with the hiring manager and a senior developer. Prepare structured stories and questions for the team.
