The company attracts genuinely talented people across all teams. The compensation is competitive with strong base salaries, and the work-life balance is quite good.
There's a generous health day policy of 5 days. The product itself is interesting and technically challenging, so you're working on something meaningful rather than just maintaining legacy systems.
Equity compensation feels increasingly meaningless as an IPO remains years away, making stock options essentially worthless paper.
The return-to-office policy is particularly frustrating, requiring a minimum of 2 days per week (12 days monthly) with unnecessarily complex tracking that nobody asked for. The policy appears driven by external investor pressure rather than actual business needs, as internal sentiment is overwhelmingly negative.
Management implemented this despite clear employee opposition, which raises questions about how much employee feedback actually influences decisions.
Listen to the employees.
I didn't make it through the whole process (I failed at one of the technical interviews), but up to this point, everything was nice and smooth. I received all of the required information from the recruiter, including an overview of the whole process
4 interviews: * Tech screen - implementing an API * Code review - find bugs in a service, it leans toward a systems design approach * System design - checks the basics, not predefined answers * Team fit - a discussion with the hiring team
The interview begins with a recruiter call where they will tell you more about the company, its mission, culture, along with ongoing projects and the technical stack. This is followed by a short review of yourself. Next up is a technical assessment,
I didn't make it through the whole process (I failed at one of the technical interviews), but up to this point, everything was nice and smooth. I received all of the required information from the recruiter, including an overview of the whole process
4 interviews: * Tech screen - implementing an API * Code review - find bugs in a service, it leans toward a systems design approach * System design - checks the basics, not predefined answers * Team fit - a discussion with the hiring team
The interview begins with a recruiter call where they will tell you more about the company, its mission, culture, along with ongoing projects and the technical stack. This is followed by a short review of yourself. Next up is a technical assessment,