The opportunity that Facebook offers for autonomy and career growth is incredible. Coming in as a new grad PE, I have the opportunity to grow based on merit and performance, not time in the role.
Flexibility in when I work, how I prioritize my projects, and the scope of my work is invigorating and makes me excited to come to work each day. The company is mission-driven to a great extent, and I have been impressed with the way we have owned up to prior mistakes and fixed them head-on.
The Production Engineering role is well respected within the company, and the importance of reliability and scaling increases as our services reach more of the world. As a PE, you will gain the knowledge necessary to build and operate real hyperscale systems capable of providing services to billions of people.
My team is comprised of some of the smartest, experienced engineers I have ever met—some of which have been building Linux services since 0.01. Even though sometimes working at Facebook feels like drinking from the proverbial firehose, I am grateful I have the opportunity to learn from some of the top people in their field. For example, in bootcamp, I took a command-line efficiency class from Jim Meyering, one of the maintainers of coreutils and also a Facebook employee.
Many other people have commented on this, but the perks and compensation are still top-notch. The company helps take care of your life so you can focus on work while you're working.
Facebook hires the kind of people that expect a lot from themselves. Despite some reports, you do not need to work long hours in order to succeed at Facebook.
Bootcamp gives you the chance to find a team that matches you well, and new hires should come in intending to join a team where they can both find balance and grow in their career.
The company is growing, and there is some sentiment around slowing down, but most engineering teams are still bottom-up driven and innovating in their space. The things we are doing around privacy and AR/VR are on the bleeding edge, and we are strong leaders in these areas.
On the other hand, ironically, there is also sentiment around moving too fast as a company. Since we are people- and product-focused (as opposed to engineering-focused, like at Google), our primary goal is to impact the lives of people for good. Sometimes this means we opt for rapid prototyping over beautifully designed code.
However, we are doing much better at recognizing better engineering work, such as cleaning up code and improving monitoring, especially in the PE role.
As is the case with many large companies, some middle management fails to display leadership to a large extent. We should hire better senior managers and directors to embrace, evolve, and relay the company vision and values.
Total process around 2 months. First round: one coding interview and one Linux troubleshooting. Passed and moved forward to the full loop interview: - One coding interview - One CS fundamental interview - System design interview - Behavioral questi
The HR representative reached out unexpectedly, proposing the application. Everything looked promising until it didn't. I was ghosted after the phone screening call. There were no next steps and no follow-up email. I realized I had been filtered
45-minute interview, consisting of one coding round and one networking round. The coding round had two questions, which were pretty straightforward LeetCode style problems. The networking round focused on how ping works. You also had to design an e
Total process around 2 months. First round: one coding interview and one Linux troubleshooting. Passed and moved forward to the full loop interview: - One coding interview - One CS fundamental interview - System design interview - Behavioral questi
The HR representative reached out unexpectedly, proposing the application. Everything looked promising until it didn't. I was ghosted after the phone screening call. There were no next steps and no follow-up email. I realized I had been filtered
45-minute interview, consisting of one coding round and one networking round. The coding round had two questions, which were pretty straightforward LeetCode style problems. The networking round focused on how ping works. You also had to design an e