GeeksforGeeks Question · May 2024

Persistent Systems Work Experience

PM System Design Intern Easy

Question Details

Being part of Persistent Systems has been a core for me since the summer internship last year become I had spent 5 months as an intern and the subsequent 3 months as a ful...

Full Details

Being part of Persistent Systems has been a core for me since the summer internship last year become I had spent 5 months as an intern and the subsequent 3 months as a full-time worker. For the second time I had again a good job offered, but the attitude of the employees towards my app in Airtel made the option look ridiculously simple for me. As it was one week following my start date, and initially during the phases of system setup and the knowledge transfer sessions, the task given to me was to work with the Airtel Payments Team for the African region in particular. Initially, it was a bit tricky, I had to run to learn the technologies chosen for me to work with which were previously unknown to me such as Angular and Spring Boot. Contrary to that, what motivated me the most was the firm but cheering support of my staff members. Key Responsibilities: I was a supervisor in front-end work processes the role was principal in my capacity as the front-end developer. I began with amending a few bugs, which were reported by the end users of the already running pages. After trading jobs with the lead frontend developer, I tailored the code produced into the clean and functioning final product. In addition, this assignment was my task for an internship class. After switching from being full-time, I entered the backlines and dealt with the system overseer and flow of the cargo. It was a fascinating as well as a great chance which I had during my working hours at Airtel, through which I met customers from different corners of the world. Moreover, regularly I interacted with the Product Managers to help them innovate by introducing new ideas for design and user experience, which was done through joint teamwork. Pros: Contrary to what most MNCs might have on their call, we won't have them. Let’s cut to the chase, with lax project deadlines being the most significant advantage of getting engaged at Airtel. Teammates that help create an environment where collaboration is a priority. The learning from the course was to learn how to independently feature completion, which was a great benefit. There is a lot of interesting technology and code-writing involved. Cons: Most people like the daily standup meetings, but they are blithely boring and nothing is new. Being a part of a small group allows more individual responsibility to be devoted to each team member. Sometimes, it feels like there could be less frequent heavy meeting schedules for agreeing on the approach although it adds to comprehensive end-to-in-tests. In general, it has been a great learning experience for me working at Persistent Systems, especially in the telecom sector dealing with Airtel. Regardless of the few challenges faced, I am happy and I have accomplished so much. A supportive environment, which brought forth a chance for me to grow independently and to be innovative also revamped my work experience.

Free preview — 6 questions shown. Unlock all Persistent Systems questions →

About This Question

This is a reported interview question from a persistent systems interview for a pm role (intern level) during the system design round reported in 2024.

Difficulty rating: Easy

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.