Persistent Systems Interview Experience for Freshers
Interview Experience
Round: 1In the first round, Online MCQs were based on Core CS Subjects like Computer Networking, DBMS, C Programming, OS, etc, then there was English, Logical Reasoning, P...
Full Details
Round: 1 In the first round, Online MCQs were based on Core CS Subjects like Computer Networking, DBMS, C Programming, OS, etc, then there was English, Logical Reasoning, Puzzles, and Numerical Aptitude MCQs. The Aptitude questions were basic-medium level, one can easily solve them if they practice the basic questions of each Numerical Aptitude category like Time Series, GCD and LCM, Profit, and Loss, Percentage, etc. There were also 2 basic-medium-level coding questions. The coding questions carried the maximum weightage, as those who didn't do well on the MCQ section were also allowed in the
next round because they successfully completed both codes and got a 100% score. Round: 2 The second round was a Technical interview. Those who were qualified from the last round received an email consisting of the joining link for the Virtual Technical Interview. The interview lasted for at least 45 minutes for me. The questions that were asked are given below: Introduce yourself. Then he asked me to show him my resume. I opened it on my device and shared the screen. He went through that. Then he asked me about my projects and told me to explain them, like what my approach was, which Technologies I have used, how that project would be useful if implemented heavily, etc. I also had four research papers published in IEEE, he looked interested in those two and said that out of all the candidates he has interviewed today, none of them had anything like that. So he also asked me about the topics of those research works and how they were unique. Then he asked me about my preferred language. I said Python. He then asked me what the difference was between a Set and a List. Then he asked me some OOP-related questions, like what is the difference between Encapsulation and abstraction? Then he asked me what is the similarities and differences between Python's Dictionary and Java's HashMap. Then he asked me Then he asked me what is the difference between NoSQL and SQL Databases. Then he asked me what I know about Cloud Computing. What is Virtualization? What are Horizontal Scaling and Vertical Scaling? What is the role of a Hypervisor in Cloud Computing? Name some renowned cloud service providers. Can you explain in brief about IaaS, SaaS, and PaaS? After the questions and my answers, he looked satisfied and asked me if I have any questions for him. I said no and he said okay you may leave. Round : 3 After the Technical Interview round, the HR interview was conducted, it was also an online virtual interview. The interview span was hardly 15 minutes, The HR asked me the following questions - Introduce yourself Where do you see yourself in 10 years? Why Persistent? What do you know about our company? If you have multiple offers which is more attractive than Persistent, would you accept Persistent? What are your hobbies? After that, she asked me if I have any questions for her, I asked how was my interview, in which parts I could improve myself, etc. Then she told me that I can leave. TIP: Focus on building projects and make your Resume strong, practice some basic questions related to your course curriculum. Don't panic if you can't remember any answer, just reply politely that you are unable to answer it now.
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.