HR interview questions and answers

Give a story of 60 to 90 seconds in three parts: who you are, what you have built, and why you want this role.

Sample answer: "I am [your name]. I recently finished my [degree] at [your college]. During my degree I became interested in [web development / data / testing]. I built projects such as [project name], a [one-line description] using [technologies]. It taught me [skill]. I also did an internship at [company], where I [contribution]. I am comfortable with [two or three skills] and I learn quickly. Now I want a [role] position where I can use these skills in a real team and grow. That is why this opening at [company] interests me."

Keep it professional. Skip family and hobbies unless they matter for the job. End by linking your story to the role.

What they are checking: Can you give a clear, relevant summary in under two minutes?

Use present, past, future: your current role, your main achievements, and why you want this next step.

Sample answer: "I am a [role] with [number] years of experience in [domain]. Right now at [company], I lead/own [area]. There I [achievement with a number, for example cut release time by 40 percent]. Before that I worked on [previous experience], which gave me depth in [skills]. I enjoy [what motivates you: solving production problems, mentoring, building systems that scale]. Now I want a role with bigger [scope / ownership / technical challenges]. Your team's work on [area] fits that well."

Stay at about two minutes. Use numbers for your results. Do not read your CV line by line.

What they are checking: Can you tell a focused career story that shows impact?

Match your strengths to what the job needs, and show proof.

Sample answer: "You need someone who can [key requirement from the job description]. I have the base for it. I know [skills], and I showed them in [project/internship], where I [result]. I learn quickly and take feedback well. I do my work to a high standard. I will bring energy and ownership to the team, and with some guidance I will become productive fast."

If you have experience, replace the base with proven results: "In my last role I delivered [result]. This is similar to what this role needs." Do not criticize other candidates.

What they are checking: Can you connect your skills to what the employer needs?

Choose two or three strengths that matter for the job. Give one example for each.

Sample answer: "My main strengths are problem solving and quick learning. In my final-year project I had to add a payment API that I had never used. I read the documentation, built a small prototype, and finished on time. I am also a good team player. I communicate clearly and ask for help early. And I am careful about deadlines."

Pick real strengths, such as technical skills, learning speed, communication, ownership, or debugging. Do not make general claims without proof. Do not list more than three.

What they are checking: Do you know yourself, and can you back your claims with proof?

Name a real weakness that is not critical for the job. Show that you are working on it, and share your progress.

Sample answer: "I used to hesitate to ask for help. I spent too long stuck on a problem. I saw that this delayed one of my projects. Now I set a time limit. If I am stuck for 30 minutes after trying the documentation and a search, I ask a teammate. This has made me faster."

Other honest examples: public speaking (you joined presentations), polishing work too much (you set time limits), or giving work to others (for experienced people). Avoid fake weaknesses such as "I work too hard". Also avoid a weakness that the job really needs you to be good at.

What they are checking: Do you know your own limits, and do you want to improve?

Show that you studied the company. Connect it to your own goals.

Sample answer: "I have read about [company]'s work on [product/domain]. I like that [specific thing: engineering culture, product, learning programs]. I read about [recent news or project], and it matches my interest in [area]. I can help with [skill], and I can grow with the mentoring in your team."

Before the interview, read the website, product pages, blog, and job description. Avoid answers about salary only, or "it is close to home".

What they are checking: Are you truly interested, and did you prepare?

Show ambition that fits the company and the role. Do not name a job title that you must reach.

Sample answer: "In five years I want to be a strong engineer with deep skills in [area]. I want to own features from start to end and help newer team members. I would like to grow with a company like yours, maybe toward a senior or tech lead role, wherever I can add the most value."

Avoid "I will be in your seat" and "I do not know". Also avoid plans to leave the industry or start your own business within a year.

What they are checking: Do your goals match the role, and do you plan to stay?

Be positive and look forward. Never criticize your employer or manager.

Sample answers:

• Growth: "I have learned a lot at [company]. But now there are few new challenges for me. I want to work on [larger scale / new technology]."
• Role: "I want to move from [maintenance / support] into [development / architecture]."
• Stability or location: "The company changed its structure. I want a stable team with a clear plan."

Keep it short, honest, and the same as your CV. Then turn to the new job: "This role offers exactly [what you seek]."

