Real, anonymous reports from people who interviewed for Software Engineer at Tiger Analytics, newest first and distilled into what to expect across the loop.
I didn’t really get a true interview experience. I expected a call, but the interview never materialized, and eventually I was rejected. The feedback, when it came, pointed to factors like a longer notice period than expected and weak scores—both the interview scoring and an assessment score weren’t good enough.
After a recruiter screening, I went into two technical interview rounds. Both rounds leaned heavily on coding: I remember doing LeetCode-style questions, and the difficulty landed around easy-to-medium. Between the questions, they tested how I reasoned through problem-solving and how well I could apply basic concepts in a more practical way, not just recite theory.
The interview process typically consists of an online assessment followed by two to three technical rounds and an HR round, with a focus on technical depth and practical application. Candidates reported varying experiences with communication and scheduling, leading to some frustration regarding clarity and closure.
Technical interviews emphasize coding skills, often involving LeetCode-style questions and practical coding tasks that assess problem-solving abilities and understanding of data structures and algorithms. Candidates should prepare for a mix of easy to medium difficulty questions that require both theoretical knowledge and practical application.
SQL proficiency is a significant focus, with candidates expected to demonstrate their ability to write queries and understand database concepts. Questions often cover SQL joins, views, and practical applications, making it essential for candidates to be well-versed in SQL fundamentals.
The HR round typically assesses cultural fit and alignment with role expectations, often involving discussions about past experiences and motivations. Candidates noted that the HR discussions could sometimes feel misaligned with earlier technical evaluations, impacting overall candidate experience.
Candidates reported a range of experiences regarding interview difficulty, with some finding the process mentally demanding and others feeling that the evaluation did not correlate with their effort. The overall experience varied, with some candidates expressing frustration over communication and feedback post-interview.
Candidates emphasized the importance of strong foundational knowledge in programming languages and concepts, particularly in SQL and Python, to navigate the technical rounds successfully. Many suggested that understanding the role's requirements and preparing accordingly could improve outcomes.
