Tiger Analytics Data Scientist candidates report assessments and technical interviews covering Python, SQL, machine learning fundamentals, and detailed project walkthroughs, followed in some cases by manager and HR discussions.
$133K
Avg. Base Comp
$155K
Avg. Total Comp
3-5 rounds
Typical Rounds
3 weeks
Process Length
Tiger Analytics Data Scientist interviews reported by candidates repeatedly center on explaining practical work, not just naming tools. Be ready to walk through a project end to end: candidates describe follow-up questions on EDA, preprocessing, feature engineering, model selection, evaluation, deployment, monitoring, business impact, and the trade-offs behind those choices.
Technical screening varies by candidate. Reported assessments included Python and SQL problems alongside data-science multiple-choice questions, while technical conversations included Python data handling, SQL joins and aggregations, classification metrics, bias-variance, and ML algorithms such as XGBoost. Specific coding prompts included string containment, salary queries, and time-series forecasting. One recent candidate also described a GenAI-project discussion spanning RAG design, retrieval, scaling, cost optimization, evaluation, and hallucination mitigation.
Later conversations may go deeper on projects and problem solving. Candidates reported manager or HR discussions focused on communication, career goals, project experience, fit, and compensation. The evidence is drawn from a limited set of candidate reports, so individual sequences can differ. Prepare concise explanations of your decisions and results, then practice writing and explaining core Python and SQL solutions under time pressure.
Synthesized from 8 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.
It was the first technical round. It started with an introduction, and then I was asked to explain one of my previous projects end to end. They then moved on to a technical round, where they shared problems based on SQL and Python code. I answered the technical questions well but struggled to finish the Python code.
Questions asked: I remember being asked to write Python code for time-series forecasting.
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 | |
| Experiment Validity | |
| Prime to N | |
| Top 3 Users | |
| Find the Missing Number | |
| Maximum Profit | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Get Top N Frequent Words | |
| New Partner Card | |
| Minimum Absolute Distance | |
| Missing Housing Data | |
| Target Indices | |
| Production Model Monitoring | |
| Median O(1) | |
| Assumptions of Linear Regression | |
| Digit Accumulator | |
| Transformer Encoder Layer | |
| Bias - Variance Tradeoff and Class Imbalance in Finance | |
| Count Transactions | |
| Matrix Rotation | |
| KNN From Scratch | |
| Possible Triangles | |
| Yelp-like System | |
| Data Preparation for Imbalanced Data | |
| Finding the Maximum Number in a List | |
| String Palindromes | |
| SARIMA in Retail Forecasting |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an early assessment or first technical conversation that may combine Python and SQL with machine-learning fundamentals. Reported examples include data handling, loops, joins, aggregations, probability, confusion-matrix interpretation, bias-variance, and basic coding problems.
Candidates commonly report detailed questions about prior projects. Expect interviewers to probe preprocessing, feature engineering, model choice, evaluation, technical challenges, and how you reasoned through trade-offs rather than relying on a polished high-level summary.
Some candidates report a later technical round with more involved coding and applied ML questions. Topics reported include XGBoost, NLP and transformers, imbalanced data, AUC-ROC, deployment, drift monitoring, time-series forecasting, and SQL query writing.
Where reported, later non-coding conversations focused on project experience, communication, career goals, team alignment, cultural fit, and compensation. Candidates describe this as separate from the technical evaluation, though the exact sequence varies.
