Real, anonymous reports from people who interviewed for Software Engineer at Persistent Systems, newest first and distilled into what to expect across the loop.
I experienced a fairly standard multi-round flow—HR screening, several technical discussions, and a final HR step—followed by a quick rejection with little transparency over timing.
I went through an HR-led early screening, then a single follow-up interview, with limited feedback and mixed communication.
The interview process typically consists of multiple rounds, starting with an HR screening followed by several technical discussions, often culminating in a managerial or final HR round. Candidates should be prepared for a sequential flow that may include both technical and client-focused evaluations.
Interviews heavily emphasize core technical skills, particularly in Java, Spring, and DSA concepts, with questions ranging from fundamentals to practical problem-solving scenarios. Candidates should be ready to discuss their projects and demonstrate their technical reasoning.
Feedback and communication throughout the process can be inconsistent, with many candidates reporting a lack of clarity regarding their performance and outcomes. It's advisable to seek feedback proactively and clarify any uncertainties during the process.
Candidates can expect a medium to high level of difficulty, particularly in technical rounds that test both theoretical knowledge and practical application. Preparation should focus on core concepts, coding challenges, and system design principles.
Several candidates experienced logistical challenges, such as scheduling conflicts and disorganized interview setups. Being flexible and prepared for potential delays or changes in the interview schedule is advisable.
Many candidates reported a lack of closure after the interview process, often receiving rejections without detailed explanations. Candidates should be prepared for this possibility and consider following up for clarity post-interview.