Comp is good, work can be interesting.
Hiring bar seems lower than places like Google or Facebook, especially for experienced hires.
No concept of work-life balance. The company survives by the "heroics" of engineers who work nights and weekends to get features ready. This is normalized by leadership celebrating the work of these engineers instead of accepting that every time engineers have to pull these heroics, it means that management has failed. With that being the culture, it's expected that you'll work long hours and sometimes weekends when there's an important project. People will ping on Slack at all hours.
The company is extremely sales-driven, and work gets prioritized based on what will sell, not what is best for the quality of the product. Management claims to have a long-term quality focus, but it keeps getting deprioritized for features.
While main projects can be interesting, there's a lot of grunt work involved in customer issues and small fixes (much more than at my previous companies). This is because the quality of the product, code, and tests are low, which leads to issues being found in production.
Very bureaucratic for a company of its size. A lot of process is involved when making small fixes.
Stop celebrating heroics and start admitting responsibility for them. Stop prioritizing features over quality.
The interview process involved: * 1 recruiter screen * 1 live coding screen (somewhat similar to LC snapshot array) * 5 rounds in the onsite, including: * 1 behavioral * 2 OS concurrency/mutual exclusion * 2 DSA The intervie
The interview process was very smooth. Recruiters were communicative, but you might have to push them a bit. In general, if you perform well, the manager will be after you.
Very much like any top engineering company – a good code test. I think it was clear they were looking for engineers that could deal with a lot of complexity and ambiguity.
The interview process involved: * 1 recruiter screen * 1 live coding screen (somewhat similar to LC snapshot array) * 5 rounds in the onsite, including: * 1 behavioral * 2 OS concurrency/mutual exclusion * 2 DSA The intervie
The interview process was very smooth. Recruiters were communicative, but you might have to push them a bit. In general, if you perform well, the manager will be after you.
Very much like any top engineering company – a good code test. I think it was clear they were looking for engineers that could deal with a lot of complexity and ambiguity.