Cibc Data Engineer interview typically runs multiple rounds: technical interviews and live SQL/coding rounds. It usually takes a few weeks and can feel disorganized, with verbal signals not always matching the final outcome.
$81K
Avg. Base Comp
$143K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that CIBC leans heavily on schema-based SQL that feels close to day-to-day engineering work, not abstract puzzle solving. In the experience we saw, the interviewer handed over a database schema and expected the candidate to reason through table relationships and write clean queries on the spot. That tells us the bar is less about memorizing syntax and more about whether you can translate a business question into correct, readable SQL under pressure.
A recurring theme is that the coding side is present, but it tends to be secondary to the database work. The LeetCode-style questions described were easy-to-medium, which suggests CIBC is using them more as a baseline screen than as the main differentiator. What seems to matter most is whether candidates can stay precise when the prompt is practical and slightly messy, especially in a live setting where small mistakes in joins or filters can change the result.
We also noticed a non-technical signal that candidates should not ignore: communication can be inconsistent. One candidate was verbally told an offer was coming and even discussed logistics, only to be told days later they were no longer being considered, with no written confirmation in between. That kind of experience suggests the process may reward patience and caution; we’d treat verbal momentum as provisional until something is in writing.
Synthesized from 1 candidate report 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 | |
|---|---|
| Text Editor With OOP | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Docs Metrics | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Cumulative Distribution | |
| Experiment Validity | |
| Find the Missing Number | |
| String Shift | |
| Prime to N | |
| Last Transaction | |
| Maximum Profit | |
| Like Tracker | |
| Alphabet Sum | |
| Google Maps Improvement | |
| Paired Products | |
| Monthly Customer Report | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| Over-Budget Projects | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
The process appears to begin with an initial conversation to discuss the role and candidate fit. In this case, later phone communication also covered logistics such as start date, relocation, and compensation, suggesting recruiter involvement throughout the process.
The main evaluation consisted of several live technical rounds split heavily between SQL and a couple of easy-to-medium algorithm questions. Candidates were given a database schema and asked to write SQL queries against it, with emphasis on understanding table relationships and expressing logic clearly.
After the technical rounds, the candidate received a phone call indicating that an offer would be issued and discussing offer logistics. However, there was no written confirmation, and the candidate was later told they were no longer being considered.