A recruiter reached out on LinkedIn and discussed opportunities, arranging a phone screen. The phone screen was conducted by Karact and included system design questions related to load balancing rules, Google Docs design, and eventual consistency versus strong consistency. Following this, there was a coding question, which needed to be finished within 30 minutes, but this timeframe also required time for reading the question.
A few days later, I received an update from the recruiter and moved on to the next stage. This stage included three rounds: system design, behavioral questions, and a coding question.
The coding question focused more on the business logic of the platform. The questions were also very long, and time was tight, requiring the best answer within a limited period. All interviewers had joined within the last six months, and it's unclear why this was the situation. This gave me the feeling that I had behaved fairly, but I actually didn't meet their expectations.
The following metrics were computed from 75 interview experiences for the Robinhood Software Engineer role in United States.
Robinhood's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Robinhood's Software Engineer interview process in United States.