What they are checking: Are you professional, and is your reason sensible?

First research the market range. Then give a range, not one number, and stay flexible.

Sample answer: "I have [X] years of experience and skills in [stack]. Based on the market for this role in [city], I am looking for something in the range of [X to Y]. The right role and growth matter more to me. So I am flexible, depending on the full package and responsibilities."

Tips:

• Check salary data on job sites and ask your peers.
• Think about total pay: bonus, insurance, learning budget, remote work.
• If they ask too early, ask back: "Could you share the budget range for this role?"

What they are checking: Do you know your market value, and can you negotiate in a professional way?

State your real notice period and say how flexible you are.

Sample answer: "My notice period is [60 days]. I have talked about it informally. I believe I can reduce it to [30 days] with a proper handover. I want to leave on good terms and make sure my work is handed over well."

For freshers: "I can join immediately / after my final exams on [date]." Do not promise a short notice that you cannot get. It causes trouble after the offer.

What they are checking: Is your joining time realistic, and are you professional about leaving?

Yes. Always ask two or three good questions.

Describe the company in a few words. Link it to your interest.

Show a method, not just "I stay calm".

Welcome it, act on it, and follow up.

Sample answer: "I listen without being defensive. I ask for specific examples and I say thank you. In one code review, a senior said my functions were too long and had no tests. I split them up, added tests, and asked for another review. Feedback is the fastest way to grow."

Give a specific, realistic date.

Sample answer for freshers: "I can join right after my final results / within [two weeks] of an offer."

Sample answer for experienced candidates: "My notice period is [60 days]. It may be possible to buy it out or reduce it to [30 days]. I will confirm after I talk to my manager."

Use STAR: Situation, Task, Action, Result. Keep the focus on what you did.

Sample answer:

• Situation: In my [final-year project / last project], a teammate and I disagreed. We could not agree if the backend should use [technology A] or [technology B].
• Task: I needed to settle it without delaying the project.
• Action: I asked to talk one-on-one and listened to their reasons. Then I suggested we compare both choices. We looked at speed of development, learning time, and project needs. We built a small prototype of each in half a day.
• Result: We chose [A] based on the facts. We finished on schedule. The teammate and I worked well together after that.

Show respect, good listening, and a focus on the goal, not on winning.

What they are checking: Can you solve conflict in a mature way and keep good relationships?

Choose a real failure with limited damage, own it, and show what changed.

Sample answer:

• Situation: In [project/internship], I was responsible for [feature] and underestimated the work.
• Task: Deliver by the sprint end.
• Action: On day three I saw that I was behind, but I waited to tell my lead. Later I told them. We cut the scope, and I stayed late to finish the main part.
• Result: We delivered a smaller version, one day late. I learned to report risks early and split work into smaller tasks. Since then I give daily status updates and add extra time to my estimates. My next two deliveries were on time.

Avoid failures that show a lack of honesty. Never blame others.

What they are checking: Can you take responsibility for mistakes and improve?

Show how you set priorities, communicate, and deliver.

Sample answer:

• Situation: Two days before a client demo, [feature] was still incomplete.
• Task: Get a working version ready for the demo.
• Action: I listed the remaining work and split it into must-have and nice-to-have. I agreed on this list with my lead and focused on the must-haves. A teammate reviewed code at the same time. I tested the demo flow twice.
• Result: We did the demo on time and the main flow worked. The client approved. We finished the rest the next week.

Say what you would do differently, such as making estimates earlier.

What they are checking: Can you set priorities and deliver under pressure?

Show that you disagreed with respect, used facts, and accepted the decision once it was made.

Sample answer:

• Situation: My manager wanted to ship a release without a full regression test to meet a date.
• Task: Raise my concern while supporting the business need.
• Action: I met them in private with facts: the last two releases without regression tests had [number] production bugs. I suggested testing only the most important flows (about four hours) and releasing on time.
• Result: They agreed. We shipped on schedule, and we found one blocking bug before the release.

If the manager decides otherwise, say you supported the decision and wrote down the risk.

What they are checking: Can you disagree with your manager in a helpful way?

Show a fast, structured learning approach and a result.

Sample answer:

