Persistent Systems Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 1,118 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Persistent Systems.
Persistent Systems
Software Engineer
Senior Average Negative experience No offer 1 round
Interview process
Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral
I spent the whole day doing all the interview rounds. After the last HR talk, I got an email to send my documents, which I did fast. But soon after, they told me someone else got the job. It was super disappointing and felt like a fake interview. The company wasn't clear or organized, so I totally wasted my time. Management tip: Make sure the job is still open before you do final interviews and ask for papers. Value the candidate's time and effort.
Confirmed questions1 question
- Could you answer some technical questions related to your experience and past projects?
Persistent Systems
Software Engineer
Entry Difficult Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Coding Behavioral Technical
So the whole thing had three parts. First, there was this online test, you know, with like aptitude stuff, basic coding, and data structures. Then, the second part was a proper technical interview, where I had to code some things, explain how I did it, and talk about OOP, databases, and OS. The last part was with a manager, mostly about my past projects, how I figure things out, how I talk to people, and how I deal with deadlines or disagreements.
Confirmed questions1 question
- Can you describe a project you were involved in, detailing its architecture, your specific contribution, and the main technical hurdles you encountered?
Persistent Systems
Software Engineer
Mid Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical
So I had this interview yesterday for a Node.js gig, and man, it was rough. The guy interviewing me was super rude and unprofessional the whole time. He hit me with three coding questions, which I totally aced. Then he went on to some basic Node.js stuff, and I nailed those too. But then he started throwing these weird, unclear questions that didn't even seem related to the job, and I got the vibe he didn't know the answers himself. Even though I crushed the technical parts, his attitude just made the whole thing feel awful. It really sucked to see that kind of unprofessionalism after I worked hard to get ready.
Confirmed questions1 question
- Could you explain the event loop in Node.js and its thread pool?
Persistent Systems Software Engineer Interview Questions
Quoted word for word from Persistent Systems interview reports.
“What's an algorithm to find all positions of a character in a word, even if it appears multiple times?”
Read reports →“Can you find the index of the second non-repeated character in a given string?”
Read reports →“What is the difference between a switch and a router, and what is subnetting?”
Read reports →“How would you write an SQL query to retrieve the top two records from a table?”
Read reports →“Can you explain the distinctions between Java's public, private, protected, and default access modifiers?”
Read report →“What is a lock and what types of data structures are there? How do we use locks in the real world?”
Read report →“What are the core concepts of OOP, such as inheritance, polymorphism, abstraction, and encapsulation?”
Read report →“What are BFS and DFS and where are they used in the real world?”
Read report →“Can you explain the Java 8 stream API and its core concepts?”
Read report →Formats, difficulty and experience
Across all 1,118 Persistent Systems interview reports.