Tiger Analytics software engineer candidates report an online screen, SQL and Python or DSA technical rounds, and an HR conversation. Some also report Spark, Databricks, Java or database design rounds.
$113K
Avg. Base Comp
$130K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Tiger Analytics software engineer roles most often describe an online assessment followed by technical interviews and an HR conversation. The screen varies. Reports mention aptitude or quantitative MCQs, Django MCQs, SQL and coding problems. One candidate describes a roughly one-hour test, and another describes a 20-question MCQ followed by four problem-solving challenges.
SQL is the most repeated topic. Candidates mention ranking-style salary queries, including second-highest salary by department and third-highest salary. They also describe joins, window functions or subqueries, and a date-filtered department query. Two candidates mention Python fundamentals such as shallow versus deep copy, decorators, list versus tuple and list behavior.
Coding difficulty is described differently by different people. Some report easy-to-medium LeetCode-style problems, such as sum-of-digits variations and a base-conversion puzzle. One candidate describes a greedy problem, a harder dynamic programming problem on quadruplets and a NumPy or pandas deduplication task. Candidates who got offers talk about explaining their reasoning, optimizing from a working brute-force solution and justifying design choices.
Later rounds depend on the team. Reports mention Spark and Databricks questions, data lakehouse architecture, Java and Spring Boot depth, ER diagrams, and deep dives into resume projects and their architecture. These are followed by an HR round on behavioral questions and culture fit. One candidate described last-minute rescheduling, so confirm round formats and logistics with your recruiter.
Synthesized from 14 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tiger Analytics process.
The take-home assessment was the part I kept coming back to. The brief was to build a small application where users could add and delete products, and it had to support offline use. It sounds simple, but the offline requirement was the real test, and the team came back to that exact code later in the process.
The first round was a DSA session focused on problem-solving speed, logic, and core coding patterns. It was either a live coding session or a timed platform, and the emphasis was on recognizing the right pattern quickly rather than writing anything elaborate.
The round that caught me off guard was the assessment walkthrough. Instead of a new problem, an interviewer reviewed the solution I had submitted with me, so I had to be ready to explain every decision in code I had written days earlier. After that came a technical interview that covered my resume projects, core concepts, and practical problem-solving, and it went deeper into my past work than I expected.
The last two rounds were managerial. The first focused on past system architecture, trade-offs, tight deadlines, cross-team collaboration, and technical ownership. The final round was a more senior conversation covering scalable thinking, how I handled failures, long-term technical vision, cultural fit, and behavioral scenarios. I received an accepted offer at the end.
Prep tip from this candidate
Be ready to walk through your own take-home solution line by line, because the assessment review round went through it in detail. Bring specific examples of architecture trade-offs and failures from past projects, since both managerial rounds pressed on those areas.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tiger Analytics
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Closest SAT Scores | |
| Top 3 Users | |
| Find the Missing Number | |
| Get Top N Frequent Words | |
| Prime to N | |
| Maximum Profit | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Minimum Absolute Distance | |
| Production Model Monitoring | |
| Target Indices | |
| Median O(1) | |
| Transformer Encoder Layer | |
| Digit Accumulator | |
| Matrix Rotation | |
| Count Transactions | |
| KNN From Scratch | |
| Design a query-retrieval system | |
| Possible Triangles | |
| Yelp-like System | |
| Finding the Maximum Number in a List | |
| String Palindromes | |
| Cloud-Agnostic Deployments | |
| Deciding Between Solutions | |
| Minimum Directional Path | |
| k-Means from Scratch | |
| Area Under the ROC Curve | |
| Generative AI Privacy |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report being contacted by a recruiter or through a job portal. One describes a recruiter screen before technical rounds. Expect questions about your background, and confirm the role and team early.
Candidates report an online test that typically mixes aptitude or MCQs with SQL and coding. Reports include a roughly one-hour test, a 20-question MCQ set, Django MCQs, and one easy plus one medium coding problem.
Candidates report one to three technical discussions covering projects, Python or Java fundamentals, SQL window functions and LeetCode-style problems. Interviewers reportedly pay attention to how you explain your approach, complexity and edge cases. Some live coding happens on CoderPad.
Some candidates report deeper rounds on ER diagrams, Spark and Databricks, data lakehouse design, Spring Boot or past project architecture. These rounds likely vary by team, so prepare to defend design decisions.
Candidates commonly report an HR round covering introductions, motivation, behavioral questions and culture fit. Outcomes in the reports are mixed, with both offers and rejections at this stage.
