Robinhood Backend Engineer Interview Experience — Scheduling, Project Discussion, and an Interrupted Coding Round

I entered Robinhood’s mid-level backend process through a September referral. The phone screen involved referral counts and a leaderboard; nerves cost me a few minutes on a small coding mistake.

The virtual onsite had three rounds. For the project discussion, I prepared slides with operating figures, a timeline, and a design diagram, then annotated the diagram while presenting. Follow-ups explored synchronous versus asynchronous work, consistency, conflict, and failure.

The design exercise was a scheduler limited to cron jobs with at-least-once delivery. After clarifying requirements, we discussed monitoring, logs, an independent watchdog, object storage, and transaction/outbox improvements.

The coding round covered fractional shares and inventory. A connection failure took about ten minutes. Its logging extension needed to describe transactions from the system’s perspective, such as a sale when a customer bought shares. The logs did not need to run.

Familiar questions helped throughout. I recommended practicing recurring topics and using AI to rehearse design and project discussions; my report did not announce a final offer.