I had a really good phone tech interview at fb, I think I solved the problem very quickly and even had 50% working code. The interviewer asked if I knew the problem late to which I said no and then we carried on with coding. By the end had almost working code in place and also found a bug and solved that in time. Next thing I know is FB doesn't want to go ahead with the process. It sucks as I genuinely solved the problem first time. Did I miss something here?
I thought fb usually asks 2 questions for the phone screen and yes they expect you to code bug free. Was it a leetcode hard?
The process is pretty random. I bombed the first phone screen (DP problem) even though they explicitly told me no DP questions will be asked. They sent not moving forward email. Few weeks later they reached out if I want to do interview again, this time it's some non leetcode question. I did brute Force first and then optimized with the help of a hint. Wrote working code. Got an on-site. I only did that one question during the second phone screen. So I think what helped was that I did really thought out loud of all possible ways I can optimize it. Like it didn't see the question before so I had no option to but quickly think.
Did you pass the on-site?
I have to schedule it.
Nothing to do with FB. Happens all the time and happens to the best of us. Move on. Good Luck!
FB almost always expects two questions to be answered for the screen - usually easy/medium
Yay for us Oracle employees tired of their crap. I'm also interviewing at FB. Good to see this discussion. My screening interview is on-site. Then a follow-up full day if I progress.
I had quite a similar experience some time back with Facebook. I felt that I gave one of my best phone screens but still got rejected. I breezed through both the questions and it's variations and still had time left. For what it's worth, I do have a standing offer from Google, so I don't care a lot, but it did sting a bit.
Lol you're too naive. The expectation is much higher than solving just one qn with almost working code.
Most likely you had a second part to the problem that you were too slow to get to.
FB interviews are tough because you need to solve 2 leetcode medium problems in 30mins. The length of interview is 45mins but only 30 is for coding, they'll hard stop you and move in to bs like asking Qs etc. You need to have bug free complete working code, big O analyzed, then finish the 2nd problem bug free, complete code. I managed to almost get an offer from FB, so sad missed it by a bit.
Yeah it's a test for whether you have seen the question before I guess. Sometimes it takes to 5 mins to put your thoughts together, by then you are gone I guess
I think (and in my experience) fb expects you to code complete and bug free solution
I agree. In FB phone interview I was asked a LC easy which I coded full, second was LC hard, I was discussing solution, then interviewer asked me to write complete code.. I was struggling and he motivated me and asked me write as much as I could in the last 5 mins. I was selected for on-site.
Are you done with your on-site? How was the on-site difficulty Questions?