Great compensation and perks.
Chance to meet awesome professionals and learn from them.
Great to list on CV.
Chance to see and work on services used by billions of people.
Great chance of career growth if you are a junior or mid-senior engineer.
The performance review process (called PSC) is frustrating. It feels like it's very hard to improve your rating or get a promotion at a senior level. It's more about being liked by the manager and getting a great scope to work on.
The code quality is surprisingly abysmal. I would again blame the PSC structure.
Most of the codebase is unowned or even abandoned and not documented. To accomplish anything, there are a lot of painful processes to go through. Consequently, the coding experience is quite bad.
Surprisingly, this is no longer a company where SWE is the ideal role. Nowadays, it's much better to be an Engineering Manager, as they get rewarded mostly for team impact, but they don't need to prove correlation. So, they can just cuddle a few high performers and make the bad ones' lives miserable so they'll change teams fast. The hardest part of being a manager, helping reports' careers, is really not a thing at Meta (for senior engineers).
I was contacted by a recruiter for a London Software Engineer position. There were 4 interview stages. After a week, I received a rejection email from the recruiter. Conclusion: solve a ton of LeetCode problems, especially medium, and prepare to l
90-minute technical interview that consisted of 4-5 moderate to difficult questions. The recruiters I liaised with were very nice and encouraged me to apply again despite being unsuccessful the first time around, as they said this was very common.
For phone screening sessions, before the virtual onsite. Leetcode questions, about two questions at medium levels within 45 mins. The interviewer asked about time complexity and space complexity. The interviewer doesn’t give much hints but is calm an
I was contacted by a recruiter for a London Software Engineer position. There were 4 interview stages. After a week, I received a rejection email from the recruiter. Conclusion: solve a ton of LeetCode problems, especially medium, and prepare to l
90-minute technical interview that consisted of 4-5 moderate to difficult questions. The recruiters I liaised with were very nice and encouraged me to apply again despite being unsuccessful the first time around, as they said this was very common.
For phone screening sessions, before the virtual onsite. Leetcode questions, about two questions at medium levels within 45 mins. The interviewer asked about time complexity and space complexity. The interviewer doesn’t give much hints but is calm an