After a recruiter call, I ended up with a technical screen and then a coding-style round. The whole thing didn’t feel overly drawn out, and the experience was generally okay. The recruiter call set the stage, and then the next step quickly moved into practical work.
The coding round focused on SQL and predictive modeling. The SQL part felt medium for me, and the modeling questions were the harder edge—honestly, I thought it would have fit better as a take-home since it felt more like a task than a short interview question. One thing that threw me off was logistics: the test ended up being closed before the promised time, and the session itself lasted about 89 minutes.
3 months ago
Difficult Negative United States
This process dragged on for a long stretch—about three months—and it ended with a rejection after a final interview that felt mismanaged. The final conversation stood out because the interviewer didn’t seem to have the resume information, and they asked something different than what the recruiter had suggested I needed to prepare for.
I also had another experience earlier in the journey where I was explicitly told to prepare something foundational, but the interviewer ended up probing areas that felt like they were testing expectations as if I was already doing the job. That mismatch made the interview feel less like an evaluation of fit and more like the preparation scope had shifted without warning.
7 months ago
Average Positive Sunnyvale, CA
I went through a pretty conventional early sequence: first I heard back from HR a few weeks after applying, answered some basic qualifying questions, …
9 months ago
Average Neutral Bengaluru
My interview process felt oddly all-over-the-place, and I never got a sense that the rounds had one single theme. Across each stage, I dealt with a mi…
10 months ago
Average Neutral United States
This process felt uneven and heavily technical, with the early rounds moving through coding-style checks and then into deeper technical questioning. I…
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 can be lengthy, often taking around three months, with various stages including recruiter calls, technical screens, and coding rounds. Candidates reported a lack of clarity on timelines and expectations, leading to frustration.
TimelineProcess LengthRecruiter Communication
Technical Coding Rounds
Candidates experienced technical coding rounds that included HackerRank assessments and live coding sessions, often focusing on Python and pandas rather than SQL or traditional coding challenges. The difficulty level was generally perceived as average, but the mismatch between expected and actual content was common.
HackerRankPythonPandas
Behavioral & Values Assessment
Interviews included behavioral questions, typically towards the end of technical rounds, but candidates noted that the behavioral focus sometimes felt overshadowed by the technical content. This aspect was less emphasized compared to technical evaluations.
BehavioralValuesSTAR
Technical Depth & Focus
The technical interviews covered a broad range of topics, including machine learning concepts and statistical methods, but candidates felt the depth was lacking due to the wide scope of questions. This made it challenging to demonstrate expertise in specific areas.
Machine LearningStatisticsTechnical Depth
Communication & Alignment Issues
Several candidates reported discrepancies between what was communicated by recruiters and the actual interview content, leading to confusion and misalignment in preparation. This lack of synchronization was a common source of frustration.
CommunicationExpectationsMisalignment
Outcome & Reflections
Most candidates did not receive offers and reflected on the experience as challenging due to the unclear expectations and technical focus. Many wished they had better aligned their preparation with the actual interview content.