My overall experience was frustrating.
The first part of the process was a take-home task: creating a test plan for a rider taxi application. It wasn't particularly difficult, but it was time-consuming.
The second part was a video call with a hiring manager who did not seem prepared for the interview. He had no idea about my previous experience, and even after I gave a self-introduction, he repeatedly asked me questions I had just answered. It felt like I was talking to myself.
The interview lacked structure. The manager jumped from one topic to another, which was frustrating, to say the least. We never discussed the take-home task, which I had spent a week working on, suggesting that it was not valued. He only briefly mentioned it once at the very end of the conversation.
The questions were too simple and basic, such as 'test any object you choose.' These are beginner-level questions.
From the conversation, it seemed the QA team does not have established processes. I was told that "every team does what they think is applicable." Furthermore, I was informed that there is no hierarchy within the team; it is organized "horizontally." I assume this would make promotions an issue.
I was not happy with the interview, but they surprised me further.
Instead of a standard rejection email, I received a generated "your application is declined" message after a video call with the manager.
Dear HR, I believe your candidates deserve more respect.
Create a test plan for any object you choose.
What features would you add to the object you chose?
How would you handle bad user reviews for the features you tested?
The following metrics were computed from 5 interview experiences for the Robinhood QA Engineer role in United States.
Robinhood's interview process for their QA Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having negative feelings for Robinhood's QA Engineer interview process in United States.