This company is a body shop. There is zero work life balance. The executives and managers do not care much of their people. They keep pushing new projects on the employees and let them burnout. The company provides not only lunch but also dinner everyday. You know why? Because people have to work super late and the catered dinner saves them time from going outside to grub food.
The company has a solo focus on velocity. Engineers rush for new customer requests all the time and do not have time to architect or code properly. Priorities change every few days (yes, it sounds crazy). The former VP of engineering left the company because he did not agree with the company's over-emphasis on speed. Most of the engineering teams could not even plan a project of one month long. Most of the features are rushed and have accumulated a ton of tech debt, which has been causing a lot of damage now. If you are an engineer, you will not have the time to follow any of the best practices. Be prepared to become a lousy engineer if you work here for too long.
The recruiter was nice and candid about the poor work-life balance. My interviewer wasn't paying attention and was obviously doing something else on the side, so the interview experience was poor.
Clear expectations, thoughtful questions, and a collaborative tone. It covered system design, coding, and behavioral rounds. Interviewers were sharp but kind. It ultimately wasn't the right fit, or I would have taken it.
I was asked one question given in six parts. It was more design and implementation focused rather than algorithms/runtime heavy. They wanted to see how much code I could produce in an hour.
The recruiter was nice and candid about the poor work-life balance. My interviewer wasn't paying attention and was obviously doing something else on the side, so the interview experience was poor.
Clear expectations, thoughtful questions, and a collaborative tone. It covered system design, coding, and behavioral rounds. Interviewers were sharp but kind. It ultimately wasn't the right fit, or I would have taken it.
I was asked one question given in six parts. It was more design and implementation focused rather than algorithms/runtime heavy. They wanted to see how much code I could produce in an hour.