Saviynt Software Engineer candidates may face two coding-led rounds that also probe Java, multithreading, APIs, design choices, and resume details.
$95K
Avg. Base Comp
$100K
Avg. Total Comp
2 rounds
Typical Rounds
Not reported
Process Length
For a Saviynt Software Engineer interview, one candidate reported a two-round process that combined live coding with close technical follow-ups. Prepare to explain the reasoning after the code, not just arrive at a solution. In the first round, the candidate coded a grid-islands problem, then discussed whether BFS could solve it and the tradeoffs between approaches. The conversation also moved into Java theory, maps, multithreading, and how APIs work.
The second reported round opened with a meeting-rooms problem and then shifted to a high-level design discussion involving a file system. The interviewer reportedly examined each technical decision, so practice stating assumptions, alternatives, and consequences as you design. Resume keywords were also discussed; be ready to explain the implementation details and choices behind every project or technology you list.
The available account is limited to one candidate, so the exact emphasis may vary. Focus your preparation on coding fluency, Java fundamentals, concurrency, API concepts, and defensible design decisions.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Saviynt 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 Saviynt
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Minimum Days for Scheduling All Meetings | |
| Minimum Directional Path | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported coding and running a standard islands problem, followed by a discussion of BFS and approach tradeoffs. The same round included theory questions on Java, maps, multithreading, and how APIs work, so candidates may need to explain both implementation and fundamentals.
The reported second round began with a meeting-rooms problem before moving to a high-level design problem related to a file system. The candidate said the interviewer probed every technical decision, so clearly state your assumptions, alternatives, and tradeoffs as you work.
Within the second reported round, the candidate was asked about keywords from their resume. Candidates should be prepared to discuss the technical choices, implementation details, and rationale behind every project or technology they present.
