Persistent Systems Recruitment Process: 2026 Guide

Persistent Systems runs a three-stage campus selection: an online assessment, a technical interview, and an HR round. Each stage is eliminatory.

The online assessment is the widest filter. Most candidates who prepare only for aptitude find the CS fundamentals section harder than expected. Getting the sequence right matters: the coding section carries significant weight, and verbal and logical sections together contribute roughly half the assessment score.

This guide covers the full pattern, section by section, then goes through what the technical and HR rounds actually test.

How the Persistent Systems Selection Works

Persistent Systems is a Pune-headquartered technology services company with delivery centres across India. Its campus hiring runs through a standardised three-round format for software engineering roles.

Round	Format	What It Filters
Online Assessment	MCQs + coding	Technical aptitude, logical reasoning, coding fundamentals
Technical Interview	Live discussion + problem-solving	Depth in CS concepts, project understanding, coding under pressure
HR Interview	Conversation	Cultural fit, communication, career intent

All three rounds are eliminatory. Moving from the online test to the technical interview already places you in the shortlisted pool; the technical interview is where depth gets tested. The HR round is the final gate.

The selection timeline varies by campus and batch, but most drives complete all three rounds within one to two weeks of the online test date. For current openings and the latest eligibility criteria, check the Persistent Systems careers page directly. Drive-specific cutoffs for percentage and backlogs differ from one batch announcement to the next.

Online Assessment: Pattern and Full Syllabus

The online assessment is split into four sections, each with its own question count and topic scope.

CS Fundamentals

About 20 multiple-choice questions. This is the section most candidates underestimate.

Topics covered:

• C Programming: pointers, operators, operator precedence, output prediction
• C++: object-oriented concepts, overloading, inheritance
• Data Structures: stacks, queues, linked lists, trees, graphs — expect output questions and concept checks
• Operating Systems: process management, scheduling, memory management basics
• Networking: key protocols, OSI layers, TCP/IP concepts
• Database Management Systems: normalization, SQL query output, keys and constraints
• Software Testing: concepts like black-box testing, white-box testing, test coverage

The emphasis is on output prediction and concept application, not definition recall. A question on C pointers is more likely to ask what this code prints than to ask you to define a pointer.

Verbal Ability

12 to 14 questions covering:

• Reading comprehension passages
• Para-jumbles (reordering scrambled sentences into a coherent paragraph)
• Sentence completion
• Sentence correction
• Vocabulary in context

This section is timed along with the full assessment, so spending too long on a single comprehension passage affects your score in other sections. One read-through per passage, answer what you can, and move on.

Logical Reasoning

12 to 14 questions. Topics:

• Data arrangements (linear, circular, tabular)
• Blood relations
• Coding and decoding
• Number and letter series
• Analogies
• Odd one out

The logical reasoning section at Persistent follows the same pattern as most mid-size IT services assessments. If you have already drilled these topics for other drives, no separate prep is needed here. See the guides on Sopra Steria online test pattern and Tata Elxsi recruitment process for how similar companies structure their logical sections.

Coding Section

2 problems in 45 minutes. This is the second most weighted section after CS fundamentals.

• Problems typically sit at easy-to-medium DSA difficulty
• Trees, graphs, arrays, stacks, and recursion appear regularly
• C is the preferred language historically, though most drives now accept Java and Python as well
• Partial marks may be awarded based on test case pass rates — write clean code that handles edge cases, not just the sample input

Technical Interview: What Gets Tested

Candidates who clear the online assessment move to a one-on-one technical interview, typically conducted by a software engineer or tech lead. Three areas dominate.

Project Discussion

Expect a thorough walkthrough of your final-year or major academic project. The interviewer will ask about design decisions, why you chose a particular technology, what broke during development, and how you fixed it. Vague answers trigger follow-up questions that expose surface-level understanding fast.

Prepare to explain your project without slides. Be specific about what you built versus what you used from libraries or existing frameworks.

Core CS Questions

Common topics:

• Data Structures and Algorithms: implementing queues using stacks, explaining time complexity, identifying the right structure for a problem
• Operating Systems: process vs. thread, context switching, deadlock conditions
• Networking: TCP vs. UDP differences and when each applies, buffer overflow and its consequences
• DBMS: joins, indexing, normalisation trade-offs

Sample questions from past Persistent technical interviews:

• “Explain buffer overflow and what can go wrong.”
• “How would you implement a queue using two stacks?”
• “What is the difference between TCP and UDP? Which would you use for a video stream?”

Reviewing these topics in the context of how you would answer out loud (not just how you would write them down) makes a material difference in the interview.

Live Coding or Puzzle

At least one on-the-spot problem. It may be a DSA question or a logical puzzle. The interviewer watches your approach as much as your solution. Think aloud, state your assumption before writing code, and verify with a small example.

For a detailed breakdown of how technical interviews at similar companies are structured, the guide on Bosch technical interview process covers the same core subjects in a comparable interview format.

HR Interview: What to Expect

The HR interview evaluates communication clarity, cultural fit, and career intent. It is not a formality. Candidates who clear the technical round and then give uncertain or generic HR answers do get screened out.

Common topics:

• Personal introduction: background, interests, why software engineering
• Career goals: short-term (first two years at Persistent) and longer-term direction
• Company knowledge: what Persistent does, its service areas, recent projects or clients if you can find them on their site
• Behavioural questions: how you handled a team conflict, a project that did not go as planned, a time you had to learn something quickly

Sample HR questions:

• “Tell me about yourself.”
• “Why Persistent Systems over other companies?”
• “What do you know about Persistent’s service areas?”
• “Where do you see yourself in three years?”

Interviewers at this stage are assessing whether you can communicate clearly in a professional setting, not whether you can recite your resume. Keep answers specific and brief. Reading community accounts of recent drives on AmbitionBox is a good way to see what questions have appeared in recent months.

Preparation Approach by Round

For the Online Assessment

• CS fundamentals: work through C pointer output questions and OOP inheritance problems. DBMS: practice SQL queries involving joins and subqueries. DSA: know how stacks, queues, and trees work at the implementation level.
• Verbal: timed reading comprehension practice. Aim for one passage per 4 minutes.
• Logical reasoning: blood relations and data arrangement sets take the most time. Drill both until you have a consistent approach.
• Coding: solve 1 to 2 DSA problems daily for the three weeks before the drive. Focus on problems involving arrays, linked lists, trees, and graphs.

For the Technical Interview

Build a 10-minute verbal walkthrough of your project. Know your code well enough to explain any function you wrote. Revise operating systems and networking at the concept level, not just at the definition level.

For the HR Interview

Research Persistent Systems before the interview: their main service lines (digital engineering, enterprise modernisation, cloud services), their approximate size, and any recent news or client wins. Arrive knowing more about the company than a candidate who read only the Wikipedia summary.

Where DSA Meets Applied AI

The two coding problems in Persistent’s online assessment test the same algorithmic foundation that shows up in production software beyond placement season. Tree traversals, graph searches, and stack-based problems are not just interview constructs; they appear in compilers, operating systems, and the data pipelines that LLM-powered applications run on.

If you have finished your Persistent prep and want to see that DSA foundation applied to building real AI tools, TinkerLLM is the practical next step at ₹299: the entry track takes you from DSA intuition to building and deploying your first LLM-backed application, using the same C and Python fundamentals the Persistent assessment already made you revisit.