Good money. Scale is big, so you will learn about distributed systems, but most likely you will be working on DB migrations and legacy code patching.
Bad tooling for engineers.
Bad RSU vesting structure (only 5% vested in 1 year, after which they put you on a performance improvement plan to save most of the stock growth profit).
Hire-to-fire policy. You will be hired and deliberately given a vague project so you fail to meet the deadline and are put on a performance improvement plan (mandatory 10% quota for focus, a mentorship plan, and 5% for PIP - performance improvement plan, which is like an ultimatum to leave the company right away or after 1 month with less or no severance pay).
Confirmed by a manager that they have to put employees on focus and performance improvement plans otherwise, they lose their job.
Code revision statistics, like counting the number of revisions it takes you to push code, are used against you to show that you are not performing well, so you have to get your Git merge request correct the first time.
The manager has too much power. They can block internal transfers and put you on focus for taking a vacation anytime.
Frugality is supposed to be a factor for designing systems but is plaguing the employees, leading to employees being unable to expense even a headset.
Please eliminate mandatory URA quotas and remove the "Do not rehire" flag for employees who have been abused by this system.
Coding + Behavioral questions: The interview will include a combination of coding challenges and behavioral questions, focusing both on your technical problem-solving abilities and on how you collaborate, communicate, and approach real-world team si
They hounded me via email for a matter of weeks before I consented. They gave me a take-home test over email, and it was really annoying. It was a difficult problem, and they really didn't give enough time for completion. It seemed like a terrible
OA: over 4 rounds, 3 hours + time 3 rounds of interviews, each containing 30 minutes of LP type questions and live coding experience. Mostly discussion, but no implementation required.
Coding + Behavioral questions: The interview will include a combination of coding challenges and behavioral questions, focusing both on your technical problem-solving abilities and on how you collaborate, communicate, and approach real-world team si
They hounded me via email for a matter of weeks before I consented. They gave me a take-home test over email, and it was really annoying. It was a difficult problem, and they really didn't give enough time for completion. It seemed like a terrible
OA: over 4 rounds, 3 hours + time 3 rounds of interviews, each containing 30 minutes of LP type questions and live coding experience. Mostly discussion, but no implementation required.