I had a phone screen interview with Facebook and I thought it went well, as I coded 2 questions in the 45 minutes. But surprisingly I got a reject email from them "Thank you for interviewing with Facebook. I received feedback from your technical screen and unfortunately, the feedback is not strong enough to progress to an onsite interview at this time. That being said, we would like to keep your resume on hand as future opportunities present themselves and we continue to grow. We certainly appreciate your interest in Facebook and encourage you to check back on our careers page for future opportunities. We value the time you have taken to find out more about opportunities within Facebook and wish you well in your career search. Please do keep in touch as you are eligible to interview after 1 year. We would welcome the opportunity to work with you again." What does it mean? How can I do better next time? Any Facebook recruiter/interviewee can help here?
Why do you think you were rejected? Did you solve both problems optimally? Were those seen problems and you failed to convey that to interviewer
Optimally yes. One was solved in o(n) and the other one with other o(1). The second problem its kind of similar to lru cache ( which I have seen) with no capacity or eviction. I haven't mentioned that I know lru cache since it's not exactly same, but solved it using a hashmap, linkedlist.
Don't take it too hard !!! It happens sometimes !!! Just keep practicing and applying ! You can do well in your phone screen interview but if the interviewer is not convinced that you can be a good fit or didn't do well comparatively to other (past) candidates , he won't give a strong feedback ! Good luck !
Did the interviewer give you hints? Did they point out bugs with your code?
Yeah he sounded pretty happy with the solution
But did he give you hints for you to arrive at the solution?
Sometimes I reject candidate even they "solved" the problem with optimal solution. There are something else other than just figuring out the solution.
What is it ? Might be helpful to know
For me, I look more on the actual coding. How you convert your thought into code, for example when you code, you're actually write your thought. If the code is mess, that either means you're not clear in your mind or you're not good at convert thought to code. But this is only my evaluation, people have different weights.
@wakao if you go with that logic, code is pretty neat and almost gives the solution but couldn't finish due other constraints, would accept it ?
That depends, I am just saying the priorities. Some people may focus on optimal solution without a hint. Some people focus more on bug free.
Damn this makes me more nervous for my fb phone interview coming up :/
You will be fine..don’t overthink
Post the questions and I will tell you what was the issue. For example, sometimes people don't know that there is a more optimal solution with O(1) extra space that modifies the input.
are you still around?
Bruh you just commented on a post from 2.5 years ago…
AFAIK, you can ask your feedback from recruiter. They can give you your full comprehensive feedback as we always submit in detail of every round
I had my phone screen yesterday and the recruiter has an update already, wants to talk on the phone, could this be good? Or are they going to let me know about a hiring freeze. ::update:: they couldn’t make a decision and have to do another phone screen, ugh, guess this is better than a rejection
Did you get to solving 2 problems?
Just 1, don’t know how they expect you to think through an entire problem. Code it, and come up with an optimal bug free solution so fast, guess it gives me more practice time at least
In how many days you were able to get a feedback
On the 3rd business day after interview
I didn't even received this email. They just ghosted me.