There was a HackerRank-based coding test for screening. After that, it was followed up with HR for next steps, which involved a video interview with one of the engineers. It was non-technical; they were more interested in learning about me, and I was learning about the position and the company.
Though he seemed distracted at times, he was cheerful and good to talk to.
I was given a coding exercise with a good amount of time to complete. IMO, it was a good step since the question tested for important concepts and foundational knowledge while giving ample time to work on it, as opposed to traditional interviews.
The following steps, which were supposed to be after that, were a discussion with the engineers about the assignment, followed by an on-site.
Unfortunately, I was unable to submit the assignment due to unforeseen reasons, so I cannot say how the rest of my experience would have been. But I wanted to mention that they were patient and understanding during the process, giving me the time and space required.
I appreciate that, especially since there are many companies where the recruitment process seems impersonal and robotic due to the attitude of HR, interviewers, policies, etc.
Implementing a cache-placement policy as a library. Production-level code and documentation are required.
The following metrics were computed from 2 interview experiences for the The Trade Desk Software Engineer role in Seattle, Washington.
The Trade Desk's interview process for their Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for The Trade Desk's Software Engineer interview process in Seattle, Washington.