Chaos In Codebase, Good Pay
Chaos In Codebase, Good Pay
Remote work and relatively good compensation.
Terrible codebase with a monolith where 150+ developers are checking in, resulting in a lot of chaos. And surprisingly, management is proud of this stupidity.
Microservices have nothing to do with code quality and scalability. They are aimed to simplify the work environment. If you want to keep this sadistic pleasure, keep continuing on this.
Additional Ratings
Was this helpful?
Apollo.io Interview Questions
Apollo.io Interview Experiences
Software Engineer
Initial screening through Coderbyte. There were 3 questions: two problem-solving and one React. Needed to solve all 3 within 50 minutes in order to move to the next round.
Senior Front End Engineer
The interview process consists of five rounds, each lasting 60 minutes, with 50 minutes dedicated to solving the problem: DSA & Coding Round – Solve three string-related problems, one of which involves building a basic React app. React Application
Staff Software Engineer
Oh man... A simple data structure question, and I passed the test cases as well as gave the right output. Shortly after that, I received a rejection email. No idea what went wrong.
Software Engineer
Bengaluru, Karnataka, IndiaMarch 11, 2025Initial screening through Coderbyte. There were 3 questions: two problem-solving and one React. Needed to solve all 3 within 50 minutes in order to move to the next round.
Senior Front End Engineer
Bengaluru, Karnataka, IndiaNovember 1, 2024The interview process consists of five rounds, each lasting 60 minutes, with 50 minutes dedicated to solving the problem: DSA & Coding Round – Solve three string-related problems, one of which involves building a basic React app. React Application
Staff Software Engineer
Bengaluru, Karnataka, IndiaSeptember 1, 2024Oh man... A simple data structure question, and I passed the test cases as well as gave the right output. Shortly after that, I received a rejection email. No idea what went wrong.
