Persistent Systems is known for a rigorous campus hiring process that includes a timed coding test with a noticeably higher difficulty bar than most Indian IT services firms.
Engineers join product engineering and ISV teams primarily in Pune, Nagpur, and Bengaluru, building software for healthcare, BFSI, and technology clients. Interviewers value clean code, proper time and space complexity analysis, and hands-on debugging ability.
About Persistent Systems
Persistent Systems is a mid-tier IT services company listed on NSE/BSE, with deep domain in healthcare technology, banking and financial services (BFS), and enterprise digital transformation. Salary benchmarks are above average for pure IT services peers.
Apply through the Persistent Systems careers page or via your campus placement cell.
Clear the online coding assessment: two to three DSA problems with time and space complexity requirements.
Attend technical interview round 1: algorithmic problem-solving and code walkthrough.
Clear technical round 2: system design basics, OOPS, DBMS, and project deep dive.
HR round: compensation, location, technology specialisation track, and onboarding date.
Online Coding Test (90 min)
two to three DSA problems (arrays, trees, dynamic programming), evaluated on correctness and complexity. No MCQ filler.
Technical Round 1 (45-60 min)
live coding on a shared editor, OOPS design, and discussion of time and space trade-offs in your solutions.
Technical Round 2 (45-60 min)
DBMS concepts (normalisation, indexing, SQL), OS fundamentals, and a walkthrough of your most complex project.
HR Round (20-30 min)
offer details, technology domain preference, expected joining date, and relocation discussion.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical Persistent Systems recruitment process has 5 stages: Apply through the Persistent Systems careers page or via your campus placement cell. → Clear the online coding assessment: two to three DSA problems with time and space complexity requirements. → Attend technical interview round 1: algorithmic problem-solving and code walkthrough. → Clear technical round 2: system design basics, OOPS, DBMS, and project deep dive. → HR round: compensation, location, technology specialisation track, and onboarding date..
Persistent Systems typically conducts 4 interview rounds: Online Coding Test (90 min): two to three DSA problems (arrays, trees, dynamic programming), evaluated on correctness and complexity. No MCQ filler.; Technical Round 1 (45-60 min): live coding on a shared editor, OOPS design, and discussion of time and space trade-offs in your solutions.; Technical Round 2 (45-60 min): DBMS concepts (normalisation, indexing, SQL), OS fundamentals, and a walkthrough of your most complex project.; HR Round (20-30 min): offer details, technology domain preference, expected joining date, and relocation discussion..
HireStepX recommends the Clean Code Under Pressure framework for this type of interview: Solve DSA problems with explicit complexity analysis, write readable code without IDE support, and articulate design decisions clearly: Persistent values depth over memorised answers.
To answer this question well, HireStepX recommends the Clean Code Under Pressure approach: Solve DSA problems with explicit complexity analysis, write readable code without IDE support, and articulate design decisions clearly: Persistent values depth over memorised answers. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clean Code Under Pressure approach: Solve DSA problems with explicit complexity analysis, write readable code without IDE support, and articulate design decisions clearly: Persistent values depth over memorised answers. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clean Code Under Pressure approach: Solve DSA problems with explicit complexity analysis, write readable code without IDE support, and articulate design decisions clearly: Persistent values depth over memorised answers. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clean Code Under Pressure approach: Solve DSA problems with explicit complexity analysis, write readable code without IDE support, and articulate design decisions clearly: Persistent values depth over memorised answers. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clean Code Under Pressure approach: Solve DSA problems with explicit complexity analysis, write readable code without IDE support, and articulate design decisions clearly: Persistent values depth over memorised answers. Ground your answer in a specific real example from your own experience.