The process included a take home challenge as a first step and a round on describing how the challenge was approached.
Team is not that technically strong based on the discussions. I had a bug in code and I highlighted the reason for the bug, no one from the team was able to debug it together to solve the problem. However I resubmitted it with solution.
It was a 2 hour coding challenge with asynchronous programming. In the description of the assignment it was said that "We're not looking for perfect, production-ready code". And the rejection reason that I got was coding standards are not at a level that they are looking for. I highlighted the parts of the code that can be improved and there is no proper response on that.
This is ridiculously a waste of time to interact with the team, but got a refresh on asynchronous programming.
The task is a take home challenge on asynchronous programming.
The following metrics were computed from 1 interview experience for the Ro Software Engineer Data Infrastructure role in United States.
Ro's interview process for their Software Engineer Data Infrastructure roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Ro's Software Engineer Data Infrastructure interview process in United States.