I was interviewed by a team with different skill sets and expectations than the role I was being interviewed for. Throughout the process, interview schedules were a complete mess, with interviews being rescheduled multiple times, often with very little notice.
I passed the Hiring Manager screen (the interviewer was a Principal Engineer from a different but related team). They acknowledged and set expectations that the interview process could easily get drawn out and last about 8 weeks.
The Technical screen that followed (again with multiple reschedules) was one of my worst interview experiences.
Skipping introductions, the interviewer pasted the CodeSignal link in the Zoom chat and then went about doing something else. They did not even care to walk me through the problem. I basically started reading the question out loud, going about my thought process on how to approach the problem (felt like talking to myself), and started coding out the solution.
Once I wrote the solution, the interviewer read through my code and bluntly told me that the code had glaring issues and would never work. Then there was silence. No hints, pointers, or any other feedback.
The lack of engagement from the interviewer made me really uncomfortable, and I couldn't focus too well on coding out the solution. I had quite a few bugs, especially with handling special cases.
However, my general algorithm and choice of data structure were in the right direction.
At the 45-minute mark, I requested the interviewer to end the interview to save myself from further misery.
A little different from your average LeetCode problem, but it wasn't too hard.
The following metrics were computed from 2 interview experiences for the Roblox Data Engineer role in United States.
Roblox's interview process for their Data Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Roblox's Data Engineer interview process in United States.