Persistent Systems Work Experience as a Software Developer
Interview Experience
I joined the company with 2 rounds of technical coding, last year in august. The Interview process was smooth and fast, I loved how all the communication was transparent. ...
Full Details
I joined the company with 2 rounds of technical coding, last year in august. The Interview process was smooth and fast, I loved how all the communication was transparent. (Its because we are given proper training and description of the requirements is often clear. I know this from the other side of the table.) Its a great company to start your career, if you are looking for some job security and learnings as well. This company is almost 30 year old and this year we hit billion dollar mark, I was lucky to be one of them who could actually see their company growing in stocks and performing well. Being a fresher, you will get a three months training ending with one exam to clear your probation period, and then based on your performance you would be assigned to projects which may or may not align with your training. I was lucky to be trained in full stack and get a project as a fullstack developer. I work with intuit as our client on QuickBooks. Nowadays, My key skills involve feature development using React. One of the highlights of my experience at persistent has been incredibly supportive colleagues, people here readily offer assistance, share knowledge and collaborate seamlessly making the overall learning experience satisfying. Seniors or juniors you will love the work culture and people. Overall its a good company to start your career but I must warn you for a few things as well. I have listed it down as pros and cons below . Cons/warnings Your over all experience in the company depends on the client project you work with, like in my case its intuit. Your seniors will be really friendly and helping towards your learning, but try respecting seniors and do not consider them your friend with whom you share your personal life with. Some times nature of your work can be repetitive leading to no growth. pros Location and timing flexibility ( you have to inform your manager about it.) Food facility Health care and investment support Goodies and talent recognition activities.
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.