Persistent Systems HR interview questions and answers

12 Persistent Systems HR interview questions with sample answers: why HR asks each one and how to answer. From public candidate reports. Free.

At Persistent Systems the HR round usually comes after you clear the online test and the technical interview, and for freshers it is often bundled into the same day or the next slot. It is run by an HR executive, not your future manager, and most candidates report it lasting 20 to 30 minutes. The tone is conversational, but this is where they lock down salary, joining date, location and the service agreement, so treat it as a real filter and not a formality.

What the Persistent Systems HR round checks:

Clear and honest motivation for joining Persistent
Comfort with the offered CTC and the service agreement
Willingness to relocate or work in shifts
Stable background and no gaps you cannot explain
Notice period and how soon you can join

The first question is always some version of "tell me about yourself". Write your self introduction for the interview (free, no signup).

Persistent Systems HR interview questions with answers

6 of these 12 questions appear in public Persistent Systems interview reports; the rest are standard HR questions the company is known to ask.

1. Tell me about yourself. (reported)

Why they ask: It is the opener, and they use it to see if you can summarise your background in under two minutes without rambling.

How to answer: Cover three things in order: where you studied or worked, what you have built or worked on, and why you are sitting in this interview. Keep it to 90 seconds and end on Persistent, not on your childhood. Do not recite your resume line by line.

Sample answer: I completed my [degree] from [your college] in [year], and my main interest has been backend development. During my final year I built a [project name] using [tech stack], where I handled the API layer and the database design. After that I worked on [internship or job] for [duration], mostly on [main task]. I am looking at Persistent because the work spans product engineering for global clients, and I want to grow in a place where I get exposure to real delivery pressure early.

2. Why do you want to join Persistent Systems? (reported)

Why they ask: They want to hear something specific about the company, not a generic line about a good work culture.

How to answer: Pick one or two real things about Persistent, like its engineering work across cloud, data and product development, or its long-running client engagements. Connect it to what you have actually done. Avoid saying you want to join because it is a big company.

Sample answer: Two reasons. First, Persistent works on product engineering for global clients rather than only support projects, and that is the kind of work I want to do early in my career. Second, from what I read and from people I spoke to, the teams are small enough that a junior gets real ownership of a module. I have done [project or task] on my own, so that setup suits how I like to work.

3. Are you willing to relocate to any Persistent location? (reported)

Why they ask: Persistent places people across Pune, Hyderabad, Bangalore, Nagpur and client sites, and they need to know you will not back out after the offer.

How to answer: Say yes clearly if you mean it, and mention any genuine constraint upfront rather than after joining. If you have a real limitation, state it once, calmly, and say what you can do instead. Do not say yes and then negotiate location later.

Sample answer: Yes, I am open to relocating. I have already discussed it at home and there is no problem. My only request would be that if there is a choice, I would prefer [Pune or your preferred city], but I am fine with whatever the project needs. I would rather sort this out now than after joining.

4. What is your expected CTC? (reported)

Why they ask: They are checking whether your number fits the band they have already fixed for your role and level.

How to answer: For freshers, the number is usually fixed, so say you are comfortable with the standard offer for the role. For experienced candidates, give a range based on your current fixed pay plus a reasonable hike, and mention that you are open if the role is strong. Never give a single rigid number without context.

Sample answer: For this role I understand there is a standard band, so I am comfortable with whatever Persistent offers for my level. If you want a number from my side, my current fixed pay is [amount] and I am looking at something in the range of [X to Y], but I am flexible if the project and the learning are right. I care more about the work than squeezing the last rupee.

5. Are you comfortable with the service agreement or bond? (reported)

Why they ask: Persistent, like most Indian IT firms, asks freshers to sign a service agreement, and they want to know you have read it and are not going to leave in six months.

How to answer: Say you are aware of it and comfortable, and ask the duration and the amount if it has not been stated. Do not act surprised or start negotiating the bond in the HR round. If you have a genuine plan to study further, say so now.

Sample answer: Yes, I am comfortable with it. I understand there is a service agreement for freshers and I have no plans to leave early. Could you tell me the duration and the amount so I have it clear? I am asking only so I can plan properly, not because I have an issue with it.

6. What is your notice period and when can you join? (reported)

Why they ask: They are matching you to a project start date, and a long notice period can push you out of the current batch.

How to answer: Give the exact notice period from your offer letter or company policy, and then give the earliest realistic joining date. If you can join earlier, say so. Do not say immediate if you actually have 60 days to serve.

Sample answer: My notice period is [30 or 60 or 90] days as per my current company. If the offer comes through, I can serve it and join by [date]. If you need someone earlier, I can check whether my manager will release me sooner, but I cannot promise that until I ask.

7. Tell me about a time you worked in a team and handled a disagreement.

Why they ask: They want evidence that you can work with people without creating friction, which matters more in services than raw coding skill.

How to answer: Pick one real incident, keep it short, and focus on what you did, not on how wrong the other person was. End with the outcome and what you changed in your own approach. Do not pick a story where you were clearly the hero and everyone else was stupid.

Sample answer: In my final year project, four of us were building [project], and two of us wanted to use [tech A] while the others wanted [tech B]. We were stuck for two days. I suggested we each build a small proof of concept over a weekend and compare. [Tech B] turned out faster for our use case, so we went with it. I was on the losing side, but the decision was based on data, and we finished on time.

