A former colleague pointed me to the Data Scientist role at Robinhood, and I ended up going through an initial recruiter call followed by a technical screen. The SQL questions hit quickly and felt trading-analytics heavy: I worked through user trading volume using SQL, and I also got an A/B testing design prompt where they wanted me to lay out how I’d structure the experiment and interpret results.
After that, the process ramped into another technical-heavy step before an in-person/virtual follow-up. The experience overall felt intense and high standards; I spent a lot of time working through similar scenarios beforehand, and that helped me stay calm while the questions got more demanding. I remember it taking a few days between major steps, with the conversation quality and question pacing making the rounds feel like a real test of how I think under pressure.
> 1 year
Average Negative United States
I got far enough to clear an initial technical phone screen, but the process quickly soured afterward. The recruiter asked about my on-site availability, and then I never heard back despite my follow-ups. It felt less like a scheduling gap and more like I’d been dropped from the pipeline.
The disconnect was frustrating because the technical part itself had been manageable, but the human follow-through never materialized. I was left with no explanation and no clarity on whether the decision had already been made or whether the communication simply failed. The result was that the experience ended on a confusing, demotivating note rather than a clean close.
> 1 year
Average Positive United States
After reaching the assessment stage, my experience leaned heavily toward analytics workflows. One round had me walk through a churn-rate prediction sc…
> 1 year
Average Negative United States
My first step started before I ever spoke to anyone: I received a time-limited take-home challenge and was given a couple of weeks to finish it. The w…
> 1 year
Average Negative United States
My path started with an online technical assessment that was fairly time-consuming—once I got into it, I ended up spending around half a day completin…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Assessment & Take-Home Challenge
Candidates typically start with a time-limited take-home challenge focused on data extraction and analysis, which can be time-consuming and may include SQL components. Feedback on this stage is often minimal, leading to frustration.
Take-home challengeSQLData analysis
Technical Phone Screen
The technical phone screen often includes SQL and coding questions, with a focus on analytics and A/B testing scenarios. Candidates report varying experiences with interviewer clarity and engagement, impacting the overall assessment quality.
SQLA/B testingTechnical screen
Analytics & Modeling Focus
Interviews frequently emphasize analytics workflows, including model selection and interpretation of results from A/B tests, requiring candidates to demonstrate a thorough understanding of the processes involved.
AnalyticsModelingA/B testing
Communication & Follow-Up Issues
Candidates report significant issues with communication throughout the process, including delays in feedback and lack of clarity regarding next steps, which can lead to frustration and a sense of being left in the dark.
CommunicationFeedbackFollow-up
Overall Experience & Pressure
The interview process is described as intense and demanding, with candidates feeling the pressure to perform under high standards. Preparation is crucial to navigate the challenging questions effectively.
High pressurePreparationIntense
Inconsistent Evaluation Experience
Candidates have noted inconsistencies in how their technical skills were evaluated, with some interviews feeling mechanical or overly standardized, which may not accurately reflect their capabilities.