I had a positive overall experience interviewing with Kota. The team was friendly, professional, and the conversations felt engaging and respectful throughout the process. Communication with the recruiter was smooth and timely, and I got a good sense of the company’s vision and culture.
The only point of confusion for me was the final technical round labeled as a “System Design” interview. The format differed from the more typical system design structure that candidates usually prepare for (requirements → high-level design → APIs, etc.). Instead of a more open-ended “design a system” discussion, the interview was based on a fairly detailed specification, with an expectation to go deeper into specific parts of the system rather than focusing on high-level building blocks.
Because of this difference in format, the discussion felt a bit rushed at times. It may be helpful to clarify the expected structure and depth of the design discussion in advance, especially as the interview process evolves.
Pros:
- Friendly and professional interviewers
- Smooth and responsive communication
- Clear product vision and interesting problem space
Cons
- System design interview format not clearly aligned with typical expectations
Advice to Management
- Consider clarifying the structure and expectations of the system design round upfront
