In general (i.e., I and most of my colleagues generally estimate for > 50% of the company):
Take care of your employees, otherwise, you might find yourself in a situation that can prove difficult to climb out of once too many engineers learn of the company's reputation.
Other than the treatment of employees and bad reputation being a major issue, many parts of the business are great and likely to do well in the long-term.
Coding + Behavioral questions: The interview will include a combination of coding challenges and behavioral questions, focusing both on your technical problem-solving abilities and on how you collaborate, communicate, and approach real-world team si
They hounded me via email for a matter of weeks before I consented. They gave me a take-home test over email, and it was really annoying. It was a difficult problem, and they really didn't give enough time for completion. It seemed like a terrible
OA: over 4 rounds, 3 hours + time 3 rounds of interviews, each containing 30 minutes of LP type questions and live coding experience. Mostly discussion, but no implementation required.
Coding + Behavioral questions: The interview will include a combination of coding challenges and behavioral questions, focusing both on your technical problem-solving abilities and on how you collaborate, communicate, and approach real-world team si
They hounded me via email for a matter of weeks before I consented. They gave me a take-home test over email, and it was really annoying. It was a difficult problem, and they really didn't give enough time for completion. It seemed like a terrible
OA: over 4 rounds, 3 hours + time 3 rounds of interviews, each containing 30 minutes of LP type questions and live coding experience. Mostly discussion, but no implementation required.