Good scale and exposure to interesting backend and distributed-system problems.
Diverse technology stack with opportunities to work across application, data, infrastructure, and production systems.
Remote work has been one of the biggest positives, although the company appears to be moving toward more office attendance.
Most engineers are capable, supportive, professional, and generally good to work with.
Leadership culture can be quite toxic. There is constant pressure to move fast, but engineering quality, maintainability, and technical debt do not always get the attention they deserve.
There is a contradiction between the expectation of fast delivery and the amount of internal process, dependencies, approvals, and coordination required, which often slows development significantly.
Work pressure is consistently high and work-life balance is poor. The environment can feel unnecessarily stressful even for experienced engineers.
Compensation is not very competitive compared with the workload, expectations, and market standards for similar engineering roles.
A large part of the platform still relies on an old monolithic architecture and legacy development patterns. Development environments and infrastructure are not always well organized, which leads to slower debugging, local setup, and feature delivery.
There is too much uncertainty around performance management and workforce decisions. This creates insecurity and makes it harder for engineers to focus on long-term ownership and quality.
Leadership should invest more in simplifying engineering processes, improving infrastructure, and reducing unnecessary pressure instead of pushing teams primarily on delivery speed.
Remote work is one of the strongest reasons many engineers would choose to join or stay, so removing that flexibility would make the company less attractive.
Compensation should be brought closer to market standards, especially considering the expectations placed on engineers.
Most importantly, improve leadership culture and create more stability around performance and workforce decisions. Constant pressure and uncertainty may produce short-term output, but they hurt morale, engineering quality, and long-term retention.
After recruiter’s phone call, there was a HM interview. The interview went quite well according to me. He was happy at the end of interview. But I received a rejection from their side. Since then I’ve been trying to connect with the recruiter to
Campus hiring process for motive: First an online assessment at CodeSignal. You have to solve every question and get the maximum possible score to be eligible. First actual round: Peer coding round 2 LeetCode problems, medium Final Hiring Manager
The interview process consisted of 5 rounds. 1. HR screening round Initial discussion about my background, experience, and why I was looking for a change. 2. Hiring manager round A deep dive into my previous projects and responsibilities. The discu
After recruiter’s phone call, there was a HM interview. The interview went quite well according to me. He was happy at the end of interview. But I received a rejection from their side. Since then I’ve been trying to connect with the recruiter to
Campus hiring process for motive: First an online assessment at CodeSignal. You have to solve every question and get the maximum possible score to be eligible. First actual round: Peer coding round 2 LeetCode problems, medium Final Hiring Manager
The interview process consisted of 5 rounds. 1. HR screening round Initial discussion about my background, experience, and why I was looking for a change. 2. Hiring manager round A deep dive into my previous projects and responsibilities. The discu