ZS Associates Data Analyst (often titled BTSA I) interviews typically combine an online aptitude or case-based screening test with three to five rounds covering SQL, business case analysis, guesstimates, and behavioral questions.
$84K
Avg. Base Comp
$105K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
ZS Associates' Data Analyst interviews, often reported under the BTSA I title, typically open with an online assessment covering aptitude and verbal reasoning, and in some processes a case-based screening test. One candidate instead started with an HR screening. From there, candidates describe three to five rounds, and SQL is the most repeated technical skill across the reports. Candidates were asked about joins, window functions, delete queries, sorting optimization, and how they structured databases in their own projects.
Beyond SQL, expect guesstimates and logic puzzles: one candidate compared a prompt to the 8 queens problem, and another described an hourglass puzzle. Expect a case study or case interview too, where you analyze a business scenario. One report described a profitability case at a food outlet, with the follow-up case interview building directly on the written analysis. Several candidates also described resume deep-dives and HR rounds with behavioral and situational questions, including direct prompts like "why should we hire you" or "why ZS." Outcomes varied: some candidates accepted offers and called the process welcoming, while others were rejected or found back-to-back, same-day scheduling exhausting. Treat each report as one candidate's path rather than a fixed script, and prepare broadly across SQL fundamentals, case reasoning, and quick mental-math puzzles.
Synthesized from 9 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 Zs Associates process.
The hardest part of my ZS Associates Data Analyst interview was that it felt a bit uneven from the start. I had to reschedule twice, which honestly made the process feel less professional than I expected, but once the interviews actually began, the content itself was pretty straightforward. My process had two test rounds that were non-eliminating, and those were mostly aptitude-based. After that came the main interview rounds, which in my case were a mix of case-style discussion and a more traditional interview. I was also asked a couple of basic personal questions, including why they should hire me and a brief introduction about myself, along with some family background questions that felt more conversational than technical.
On the technical side, the interview was medium difficulty. I got 2–3 SQL questions, and the rest centered on my projects. They also asked a few questions related to Java or another programming language, so it wasn’t purely analytics-focused. One small surprise was a guesstimate that reminded me of the 8 queens problem, which made that round feel more like a logic puzzle than a standard business case. I didn’t have a case study in my own process, although I had heard that the overall process can include case study rounds and an EBI-style interview. The main thing I’d tell others is to be ready to talk clearly about your projects, brush up on basic SQL, and expect a mix of aptitude, behavioral, and light problem-solving rather than deep algorithmic coding. I ended up accepting the offer, but the scheduling experience definitely stood out as the least polished part.
Prep tip from this candidate
Brush up on 2–3 SQL questions, be ready to explain your projects in detail, and practice a small guesstimate/logic puzzle similar in feel to the 8 queens problem. Also prepare for basic behavioral prompts like why they should hire you and a short self-introduction.
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 Zs Associates
What are the assumptions of linear regression?
| Question | |
|---|---|
| Late Deliveries | |
| Data Preparation for Imbalanced Data | |
| Your Strengths and Weaknesses | |
| PCA and K-Means | |
| Docs Metrics | |
| Creating Companies Table | |
| Interpreting Fraud Detection Trends | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| First Touch Attribution | |
| Experiment Validity | |
| First to Six | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| Find the Missing Number | |
| Size of Joins | |
| 500 Cards | |
| Over-Budget Projects | |
| Month Over Month | |
| Encoding Categorical Features | |
| Longest Streak Users | |
| Maximum Profit | |
| Paired Products |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates report starting with one to three online tests covering aptitude, logical reasoning, verbal ability, and occasionally guesstimate-style questions. Some describe a dedicated case-based test in this stage, where you analyze a business scenario and write up findings before being invited to interviews. One candidate instead began with an HR screening.
Most candidates describe a technical round centered on SQL, including joins, window functions, delete queries, and sorting optimization, often tied to how you built a database in a personal project. A few reports mention lighter DSA questions, such as polymorphism, or basic Java/Python familiarity. Interviewers reportedly treat SQL as the essential skill rather than algorithmic coding depth.
Several candidates describe a case study round where you're given a business problem and asked to analyze data and present conclusions; one report mentioned a profitability case at a food outlet. In some processes, a later case interview builds directly on that same case, with interviewers asking follow-up questions about your reasoning.
Guesstimates and brainteaser-style puzzles show up across most reports, sometimes layered on top of the case or SQL rounds rather than appearing as a standalone step. Candidates mention examples like an 8-queens-style logic puzzle, an hourglass puzzle, binary number manipulation, and basic probability questions. Interviewers reportedly care more about how you talk through your reasoning than whether you land the exact number.
The later rounds typically involve a resume-focused discussion of your internships and projects, plus behavioral or situational questions such as why you want to join ZS or why they should hire you. One candidate also described a brief, more conversational segment with basic personal questions. Outcomes after this stage ranged from accepted offers to rejections.
