Persistent Systems Interview Questions 2026 — Fresher Process, Coding & Model Answers
Persistent Systems freshers commonly report an online test (computer-science MCQs, English, logical reasoning and a coding section), an optional Advanced Coding round that unlocks a higher offer tier, two technical interviews and an HR round. Commonly reported technical questions include array problems such as Moore's voting algorithm and finding a missing number, SQL joins vs subqueries and indexing, OS deadlocks and threads, Git merge conflicts and HTTP status codes.
Preparing for your Persistent Systems Interview?
Practice a simulated AI Mock Interview using real Persistent Systems questions and receive instant feedback.
Persistent Systems is a Pune-headquartered digital engineering and IT services company that hires engineering freshers through campus drives and its early-career programs. Its process rewards candidates who can code under time pressure and talk about practical engineering — Linux, Git, APIs and testing — not just theory.
Persistent’s Official Early-Career Programs
Persistent’s Early Careers page lists hiring programs for technology and business roles and several enablement programs, including:
- Train and Hire — a 2-month self-learning program that prepares students for Persistent’s campus hiring drive.
- Career Compass — pre-joining enablement for future engineering graduates.
- Hyperscaler Enablement — support for cloud certifications.
The page does not publish eligibility, rounds or salary — those details below come from candidate reports.
The Persistent Systems Selection Process
| Stage | Commonly reported format | Notes |
|---|---|---|
| Online test (objective) | Computer-science MCQs, English and logical reasoning in timed sections | PrepInsta lists CS 20 questions in 20 min, English 12 in 15 min, Logical 12 in 15 min (2024) |
| Coding | 2 problems in about 45 minutes | Strings and arrays are common |
| Advanced Coding (optional) | 2 harder problems in about 60 minutes | Reported to unlock a higher offer tier |
| Technical interview 1 | DSA, SQL, OOP, OS | Coding live plus fundamentals |
| Technical interview 2 | Project deep dive and practical engineering | Linux, Git, APIs, testing |
| HR interview | Fit, relocation, motivation | Usually short |
Recent GeeksforGeeks reports name AMCAT as the test platform. Formats vary by season and campus.
🚀 Start Free Persistent Mock Interview
Practice Persistent technical and HR questions with real-time AI feedback on structure, pacing and confidence.
Start Free Mock InterviewTechnical Interview Round: Key Focus Areas
1. Data Structures and Algorithms
- Commonly reported topics: Moore’s voting algorithm, missing number, two-pointer string problems, sorting complexities.
2. Databases
- Commonly reported topics: indexing, joins, subqueries, writing SQL live.
Make sure your resume carries the skills Persistent's screeners search for. Scan Resume with ATS Checker →
3. Operating Systems and OOP
- Commonly reported topics: threads, multithreading, deadlock, inheritance and polymorphism.
4. Practical Engineering
- Commonly reported topics: Linux permissions and process management, Git merge conflicts, HTTP status codes, software testing types.
4-Week Persistent Preparation Plan
- Week 1 — Online test: CS fundamentals MCQs, English and logical reasoning under section timers.
- Week 2 — Coding: 30 easy-to-medium array and string problems; then 10 medium problems for the Advanced Coding round in timed pairs.
- Week 3 — Fundamentals: SQL (joins, subqueries, indexes), OS (threads, deadlock), OOP, plus Linux, Git and HTTP basics on your own machine.
- Week 4 — Interviews: project deep-dive rehearsal and two mock interviews.
For behavioural answers, use our STAR method examples for IT interviews.
Practice communication, confidence, pacing, filler words, and HR responses. Try Persistent HR Mock Interview →
Salary and Offer Details
Persistent does not publish fresher pay. PrepInsta (February 2024) reported offer tiers of approximately 5.01 LPA (standard) and approximately 7.8 LPA (after clearing Advanced Coding); a third “Super Achiever” tier is mentioned there but its source admits the details are unconfirmed. Treat these as approximate figures for one hiring season, and use the CTC to in-hand salary calculator to estimate monthly take-home.
Resume Tips for Persistent Systems
- Format: one page, single column; put coding profiles and projects with measurable outcomes near the top. Build your resume and check your ATS score.
- Keywords: Java or Python, Data Structures, SQL, REST APIs, Git, Linux, Cloud (AWS/Azure/GCP), Unit Testing, Agile.
- Templates: see the Software Engineer Resume India and Full Stack Developer Resume India examples.
- Keywords Map: use the Full Stack Developer ATS Keywords sheet.
- Company Hub: visit the Persistent Systems Company Hub, or compare with the LTIMindtree interview guide.
Sources
Checked November 2026:
- Persistent Systems — Early Careers / Campus Program: persistent.com
- PrepInsta — Persistent recruitment process (2024): prepinsta.com/persistent/recruitment-process
- PrepInsta — Persistent eligibility criteria (2024, drive-specific): prepinsta.com/persistent/eligibility-criteria
- GeeksforGeeks — Persistent on-campus Software Engineer interview experience (2024): geeksforgeeks.org
- GeeksforGeeks — Persistent interview experience (2024): geeksforgeeks.org
Round details and salary tiers are candidate- or prep-site-reported, not official Persistent statements.
Persistent Systems Interview Questions with Model Answers
These are real questions asked in Persistent Systems interviews in India, with model answers that interviewers have told us they score highly. Each answer is self-contained.
Use Moore's voting algorithm for O(n) time and O(1) space. Keep a candidate and a count = 0. For each element x: if count is 0, set candidate = x; then if x equals candidate increment count, else decrement it. Every pair of different elements cancels out, so a true majority element survives as the candidate. If the problem does not guarantee a majority exists, make a second pass to count the candidate and confirm it appears more than n/2 times. A HashMap counting approach also works in O(n) time but uses O(n) space.
Moore's voting algorithm appears in a 2024 Persistent candidate report. Mention the verification pass — many candidates forget it.
Approach 1 (sum formula): the expected sum is n(n+1)/2; subtract the actual sum of the array to get the missing number. It is O(n) time and O(1) space, but in languages with fixed-size integers the sum can overflow for large n. Approach 2 (XOR): XOR all indices 0..n with all array values; every number present cancels out and the result is the missing number. This is also O(n) time and O(1) space and avoids overflow. Sorting first would work but costs O(n log n).
Give the simple solution first, then improve it. Interviewers value hearing the trade-off (overflow) explained.
Convert the string to a character array (strings are immutable in Java and Python). Set left = 0 and right = length - 1. While left is less than right, swap the characters at left and right, then move left forward and right backward. This takes O(n) time and O(1) extra space beyond the array. Follow-ups to expect: reverse the words in a sentence (reverse the whole string, then reverse each word), or check whether a string is a palindrome using the same two-pointer idea.
Candidates report string questions in both the online coding section and interviews. Handle empty strings and single characters.
A JOIN combines rows from two or more tables on a related column in a single query, for example orders joined with customers on customer_id. A subquery is a query nested inside another, used to filter or compute a value — for example customers whose total order value exceeds the average. Many subqueries can be rewritten as joins, and optimisers often execute joins more efficiently, but subqueries can be clearer for existence checks (EXISTS) or aggregates. Add an index on columns that appear frequently in WHERE clauses, JOIN conditions and ORDER BY, and that have high selectivity. Avoid over-indexing write-heavy tables, because every INSERT and UPDATE must also update each index.
Indexing, joins and subqueries are all named in a 2024 Persistent candidate report — practise writing the queries, not just defining them.
A deadlock occurs when two or more processes or threads each hold a resource and wait for a resource held by another, so none can proceed. It requires mutual exclusion, hold and wait, no preemption and circular wait. Starvation is when a process waits indefinitely because other processes keep getting priority — the system is still making progress, just not for that process. Deadlocks are handled by prevention (break a condition, such as ordering lock acquisition), avoidance (Banker's algorithm), or detection and recovery. Starvation is solved with fair scheduling, such as ageing, which gradually raises the priority of waiting processes.
Threads, multithreading and deadlocks appear in recent candidate reports. Contrasting deadlock with starvation is a common follow-up.
Each file has permissions for three classes: owner (user), group and others, and each class can have read (r = 4), write (w = 2) and execute (x = 1). The numeric mode is the sum per class. chmod 755 file means owner = 7 (read + write + execute), group = 5 (read + execute), others = 5 (read + execute) — typical for scripts and directories that everyone can run or enter but only the owner can modify. ls -l shows this as rwxr-xr-x. chmod 644 (rw-r--r--) is typical for regular files. To find and stop a process you would use ps or top to get its PID and kill PID (or kill -9 PID to force it).
Linux permissions and killing processes are named in a 2024 candidate report — practical questions like these separate hands-on candidates.
A merge conflict happens when two branches change the same lines of a file (or one deletes a file the other edits) and Git cannot decide automatically which version to keep. Git marks the conflicting sections in the file with conflict markers showing both versions. To resolve: run git status to see conflicted files, open each file, edit it to the correct final content and remove the markers, then git add the file and complete the merge with git commit (or git rebase --continue during a rebase). To reduce conflicts, pull from the main branch frequently, keep pull requests small, and communicate when editing shared files.
Explain the workflow commands in order. Mentioning small, frequent merges shows team experience.
2xx means success: 200 OK (request succeeded) and 201 Created (a new resource was created, typically after POST). 4xx means a client-side error: 400 Bad Request (malformed input or failed validation), 401 Unauthorized (authentication missing or invalid), 403 Forbidden (authenticated but not allowed), 404 Not Found (resource does not exist). 5xx means a server-side error: 500 Internal Server Error (an unhandled failure on the server). Using the correct code helps API clients react properly — for example, retrying on some 5xx errors but not on a 400.
API status codes are listed among recent Persistent interview topics. The 401 vs 403 distinction is the most common follow-up.
By level: unit testing (individual functions or classes), integration testing (modules working together), system testing (the full application against requirements) and user acceptance testing (business users confirm it meets their needs). By knowledge of the code: white-box testing (internal logic) and black-box testing (behaviour only). Other important types include regression testing (re-running tests after changes), smoke testing (quick check that a build is stable), performance and load testing, and security testing. In practice, automated unit and integration tests run in a CI pipeline on every commit.
Link it to your own project — even a few unit tests you wrote make this answer far stronger.
Be specific: Persistent is a Pune-headquartered digital engineering and IT services company, so you would work on building software products and platforms for clients rather than only maintaining them. Mention something you verified — for example its early-career programs such as Career Compass and Hyperscaler Enablement for cloud certifications — and connect it to your own goals: 'I want to get cloud-certified early and work on product engineering; Persistent's programs and client work fit that path.' End with one skill you will bring from your projects.
HR rounds check that you researched the company. One accurate, specific detail is enough.
Common Mistakes in Persistent Systems Interviews
These are the mistakes that eliminate candidates at this stage — often before the technical round even begins.
- Skipping the Advanced Coding round preparation, which candidates report is tied to a higher offer tier.
- Preparing only textbook DSA and freezing on practical questions about Linux, Git or HTTP.
- Not knowing your own project deeply enough for a second technical interview focused on it.
- Treating the English section of the online test as easy and losing marks to time pressure.
- Relying on old reports of the test pattern without checking the current invite.
Frequently Asked Questions
Ready to Land Your Offer at Persistent Systems?
Practice with real interview questions and optimize your resume using FundoCareer's placement prep suite.