Friendly team members, fast-moving company.
Cares more about speed than quality of product, expects you to work a lot.
The interview process included: * Two technical screens (coding, ML coding). * An onsite interview with four rounds: coding, debugging, system design, and a hiring manager interview. Coding questions focused on OOP and class orientation. The pr
A one-hour HackerRank challenge involving payment processing presented some easy questions. However, the output types were not provided, leading to significant time spent guessing what HackerRank expected. The question was split into multiple parts
HackerRank 1-hour OA. Very negative experience. Super long text description made it too difficult to understand. Unclear input types and misleading variable names. Split into 3 parts, but they all share the same function, and all test cases are mix
The interview process included: * Two technical screens (coding, ML coding). * An onsite interview with four rounds: coding, debugging, system design, and a hiring manager interview. Coding questions focused on OOP and class orientation. The pr
A one-hour HackerRank challenge involving payment processing presented some easy questions. However, the output types were not provided, leading to significant time spent guessing what HackerRank expected. The question was split into multiple parts
HackerRank 1-hour OA. Very negative experience. Super long text description made it too difficult to understand. Unclear input types and misleading variable names. Split into 3 parts, but they all share the same function, and all test cases are mix