CIBC software-engineer candidates report a three-stage process with a phone screen, discussion of prior work, and a coding-focused technical interview that also touched on statistics.
$133K
Avg. Base Comp
$155K
Avg. Total Comp
3
Typical Rounds
1-3 weeks
Process Length
For a CIBC Software Engineer interview, the most concrete recent report describes three stages: a phone screen, an introduction and presentation about previous work, and a one-hour technical interview. The technical portion was described as mostly coding and statistics, with no SQL. That makes clear explanation of your prior work as important to rehearse as the coding itself: be ready to present what you built, the decisions you made, and your individual contribution in a concise narrative.
The reported coding question focused on an array of people’s heights and asked for the maximum number visible in either direction under a blocking rule. Practice turning a wordy visibility rule into a precise algorithm before coding: identify what blocks visibility, test small edge cases, and explain the time and space trade-offs. A monotonic-stack approach may be a useful pattern to review for this kind of line-of-sight array problem, but candidates should be prepared to reason from first principles.
Statistics was also named as part of the technical conversation, though the specific material was not reported. Review the fundamentals you can explain clearly rather than assuming a particular question set. Evidence is limited to one recent role-matched account, so the order and emphasis may vary.
Synthesized from 4 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 | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Google Maps Improvement | |
| Total Spent on Products | |
| P-value to a Layman | |
| Size of Joins | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Top 3 Users |
Synthesized from candidate reports. Individual experiences may vary.
A recent candidate explicitly listed a phone screen as part of a three-stage process. The topics for this conversation were not reported, so prepare a concise introduction and role-focused examples without assuming a fixed script.
The same candidate reported a one-hour introduction and presentation about previous work. Be prepared to explain your ownership, technical choices, and results in a clear sequence; the account does not specify a required presentation format.
Candidates report a one-hour technical interview focused mostly on coding and statistics, with no SQL in this account. One reported problem involved visibility among heights in an array, so practice converting constraints into an efficient algorithm and articulating your reasoning.
