Two candidates describe varied TD Bank software engineer interviews: a manager or phone screen, a virtual interview that in one case was a 2-hour team session with code reading, and in the other case an on-site day of manager interviews.
$130K
Avg. Base Comp
$155K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The two TD Bank reports we have point to different shapes of process, so it helps to prepare for conversation first and technical depth second. A graduate Python developer candidate described two virtual rounds. The first was a manager screen where the manager mostly described the role and tied it to the candidate's resume. The second was a 2-hour virtual session with about six team members, with questions touching front end, back end, logic and data structures and algorithms. The candidate was also asked to read a piece of code and explain what it would do, and did not receive an offer.
A software engineer candidate described a faster path: a phone screen, a virtual interview, and then an on-site day with three or more back-to-back 45-minute one-on-one interviews, each with a different hiring manager. The conversations centered on their background and how they would fit each team. They received an offer the day after the on-site day and accepted it.
Taken together, the useful preparation is to know your own projects and your role in them well, practice reading unfamiliar code aloud, and have a short introduction you can repeat comfortably for several managers in a row.
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 Td bank process.
1 round, behavioral mainly going through project experience and culture fit. The basic behavioral questions like how to deal with conflict, how to work in a team. There was a very brief technical portion, but it was verbal and covered basic CS concepts.
Questions asked: Things like describe OOP and the basic difference between sorting algorithms and graph search algorithms.
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
How would you justify the complexity of building such a model and explain the predictions to non-technical stakeholders
| Question | |
|---|---|
| Duplicate Product Names | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Size of Joins | |
| Total Spent on Products | |
| Top 3 Users | |
| Get Top N Frequent Words | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Google Maps Improvement | |
| Scrambled Tickets | |
| Prime to N | |
| Comments Histogram | |
| Slacking Employees Salaries | |
| Last Transaction | |
| Like Tracker |
Synthesized from candidate reports. Individual experiences may vary.
The graduate Python developer candidate described the first virtual round as a manager screen: the manager spent most of the time talking up the role and connecting it to the candidate's resume, in a conversational way. The software engineer candidate's process also began with a phone screen before moving to a virtual interview.
The graduate Python developer candidate reported a 2-hour virtual session with about six team members. Questions touched front end, back end, logic and data structures and algorithms, and the candidate was asked to look at code and explain what it would do. The software engineer candidate also had a virtual interview before the on-site day but did not describe its content.
The software engineer candidate described an on-site day with three or more one-on-one interviews of about 45 minutes, each with a different hiring manager from a different team. The conversations focused on their background and fit with each team. They received an offer the day after the on-site day and accepted it.
