Real, anonymous reports from people who interviewed for Software Engineer at Tiger Analytics, newest first and distilled into what to expect across the loop.
Get your personalized Tiger Analytics Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My interview journey leaned heavily into a data-engineering style set of questions. After the initial steps, I got two technical rounds that focused on Python and PySpark coding with DSA of moderate difficulty. The scenarios also pulled in platform context, including Azure Data Factory topics, so I wasn’t only writing algorithms—I had to reason through how data workflows work in practice.
At times the technical questions felt fast and a bit argument-driven in the way the discussion moved, and I remember not feeling given much time to fully write out or iterate on query-style work. That pressure made it hard to show depth on the backend concepts I’d expected to be central, and I left with the sense that the evaluation wasn’t matching the level of detail I was trying to reach.
3 months ago
Average Neutral India
My interaction with Tiger Analytics mostly ended before the real interview work began. I was pulled in for what sounded like an initial screening stage, but the process didn’t really take off afterward, and I was ultimately rejected without a full set of interviews happening.
The feedback I received was vague and pointed more toward administrative or scoring outcomes—things like fit to timeline and assessment results rather than any detailed breakdown of performance. It left me feeling like there wasn’t much meaningful evaluation of my work beyond a couple of early signals.
5 months ago
Average Positive India
The process started with a recruiter screening, and then I moved into two technical interview rounds. Both rounds included LeetCode-style questions, a…
8 months ago
Average Negative Hyderābād
I went through a full multi-round process where I felt I answered thoroughly and stayed engaged through the technical conversations. The overall struc…
9 months ago
Average Negative Bengaluru
After my screening, I went through three rounds. The first started with basics and DSA, and it also turned into a discussion of my projects, so it was…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Rounds
Candidates can expect multiple technical interview rounds focusing on coding, data structures, and algorithms, with a mix of Python and SQL questions. The difficulty varies from easy to medium, with an emphasis on practical problem-solving and reasoning through trade-offs.
PythonSQLDSA
Behavioral & Managerial Discussion
The final stages often include a managerial round that assesses fit and alignment with the company's values, alongside discussions about past projects and real-world problem handling. Candidates should be prepared to articulate their experiences and how they relate to the role.
FitProject DiscussionValues
Assessment & Screening Process
The interview process typically begins with an online assessment or screening, which may include basic coding and SQL questions. Candidates should be ready for this initial evaluation as it sets the tone for subsequent rounds.
Online AssessmentScreeningBasics
SQL Focus
SQL questions are a recurring theme throughout the interviews, often requiring candidates to demonstrate understanding of complex queries, including joins, window functions, and data modeling. Candidates should be well-versed in SQL fundamentals.
SQLJoinsWindow Functions
Pacing & Pressure
Candidates report a fast-paced interview environment where they may feel pressured to provide quick responses. It's important to practice articulating thoughts clearly and efficiently under time constraints.
PacingPressureArticulation
Communication & Logistics
Many candidates experienced issues with communication and scheduling throughout the interview process, leading to uncertainty and frustration. It's advisable to seek clarity on timelines and next steps proactively.