8. What are your strengths and weaknesses?

Why they ask: Standard question, but they are really checking whether you can be honest about a weakness without dressing it up as a strength.

How to answer: Give one real strength with a short example, then one real weakness and what you are doing about it. Keep the weakness genuine but not disqualifying. Do not say you are a perfectionist.

Sample answer: My strength is that I finish what I start. In my internship I was given a small module and I stayed on it until it was tested and documented, even after my mentor moved to another project. My weakness is that I used to spend too long polishing code before showing it. I have started pushing early drafts for review, and it has cut down my rework a lot.

9. Where do you see yourself in three years?

Why they ask: They want to hear that you plan to grow inside Persistent and not use it as a stepping stone for a master's abroad.

How to answer: Talk about depth in one area, taking ownership of a module, and being the person juniors come to. Avoid saying you want to do an MBA or move into management by year two. Keep it grounded in the work you would actually do.

Sample answer: In three years I want to be strong in one area, probably [backend or cloud or data], and be the person who can own a module end to end without hand holding. I would also like to have mentored a couple of juniors by then. I am not in a hurry to move into management, I would rather be genuinely good at the engineering first.

10. Do you have any questions for us?

Why they ask: They are checking whether you have thought about the role seriously or are just collecting offers.

How to answer: Ask two questions about the work, not about perks. Good ones are about the team you would join, the tech stack, or how the first six months are structured. Avoid asking about salary again or about work from home policy at this stage.

Sample answer: Yes, two things. What kind of projects would a fresher typically be staffed on in the first year, and is there a training period before that? And second, how is the team structured, do we report to a project manager or a technical lead? I am asking because I want to know what the first six months actually look like.

11. Are you comfortable working in shifts or on client time zones?

Why they ask: Persistent serves global clients, so some projects need early morning or late evening overlap, and they want to filter out people who will refuse later.

How to answer: Be honest. If you can do it, say yes and mention any hard limit you have. If you cannot, say so now rather than after training. Do not agree to something you know you will not sustain.

Sample answer: Yes, I am fine with shifts as long as it is planned and not changing every week. I have worked late during my internship when a release was close, so it is not new to me. If there is a fixed night shift for months together, I would like to understand that before I commit, but occasional overlap with a client time zone is not a problem.

12. Why should we hire you?

Why they ask: It is the closing question, and they want a short, confident summary rather than a repeat of your resume.

How to answer: Give two concrete reasons tied to the role, one on skill and one on attitude, and stop. Do not list five things. Confidence here matters more than content, so keep your voice steady and do not trail off.

Sample answer: Two reasons. On skill, I have already built and shipped [project or feature] using [tech stack], so I can start contributing to a module instead of only learning for six months. On attitude, I ask questions early and I do not sit stuck on a problem for two days. In my internship my mentor told me that was the main difference between me and the previous intern, so I will take that as a good sign.

What candidates report about the Persistent Systems HR round

Service agreement. Candidates commonly report that Persistent asks freshers to sign a service agreement with a defined bond period and amount. Confirm the exact duration and figure with HR in this round rather than assuming.

Locations. Persistent has offices in Pune, Hyderabad, Bangalore and Nagpur, and freshers are often posted based on project need. Relocation willingness is asked directly in the HR round.

Shift work. Because the company serves global clients, some projects need overlap with US or Europe time zones. HR may ask about shift flexibility, so have a clear answer ready.

Offer and joining timeline. Freshers commonly report that the HR round happens on the same day as or right after the technical round, with the offer following within a few weeks. Keep your documents ready in case verification starts early.

Document checks. Standard Indian IT verification applies: marksheets from class 10 onwards, degree certificate or provisional, ID proof, and previous offer or relieving letters if you are experienced. Commonly reported, not specific to this company alone.

How to prepare

Decide your relocation and shift answers before the interview. Changing your mind after the offer is the fastest way to lose it.
Know your own resume cold. HR often picks one project or internship line and asks you to explain it in plain words.
Have your CTC number or range ready for experienced roles, and know your exact notice period from your offer letter.
Read the service agreement terms if HR shares them, and ask about duration and amount in the same conversation, not later.
Keep scanned copies of marksheets, ID and relieving letters in one folder on your phone. Document verification can start soon after the HR round.

Practise the Persistent Systems HR round in a free 5-minute mock

Persistent Systems technical rounds

Quick answers about the Persistent Systems HR round

What is asked in the Persistent Systems HR interview?

Candidates report questions such as: Tell me about yourself.; Why do you want to join Persistent Systems; Are you willing to relocate to any Persistent location; What is your expected CTC. Each one is answered on this page.

How long is the Persistent Systems HR round?

Can I fail the Persistent Systems HR round?

Yes. Candidates are rejected in the HR round for unclear answers on relocation, shifts or the package, for contradicting their resume, or for seeming uninterested in Persistent Systems. Decide your honest answers before the call.

Are these questions official?

No. They come from public candidate reports and are unofficial. PortLume AI is not affiliated with Persistent Systems.

Sources

Based on 11 public reports: YouTube (11), last updated Oct 2026.

Unofficial guide from public candidate reports. PortLume AI is not affiliated with Persistent Systems. HR questions for other companies · all company interview guides.

PortLume AI

Loading…