The phone interview process involved introducing myself, talking about my current work, a coding question, and five minutes at the end for asking questions to the interviewer. It was a very standard format.
The coding question was very easy, and I solved it. However, the interviewer was not communicative at all from the start. They introduced themselves briefly and, after I explained my projects, asked what seemed like irrelevant questions about my past projects, picking random keywords from my explanation (I suspect they were not fully present when I was talking).
During the coding question, it felt as if I was talking to a wall. I solved the question completely, matching their test case output, discussed the space and time complexity, and performed optimizations on my own. Nevertheless, the interviewer offered no input, and their interaction was extremely limited.
It's frustrating to do everything correctly and be rejected because the interviewer was aloof, disengaged, and disinterested. That's an hour of time I'll never get back.
Coding question: Iterate through a list of trades and transform it to output a list of buy/sell pairs. Also, calculate the overall profit while doing so.
The following metrics were computed from 4 interview experiences for the Robinhood Software Engineer role in Palo Alto, California.
Robinhood's interview process for their Software Engineer roles in Palo Alto, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Robinhood's Software Engineer interview process in Palo Alto, California.