The interview process began with a recruiter email scheduling a phone interview. I was rescheduled with another recruiter at the last minute.
It was clear the recruiter I spoke with spent zero time reading my resume, as she kept getting simple details wrong that I had to correct her on (e.g., what school I attended, details about my projects/experience that were clearly written).
As a candidate who spent several days/hours preparing for the screen, it is disrespectful to talk to someone who spent no time at all getting simple details about the candidate you're talking to correct.
I then received an invitation for a coding test. The coding platform (TestDome) is horrible, and the formatting of the questions was very poor.
The question/examples were presented as one large block of text with no line breaks, making them very hard to read. Furthermore, it didn't even allow me to copy/paste the question to a text editor to make it easier to read.
The instructions for the test were very unclear. I did not realize until several minutes in that we are allowed and expected to use STL for the test. Much of the test involves figuring out what library to import and use.
When you run the code, it is tested against several test cases with bad naming (e.g., "backity back") that you cannot see the output for.
Not only is this unrealistic, but it means you have to account for any error that may go wrong with the program, and the instructions don't tell you how to handle cases that may throw these errors. For example, if the program should only take alphabetical characters, the question gives no instructions on how to handle numeric input when you know it's probably one of the test cases.
Since you cannot see the output, you are left guessing on whether you are returning the correct error value or if you are even passing a correct test case.
Overall, this was a pretty bad interview experience. Things were timely, but the recruiter was a bit rude, and the coding platform and questions were quite poor and could have been phrased much more directly.
A string counting question and a question to implement CD, which is really just a string parsing question.
The following metrics were computed from 60 interview experiences for the Roblox Software Engineer role in San Mateo, California.
Roblox's interview process for their Software Engineer roles in San Mateo, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Roblox's Software Engineer interview process in San Mateo, California.