A recruiter presented me. A couple of days later, I received an email from an HR representative.
We scheduled a time to speak, and he was very punctual. During the call, he was very effusive about the company.
In an off-hand manner, he mentioned he would be sending me a coding test. The coding test arrived, and I was told I had 10 days to complete it, which seemed fair. However, I was cautioned that once I opened it, I had two hours to complete the test.
The coding test consisted of two questions. I had one hour to complete each.
I did not complete the first one in an hour. I think it is possible to complete it within that time if you don't have to look up methods and arguments on the internet. This assumes you complete the code in the first 30 to 45 minutes and then debug/polish in the remaining fifteen minutes.
My solution in my IDE was 150 lines long, including comments and whitespace. Omitting these could save time, but since I did not know if Roblox would see the code, I was unsure if I would be judged on style and documentation. The directions were silent on this matter, and I assumed they would see the code and I would be judged.
The second problem was not well-worded. Many details were glossed over; the description was terse and incomplete. If I had encountered the same problem in a face-to-face interview, I would have spent the first fifteen minutes discussing the boundaries and edge cases. Given it was an online test, I did not have that opportunity. Instead, I got to work, resolving to use the testing environment to answer my questions by printing the output from the runs.
The testing framework only indicates if your code passed or failed each test. Each test has a cryptic label, and you do not see the input or output. In effect, you are shooting in the dark. You cannot debug your code using the input to gauge the missing spaces in the problem specification, nor can you use it to see what the inputs are so you can debug the code in your IDE.
After my first run, I stopped working on the problem. The test framework advised me to 'develop more careful tests.' This would be effective if I knew what conditions to test.
I suppose I could have simply looked up the problem on the internet, but that did not seem honest. If you take the same test, I recommend doing just that. You will be under significant time constraints to solve the problems.
Would I work at Roblox given what I now know about their process? No, I would not. If the interview testing methodology reflects the company, then this is not a place I would choose to work.
The following metrics were computed from 1 interview experience for the Roblox Senior Network Software Engineer role in San Francisco, California.
Roblox's interview process for their Senior Network Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Roblox's Senior Network Software Engineer interview process in San Francisco, California.