You will be exposed to a lot of new internal technologies and tools designed specifically for the work and development of Meta products. You will also face a lot of new technical challenges and will be required to think in ways to provide services and products to 2+ Billion users.
Obviously, there is a lot of opportunity to grow and make an impact, especially at such a scale.
Sometimes the product or service you are working on is not the most interesting. A lot of the time, if you are working on very legacy products or features, you will be required to work on top of very old code or refactor things that sometimes takes a while to figure out, especially because there are many very FB or Instagram-specific use cases.
There is a lot of bureaucracy within the company, and you feel like you have to show off the work you are doing or what kind of impact you are having by making posts regularly. This is one of the few ways to get noticed.
There is a huge focus on the type of impact you are doing, even if sometimes you cannot see this in a very concrete way.
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