So I recently gave an interview at Roblox, not with the intention of leaving FB, but wanted to get an experience of job interviews since I got into FB as an intern and never gave a job interview. They took 6 rounds. One was the karat interview where they asked some DS/algo questions, once that was done, they took 5 onsite virtual rounds. I thought all 5 rounds went pretty well. 1 was system design, 1 was with a tech director, 2 coding and 1 hiring manager. For the coding rounds, I ended up writing all the code with all test cases passing. For system design, the interviewer seemed happy (he didn't ask too many questions, nor did he tell me if my approach was bad, so either he didn't show any interest, or he was just happy). But I got a reject from them and the recruiter told me that the interviewers wanted to go more in depth in the interviews, whatever the hell that means. Does it mean that for the coding rounds, they wanted me to solve more questions? If so, would have appreciated if the interviewer would have told me that he would ask around 3-4 questions, i would have adjusted with that pace. #engineering #software
Tech Industry
Yesterday
1369
😞 Girlfriend help! 😞
Tech Industry
Yesterday
2899
Are tech workers as rich as they think we are?
Tech Industry
Yesterday
3512
I took a stand and got terminated lol
Layoffs
Yesterday
3088
Half of Google employees and prolly also Apple Amazon Meta don’t do any work…
Tech Industry
Yesterday
331
Help Needed: Choosing Between Offers
Interesting. How many questions did you solve in each coding round ? Also, how hard were the questions ? Medium or hard ?
Different topic: Is that how we calculate the total rounds? I would say it’s just two rounds - karat and onsite
I would rather work in fb Glad u didn’t like them
Why is that?
The only reason to join them is their potential IPO.
Should look up other threads regarding interview. They said the same
For the Karat interview, they asked 2 coding questions, I would say they were leetcode medium level. For the 2 onsite coding interviews, I did 1 question in both interviews. Considering that it was interview environment, for 1 of the interview, I think it would be somewhat in between medium and hard, and for the 2nd interview, it was medium level. I did both questions with little to no help. Interesting thing is that for the 2nd interview, the interviewer kept on asking me to run a lot of edge cases and all of them passed, and then told me if I had any questions, that process of asking questions about company and running edge cases took around 20 mins, so we could have definitely squeezed in 1 more question. There wasn't any need to ask questions about the company in all the rounds, it was just a time waste. Personally, I think they wanted to ask more coding questions, but how would I know what they want. If they could have told me that its just a warm-up question, I would have adjusted my pace according to that. In any case, I don't think checking for speed is the right test. But overall interview experience was good, they didn't ask me any stupid algo questions
Little tip: proactively testing edge cases yourself is a huge plus and expected at more senior levels. It wouldn't be enough for my team to reject if this was missing from an intern or entry level, but still a good strength you can add yo your skillet before you have an interview that matters to you
it's not as simple as just getting the code right. they expect you to proactively talk about your decision making in both code and system design. for roblox interview, it's not just about whether you can write code or not. they also want to see how you can take things to the next level
I guess its not just for roblox, its for any company. Everyone wants to see how you can take things to next level. But in any case, i was very vocal in my approach. I think they just wanted me to solve more questions, I mean that's the only reason I could think of. In any case, it was just good getting into the interview envt after almost 3 years
Move on. If you did these many rounds it’s probably the last one or two. Also you don’t expect the recruiter to tell you the real reason why you are rejected. It’s probably just the hiring manger or director have a different background.
How was the system design?
it was normal I would say, interviewer wanted me to first think about what features the product will have, then we wrote down some apis and created classes. Once all that was done, he asked me what would the database look like and on which columns we can do indexing, so in my opinion it went well
The training for interviews is low at most companies so I wouldn't take it personally. If you're solving two questions in the interview, thats definitely sufficient. If you're getting one done, take an introspective look at the difficulty of the questions and ask yourself if it was the "warmup" question or the "actual" question. Sounds like this could be speak for either they wanted faster coding or that they suck at interviewing