Persistent Systems Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Persistent Systems.
Persistent Systems
UI Developer
Entry Average Positive experience Accept offer 5 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Background check Recruiter call
Interview formats
Technical Coding Behavioral
So the whole process starts with like an online assessment, then after that there are like two to three technical rounds, then you have a chat with a manager, and finally, an HR interview. Basically, they want to see how good you are at coding, how you solve problems, what you know technically, how you communicate, if you can work with a team, and if you're a good fit for the company and its future plans.
Confirmed questions1 question
- For a given array, describe a method to partition its elements such that all odd numbers appear on the left and all even numbers appear on the right.
Persistent Systems
UI Developer
Mid Average Neutral experience No offer 3 rounds
Interview process
Technical screen Technical screen Background check
Interview formats
Technical Behavioral
So I had two technical rounds and totally passed them. The next step was a manager round, but it ended really quickly, like in five minutes because the manager was arguing with his wife and wasn't on mute. I tried to ask HR about it but they never got back to me.
Confirmed questions3 questions
- Can you tell me about your experience with HTML, CSS, JS, and Bootstrap basics, as well as your current project and role?
- What do you think went wrong during the interview process?
- What went wrong with the interview
Persistent Systems
UI Developer
Senior Difficult Negative experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding
I had an Angular front-end interview, not sure if it was screening or first technical round. They really dug into concepts, and it was tough. They wanted every piece of code written out. The interview lasted over 1.5 hours. Then I got a call for a client interview. The client was unhappy with my answers and kept asking if there was another way to do things even after I gave multiple solutions, like they had a specific answer in mind. They didn't even grasp basic shallow and deep copy concepts, needing more than 5 explanations. It felt unprofessional and like a waste of time.
Confirmed questions1 question
- Questions about Angular, JS, HTML, and Bootstrap.
Persistent Systems Frontend Engineer Interview Questions
Quoted word for word from Persistent Systems interview reports.
“Can you design a search bar component in React?”
Read reports →“Can you explain state management and the Context API in React?”
Read reports →“What went wrong with the interview”
Read reports →“Were there basic Node.js questions?”
Read reports →“Was there a programming question in React?”
Read report →“Can you explain Object-Oriented Programming concepts?”
Read report →“What do you think went wrong during the interview process?”
Read report →“Could you elaborate on how you've utilized ReactJS in your projects?”
Read report →“Can you tell me about your experience with HTML, CSS, JS, and Bootstrap basics, as well as your current project and role?”
Read report →Formats, difficulty and experience
Across all 11 Persistent Systems interview reports.