Persistent System Interview Experience
Question Details
Round-1: Technical Interview Round-1The first technical interview lasted for about 2 hours and covered a broad spectrum of Data Structures and Algorithms (DSA) topics. The...
Full Details
Round-1: Technical Interview Round-1 The first technical interview lasted for about 2 hours and covered a broad spectrum of Data Structures and Algorithms (DSA) topics. The interviewer asked in-depth questions on linked lists, trees, and dynamic programming (DP). The questions were challenging and required a solid understanding of the concepts as well as the ability to apply them to solve problems efficiently. Suggestions for Preparation: Linked Lists: Be well-versed with operations like insertion, deletion, reversal, and detection of cycles. Understand different types of linked lists (singly, doubly, circular). Trees: Focus on binary trees, binary search trees, AVL trees, and heaps. Be prepared to write code for traversals (in-order, pre-order, post-order) and understand concepts like balancing trees. Dynamic Programming: Practice problems involving memoization and tabulation. Common topics include the Knapsack problem, longest common subsequence, and matrix chain multiplication. Using resources like GeeksforGeeks for DSA practice can significantly boost your confidence and problem-solving skills. Round-2: Technical Interview Round-2 The second technical interview was around 1.5 hours long and consisted of solving two coding problems. The problems tested my ability to write efficient and clean code under time constraints. The focus was on understanding the problem, devising an optimal solution, and implementing it correctly. Tips for Success: Practice coding problems regularly on platforms like GeeksforGeeks, LeetCode, and HackerRank. Focus on writing readable and optimized code. Pay attention to edge cases and test your solutions thoroughly. Round-3: Verbal English Round This round involved various activities to assess my English speaking and typing skills. The tasks included speaking on given topics, typing passages accurately, and participating in a mock conversation. The goal was to evaluate my communication skills, both verbal and written. Preparation Advice: Engage in regular reading and writing practices. Participate in discussions or debates to improve verbal communication. Use typing practice tools to enhance speed and accuracy. Round-4:
HR Round The HR interview focused on understanding my personality, background, and future aspirations. Questions ranged from "Tell me something about yourself" to scenarios involving team conflicts and management. The interviewer also inquired about my projects, extracurricular activities, and location preferences. Tips for the
HR Round Be honest and articulate about your experiences and goals. Showcase your problem-solving and team collaboration skills through examples. Stay calm and answer questions politely and confidently.
About This Question
This is a reported interview question from a persistent systems interview for a eng manager role during the oa round reported in 2024.
It covers the following topics: Oop, Linked List, Trees, Dynamic Programming, Binary Search, Matrix .
Difficulty rating: Hard
More Persistent Systems Interview Questions
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.