The Trade Desk·Machine Learning Engineer·Technical Phone Screen
Jul 2026
Interviewed for an MLE role at Tradedesk and got handed a multi-level in-memory database design problem that kept growing in scope. Each level added new requirements on top of the last, which was either a clever way to test adaptability or just exhausting depending on how you look at it.
- Implement basic set, get, compare-and-set, and compare-and-delete operations for an in-memory key-field-value store with timestamps.
- Add scan and prefix-filtered scan operations that return all visible field-value pairs for a given key at a given timestamp.
- Extend the store to support per-write TTL expiration, where a value is only visible within a half-open time window starting at the write timestamp.
- Implement a time-travel query that returns the value of a field as it existed at some past timestamp, accounting for all historical writes, deletions, TTL expirations, and compare-and-set updates.
“Level 1 felt manageable.”