The Trade Desk Online Assessment Experience on CodeSignal: Bank System Variant
Question Details
I received an online assessment (OA) from TTD on Friday. It was from ICA, and the question I drew was the classic Bank System. Although I had done it before, this one seemed to be a variation. My prev
Full Details
I received an online assessment (OA) from TTD on Friday. It was from ICA, and the question I drew was the classic Bank System. Although I had done it before, this one seemed to be a variation. My previous post on this topic is here: https://www.1point3acres.com/bbs/thread-1143333-1-1.html L1, L2, and L4 are the same. L3 required implementing a payment behavior, similar to everyday spending. However, this account has a 2% rebate, which is returned to the issuing account after 24 hours, similar to scheduled payment. This 2% is rounded down. Unfortunately, I still couldn't debug two cases in L4. I didn't expect CodeSignal to ask me to do it again, even though I had already done it once. I don't know what CodeSignal's logic is... However, my score was better than last time, ending with 580/600. It's a bit frustrating not to get a perfect score on my second attempt. I won't go into the specific code this time, because I still didn't get it completely correct.
More Tradedesk Interview Questions
About Tradedesk Interview Reports
This question was reported by a candidate who interviewed at Tradedesk. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Tradedesk are the higher-signal extractions to take from this report.
For broader preparation context, the Tradedesk interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Tradedesk reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Tradedesk Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Tradedesk reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.