Probably the most important thing about Facebook is the culture. Engineers are always free to solve problems when they see them. Generally there are no hard deadlines to meet, so you can almost always put something to the side when you think there's something more valuable to do.
If you find a bug in somebody else's project, fix it. If you have an idea for a useful feature, make it. We're willing to try anything once. The agility of Facebook is amazing, because all engineers are expected to be able to help out with anything. The org is very loose.
And the benefits are fantastic: free food, laundry, shuttle service from all over the Bay Area, and much more.
I frequently take a moment to consider what I would want to improve at Facebook, and I never come up with anything. I could see how, if you were somebody who really needed structure and direction, you could get frustrated. Facebook strongly encourages engineers to try working on new things every so often so that you're always learning, and also expects autonomy.
Never let Facebook lose its agility, and keep up the amazing transparency.
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