Ho presentato la mia candidatura online. La procedura ha richiesto un giorno. Ho sostenuto un colloquio presso Meta (Menlo Park, CA)
Colloquio
I had chosen to go onsite for the facebook recruiting process, so I interviewed at the Menlo Park HQ office. For the first fifteen ish minutes their engineer asked me about my background, some interesting problems I had worked on on Android etc.
Then he asked me Leetcode medium question based on trees. I'm the sort of person who likes to take the time to understand the problem better, talk about possible approaches and agree on a solution, but in this case the interviewer seemed like he just wanted a solution as quick as possible. I took about 30 minutes to code and to test the edge cases. The code was perfect, and I was figuring out edge cases along the way by testing but the interviewer just kept interrupting me - giving me hints and edge cases and I hated that.
He then proceeded to ask me a second question - a variation of a leetcode medium question that can be solved in linear time by using a "trick". If you try to normally solve this problem the first time you're not going to solve it optimally or take some time to think about it (which is what happened to me). I told the interviewer the solution and I started to code, but could not finish the problem.
Needless to say next day I got a reject.
If you're going to do a phone interview at facebook this is what I have noticed (and feedback from friends who went through the same):
1) You need to finish Leetcode. There is no better way to say this but they want a monkey who can spit out code. They're really not interested in how you work your way through the problem or optimize it.
2) Don't waste time thinking about how to solve the problem. The interviewer will just scribble in their notebook if you do this and flag you for slow coding. Again - spit out leetcode.
3) You will either get 2 mediums or 1 easy - 1medium for a phone screen.
4) You are responsible for keeping track of time. The interviewer will not rush you but if you go over the 20 minute unofficial limit for leetcode mediums, bye bye.
This is not a company that care about how intelligent you are but how fast you can spit out code.
The technical round hit me with a classic array manipulation problem: moving zeroes to the end without disrupting the order of non-zero elements. As I tackled it, I felt a wave of familiarity wash over me; I had just practiced a similar challenge on PracHub. The rest of the interview followed a straightforward path, with some easy behavioral questions sprinkled in. Overall, it felt very easy, but I wasn’t quite the right fit for what they needed, so I didn’t receive an offer.
Domande di colloquio [1]
Domanda 1
Move zeroes in an array to the end while keeping non-zero element order, in place
1 leetcode med, 1 leetcode hard. make sure you know your DSA and leetcode questions. I wasn't able to get an offer bc i didnt complete the second question. Got a reply 2 days later saying they would move on
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Meta (Menlo Park, CA)
Colloquio
It's honestly striaght from leetcode tagged
There are no surprises if you do tagged you would be good and do well.
System design is much harder. Would recommend using hello interview.
Domande di colloquio [1]
Domanda 1
Design Twitter and consider if it was suddenly an extremely low latency env