Real ZS Associates interview questions - candidate interview experiences and HR round prep, in one place.
Explore: Interview experience · HR interview questions · Overview · Placement papers · Preparation guide
ZS Associates hires on structured problem-solving, not DSA - a quant-heavy aptitude test, a 30-35 minute case interview with guesstimates, and a track-dependent analytics/technical round set it apart from a typical IT-services loop.
Interview experience
ZS Associates interview experiences covering Online aptitude assessment, Behavioural / video assessment (some drives), Case interview, Technical / analytics interview (track dependent), +1 more. Round-wise notes, common questions, and what candidates report clears each stage.
HR interview questions
ZS Associates HR interview questions with sample answer frameworks - motivation, relocation, STAR stories, and culture-fit prompts.
| Round | Duration | What they test |
|---|---|---|
| Online aptitude assessment | 50-75 min (varies) | Quant, logical reasoning, data interpretation, verbal |
| Behavioural / video assessment (some drives) | 15-30 min | Situational judgement, communication |
| Case interview | 30-35 min prep + discussion | Structured problem solving, guesstimates, assumptions |
| Technical / analytics interview (track dependent) | 30-45 min | SQL, Python or Excel, statistics, data interpretation |
| Fit / HR interview | 20-30 min | Why ZS, resume deep-dive, behavioural stories |
Many campus cycles add layers before the live case debrief:
| Stage | What reports describe | What to practise |
|---|---|---|
| Core aptitude | 40–60 min, quant + DI + verbal under tight clocks | Section-wise timing logs |
| PSDD (Problem Solving Deep Dive) | Business passage + MCQs - answers depend on case details (budget, client orientation) | Read twice, underline constraints |
| Video / behavioural (some drives) | 2–3 min recorded answers; guesstimate or situational prompts | Speak loudly; test webcam/mic early |
| Written case upload | Rough work on paper, scan/upload; then live debrief | Neat assumption box on every page |
BTSA pipelines often add SQL debugging MCQs, one easy–medium coding problem, and handwritten SQL in a separate online technical before manager interviews - still not a LeetCode grind, but joins and window functions recur.
These answers are compiled from public candidate reports, not from an official ZS notice, and drives differ. The instruction screen of your own test is the final word.
| Question | Answer |
|---|---|
| How many questions and how long? | Reports conflict. 2023-2025 drives (placementpreparation.io) describe 59 questions in 52 minutes across six sections on Mettle: Logical/Attention to Detail (25 questions in 5 minutes), Analytical Ability (8 in 15 minutes), Unstructured Problem Solving, Numerical Ability, Critical Thinking and Verbal Ability. An older GfG report describes 50 questions in about 45 minutes, with computer fundamentals and DBMS for the technology profile. |
| Does it have negative marking? | Not published, and reports do not settle it. Read the instruction screen before guessing. |
| Is there a sectional cutoff? | No cutoff is published. 2023-2025 reports say each section has its own timer and you cannot switch sections, so log your section-wise timing in practice. |
| How much is the cutoff? | No official score cutoff; shortlists are relative to the batch (one prep site reports about 40 per role reaching interviews). Reported eligibility ranges from 60% to 70% (6.0 to 7.0 CGPA) throughout, depending on the drive. |
| Is there a case study in the test? | Yes. Reports describe a short business scenario with 8-10 MCQs in about 30 minutes (the Problem Solving Deep Dive), and later a written case you work alone before a live debrief. |
| Is there a communication or video round? | On many drives, yes. 2023-2025 reports describe a communication test of spoken English, sometimes with audio-based questions and a short written response. One report describes 8 recorded questions of about 3 minutes each with 10 seconds to think, mixing behavioural prompts and guesstimates such as paint needed for a 10 m by 12 m wall. |
| Is there coding? | Only on technology tracks. 2023-2025 reports describe a BTSA role test with 2 full SQL queries on a given schema plus string and array coding problems with complexity analysis; DAA gets a data-driven case study instead. |
Questions below are ones candidates report in GfG and other campus write-ups for each ZS hiring track. They show the level and style, not a fixed list.
| Role | Reported questions and topics |
|---|---|
| Decision Analytics Associate (DAA) | A pharma or healthcare case worked alone then presented, guesstimates (market size of a diabetes drug in India, cab movements at Delhi airport per month; 2023-2025 reports add bikes in Bangalore and traffic signals in Pune), p-values, Type I vs Type II errors, correlation vs causation. |
| Business Technology Solutions Associate (BTSA) | 2023-2025 reports: palindrome check in 3-4 different ways, find the non-anagram in an array with a dry run, deleting duplicate rows in SQL, inheritance and polymorphism output questions. Also nth highest salary, RANK vs DENSE_RANK vs ROW_NUMBER, joins and subqueries, handwritten SQL, one easy-to-medium coding problem, DBMS basics, plus a lighter case. |
| Campus Beats entry (case competition route) | Teams that make the top cut sit the aptitude, case MCQ and video rounds; video prompts include a client unhappy with a missed deadline and convincing a teammate who disagrees. |
Asked across every role: tell me about yourself, why ZS and why analytics or consulting, a time you used data to change someone’s mind, and the assumptions behind a project on your resume.
Sample answer frameworks for each of these are on the ZS Associates HR interview questions page.
ZS hires freshers into two main tracks that share the aptitude test and case round but split afterwards. Decision Analytics Associates work on commercial analytics for pharma and healthcare clients - sales-force sizing, targeting, forecasting - so the technical round leans on statistics, Excel and case reasoning. Business Technology Solutions Associates build the data platforms and applications behind that work, so their pipeline adds SQL, a coding problem and DBMS questions.
Older candidate reports put BTSA around ₹8-12 LPA and DAA around ₹10-14 LPA; ZS does not publish these and we could not confirm them against a 2024-2026 source. 2024-2025 eligibility summaries also differ by track: BTSA is reported as open to CSE, IT and ECE only, DAA to all branches. This page covers both; check which track your application names, because the technical round you face depends on it.
Work top-down from population and state every assumption out loud. Start with roughly 1.4 billion people in India, take the adult share at about 65 percent, giving around 910 million adults. Apply a diabetes prevalence of roughly 10 percent for about 90 million diabetics. Then narrow with funnel steps: perhaps 50 percent are diagnosed, of whom around 60 percent are on regular medication, and your drug’s therapeutic class might address 30 percent of those - about 8 million patients. Multiply by annual therapy cost, say 6,000 rupees, for roughly 48 billion rupees of addressable market, then apply a realistic market share. Interviewers care far more about the clean structure and the sanity check at the end than about your exact prevalence figure.
The most readable version uses DENSE_RANK: SELECT DISTINCT salary FROM (SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk FROM Employee) t WHERE rnk = N. DENSE_RANK is the right function because ties should share a rank without skipping the next value - ROW_NUMBER would give two employees on the same salary different ranks, and RANK would skip N entirely after a tie. Without window functions you can use LIMIT with OFFSET on a DISTINCT salary list, or a correlated subquery counting how many distinct salaries are strictly greater. Always mention what should happen when fewer than N distinct salaries exist: the window version returns no rows rather than an error.
All three assign a number over an ordered partition, but they differ on ties. ROW_NUMBER always gives distinct sequential numbers, so tied rows get arbitrary but different values - use it for deduplication, such as keeping one row per customer. RANK gives tied rows the same number and then skips, so two rows at rank 1 are followed by rank 3. DENSE_RANK gives tied rows the same number and does not skip, so the sequence continues at 2. For an analytics question like the top three products per region, DENSE_RANK is usually what a business stakeholder means, because it includes every product genuinely tied for third.
A p-value is the probability of observing data at least as extreme as yours if the null hypothesis were true. It is not the probability that the null hypothesis is true, and it is not the probability your result happened by chance. A p-value of 0.03 against a 0.05 threshold means you reject the null, but it says nothing about effect size - with a large enough sample, a commercially meaningless 0.1 percent lift becomes statistically significant. That is why ZS-style analytics answers should pair significance with a confidence interval on the effect and a judgement about whether the magnitude is worth acting on.
A Type I error is a false positive - rejecting a true null hypothesis - and its rate is alpha, the significance level you choose, typically 0.05. A Type II error is a false negative, failing to reject a false null; its rate is beta, and power is 1 minus beta, conventionally targeted at 0.80. The two trade off: tightening alpha to 0.01 reduces false positives but raises the chance of missing a real effect. The only way to reduce both at once is a larger sample. In a commercial context the choice depends on cost - launching an ineffective campaign versus missing an effective one - so state which error is more expensive before picking a threshold.
First clarify the number: 15 percent versus what baseline, in units or in revenue, and across which geographies and channels - a revenue drop with flat units is a price or mix problem, not a demand problem. Then decompose sales into volume times price, and volume into number of prescribers times prescriptions per prescriber times units per prescription. Segment each factor by region, specialty, and payer to see whether the loss is broad or concentrated in a few accounts, which points at very different causes. External hypotheses come next: a competitor launch, a generic entry, a formulary or reimbursement change, or a supply disruption. Close with a recommendation tied to whichever branch the data actually supports, plus what you would measure to confirm it.
Correlation means two variables move together; causation means changing one produces a change in the other. They diverge for three reasons: a confounder driving both, reverse causality, or coincidence in a small sample. The classic commercial trap is finding that high-detailing physicians write more prescriptions and concluding that detailing works - when the sales force was targeting high-volume prescribers in the first place, so prescription volume caused the detailing. Establishing causation needs a randomised controlled test, or a quasi-experimental method such as difference-in-differences with a matched control group when randomisation is not possible.
First diagnose why the data is missing, because the mechanism dictates the fix: missing completely at random can be dropped with little bias, missing at random can be imputed conditionally on other variables, and missing not at random - where the reason relates to the missing value itself, such as high earners skipping an income field - biases any simple imputation. Options range from listwise deletion to mean or median imputation, to model-based imputation like KNN or MICE, and adding an explicit missing-indicator column often preserves signal. For outliers, distinguish data-entry errors, which should be corrected or removed, from genuine extreme values, which usually should not - a handful of very high prescribers are often the most commercially important accounts. Winsorising, or a log transform, keeps them in the analysis while limiting their leverage.
Classic approach: two perpendicular diameters give four pieces; a horizontal cut through the middle of the cake’s height doubles them to eight. GFG-style follow-ups ask for a second valid layout - stacks of interviewers use this to see whether you explore geometry instead of stopping at one trick. State assumptions (cuts are full planes, equal volume) before drawing.
Use a balance scale in groups of three: weigh 3 vs 3; if equal, the heavy ball is in the remaining three, else in the heavier pan. Second weighing narrows to one ball. Total two weighings. ZS technical and EBI rounds reuse lightweight probability puzzles like this to grade process, not memorization.
Segment: active smartphone users → fraction who shop online → fraction using Flipkart → orders per active user per day. Example skeleton: ~900M adults, ~60% smartphones, ~25% e-commerce shoppers, ~30% Flipkart share → funnel to daily orders, then sanity-check against public GMV hints. Multiple approaches (top-down vs city sample) impress debriefers more than a single magic number.
ZS does not publish a negative-marking rule, and public candidate reports do not settle it. Check the instruction screen before you guess. Reports on the format conflict: 2023-2025 drives describe 59 questions in 52 minutes across six separately timed sections on the Mettle platform, while an older GfG report describes about 50 questions in 45 minutes of quant, verbal, data interpretation and logical reasoning.
No score cutoff is published; shortlists are relative to the batch. Reported eligibility conflicts: placementpreparation.io’s 2024-2025 summary gives 70% or 7.0 CGPA in 10th, 12th and graduation (60% on some drives), with BTSA open to CSE, IT and ECE and DAA open to all branches. Older campus reports cite 60% or 6.0 CGPA throughout. Backlog rules vary by drive, so check your notification.
ZS Associates fresher hiring typically runs in four stages: 1. Online aptitude assessment - quantitative aptitude, logical reasoning, data interpretation and verbal ability, tightly timed. 2. Behavioural / video assessment - recorded situational responses, on many but not all drives. 3. Case interview - a business case you analyse on your own for roughly 30-35 minutes, then discuss with the panel, often with guesstimates and puzzles. 4. Fit / HR interview - why ZS, resume deep-dive and behavioural questions. Analytics and technology tracks add SQL, Python or Excel questions.
ZS interviews centre on structured problem solving rather than heavy DSA: business cases in pharma, healthcare and commercial analytics, guesstimates (market sizing), puzzles, data interpretation, statistics fundamentals, and SQL for the analytics and technology tracks (joins, subqueries, nth-highest salary, window functions). Behavioural questions such as ‘why ZS’ and resume-based STAR stories appear in almost every round.
Most candidate reports describe three to five rounds: an online aptitude test, an optional behavioural or video assessment, one or two case / technical interviews, and a fit interview with a manager or recruiter. On-campus drives often compress the interviews into a single day. Round counts differ between the Decision Analytics and Business Technology Solutions tracks, so check that cycle’s placement email.
It is a solo case followed by a panel debrief, and it is the round that distinguishes ZS. You are usually given a business problem, often set in pharmaceuticals, healthcare or commercial analytics, and about 30-35 minutes to work through it alone before presenting your structure, assumptions and recommendation to the panel. Interviewers reward candidates who decide for themselves what to analyse next, state assumptions explicitly, and back conclusions with numbers.
Good fit: You like numbers under a clock, you can talk a market-size estimate without freezing, and you will relocate to Pune or Bengaluru. SQL does not scare you. You can say why healthcare commercial analytics is interesting in two sentences.
Harder path: You only practiced DSA and skipped quant; you refuse to guess a number; you want “pure SDE, no client.” ZS HR is a consulting-fit round.
Use this as a default four-week loop before a ZS Associates drive. Adjust to your invite timeline.
10-day crash version: Days 1–3 timed quant + data interpretation, days 4–5 guesstimates and one pharma-style case out loud, days 6–7 SQL joins/window functions (BTSA) or stats refresh (DAA), days 8–9 mock case debrief with a friend, day 10 fit-round STAR stories on the HR page.
Candidate-reported fresher/early-career packages for ZS Associates often cite BTSA ~₹8-12 LPA, DAA ~₹10-14 LPA (candidate-reported). Treat forum numbers as ranges, not guarantees - confirm the written offer letter for your team and location.
Interview process details and sample questions on this site are editorially organized from public candidate reports and hiring write-ups, with round structure, prep notes, and company-specific framing added by our team. For round-by-round stories, see the ZS Associates interview experience page. For OA papers and coding drills, use ZS Associates on placementpapers.app. OA quick answers and role-wise questions draw on GfG’s ZS Associates interview experience (Campus Beats aptitude, case MCQ and video rounds), placementpreparation.io’s ZS recruitment process, interview experience (2023-2025 drives) and eligibility pages, Glassdoor interview snippets seen via search, and the candidate reports already summarised on this page.
