Real, anonymous reports from people who interviewed for Software Engineer at Saviynt, newest first and distilled into what to expect across the loop.
The overall experience felt good throughout, and the communication was decent. They told me there would be four rounds, but the process ended up taking five rounds instead, which was the only thing that really stood out as off.
I had a first technical round that started with a straightforward discussion. The interviewer asked basic questions around DevOps topics and Linux, and I answered most of what came up.
Candidates can expect a multi-round interview process, typically consisting of technical and HR rounds, with some reports indicating variations in the number of rounds, sometimes exceeding initial expectations. The overall structure is generally consistent, but some candidates noted unpredictability in the number of rounds.
Technical interviews often emphasize data structures and algorithms (DSA), with candidates facing a variety of coding problems and theoretical questions related to system design and programming concepts, particularly in Java and DevOps. Candidates should prepare for both coding exercises and discussions about their technical background.
Interviews include behavioral rounds that assess candidates' teamwork, collaboration, and problem-solving approaches, with a focus on how candidates fit within the company's culture and values. This aspect is often evaluated alongside technical skills.
Candidates are frequently asked to discuss their previous projects and how their experiences relate to the role, which can lead to follow-up technical questions. Demonstrating a clear understanding of past work and its relevance is crucial for success in the interviews.
While many candidates report a generally positive experience with engaged interviewers, some express frustration with the lack of clear communication regarding the outcome of their interviews, leading to uncertainty about their performance and next steps.
Some candidates appreciated the availability of preparation resources shared by interviewers, which helped clarify expectations. However, others felt that the depth of knowledge required in technical discussions was higher than anticipated, indicating the need for thorough preparation.