It started with an OA. After that, I had a recruiter screen call, and then the first real technical round was a machine-learning craft style interview where I had to connect system design thinking with details from my own projects. It felt like the interviewer wanted to see how I reason end-to-end, not just whether I could answer trivia.
A further round came after the ML craft discussion, and it leaned toward values and management. Overall the process felt pretty steady and “average” in difficulty, and the pacing matched what I’d expect from a typical mid-length tech screening flow.
11 months ago
Average Neutral United States
My process began with a recruiter call, and after that the technical part ended up being fairly straightforward. I only remember getting one SQL question during the technical interview, and then I moved into the behavioral stage. That behavioral portion was split into three interviews total.
One of the onsite conversations focused on experimentation, with questions that were directly tied to how I’d think about A/B testing and outcomes. Even though I walked in expecting it to be a tougher technical grind, the SQL portion was the one concrete technical moment I recall, and the rest of my impression was shaped by how the process emphasized communication and how I explained my work. I ended up with an offer for this path, which made the overall experience feel more positive than stressful.
11 months ago
Average Positive United States
After the recruiter touchpoint, I eventually hit a timed SQL-and-metrics style round. It was split evenly: half an hour of SQL and half an hour of a b…
> 1 year
Average Neutral Bengaluru
My loop was short but structured: three rounds. The first one was conversational and focused on my actual day-to-day—what kind of work I was doing cor…
> 1 year
Average Neutral United States
I experienced the process as a long, multi-week sequence. First there was a recruiter chat, then I moved into a SQL screening, and from there I had a …
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Screening & Assessment
The interview process typically begins with a recruiter call followed by an online assessment, which may include coding and SQL questions. Candidates should prepare for a mix of technical skills, including Python and SQL, as well as machine learning concepts.
Recruiter callOnline assessmentSQL
Technical Rounds
Candidates can expect a technical interview that often includes SQL questions and case studies focused on metrics and data analysis. The emphasis is on practical application rather than abstract problem-solving, so being able to interpret data and reason through business cases is crucial.
SQLData analysisCase study
Behavioral Interviews
Behavioral rounds are a significant part of the process, often comprising multiple interviews that assess communication skills and alignment with company values. Candidates should be ready to discuss their past experiences and how they approach challenges in a structured manner.
BehavioralCommunicationSTAR
Focus on Experimentation & Metrics
Some interviews include a focus on experimentation, particularly A/B testing, and how candidates think about outcomes. Demonstrating a solid understanding of experimental design and metrics interpretation is beneficial.
A/B testingExperimentationMetrics
Overall Difficulty & Experience
The overall difficulty of the interview process is generally perceived as average, with a structured flow that emphasizes consistency across interviews. Candidates may find the pacing steady but should be prepared for a potentially lengthy timeline between rounds.
Average difficultyStructured flowTimeline
Feedback & Clarity
Candidates noted that while feedback was often informative, the lack of clarity regarding fit for specific roles and the lengthy process could be draining. It's important to seek clarity on the role being considered throughout the process.