
What four candidates report about Zenoti software engineering interviews: online and written assessments, data structures and algorithms rounds, SQL, JavaScript fundamentals, and project discussions, with prep tips.
$110K
Avg. Base Comp
$135K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Zenoti's engineering interviews as technical and centered on data structures and algorithms, though the format varies by role and hiring channel. One candidate who received an offer describes a screening call followed by two technical rounds. The first opened with a project walkthrough, then moved to finding the maximum and second maximum in an array and an anagram problem, with the interviewer pushing on time and space complexity. The second round covered deleting a linked-list node when given only a pointer to it, then detecting a cycle with Floyd's algorithm. It ended with a question about where the candidate saw themselves in five years.
A different candidate, who interviewed for a more senior role and did not get an offer, reports a HackerEarth assessment with 30 MCQs and three fairly basic coding questions. A video interview followed, with definition-style questions and JavaScript tasks using map and reduce on objects. An intern-level candidate who accepted an offer recalls depth-first search, dynamic programming, SQL, and a logic puzzle, with no HR or behavioral portion. A campus candidate reports three rounds: a technical assessment, an aptitude test with MCQs, an essay, and a coding question, and a final interview with project questions and two coding problems. That candidate did not receive an offer.
So prepare for the likely mix: linked lists, arrays, strings, graph or tree traversal, dynamic programming, and SQL. Practice explaining your complexity trade-offs aloud, and be able to describe your own projects clearly. For more senior roles, review JavaScript fundamentals as well. These are individual reports, so ask your recruiter which rounds apply to your 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 Zenoti 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 Zenoti
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Minimum Change | |
| Raining in Seattle | |
| Address Schema | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Daily Retention Summary | |
| P-value to a Layman | |
| First Touch Attribution | |
| Google Maps Improvement | |
| Job Recommendation | |
| Find Bigrams | |
| Size of Joins | |
| Recurring Character |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates describe an initial assessment. One reports a HackerEarth test with 30 MCQs and three fairly basic coding questions. A campus candidate describes a technical assessment followed by an aptitude test with MCQs, an essay section, and a coding question. Whether you get one depends on your role and channel.
One offer-receiving candidate describes a quick initial screening before the technical rounds began. The report gives no details of what the screen covered, so it may be a brief conversation about background and fit. Confirm the format with your recruiter.
In one report, the interviewer started with the candidate's projects and then moved to array and anagram problems, including a dry run and test cases. He pressed for time and space improvements. Another candidate reports a video interview with definition-style technical questions followed by JavaScript tasks using map and reduce.
One candidate reports a harder second round that included deleting a linked-list node given only a pointer to it and detecting a cycle with Floyd's algorithm. The candidate had to defend the approach before coding. An intern-level candidate recalls DFS, dynamic programming, SQL, and a logic puzzle.
The campus candidate describes a final interview that focused on project-based questions and two coding questions. Another report mentions a closing behavioral question about career goals. Expect to explain your past work clearly, though this may differ by role and level.