Roblox is extremely thorough in their interview process, where Ning is the only company where I've experienced a more challenging set of interviews. Structurally the interviews were most similar to Amazon but with a greater range of hands-on coding/architecture/design exercises but no evidence of a "bar raiser". The use of an IDE for the coding exercises was a welcome change from the usual Silicon Valley "whiteboard" format and it felt like a much clearer proxy for real-world performance. One of the C++ coding exercises particularly stood out for this as the IDE/compilation loop allowed me to submit a complete solution within a very limited time frame (and where the interviewer was understanding of the limited trial-and-error required). To anyone considering an engineering position at Roblox: this team is looking for "navy seals" so prepare appropriately. I'd recommend reading "Hello, Startup: A Programmer's Guide to Building Products, Technologies, and Teams" especially if you're not already on a world-class team and practice intermediate(+) coding exercises in an IDE (Hackerrank or something similar) so you're well prepared (as fluent as possible in the target language) for the coding questions.

One call with recruiter who reached out on linked in. Then a call with a senior manager which was moderately technical. Then after confirmation of follow up i.e. being to asked to schedule another interview, there was no response despite several emails / phone call. Only contacted back a couple months latter by another recruiter. Got to know the earlier recruiter left and the only means to track were her notes. Scheduled another interview with the same Senior manager, only to find out it was incorrectly scheduled and should have been done with some one else. Finally another coding interview scheduled with one person via hacker rank, turned out to be two people which seemed a bit too much down to earth, to the point that it felt rude. No introductions or other starters, rather quickly jumped to a coding question. Was asked a not so unique coding question. I clearly outlined the first immediate though out n^2 solution as well as the better O(n) solution and asked which one they want. The answer was weird "Its okay to attempt the O(n^2) one if you are not sure you would finish in time". So i implemented the n^2, struggled a little with one test case, but fixed it. Then outlined the O(n) solution but there wasn't enough time (Strictly 45 min) and they abruptly finished. Received rejection latter. Bottom line, especially when recruiting for a manager, if you want an O(n) only, why waste time asking some one to code a less efficient one. Why not just be clear with what you want as a bar to pass the interview. I might have been able to finish the more efficient solution in time too. But when given the choice, i picked up the easier to code one. To me that shows lack of prep before an interview. Combine this with the previous scheduling experience, this leaves a pretty bad impression of the company