Td Bank Business Analyst interview typically runs 2 rounds: a 30-minute Teams interview and an in-person round. It usually takes about 1-2 weeks and can feel rushed and thorough.
$79K
Avg. Base Comp
$84K
Avg. Total Comp
2-3
Typical Rounds
1-2 weeks
Process Length
Our candidates report that TD Bank cares less about flashy analytics depth and more about whether you can speak clearly to the basics that keep a business analysis function moving. The questions skewed toward core SQL and database concepts — things like primary keys, null behavior, and simple record deletion — alongside practical distinctions such as MySQL versus MongoDB. That tells us the bar is not about obscure syntax; it’s about whether you understand the building blocks well enough to work confidently with technical partners.
A recurring theme is the mix of BA and testing fluency. One candidate was asked about a traceability matrix, which is a good signal that TD Bank wants analysts who can connect requirements to validation, not just gather notes and move on. We’ve also seen that interviewers may skip the usual background walk-through if they’ve already reviewed your resume, so the real test becomes how concisely you can explain a past project and why it mattered. In this process, clarity under pressure seems to matter as much as correctness.
We also noticed a more transactional tone than many candidates expect: salary came up early, the pace felt rushed, and communication could drop off after the interviews. That combination suggests TD Bank is screening for people who can stay composed, answer directly, and handle a fairly businesslike conversation without over-explaining. Candidates who do best here tend to sound organized, grounded, and ready to discuss both technical fundamentals and the practical side of delivery.
Synthetized from 1 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 Td bank process.
The process started off feeling pretty rushed, which was a little stressful. I was referred for the Business Analyst/BSA Analyst role and got a 30-minute Teams interview first, followed by a second round that was in person. The recruiter was very accommodating with scheduling, and the overall process felt thorough and informative, even though the pace was intense. In my case, they had already gone through my CV, so they didn’t spend time asking me to walk through my background in detail and went straight into questions.
The first round was mostly technical with a few behavioral questions mixed in. I was asked to give a brief intro and explain why I was interested, but most of the time was spent on fundamentals like what a primary key is, whether it can be null, what would happen if it were, how MySQL differs from MongoDB, how to delete multiple records from SQL, and whether I had worked with Big Data. They also asked about a traceability matrix in testing, so it wasn’t just pure SQL — there was some BA/testing knowledge too. The questions themselves were not especially advanced, but they were direct and I felt the pressure because they moved quickly.
The second round was with a senior team contact, and there was also mention of a project I had done before. One of the interviews also included a salary requirements question, which stood out because it came up pretty early. Overall, I didn’t get an offer, and the process felt a bit pushy at times, especially since it seemed urgent on their side but then communication dropped off afterward. My main takeaway is to be ready for very basic SQL/database concepts, a few testing/BA terms, and a concise explanation of your past project work.
Prep tip from this candidate
Brush up on core SQL/database basics like primary keys, nullability, deleting multiple records, and the differences between MySQL and MongoDB. Also be ready to explain a traceability matrix and summarize a past project clearly in under a minute.
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 Td bank
Say you’re running an e-commerce website. You want to get rid of duplicate products that may be listed under different sellers, names, etc... in a very large database.
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| Interest Rates | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Find the Missing Number | |
| Rolling Bank Transactions | |
| Cumulative Distribution | |
| Bagging vs Boosting | |
| Comments Histogram | |
| 500 Cards | |
| Employee Salaries | |
| Closest SAT Scores | |
| Button AB Test | |
| Top Three Salaries | |
| Subscription Overlap | |
| Paired Products | |
| P-value to a Layman | |
| Monthly Customer Report | |
| Hurdles In Data Projects | |
| Slacking Employees Salaries | |
| Top 3 Users | |
| Size of Joins | |
| Over 100 Dollars | |
| Minimum Change | |
| Jars and Coins | |
| Compute Deviation | |
| Google Maps Improvement | |
| Total Spent on Products | |
| Sort Strings |
Synthesized from candidate reports. Individual experiences may vary.
The process began with a scheduled 30-minute Teams interview. The recruiter was accommodating with scheduling, and the conversation moved quickly because they had already reviewed the candidate’s CV. Early in the process, salary requirements were also discussed.
The first substantive round was mostly technical with a few behavioral questions mixed in. Candidates should expect direct questions on SQL and database fundamentals such as primary keys, nullability, MySQL vs. MongoDB, deleting multiple records, and whether they have worked with Big Data, along with some BA/testing topics like traceability matrices.
The second round was conducted in person with a senior team contact. This stage included discussion of prior project work and a more senior-level conversation about fit and experience, rather than a deep technical drill.