Extremely political, with lots of people playing games to try and take credit for others' work or push blame around. At review time, one person deciding they don't like you can claim that you hurt their feelings one time, and based on anecdotal evidence alone, kill your promo or lower your rating. You are constantly walking on eggshells.
Code quality tends to be poor. To be fair, the product isn't exactly critical to the day-to-day operations of the world, and Facebook being down for a few hours isn't going to kill anyone. Teams focus on getting products out as quickly as possible with little concern for quality or maintainability. There is no QA department, and you will not be rewarded for taking extra time to make your project high quality.
Be more real. Everything management says comes through as though it's been through six layers of PR committee review. It sounds utterly harmless and sensitive to every possible listener. At the same time, it is usually utterly meaningless. It would be nice to see some direction and leadership instead of just feelzy tripe.
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