What one Scotiabank Quantitative Analyst candidate reported: a conversational 45-minute interview covering a resume walkthrough, SQL and data structures, a short coding question and behavioral questions.
$130K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
This guide is based on one candidate's report for the role, so treat it as a single data point rather than a full picture of Scotiabank's quantitative analyst process. The candidate described a conversational, friendly interview of about 45 minutes that began with a resume walkthrough. The interviewer asked them to explain a couple of projects in detail, including the design choices behind them and what they would do differently.
The technical portion centered on databases and data structures. It covered SQL basics such as joins and indexing, how to design a simple schema, and the trade-offs between data structures for lookups. A short coding question followed, and the candidate talked through their approach before writing the solution. The interview closed with behavioral questions on teamwork and handling deadlines, then time for the candidate's own questions. The outcome was a rejection.
The practical takeaway is to know your own projects well enough to defend each decision, and to be comfortable narrating your reasoning while you code. The candidate did not recall exact wording, so reviewing SQL joins, indexing, simple schema design and lookup trade-offs is a better use of time than hunting for specific questions. Have concise teamwork and deadline stories ready for the behavioral close.
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 Scotiabank 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 Scotiabank
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Size of Joins | |
| Ride-Sharing App Schema | |
| Client Solution Pushback | |
| Swipe Payment API | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Dropbox Database | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Employee Salaries | |
| 500 Cards | |
| Maximum Profit | |
| Merge Sorted Lists | |
| Bagging vs Boosting | |
| Subscription Overlap | |
| Duplicate Rows | |
| Google Maps Improvement | |
| Comments Histogram | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Last Transaction | |
| Slacking Employees Salaries | |
| Assumptions of Linear Regression | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports the interview opened with a walkthrough of their resume, followed by detailed questions on a couple of their projects. The interviewer asked about the design choices behind them and what the candidate would do differently, so be ready to explain the reasoning behind anything you list.
The technical questions focused on databases. The candidate recalls SQL basics such as joins and indexing, designing a simple schema, and the trade-offs between different data structures for lookups. They could not remember the exact wording, so reviewing these fundamentals is more useful than memorizing specific questions.
A short coding question came next, and the candidate talked through their approach before writing the solution. The interview ended with behavioral questions about teamwork and handling deadlines, then time for the candidate's questions. The whole conversation lasted about 45 minutes and the candidate was ultimately rejected.
