ZS Associates software engineer candidates report an online coding or aptitude screen, technical rounds on data structures, SQL and Python, and a final round mixing technical and behavioral questions. All four reports ended without an offer.
$113K
Avg. Base Comp
$130K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Four candidates describe ZS Associates software engineering interviews, and all four ended without an offer. The common thread is that ZS tests more than algorithms. SQL came up in three of the four reports, including CTEs, window functions such as rank, dense_rank, lag and lead, and a third-highest-salary-per-department problem with ties. One candidate was also asked to convert Python code to SQL.
Coding is still central. Candidates mention arrays, strings, hash maps, binary trees, object-oriented concepts such as interfaces and abstraction, and a map-based problem about players. One candidate reported that a final-round interviewer pushed hard on whether a solution used the optimal algorithm, so practice explaining why you chose an approach and what its complexity is.
The screening stages vary by role and location. One campus-hire candidate described a coding and aptitude test, a voice assessment that acted as an elimination round, and onsite rounds in Pune. An associate platform engineer candidate described a technical online assessment and a communication assessment, then a technical interview. That interview also included guesstimates such as estimating cabs in a city. A final behavioral round followed, with leadership scenarios and puzzles such as the hourglass problem. A frontend-focused candidate was asked about React, Redux architecture, hooks, closures, promises and accessibility. Match your preparation to the specific team and role.
Synthesized from 4 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 interview process at ZS Associates started smoothly with an initial HR round where they outlined the role and the project I'd be working on. They asked about my background in Python and microservices, which felt like a straightforward conversation about relevant experience. The technical rounds that followed were solid — I felt confident going through them and the interviewers seemed engaged. But the final round took a sharp turn. There were three interviewers, and while two of them conducted thorough, fair interviews, one clearly had a different agenda. He seemed intent on finding gaps in my knowledge rather than actually assessing my abilities. After about an hour of rapid-fire questions, he finally landed on something: a problem where I hadn't applied the optimal algorithm. He pushed hard on that single point, clearly treating it as a major failure. The tone shifted noticeably after that moment. Earlier rounds also included questions around converting Python code to SQL and diving deeper into data structure and algorithmic efficiency. The whole process was rigorous — they tested both theoretical understanding and practical problem-solving under pressure. But that final round felt less like an evaluation and more like an interrogation, which soured what had otherwise been a solid technical interview.
Prep tip from this candidate
Expect at least one interviewer to adopt an adversarial stance and aggressively probe for algorithmic optimality — have a strong grasp of when and why to apply specific algorithms (sorting, searching, dynamic programming) and be ready to defend your approach under pressure. Also prepare to convert between Python and SQL, as that was a concrete question type across the process.
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 do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| First Touch Attribution | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Minimum Change | |
| Real-Time Transaction Streaming | |
| Repeated Category Purchase | |
| Get Top N Frequent Words | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an early conversation with HR about their background, projects and the role. One candidate discussed Python and microservices experience, and another covered HTML, CSS, JavaScript and React work. It is typically conversational, so prepare a clear account of your projects.
Candidates report a first filter that may include coding problems, numerical aptitude, frontend questions, or a communication assessment. One campus candidate described a voice assessment where you repeat system-spoken sentences, and said it was an elimination stage. Format likely varies by role and location.
Candidates report technical questions on arrays, strings, hash maps, binary trees, object-oriented concepts, SQL CTEs and window functions, and Python-to-SQL conversion. One candidate also reported data engineering topics such as ETL versus ELT and pipelines, along with guesstimates. One frontend candidate reported React, Redux and JavaScript fundamentals.
Candidates describe the last stage in different ways. One reported leadership scenarios and puzzles. Another reported a three-interviewer panel where one interviewer pressed on algorithmic optimality. Prepare both structured behavioral answers and clear defenses of your technical choices.
