Candidates describe a Tiger Analytics Data Scientist loop of an online assessment, several technical conversations and an HR round, with detailed project walkthroughs, Python, SQL and ML fundamentals at the center.
$128K
Avg. Base Comp
$150K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Tiger Analytics Data Scientist candidates describe a process that begins with a screening assessment and moves through technical discussions to an HR conversation. Reported round counts range from three to six, so expect some variation.
The most consistent theme is the end-to-end project walkthrough. Several candidates say interviewers wanted specifics on preprocessing, feature engineering, model choice, evaluation and the challenges they faced. One candidate was also asked about deployment, drift monitoring, missing-value handling with MICE and imbalanced data. Another described a dedicated project round focused on business benefit. Know every line of your resume.
The fundamentals are tested directly. Candidates mention string, list and dictionary Python questions, SQL such as second-highest salary or salaries above the average, and bias-variance, supervised versus unsupervised learning and evaluation metrics. Individual reports also mention XGBoost, Random Forest versus LightGBM, AUC-ROC, correlation, statistical tests and a stock-profit coding problem. One candidate saw NLP and transformers. The early assessment reportedly mixes Python, SQL and data-science multiple-choice questions.
Experiences are uneven. One candidate who was rejected felt the bar varied by interviewer, and another said a few questions, such as CI/CD, did not match the role. Practice explaining your reasoning aloud as well as writing correct code.
Synthesized from 12 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.
I went through six rounds at Tiger Analytics, and it was a mixed bag. The process started with a coding assessment on HackerEarth—seven MCQs and two programming questions, which were legitimately challenging and ate up my time. After that came a phone screening, then three technical rounds: the first was live coding Leetcode-style problems, the second was a use-case driven interview, and the third was labeled 'Team Matching.' There was also an HR round. On paper, it sounds comprehensive and thoughtful. In reality, something felt off. The technical questions didn't always align with what I'd expect for a Data Scientist role. One interviewer asked me about CI/CD pipelines and infrastructure—skills I don't have and the role doesn't require. The feedback suggested they were hiring for multiple different positions and hadn't clearly defined what they actually needed. Another positive note: one of my interviewers was genuinely engaged and excited about the company's direction in AI and Analytics, which did inspire some optimism mid-process. But the lack of coordination between HR and the technical team was evident. They scheduled me for rounds without seeming to understand what skill set the role actually demanded. By the end of the HR round, I was rejected despite having navigated a six-stage gauntlet. It felt less like a well-organized funnel and more like a series of unaligned evaluations.
Prep tip from this candidate
The process spans multiple rounds (coding assessment, phone screening, three technical interviews, and HR) with inconsistent skill mapping—candidates report being asked infrastructure and CI/CD questions that don't align with Data Scientist requirements. Focus on live coding problems and use-case analysis, but recognize that misalignment between HR's screening and actual role requirements may affect interview relevance and your odds regardless of preparation.
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 | |
| Top Three Salaries | |
| Top 3 Users | |
| Experiment Validity | |
| Find the Missing Number | |
| Get Top N Frequent Words | |
| Prime to N | |
| Normal Distribution Sample | |
| Maximum Profit | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Assumptions of Linear Regression | |
| Minimum Absolute Distance | |
| New Partner Card | |
| Missing Housing Data | |
| Production Model Monitoring | |
| Target Indices | |
| Median O(1) | |
| Digit Accumulator | |
| Bias - Variance Tradeoff and Class Imbalance in Finance | |
| Transformer Encoder Layer | |
| Count Transactions | |
| Matrix Rotation | |
| KNN From Scratch | |
| Possible Triangles | |
| Yelp-like System | |
| Finding the Maximum Number in a List | |
| Data Preparation for Imbalanced Data | |
| String Palindromes |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report an early assessment, with some naming HackerEarth. Reported formats include two Python problems, a SQL problem and data-science multiple-choice questions on topics like confusion matrices and bias-variance. Timing may be tight, so practice under a clock.
Candidates report an introduction followed by a first technical conversation. Reported topics include basic Python (strings, loops, dictionaries), SQL joins and aggregations, supervised versus unsupervised learning and evaluation metrics. One candidate was also asked to explain a past project and write time-series forecasting code.
Candidates commonly describe a more demanding technical round, sometimes led by a senior interviewer, centered on past projects. Reported questions cover EDA, model selection, deployment and monitoring, boosting algorithms, NLP and coding challenges. Interviewers appear to value clear reasoning and specifics over polished summaries.
Some candidates report a managerial, hiring-manager or team-matching conversation covering project experience, problem-solving approach and libraries used. One senior-level candidate described a VP discussion about current company work. Whether you get this round probably depends on the team and role.
Candidates report a final HR conversation on communication, career goals, cultural fit and, in some cases, compensation. Those who described it called it easier than the technical rounds. Outcomes differ: some candidates report offers, while others report rejections or slow follow-up.
