Robinhood Software Engineer Interview Experience — Referral Graphs and a Job Scheduler

The applicant reports completing Robinhood’s three-hour onsite across three separate days. A referral-count coding problem went smoothly, but the project discussion was harder: the applicant struggled to explain the system’s complexity and scalability after the interviewer exhausted questions about business logic. The report advises preparing useful starting points for a deeper technical conversation.

The final session covered a distributed job scheduler, despite the applicant having concentrated on stock-platform design. Follow-ups examined the queue choice, queue failures, and delivery of notifications to subscribers. The described scheduler also required one-time and recurring work, deadline reporting, and at-most-once execution for each scheduled run. The applicant could not fully answer the follow-ups and reports rejection, while identifying the project discussion and system design as their weakest sessions.