Persistent Systems Interview Experience | On-Campus 2022
Question Details
Round 1 Aptitude RoundIt was held on the AMCAT platform and it was an easy round as quants weren’t part of the aptitude test and there were two easy coding problems to so...
Full Details
Round 1 Aptitude Round It was held on the AMCAT platform and it was an easy round as quants weren’t part of the aptitude test and there were two easy coding problems to solve but some of the test cases of 2nd question were not passing so, I am able to solve the first question fully and second one partially.
Round 2 Technical Interview Round 1 Time: 30-35 mins Tell me about yourself (In the introduction itself I give some brief about my project) OOPs (Polymorphism, Access Specifier, How can we achieve access specifier in c++, Constructors and its types, destructors) Pattern printing with code and explanation Quick Sort only approach BFS/DFS for trees Stack using queue or Queue using stack (anyone only with approach) Hub vs Switch If you type www.xyz.com and if you are not able to reach that site, so tell me some troubleshooting steps you would perform Normalization Some query's Keys Tell me about software testing Tell me how you can test the Youtube website (so I gave him some different edge cases over which I've test this site). There wasn’t any TR 2
Round 3 HR It was a 100 question web proctored test (all were HR basic questions) but in the mail, they say that we have only 20 minutes to solve this but there was no timer and also the camera open so, I take 25-30 minutes and some of my friends even take 35 minutes. Tips: My final tip is that you have to be confident about your answer and also be vocal.
Topics
More from Persistent Systems
About Persistent Systems Interview Reports
This question was reported by a candidate who interviewed at Persistent Systems. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Persistent Systems are the higher-signal extractions to take from this report.
For broader preparation context, the Persistent Systems interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Persistent Systems reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Persistent Systems Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Persistent Systems reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.