• Situation: My team had to build a feature with [technology], which I had never used.
• Task: Become productive within a week.
• Action: I read the official documentation and followed a short tutorial. I built a small proof of concept (a quick test version). A senior colleague reviewed it. I wrote notes for the team while I learned.
• Result: I finished my part in the planned sprint. Later I used my notes to help two teammates get started.

Name a real technology and what you built.

What they are checking: Can you adapt and learn on your own?

Be honest and calm. Show that you take responsibility, communicate, and prevent a repeat.

Sample answer:

• Situation: After my change to [service], some users saw wrong [data/behavior] in production.
• Task: Restore service and prevent a repeat.
• Action: I told my lead at once, rolled back the release, and checked that the fix worked. I also told the affected team. Then I wrote down the root cause: a missing test for [edge case] and no check on staging. I added the test, a pre-release checklist item, and a monitoring alert.
• Result: Service was back in [20 minutes]. The same kind of problem has not happened since.

Do not hide it. Do not blame others.

What they are checking: Do you take responsibility and stop it from happening again?

You do not need a title to lead. Show that you took action, guided others, and got results.

Sample answer:

• Situation: Our team had uneven code quality and often had merge problems.
• Task: Improve it, even though I was not the lead.
• Action: I suggested a simple pull request checklist and a code review rotation. I set up automatic style checks (linting) in CI. Then I showed my teammates the process in a short session.
• Result: Review time dropped by [30 percent], and there were fewer merge conflicts. The lead used it for other teams too.

Freshers can use a college project, a student group, or a hackathon team.

What they are checking: Can you influence people and take action?

Show that you are open, that you act, and what the result was.

Sample answer:

• Situation: In a code review, my lead said my code was hard to read and had no tests.
• Task: Improve the quality of my work.
• Action: I asked for examples of good code and read the team style guide. I cleaned up the module and added unit tests. A week later I asked for another review.
• Result: The next review had far fewer comments. Now I check my own code against a checklist before I submit it.

Do not sound defensive.

What they are checking: Are you open to coaching?

Show that you understand the other person, that you have a clear method, and what the result was.

Sample answer:

• Situation: A client kept changing the requirements and complained about our speed.
• Task: Keep the project on track and rebuild the relationship.
• Action: I met the client to understand their pressure. I set a weekly meeting to review priorities. I started to show working demos every sprint. I wrote down each change and its effect.
• Result: Changes became fewer. The client approved the next phase, and we got good feedback.

Do not describe the person as just "bad".

What they are checking: Can you manage relationships?

Show what you did yourself and what the team achieved.

Sample answer:

• Situation: Our team of four had to build [application] for a hackathon / college project in a week.
• Task: I owned the [backend/API part].
• Action: We split the tasks on a board and agreed early on how the parts connect. We had short daily meetings. I also helped another member join the parts together.
• Result: We finished on time and came [position] / got top marks.

Use "I" for your actions and "we" for the team result.

What they are checking: Do you contribute well in a team?

Pick a project that was hard technically or with people, and that had clear results.

1. अर्थ / के सोधिएको हो

यो प्रायः पहिलो प्रश्न हुन्छ। इन्टरभ्युअरले तपाईंको जीवनी होइन, यो जागिरसँग मिल्ने तपाईंको पढाइ, सीप र लक्ष्य छोटकरीमा सुन्न चाहन्छन्।

2. How to answer

• Follow present, past, future: who you are now, what you studied or did, and what you want next.
• Keep it to 60 to 90 seconds.
• Mention one or two skills that match the job.

3. Sample answer

Good morning. I am [your name], and I recently completed my [degree] from [your college]. During my studies I built a [project name] using [skill]. It taught me teamwork and problem solving. I also did a short internship at [organization], where I learned to work with deadlines. I learn new tools quickly and I am careful about details. Now I am looking for a role like [job title] where I can use these skills and grow with a good team. That is why I applied to your company.

4. Avoid

Do not tell your whole life story, family details, or read your CV line by line.

What they are checking: Is the answer short, clear and about the job?

1. अर्थ / के सोधिएको हो

इन्टरभ्युअरले तपाईंले कम्पनीबारे अध्ययन गरेको छ कि छैन र यो जागिर किन चाहनुभएको हो भनेर जान्न खोजेका हुन्।

