I got into the process through a referral, and it moved through five rounds: one live coding round, two technical rounds, and two behavioral rounds. I remember it feeling fairly understandable throughout, like the expectations were clear enough that I wasn’t constantly guessing what they wanted. The live coding wasn’t a mystery either—I wasn’t blindsided by the format, and the overall flow made sense as it progressed.
Even though it wasn’t the fastest process, the communication was solid. I kept getting timely updates, and the prep materials helped me know what each round would look like. For the coding part, the people running it were helpful when I got stuck, which definitely lowered the pressure. The whole thing ended up feeling like a decent loop rather than something chaotic or adversarial, and that made a difference in how I performed.
3 months ago
Difficult Positive Midtown New York
I heard the process was going to be packed into a single day, with a couple of back-to-back sessions under a “power day” setup. That structure was the main thing I focused on while I was waiting, because it sounded like I’d be moving quickly through multiple conversations rather than spacing things out.
3 months ago
Easy Positive United States
I applied for the TDP AI Internship and the process started with OA and then moved into a recruiter screening, followed by a superday. The superday it…
3 months ago
Average Neutral United States
My process started when a recruiter set up a call with the hiring manager, and then I went into a loop with three rounds: DSA, system design, and beha…
3 months ago
I went through a recruiter screen, then a hiring manager interview, and then two coding rounds for a Senior Software Engineer role. The process ended …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically consists of multiple rounds, including coding, system design, and behavioral interviews, often structured in a 'power day' format where several sessions are back-to-back. Candidates noted that the overall flow was clear and well-communicated, helping them understand what to expect at each stage.
Power DayStructured ProcessMultiple Rounds
Coding Challenges
Candidates faced a variety of coding problems, primarily LeetCode-style questions, with a mix of easy to medium difficulty levels. The coding rounds were often described as low-pressure environments where interviewers provided hints and support when candidates got stuck.
LeetCodeCoding ProblemsLow Pressure
System Design Interviews
System design rounds focused on practical applications and architectural discussions, with candidates expected to explain their thought processes and trade-offs. Some candidates found these discussions challenging, especially when interviewers were less accommodating or engaged.
System DesignArchitectureTrade-offs
Behavioral Interviews
Behavioral interviews were common and often utilized the STAR method, focusing on candidates' past experiences and teamwork. However, some candidates reported that the tone of these interviews could vary significantly, affecting their overall experience.
BehavioralSTAR MethodTeamwork
Communication & Feedback
Communication throughout the process was generally described as solid, with timely updates and clear expectations, although some candidates experienced delays or lack of clarity post-interview. Feedback on performance, especially after coding rounds, was sometimes vague or unsatisfactory.
CommunicationFeedbackClarity
Overall Experience & Outcome
While many candidates found the interview process to be well-organized and fair, the emotional tone of interviews and the variability in interviewer engagement affected their experiences. Some candidates left feeling positive despite not receiving offers, while others felt frustrated by the process.