Free food.
Pay is good.
Friendly people (faked sometimes, but not backstabbing in my experience).
Free gadgets from vending machines.
No real owners on code, so in theory, you can make changes to any team's codebase (it can backfire, though).
Up or out culture: if you don't get promoted to a certain level in a set time, you're fired.
Poor work-life balance due to the up or out culture.
If more seniors on your team are workaholics, you are compared against them harshly.
Oncall infra can be nightmare-inducing.
Again, you must really love what you do and your team if you want to be happy here.
It's difficult to move to another team if you get a 'Meets Most' rating in a half. HR won't help you since it's a hard rule (I think it was updated to 2 halves recently).
Aggressive goals can cost the health (physical and mental) of employees. People who just enjoy their work but don't love it will have a hard time with the constant threat of getting fired or stuck on a team.
Calibrations is only a 3-minute exposition per person. It's difficult to show the whole 6 months of a person's activities in that time. Also, the calibration bar seems to be pushed up by workaholics, so other people are reviewed more harshly.
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