2. How to answer

• Read the company website, products and recent news before the interview.
• Name one or two specific things you like.
• Link them to your own skills and goals.

3. Sample answer

I have read about [company name] and I like that you work on [product or service]. I also saw that you [recent news or value]. This matches how I like to work. My skills in [skill] can help the team. I believe your team will help me learn from experienced people. I want to build my career in [field], and this company gives a clear path to do that. I would be happy to help from the first day.

4. Avoid

Do not say 'just because I need a job'. Do not give a general answer that fits any company.

What they are checking: Did the candidate show real research about the company?

1. अर्थ / के सोधिएको हो

तपाईंको कुन सीप यो काममा काम लाग्छ भन्ने जान्न सोधिएको हो। प्रमाणसहितको उदाहरण दिनुपर्छ।

2. How to answer

• Pick two or three strengths that match the job.
• Give a short real example for each.
• Be confident, but do not boast.

3. Sample answer

My main strengths are quick learning and responsibility. For example, in my final year project at [your college], I had to learn [tool] in two weeks, and I finished my part on time. I am also reliable. When my team gave me a task, I finished it and helped others when they were stuck. I think these strengths will help me settle in quickly in this role and support the team from the start.

4. Avoid

Do not list many good words without examples. Do not choose a strength that has nothing to do with the job.

What they are checking: Are the strengths related to the job and backed by an example?

1. अर्थ / के सोधिएको हो

इन्टरभ्युअरले तपाईं आफ्नो कमजोरी स्वीकार गर्न सक्नुहुन्छ कि सक्नुहुन्न र सुधारका लागि के गर्दै हुनुहुन्छ भनेर हेर्छन्।

2. How to answer

• Choose a real but small weakness. It should not be a core skill of the job.
• Show the steps you are taking to improve.
• End on a positive note.

3. Sample answer

Earlier I used to feel nervous when speaking in front of a large group. I noticed this during my college presentations. To improve, I started volunteering for presentations in class and joined a small English speaking group at [place]. Now I am much more comfortable, but I still prepare well before any big presentation. I keep improving through practice and feedback.

4. Avoid

Do not say 'I have no weakness'. Do not give the fake answer 'I work too hard'.

What they are checking: Is the weakness honest, and is there a clear plan to improve?

1. अर्थ / के सोधिएको हो

तपाईंको लक्ष्य के हो र तपाईं कम्पनीमा लामो समय टिक्नुहुन्छ कि हुन्न भनेर बुझ्न यो प्रश्न सोधिन्छ।

2. How to answer

• Show growth in the same field and company.
• Be realistic: first learning, then responsibility, then leadership.
• Do not describe a plan that does not include the company.

3. Sample answer

In five years I see myself as a skilled professional in [field], with bigger responsibilities. In the first years I want to learn the work and the company processes well. After that I hope to take ownership of projects and maybe guide new team members. I want to grow together with this company and add real value as I grow.

4. Avoid

Do not say 'in your chair', 'abroad' or 'I have not thought about it'.

What they are checking: Are the goals realistic and linked to the company?

1. अर्थ / के सोधिएको हो

यो प्रश्नमा तपाईंले आफ्नो सीप र कम्पनीको आवश्यकता कसरी मिल्छ भनेर छोटकरीमा बेच्नुपर्छ।

2. How to answer

• Match two or three skills to the job description.
• Mention one proof, such as a project or result.
• Show your attitude: eager to learn and responsible.

3. Sample answer

I believe I am a good fit because my skills match what you need. I worked on [project name], where I used [skill], and I can use the same skill in your work. I learn fast, I take responsibility for my tasks, and I work well with others. I may be new to the industry, but I bring energy and honesty. I will work hard to deliver results for your team.

4. Avoid

Do not compare yourself badly with other candidates. Do not just say 'I need this job'.

What they are checking: Does the candidate link their skills with the needs of the job?

1. अर्थ / के सोधिएको हो

कम्पनीले तपाईंको अपेक्षा बजेटसँग मिल्छ कि मिल्दैन भनेर हेर्न चाहन्छ। नेपालमा यो प्रश्न धेरै ठाउँमा सोधिन्छ।

