Persistent Systems logo
Persistent SystemsSoftware Engineer
Updated Sep 16, 2026

Persistent Systems Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Persistent Systems, newest first and distilled into what to expect across the loop.

Get your personalized Persistent Systems Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
1 month ago

I did an online interview via TalView for a telecom-focused software role, and it took place on September 16, 2026. The round felt aimed at gauging C++ on Linux with an emphasis on 5G Core concepts, which immediately set the tone that this wasn’t going to be generic “general programming” questioning.

I didn’t get much detail in the notes about the exact prompts or how many sub-questions I handled, but the overall setup was still clearly structured around that C++/Linux/5G Core profile. The experience itself stayed fairly contained to that one day and didn’t feel like a long, multi-stage loop. I left with the sense that my background matched the technical domain they were scanning for, but I didn’t receive an offer.
4 months ago
Difficult Positive New Delhi

After a recruiter-style touchpoint, my process felt smooth and professionally run, with timely communication at each stage. The interview environment was calm enough that I could actually focus on technical details, and it leaned toward discussing my background and career direction alongside the fundamentals.

The technical part itself ended up being pretty straightforward and time-bounded—about an hour—and it included a small group of interviewers from different regions. The questions were mostly baseline C# and .NET topics, and the overall round felt like a quick filter rather than a deep dive. It didn’t drag, and the tone stayed reasonable from start to finish.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Technical Rounds

Candidates can expect a mix of technical rounds focusing on core programming concepts, data structures, and specific technologies like Java, Spring Boot, and SQL. The difficulty can vary, but many report a steady challenge with an emphasis on practical application and problem-solving.

JavaSpring BootData Structures

Interview Structure & Flow

The interview process is generally structured with multiple stages, often starting with a recruiter call, followed by technical interviews and an HR discussion. Candidates appreciate the organized flow, but some report unexpected shifts in focus or role expectations during later rounds.

Structured ProcessHR DiscussionRecruiter Call

Behavioral & Experience Discussion

Interviews often include discussions about past projects and how candidates handle real-world challenges, emphasizing communication and problem-solving skills. Candidates are encouraged to connect their experiences to the role's requirements.

Behavioral QuestionsProject ExperienceProblem-Solving

Communication & Follow-Up

While initial communication is often timely and professional, several candidates report frustrations with a lack of follow-up or closure after interviews, leading to uncertainty about outcomes. This aspect can significantly impact the overall experience.

CommunicationFollow-UpClosure

Difficulty & Evaluation

The overall difficulty of the interviews is described as average to challenging, with some candidates feeling that the evaluation criteria were not always clear or consistent. This can lead to confusion about performance and expectations.

DifficultyEvaluation CriteriaConsistency

Coding Assessments & Practical Tests

Candidates should be prepared for coding assessments that test both theoretical knowledge and practical skills, often requiring real-time coding and problem-solving. The assessments may include specific technologies relevant to the role.

Coding AssessmentsReal-Time CodingProblem-Solving