The HR interviewer is not testing your technical skill; that happened in earlier rounds. They want to know three things: can you communicate clearly, will you fit the team and the company's way of working, and are the practical details (notice period, location, salary) going to work out. Every question below maps to one of those.
Use the sample answers as a shape, not a script. Swap in your own college, projects and numbers. An answer that is true and specific always beats a polished one that sounds memorised.
1. Tell me about yourself
What they check: whether you can summarise yourself in a minute or two and pick what matters for this job. Keep it to about 90 seconds: who you are now, what you have done, one proof of it, and why this role.
This question deserves its own preparation, so we wrote a full guide with sample answers for a fresher, an IT professional and a career switcher: how to answer "tell me about yourself".
2. What do you know about our company?
What they check: whether you are interested in them or applying everywhere. Spend ten minutes on their website, recent news and the job description before the interview.
"You build billing and payments software for banks, and I read that you recently launched a UPI product for small merchants. The role I applied for is in the payments team, which is what interested me most, because my final-year project was a small expense-splitting app with UPI links."
3. Why do you want to join us?
What they check: motivation that will last. Connect something real about the company (its products, its training, the kind of work) to something real about you. Avoid answers that are only about salary or brand name.
"I want to start my career where I can work on real client projects early and learn from structured training. Your programme puts freshers on live projects after the training period, and the role uses Java and SQL, which I enjoy and have practised in my projects."
4. Why should we hire you?
What they check: whether you understand the job and can match yourself to it. Pick two or three requirements from the job description and give one piece of proof for each.
"You need someone who can support production systems and keep improving them. For the last two years I have been on the support rotation for an order management system, where I reduced repeat incidents by writing small automation scripts. I'm also comfortable talking directly to clients, which this role needs."
5. What are your strengths?
What they check: self-awareness. Name one or two strengths that matter for this job and back each with a short example. "Hard-working and dedicated" without an example says nothing.
"I learn new tools quickly. In my internship I had to pick up Power BI in a week to build a sales dashboard, and I finished it before the review. I'm also patient with debugging; I like finding the exact cause instead of guessing."
6. What is your biggest weakness?
What they check: honesty and whether you work on yourself. Choose a real weakness that won't break this job, and say what you are doing about it. Avoid disguised boasts like "I work too hard".
"Public speaking used to make me nervous, and I would rush my presentations. In my last semester I volunteered to present our project to juniors twice, and I now practise out loud before any presentation. I'm much calmer now, though I still prepare more than most people."
7. Where do you see yourself in five years?
What they check: whether you will stay and grow. Talk about skills and responsibility, not a job title at another company.
"I'd like to be someone the team relies on for a whole module, from design to release, and to be mentoring new joiners. I'd also like to have gone deep into cloud technologies, which I see the company is investing in."
8. Why are you leaving your current job?
What they check: that you are moving towards something, not running away. Never criticise your current manager or company; keep it about growth.
"I've learned a lot in three years, but most of my work now is maintenance of the same application. I want to work on building new products, and this role is focused on exactly that."
9. Why is there a gap in your resume?
What they check: that the gap has a reason and that you kept your skills alive. Be brief and honest, then move to what you did and where you are now. Common reasons in India, such as preparing for government exams, family responsibilities or health, are understood if explained simply.
"After graduation I spent a year preparing for a government exam. It didn't work out, and I decided to return to software. In the last four months I completed a full-stack course and built two projects, which are on my GitHub."
10. Tell me about a challenge you faced
What they check: how you behave when things go wrong. Use the STAR method: the situation, your task, the actions you took and the result, with a number if you have one.
"In our final-year project, a teammate left two weeks before the demo (situation), and I had to take over the backend he was building (task). I split the remaining work into daily goals, asked our guide for an extra review and cut one feature we couldn't finish properly (action). We demoed on time, and the project got one of the top grades in our batch (result)."
11. How do you handle pressure and deadlines?
What they check: whether you stay calm and organised. Give your method and one example.
"I break the work into small pieces and do the riskiest part first, so surprises come early. During a release last year, a test environment failed a day before go-live; I told my lead immediately, we agreed what could move, and we released the critical part on time."
12. Are you willing to relocate or work in shifts?
What they check: a practical yes or no. Answer honestly; saying yes and refusing later is worse for everyone. If there is a condition, state it clearly and politely.
"Yes, I'm open to relocating to any of your locations. I can work in shifts as well; I'd only like to know the schedule in advance so I can plan my commute."
13. Are you comfortable with a service agreement?
What they check: common in IT services hiring of freshers, where training is followed by a minimum period of service. Ask for the terms in writing (duration, amount, conditions) before agreeing, and answer calmly.
"Yes, I'm looking to build my career here for the long term, so that works for me. Could you share the details of the agreement so I understand the terms properly?"
14. What are your salary expectations?
What they check: whether you are within their budget and realistic. Freshers in campus drives usually get a fixed package, so say you are fine with the company's standard offer. Experienced candidates should know their current CTC and give a researched range.
"My current CTC is 6.5 lakh. Based on the role and the market for this skill set, I'm looking at 8.5 to 9.5 lakh, but I'm open to discussing the full package, including the learning opportunities."
15. Do you have any questions for us?
What they check: interest and maturity. Always ask one or two. Good questions are about the work, not leave policy in the first round.
- "What does a typical first month look like for someone in this role?"
- "What would make someone successful in this team in their first year?"
- "What are the next steps in the process, and when should I expect to hear back?"
How to prepare in one evening
- Read the job description twice and underline the three most important requirements.
- Write one short true story for each: a project, a problem you solved, a time you worked in a team.
- Prepare your introduction and keep it to about 90 seconds.
- Say your answers out loud, not in your head. A mock interview with an AI interviewer is the quickest way to do this alone.
- Keep your documents, notice period and current CTC ready, so practical questions don't catch you off guard.
Myna can help on both sides of this: voice mock interviews built from the company and the job description, and live suggestions from your own resume when the real call happens. See the plans and the free trial.