2. How to answer

• Before the interview, research the usual pay for this role and your experience (job sites, friends in the field).
• Give a range in NPR, not one fixed number, and say you are open to talk.
• Ask about the full package: allowances, bonus, insurance, growth.

3. Sample answer

I looked at my skills and at similar roles in Nepal. I expect a range of NPR [lower amount] to [higher amount] per month. I am flexible. I am more interested in learning and growing here. If you can share the salary structure for this position, I would be happy to discuss what works for both sides.

4. Avoid

Do not give a very high or very low number without research. Do not say 'whatever you give'.

What they are checking: Is the answer researched, flexible and professional?

1. अर्थ / के सोधिएको हो

इन्टरभ्युअरले तपाईंले पुरानो कम्पनीबारे नकारात्मक कुरा गर्नुहुन्छ कि गर्नुहुन्न र तपाईंको कारण ठोस छ कि छैन भनेर हेर्छन्।

2. How to answer

• Be honest but positive: growth, learning, a new challenge.
• Never blame the old boss or colleagues.
• Connect your reason to why you want this job.

3. Sample answer

I enjoyed my time at [previous company] and learned a lot about [skill]. After [duration], I felt I needed new challenges and a bigger role. This position offers that chance, and it matches the direction I want for my career. I left on good terms and I still respect the team there.

4. Avoid

Do not speak badly about your old employer, manager or salary.

What they are checking: Is the reason positive, honest and about the future?

1. अर्थ / के सोधिएको हो

यो प्रश्नले तपाईंको चासो र तयारी देखाउँछ। 'छैन' भन्नु राम्रो मानिँदैन।

2. How to answer

• Prepare two or three smart questions.
• Ask about the team, training, what is expected in the first 3 months, or next steps.
• Do not ask about salary or leave first.

3. Sample answer

Yes, I have two questions. What would a successful first three months look like in this role? And what kind of training or support does the team give to new members? I would also like to know the next steps in the hiring process. Thank you for your time.

4. Avoid

Do not say 'No, nothing'. Do not ask things you can find on the website.

What they are checking: Did the candidate ask thoughtful questions?

1. अर्थ / के सोधिएको हो

नयाँ स्नातकसँग काम गरेको अनुभव हुँदैन। इन्टरभ्युअरले सिक्ने क्षमता र जिम्मेवारी हेर्न चाहन्छन्।

2. How to answer

• Accept that you are new, then show proof of skill: projects, internships, volunteering.
• Highlight that you learn fast and have discipline.
• Offer a trial or a small task if it suits.

3. Sample answer

I understand that I do not have full-time experience, but I have practical work to show. I built [project name] on my own, did [internship or volunteering], and learned [skill] through online courses. I learn quickly, I am willing to take guidance, and I take responsibility for my work. Please give me a chance, and I will prove my value with results and a good attitude.

4. Avoid

Do not say sorry too much. Do not sound hopeless about having no experience.

What they are checking: Does the candidate turn a lack of experience into a strength?

1. अर्थ / के सोधिएको हो

काममा समयसीमा र दबाब सामान्य हो। इन्टरभ्युअरले तपाईं शान्त रहेर काम गर्न सक्नुहुन्छ कि हुन्न भनेर हेर्छन्।

2. How to answer

• Explain your method: set priorities, break the work into steps, ask for help.
• Give a real example of a deadline you met.
• Show that you stay calm.

1. अर्थ / के सोधिएको हो

टिमवर्क लगभग हरेक जागिरमा चाहिन्छ। एउटा साँचो घटना सुनेर तपाईंको भूमिका बुझ्न खोजिन्छ।

2. How to answer

• Use the STAR method: Situation, Task, Action, Result.
• Say what you did yourself, not only 'we'.
• Show good communication and respect for others.

1. अर्थ / के सोधिएको हो

तपाईंले कम्पनीबारे कति तयारी गर्नुभयो भनेर परीक्षा गर्ने प्रश्न हो।

2. How to answer

• Read the About page, services, clients and recent news.
• Say it in your own words in 3 or 4 lines.
• End with why it interests you.

If you must answer, be honest about your current salary. Then focus on the range you expect, based on the market and the role.