After an initial coding assessment online, I moved into a recruiter conversation with the head of recruiting. That round blended fit and technical questions, and it felt like they were trying to see how I thought as much as what I knew. I didn’t progress beyond that step, even though I had the sense that the technical pieces were meant to be a quick filter.
Before that, I’d also run into a very different technical gauntlet: a phone screen followed by an online assessment and then an interview where the coding portion leaned heavily into harder LeetCode-style dynamic programming. One moment that stuck with me was being asked a classic strengths-and-weaknesses question, but the coding difficulty was the real problem—there weren’t hints and I ended up struggling with the solution flow. The difficulty level in the technical round made it clear they weren’t lowering the bar, and that ultimately matched the outcome I saw across these stages: I didn’t get further.
> 1 year
Average Negative United States
I found the process going through multiple rounds and even completing a take-home assignment, which was the kind of commitment that makes you expect at least some closure. After that, though, everything just stalled.
They ended up ghosting me completely. I never heard back and I followed up with emails after the fact, but there was no response at all. That lack of communication left a lasting negative impression on me, mostly because it felt like my time and effort weren’t treated with basic respect—even though the earlier steps had gone far enough for me to believe I was in the running.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Screening & Technical Assessment
Candidates typically start with an automated coding screen, often using HackerRank, which includes multiple parts like SQL and Python. Time management is crucial, as running out of time can lead to immediate rejection regardless of progress.
HackerRankSQLPython
Recruiter & HR Conversations
The initial recruiter conversation blends fit and technical questions, focusing on candidates' thought processes and motivations, as well as their expectations for the role. This stage is critical for assessing cultural fit.
RecruiterCultural FitMotivations
Technical Interview Rounds
Subsequent technical interviews involve multiple rounds with LeetCode-style questions, typically skewed from medium to hard difficulty, emphasizing data structures and algorithms. Candidates should prepare for in-depth discussions about their technical skills and project experiences.
LeetCodeData StructuresAlgorithms
Case Study & Take-Home Assignments
Some candidates are required to complete a case study or take-home assignment, which adds significant weight to the process and is not timed. This step assesses analytical and problem-solving skills in a more comprehensive manner.
Case StudyTake-HomeAnalytical Skills
Onsite Interviews
Onsite interviews involve multiple interviewers and cover a wide range of topics, including statistical modeling, system design, and performance optimization. Candidates should be prepared for both technical questions and discussions about their past projects.
OnsiteStatistical ModelingSystem Design
Communication & Feedback
Candidates have reported issues with communication post-interview, including delays or lack of feedback after completing multiple rounds. This can lead to frustration and a negative impression of the overall process.