Perks and pay are top-notch. Some of the engineers are truly talented.
As the title says, FB is not for everybody, in my opinion.
The recent set of 1-star ratings list pretty much all the things that made me leave:
The work-life-balance issue goes beyond the mere hours. It is expected that you become FB friends with all your coworkers, managers, etc.
FB makes it impossible for the realm of your private life to remain separate from your workplace and coworkers.
This wasn't working for me, but I recognize that for others this isn't an issue.
It seemed to me that much that is broken at FB is perpetuated by the in-clique, and in fact gets sold as the great achievements of FB's unique culture.
Do what every other successful company your size does: train your managers so they can:
You're holding on to ideas that may have worked when you were a start-up (no code ownership, no planning, documentation?, tests?). Your so-called culture is a liability, especially if you let incompetent managers corrupt it to the opposite of the values you want to stand for.
Pretty standard. Just grind LeetCode. They basically want you to make zero mistakes and solve problems like a robot. They don’t really care about your thought process, just that you find the most optimized solution ASAP.
The whole process took about two months. It started with a 30-minute recruiter call, then a 90-minute online assessment with four questions. I didn’t have time to finish all four, but somehow passed that round. The next step was a technical screenin
Technical Phone Screen A 45-minute coding interview where you will solve one or two coding problems, focusing on optimal solutions, edge cases, and complexity analysis. Usually, more than two problems will be asked, and there will be follow-ups to t
Pretty standard. Just grind LeetCode. They basically want you to make zero mistakes and solve problems like a robot. They don’t really care about your thought process, just that you find the most optimized solution ASAP.
The whole process took about two months. It started with a 30-minute recruiter call, then a 90-minute online assessment with four questions. I didn’t have time to finish all four, but somehow passed that round. The next step was a technical screenin
Technical Phone Screen A 45-minute coding interview where you will solve one or two coding problems, focusing on optimal solutions, edge cases, and complexity analysis. Usually, more than two problems will be asked, and there will be follow-ups to t