Excellent culture, small team sizes, and move fast.
No scale and hard to move to different teams.
The interview process involved initial screens followed by an onsite component. The onsite behavioral questions were the usual. The company interviews in batches, which suggests cost-cutting measures. However, here are two reasons why I would not r
Overall, it was a good experience. It took almost two weeks from the first round to the offer and negotiation. The process included a standard four to five rounds: * Three problem-solving rounds * One design round * One recruiter round
I spoke with a recruiter at the campus career fair. He asked me a few data structure questions and then signed me up for an interview the next day. This interview included a few simple questions about arrays, programming languages, OOP, etc. The nex
The interview process involved initial screens followed by an onsite component. The onsite behavioral questions were the usual. The company interviews in batches, which suggests cost-cutting measures. However, here are two reasons why I would not r
Overall, it was a good experience. It took almost two weeks from the first round to the offer and negotiation. The process included a standard four to five rounds: * Three problem-solving rounds * One design round * One recruiter round
I spoke with a recruiter at the campus career fair. He asked me a few data structure questions and then signed me up for an interview the next day. This interview included a few simple questions about arrays, programming languages, OOP, etc. The nex