Tiger Analytics Software Engineer interview typically runs 3-4 rounds: recruiter screen, written test, technical rounds. It usually takes 1-2 weeks and is fairly straightforward, with broad technical coverage.
$105K
Avg. Base Comp
$171K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
We’ve seen Tiger Analytics lean toward a broad, practical screen rather than a deeply specialized one. Across candidate reports, the company repeatedly probes core engineering fluency in Python, SQL, and everyday problem-solving, with questions that stay mostly in the easy-to-medium range. What stands out is that they don’t seem to reward narrow memorization; instead, they want candidates who can move comfortably between coding, logic puzzles, and explaining the systems they’ve actually worked on.
A recurring theme is how much weight they place on stack-specific experience when it shows up. One candidate who spoke at length about Spark and Databricks still didn’t advance, which suggests that simply naming tools isn’t enough — they appear to care about whether you can discuss real implementation details and tradeoffs. We also saw a strong emphasis on Python fundamentals and framework knowledge, especially Django basics like decorators, middleware, view types, and data structure behavior. That mix tells us Tiger Analytics is looking for engineers who can operate in consulting-style environments where breadth, clarity, and applied familiarity matter as much as algorithmic polish.
Another subtle signal is the presence of straightforward but telling questions, like base conversion, 3rd-highest salary, and output prediction on Python edge cases. Those are the kinds of prompts that expose whether someone truly understands the language and can reason under pressure. Our candidates report that the process feels accessible, but not forgiving if you’re shaky on fundamentals or can’t connect your past work to the technologies they ask about.
Synthetized from 2 candidates 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.
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 | |
|---|---|
| Closest SAT Scores | |
| Prime to N | |
| Find the Missing Number | |
| Get Top N Frequent Words | |
| Minimum Absolute Distance | |
| Target Indices | |
| Median O(1) | |
| Matrix Rotation | |
| Possible Triangles | |
| Yelp-like System | |
| Finding the Maximum Number in a List | |
| String Palindromes | |
| Digit Accumulator | |
| Minimum Directional Path | |
| Maximum Common Substring | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Largest Salary by Department | |
| String Shift | |
| Raining in Seattle | |
| First Touch Attribution | |
| P-value to a Layman | |
| Minimum Change | |
| Size of Joins | |
| The Brackets Problem | |
| Top 5 Turnover Risk | |
| Delivery Estimate Model |
Synthesized from candidate reports. Individual experiences may vary.
The process typically starts with an initial recruiter call, sometimes after outreach from a recruiter or a job board source like Naukri. This stage is used to confirm background, experience, and basic fit before moving into assessments or technical rounds.
Candidates reported an online or written test that included a mix of aptitude, coding, and SQL. One experience had a single coding question plus around 20 Django MCQs, while another included basic aptitude, one easy and one medium coding problem, and relatively easy SQL.
The first technical round tends to focus on fundamentals and past experience before moving into coding. Interviewers dug into prior projects, Python/Django basics, and core concepts such as list vs tuple, decorators with arguments, multithreading, output prediction, and SQL basics like the 3rd highest salary.
A second technical discussion usually covers LeetCode-style coding and broader problem solving. Candidates described easy-to-medium difficulty questions, including logic puzzles like base conversion, along with follow-up discussion on coding approach and fundamentals.
Some candidates had an additional technical round focused on the tools and stack used in the role. This included deeper questions on Spark and Databricks, suggesting the interview can become more specific to the project or client technology after the general technical rounds.