Zycus software engineering candidates describe a mix of coding, Java or React fundamentals, logic puzzles and infrastructure questions. Here is what individual candidates reported and how to prepare.
$115K
Avg. Base Comp
$135K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Reports on Zycus engineering interviews vary by role, so prepare for breadth rather than one fixed script. One candidate for a Software Engineer role describes an intro recruiter call, a 15-question HackerRank test, a resume-driven technical discussion on distributed networking and optimization, an in-person coding round on Java, and a manager conversation. That candidate says the Java Stream API and Spring Boot questions were deeper than expected.
A Software Development Engineer candidate describes a compressed single day: a background screen, React and JavaScript or TypeScript questions on components, props, state and hooks, a balls-and-balance logic puzzle with nine balls, and an HR round. That candidate felt unprepared for the puzzle.
A Senior Software Engineer candidate reports a technical round on the difference between web and application servers, then what can cause a Kubernetes cluster to reach CrashLoopBackoff. They struggled with the Kubernetes question.
A Solutions Engineer candidate describes a group discussion, aptitude MCQs, coding in JavaScript, Python and SQL, a two-dice reasoning problem and Fibonacci. This is a different role, so treat it as a hint about breadth only.
All four of these candidates reported no offer. The reports are few, so check your own recruiter's format. Practice your stack's fundamentals, a few classic puzzles, and explaining your reasoning aloud.
Synthesized from 5 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 Zycus process.
The process was a single day with multiple rounds. First came a screening round focused on my background and basic technical knowledge — they wanted to understand my work experience and communication skills. Then I moved into the technical assessment, which was heavy on React and JavaScript. I got questions on core React concepts like components, props, state, and hooks, plus some JavaScript/TypeScript problem-solving exercises. What caught me off guard was the puzzle component. They asked logic puzzles during the interview — specifically, I remember a balls-and-balance problem where you have nine identical-looking balls, one slightly heavier, and you need to identify it in the minimum number of weighings. It wasn't about code at all, but about reasoning and optimization. The interview felt like it was testing both my technical foundation and my ability to think through constraints systematically. I wasn't fully prepared for that puzzle angle going in, and I think that hurt my performance. The whole day felt compressed, which added pressure. By the HR round at the end, I was already feeling behind. I didn't receive an offer.
Prep tip from this candidate
Study logic puzzles and constraint-based problems (the 100 HFG puzzles set is referenced in prep materials) — these aren't coding questions but are part of the assessment. If you're interviewing for a technical role, brush up on React fundamentals, but also be ready for non-obvious problem-solving components that test reasoning beyond just coding.
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 Zycus
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Random SQL Sample | |
| String Shift | |
| Job Recommendation | |
| Rolling Bank Transactions | |
| Bagging vs Boosting | |
| Customer Orders | |
| Minimum Change | |
| Top 3 Users | |
| Scrambled Tickets | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| The Brackets Problem | |
| First Touch Attribution | |
| Flight Records | |
| Prime to N | |
| P-value to a Layman | |
| Level Of Rain Water In 2D Terrain | |
| Size of Joins | |
| Upsell Transactions | |
| Download Facts | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening conversation about background and experience. One Software Engineer candidate describes a roughly 20-minute recruiter call, and an SDE candidate describes a screen on work history and communication. Expect to summarize your projects and technologies clearly.
One Software Engineer candidate reports a HackerRank exam with 15 questions on general problem-solving. A Solutions Engineer candidate describes aptitude MCQs and coding in JavaScript, Python and SQL. Format may differ by role, so confirm with your recruiter what the assessment covers.
Reported topics depend on the role. One candidate saw Java Stream API and Spring Boot questions plus distributed networking and optimization. Another saw React, JavaScript and TypeScript. A senior candidate was asked about web versus application servers and Kubernetes CrashLoopBackoff. Prepare for the stack on your resume.
Two candidates describe reasoning problems: a nine-ball balance puzzle in an SDE interview and a two-dice sum problem in a Solutions Engineer interview. They may not involve code, so practice explaining your approach step by step.
The Software Engineer candidate describes a manager round on role expectations and team fit, and the SDE candidate describes a final HR round. Candidates may also face compensation questions. One reported silence of about two weeks before an automated rejection, so follow up politely.
