Tiger Analytics data engineer interviews typically run three to six rounds built around SQL, PySpark, and platform-specific depth (Snowflake/dbt, Azure/Databricks, or AWS), plus scenario-based project discussions and an HR or salary conversation.
$124K
Avg. Base Comp
$145K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Tiger Analytics data engineer interviews in the reports here run from three to six rounds. They typically open with an online assessment, phone screen, or technical discussion and move into progressively deeper technical interviews, with an HR or salary conversation near the end.
SQL and PySpark are the most consistently tested skills. Candidates describe live SQL coding at an easy-to-medium level, explaining joins with examples, and PySpark coding questions. Deeper rounds probed Spark architecture: drivers and executors, DataFrames versus RDDs, the Catalyst Optimizer, lazy evaluation, wide versus narrow transformations, and how many jobs and tasks get created.
Depending on the opening, the technical rounds pivot toward the team's platform. Some candidates were tested heavily on Snowflake architecture and dbt practices, others on Azure and Databricks with Spark optimization, and one on AWS architecture. It is worth confirming the team's stack before the first call if you can.
Later rounds often turn scenario-based. Expect to defend ETL pipeline design choices, data modeling decisions for OLTP and OLAP systems, or the architecture of your own projects. One candidate noted that surface-level knowledge was not enough at that point. Another was told to expect two internal technical interviews before client interviews.
Two candidates reported long delays or silence after selection or after signing an offer, so follow up proactively and confirm next steps. Preparation should center on hands-on SQL and PySpark fluency, a clear narrative of your own pipeline projects, and comfort explaining trade-offs rather than reciting syntax.
Synthesized from 16 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 have currently completed 2 rounds and am waiting to hear back from the recruiter regarding the next steps.
Both rounds were primarily focused on Data Engineering, with a strong emphasis on SQL and PySpark. The questions were more practical than purely theoretical, so having a good understanding of how you would solve real data-processing problems is important.
SQL was one of the main areas tested, so I would recommend being comfortable with joins, window functions, aggregations, subqueries/CTEs, and writing queries to solve business-oriented problems.
PySpark was another major focus. Be prepared for questions around DataFrame transformations, joins, aggregations, performance optimization, partitioning, handling large datasets, and understanding how Spark works internally.
They also mentioned that AI/GenAI knowledge is an added advantage, so having a good understanding of concepts such as RAG, LLMs, and how AI can be integrated into data engineering solutions could help differentiate you.
One thing I would emphasize is not to prepare only for SQL and PySpark. Data Engineering fundamentals are important as well — ETL/ELT, data pipelines, data modeling, incremental processing, data quality, performance, scalability, and failure handling.
I felt the interviews were primarily evaluating whether you can think through real Data Engineering problems and explain your approach, rather than simply recalling definitions.
I haven't yet received feedback on the second round, so I don't know whether there will be another technical or managerial round.
Questions asked: I interviewed for a Data Engineer position at Tiger Analytics (U.S.) and have completed 2 rounds so far. I’m currently waiting to hear back from the recruiter.
The first round focused heavily on SQL, PySpark, and my recent project experience.
Some of the questions/topics I remember:
The project discussion was important, so I would recommend being able to explain your current project clearly from business problem → architecture → technologies → your contribution → challenges → outcome.
The second round continued with SQL and PySpark, with more emphasis on understanding the concepts rather than simply knowing syntax.
Topics/questions included areas such as:
They also mentioned that AI/GenAI knowledge is an added advantage, so experience with AI-based solutions can help differentiate you from other candidates.
For this role, I would prioritize:
SQL
PySpark/Spark
Data Engineering
Project discussion Be prepared to explain your most recent project in detail. They can go beyond the resume bullet and ask why you chose a particular technology, how the pipeline works, what problems you faced, and how you optimized it.
So far, my experience has been 2 technical rounds, with SQL and PySpark being the strongest focus areas. I’m currently waiting for feedback on the second round to know whether there will be another round.
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 | |
| Experiment Validity | |
| Top 3 Users | |
| Find the Missing Number | |
| Prime to N | |
| Normal Distribution Sample | |
| Maximum Profit | |
| Retailer Data Warehouse | |
| Get Top N Frequent Words | |
| Minimum Absolute Distance | |
| Missing Housing Data | |
| Assumptions of Linear Regression | |
| Target Indices | |
| Transformer Encoder Layer | |
| Count Transactions | |
| Design a query-retrieval system | |
| Data Preparation for Imbalanced Data | |
| Finding the Maximum Number in a List | |
| Median O(1) | |
| Digit Accumulator | |
| String Palindromes | |
| Matrix Rotation | |
| Possible Triangles | |
| Deciding Between Solutions | |
| Yelp-like System | |
| Cloud-Agnostic Deployments | |
| Minimum Directional Path | |
| Generative AI Privacy |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates started with an online assessment mixing SQL coding with multiple-choice questions on Snowflake, dbt, and Python fundamentals, or with a Snowflake architecture question. Another began with a phone screen. One candidate described the assessment as a useful baseline screen rather than a trick-heavy test.
Candidates describe a first technical round with live SQL and Python coding at an easy-to-medium LeetCode level, such as a problem similar to best time to buy and sell stock. This sits alongside questions on joins, data engineering concepts, and project experience. One candidate found this round friendly and conversational, while another faced CoderPad coding with scenario-based questions.
Candidates report a harder round focused on the team's platform. For some this meant deep Snowflake architecture and dbt questions. For others it meant Azure/Databricks and Spark optimization topics such as wide versus narrow transformations, lazy evaluation, and job and task counts. One candidate was tested on AWS architecture. Another said surface-level knowledge was not enough here.
Several candidates describe scenario-based technical rounds covering ETL pipeline design choices, data modeling for OLTP and OLAP systems, or their own project work. Interviewers expected the reasoning behind design decisions rather than definitions. One candidate also had a technical discussion with a VP that was more conversational but still rigorous.
The process typically closes with an HR conversation on role fit and salary expectations, and some candidates described a separate salary negotiation discussion. Some received offers at this stage. Two reported long delays or silence after selection or after signing, so confirm next steps and timelines once an offer is extended.
