Internal tooling: Coming from Microsoft, the internal tooling here is nothing short of incredible. Everything just works, and it's mostly consistent throughout the entire company.
There are also lots of internal services that are really helpful: services for deployment, managing configuration, A/B testing, etc. Because everyone uses the same tools, everyone invests in them, and they're well-documented and easy to learn.
People: Everyone I've worked with is really smart and happy to lend a helping hand. Haven't had any issues so far.
Work: I've enjoyed the kind of problems that I get to solve at Facebook much more than the kind of problems I got to solve at Microsoft. I worked on four different teams at Microsoft. The problems here are more challenging and require scalable, efficient solutions.
Culture: The culture here is fantastic. Internally, there is a lot of transparency. There isn't too much politics. You can make improvements on part of the codebase. There isn't much process to slow you down. There is a lot of individual freedom in what you prioritize and work on.
Work-life balance: I've had great work-life balance here. I typically work 35-40 hours a week, and I've not once stayed late for dinner. On-call is pretty light—much easier than on-call at Microsoft. This might vary by team.
Food: Really good food. Lots of healthy options (and unhealthy options if you want a cheat day).
Benefits: Pretty happy with the benefits. The transportation options are really good. The baby benefits are great.
Keep up the good work!
I had a behavioral interview, then a coding interview, which was the more difficult portion. For the coding interview, there were two rounds with the same interviewer. The second round was about 45 minutes long and included two questions.
I interviewed specifically for an iOS engineer role. The entire process took about a month and a half. It could have gone faster, but I had a long vacation between the phone screen and the on-site interview. The phone screen was very standard, featu
Phone Screen Interview: The interviewer asked a LeetCode hard question. I explained my thought process. I wrote pseudocode and then coded. My code was running fine, but it was missing some corner cases. I didn't have time to run it on test cases.
I had a behavioral interview, then a coding interview, which was the more difficult portion. For the coding interview, there were two rounds with the same interviewer. The second round was about 45 minutes long and included two questions.
I interviewed specifically for an iOS engineer role. The entire process took about a month and a half. It could have gone faster, but I had a long vacation between the phone screen and the on-site interview. The phone screen was very standard, featu
Phone Screen Interview: The interviewer asked a LeetCode hard question. I explained my thought process. I wrote pseudocode and then coded. My code was running fine, but it was missing some corner cases. I didn't have time to run it on test cases.