Q1: Tell me about yourself.

What HR evaluates: Communication clarity, confidence, and whether you can summarize your professional identity in under 90 seconds. They are also checking if you ramble or stay focused.

How to answer: Use the Present-Past-Future formula. Start with what you do now, briefly mention your background, and end with why you are here.

Fresher example:
"I recently completed my B.Tech in Computer Science from 
[University]. During my final year, I built a full-stack 
inventory management system using React and Node.js, which 
my department now uses. I also completed an internship at 
[Company] where I worked on API development. I am looking 
for a role where I can apply my development skills and grow 
as a software engineer — which is why this position at 
[Company] interests me."

Experienced example:
"I am a Java developer with 3 years of experience at 
[Company], where I work on microservices using Spring Boot. 
My recent project involved migrating a monolithic billing 
system to microservices, which reduced deployment time by 
60%. Before that, I worked on REST API development and 
database optimization. I am looking for a senior role where 
I can take ownership of system design — and this position 
aligns with that goal."

Q2: Walk me through your resume.

What HR evaluates: Whether your verbal explanation matches your resume. Inconsistencies here are a red flag. They also check if you can explain career transitions logically.

How to answer: Go chronologically but spend 80% of the time on your most recent and relevant experience. Do not read your resume — add context that the resume cannot convey.

Q3: What are your hobbies and interests?

What HR evaluates: This is not small talk. They are checking for personality traits. “Reading” suggests curiosity. “Team sports” suggests collaboration. “Nothing specific” suggests low energy.

How to answer: Pick 1-2 genuine hobbies and add a specific detail. “I play badminton every weekend at my local club” is better than “I like sports.” If your hobby connects to the role (blogging for a content role, open-source for a dev role), mention it.

Q4: What are your strengths?

What HR evaluates: Self-awareness and whether your strengths match the role requirements. A developer claiming “leadership” as their top strength when applying for a junior coding role sounds disconnected.

How to answer: Pick 2 strengths relevant to the role. Back each with a specific example. The formula: Strength + Situation + Result.

Good answer:
"My strongest skill is debugging complex issues 
systematically. In my last project, we had a production 
memory leak that three developers could not find. I used 
heap dump analysis and traced it to an unclosed database 
connection pool — fixed it in 4 hours. My second strength 
is documentation — I write clear technical docs, which 
reduced onboarding time for new team members from 2 weeks 
to 3 days."

Bad answer:
"I am hardworking, dedicated, and a team player."
(Too generic — every candidate says this)

Q5: What are your weaknesses?

What HR evaluates: Honesty and self-improvement mindset. They want a real weakness — not a disguised strength. But they also want to see that you are actively working on it.

How to answer: Pick a genuine weakness that is not critical to the role. Show what you are doing to improve. Never say “I have no weaknesses” or “I work too hard.”

Good answer:
"I tend to over-research before starting a task. Earlier, 
I would spend too long reading documentation before writing 
code. I have been working on this by setting time limits — 
I give myself 30 minutes to research, then start building. 
If I get stuck, I research more. This has improved my 
delivery speed significantly."

Answers to avoid:
- "I am a perfectionist" (cliché)
- "I work too hard" (nobody believes this)
- "I have no weaknesses" (arrogant)
- "I am bad at [core job skill]" (disqualifying)

Q6: How would your previous manager describe you?

What HR evaluates: Whether you have a realistic self-image and whether your relationship with your manager was healthy. Candidates who hesitate or give vague answers raise concerns.

How to answer: Reference specific feedback you have received. “In my last appraisal, my manager mentioned that I am reliable with deadlines and proactive about flagging blockers early” is concrete and believable.

Q7: Why do you want to work here?

What HR evaluates: Whether you have researched the company. Generic answers like “It is a good company” or “For career growth” signal that you have not done any research.

How to answer: Mention something specific — a product, a recent achievement, the tech stack, or the company culture. Connect it to your career goals.

For a product company:
"I have been following [Company]'s work on [specific 
product/feature]. The engineering blog post about how your 
team handles [specific challenge] resonated with me because 
I have worked on similar problems. I want to work in an 
environment where engineering quality is prioritized."

For a service company (TCS/Infosys/Wipro):
"[Company] works with clients across banking, healthcare, 
and retail — which gives engineers exposure to multiple 
domains. I am particularly interested in the [specific 
practice/vertical] because it aligns with my experience 
in [relevant area]. The training programs and global 
opportunities are also factors."

What NOT to say:
- "For the salary" (even if true)
- "It is close to my house"
- "My friend works here"
- "It is a big brand name"

Q8: Why should we hire you?

What HR evaluates: Your ability to sell yourself without being arrogant. They want a concise pitch that connects your skills to their needs.

How to answer: Match 2-3 of your skills or experiences directly to the job description. End with what you bring that other candidates might not.

"You need someone who can build REST APIs and work with 
microservices — I have done exactly that for 2 years using 
Spring Boot and Docker. You also mentioned cross-team 
collaboration in the JD — in my current role, I work with 
3 teams across different time zones. What I bring 
additionally is strong documentation skills, which means 
faster knowledge transfer and fewer repeated questions."

Q9: What do you know about our company?

What HR evaluates: Preparation level. This is a pass/fail question — if you cannot name what the company does, the interview is effectively over.

How to answer: Before the interview, research: what the company does, recent news or achievements, the team or product you are interviewing for, and the company size and culture. Mention 2-3 specific facts.

Q10: Where do you see yourself in 5 years?

What HR evaluates: Retention risk. If your 5-year plan does not include the company, they will not invest in hiring and training you. They also check for unrealistic expectations.

How to answer: Show ambition that aligns with the company's growth path. For a developer role: “I see myself as a senior engineer or tech lead, owning the architecture of a product module.” Avoid saying “I want to start my own company” or “I want your job.”

Q11: Tell me about a time you faced a conflict at work.

What HR evaluates: Emotional maturity and conflict resolution skills. They want to see that you handle disagreements professionally — not that you avoid conflict entirely.

STAR format example:

Situation: "In my last project, a senior developer and I 
disagreed on the database design. He wanted a single 
monolithic table; I proposed a normalized schema."

Task: "We needed to decide before the sprint deadline, 
and the team was split."

Action: "I created a comparison document showing query 
performance for both approaches with sample data. I 
presented it in the team meeting without making it 
personal — just data."

Result: "The team went with the normalized approach. The 
senior developer appreciated the data-driven approach, 
and we actually became better collaborators after that."

Q12: Describe a situation where you worked under pressure.

What HR evaluates: Stress management and whether you can deliver when deadlines are tight. In Indian IT, tight deadlines are the norm — they need to know you will not crumble.

How to answer: Pick a real high-pressure situation. Describe what made it stressful, what you did (not what the team did), and the outcome. Quantify the result if possible.

Q13: Give an example of when you showed leadership.

What HR evaluates: Initiative and influence — not whether you had a “lead” title. Even freshers can show leadership through college projects, hackathons, or internship initiatives.

How to answer: Leadership is about taking initiative when nobody asked you to. “I noticed our deployment process had manual steps that caused errors, so I created a CI/CD pipeline and trained the team on it” — that is leadership without a title.

Q14: Tell me about a time you failed.

What HR evaluates: Accountability and learning ability. Candidates who say “I have never failed” are either lying or lack self-awareness. Both are red flags.

How to answer: Pick a real failure — but one where you learned something concrete. The formula: What happened + What you learned + How you applied that learning. Never blame others.

Q15: How do you handle criticism?

What HR evaluates: Coachability. Managers need team members who can receive feedback without getting defensive. This is especially important in Indian IT where code reviews and performance feedback are regular.

How to answer: Give a specific example of feedback you received, how you processed it, and what changed. “My tech lead pointed out that my code lacked error handling. I took it seriously, studied exception handling patterns, and now I write try-catch blocks as part of my standard coding practice.”

Q16: What is your current CTC and expected CTC?

What HR evaluates: Whether your expectations fit their budget. In India, the standard hike for a job switch is 30-50% for IT roles. Asking for 100%+ without justification raises eyebrows.

How to handle this:

1. Know your market value BEFORE the interview
   - Check Glassdoor, AmbitionBox, and Levels.fyi
   - Talk to peers in similar roles
   - Factor in location (Bangalore > Pune > Tier 2)

2. Give a range, not a fixed number
   "My current CTC is X LPA. Based on my experience and 
   the market rate for this role, I am looking at Y-Z LPA. 
   I am open to discussing this based on the complete 
   compensation structure."

3. Never lie about current CTC
   Companies verify through offer letters, pay slips, 
   or background checks. Getting caught lying is an 
   instant rejection.

4. If you are underpaid currently
   "My current CTC is X, which I know is below market 
   rate for my experience level. I am looking for a 
   correction to Y-Z range, which aligns with the 
   industry standard for [years] years of experience 
   in [technology]."

Q17: Are you holding any other offers?

What HR evaluates: Urgency and leverage. If you have other offers, they may speed up the process. If you do not, they know they have more negotiation power.

How to answer: Be honest but strategic. If you have offers: “Yes, I am in the final stages with two other companies, but this role is my preference because [specific reason].” If you do not: “I am actively interviewing with a few companies, but I am being selective about the right fit.”

Q18: What is your notice period? Can you negotiate it?

What HR evaluates: How soon you can join. In India, notice periods range from 30 days to 90 days. Companies with urgent requirements may reject candidates with 90-day notice periods.

How to answer: State your official notice period, then mention if you can negotiate. “My official notice period is 60 days, but I have a good relationship with my manager and can try to negotiate it to 30 days if needed.” Never promise what you cannot deliver.

Q19: Are you okay with relocation?

What HR evaluates: Flexibility and commitment. For service companies that deploy engineers to client locations, this is a critical question. Saying “no” to relocation can be a dealbreaker for many roles.

How to answer: If you are open: “Yes, I am open to relocation.” If you have constraints: “I am open to relocation to [specific cities]. I would need [timeframe] to make the move.” Be honest — accepting relocation and then refusing later burns bridges.

Q20: Why are you leaving your current company?

What HR evaluates: Whether you will badmouth them too when you leave. This is the single most dangerous HR question. Negative answers about your current employer are an instant red flag.

Safe answers:
- "I am looking for more challenging work and growth 
  opportunities in [specific area]."
- "I want to work on [specific technology/domain] which 
  is not available in my current role."
- "I have learned a lot, but I feel I have reached a 
  plateau and need a new environment to grow."

Dangerous answers (never say these):
- "My manager is terrible"
- "The company does not pay well"
- "Politics and favoritism"
- "I hate the work culture"
- "They make us work overtime"

Even if all of these are true, saying them in an 
interview signals that you will say the same about 
the new company when you leave.

Q21: Why is there a gap in your resume?

What HR evaluates: Whether the gap was productive or a red flag. Career gaps are common in India — health issues, family responsibilities, higher education, or layoffs. HR understands this, but they want honesty.

How to answer: Be honest about the reason, then pivot to what you did during the gap. “I took 6 months off for a family health situation. During that time, I completed two AWS certifications and contributed to an open-source project to stay current.”

Q22: If you get a better offer after joining us, will you leave?

What HR evaluates: Loyalty and commitment. This is a trap — saying “yes” is honest but disqualifying. Saying “no, never” sounds fake.

How to answer: “I do not make career decisions based on short-term offers. I am looking for a role where I can grow for at least 2-3 years. If the work is challenging and the growth path is clear, there is no reason to look elsewhere. That is exactly what I am evaluating in this conversation.”

Q23: What if we offer you a lower package than expected?

What HR evaluates: Negotiation skills and whether you will accept a lowball offer. This is a negotiation tactic — they want to see if you fold immediately.

How to answer: “Compensation is important, but it is not the only factor. I would want to understand the complete package — base, variable, benefits, learning opportunities, and growth path. If the overall value proposition is strong, I am open to discussion. But I do have a minimum threshold based on my market research.”

Q24: Do you have any questions for us?

What HR evaluates: Genuine interest and critical thinking. Saying “No, I am good” signals low interest. Asking smart questions shows you are evaluating them too — which is a sign of a strong candidate.

Good questions to ask HR:
- "What does the onboarding process look like for this 
  role?"
- "How is performance evaluated here — what does a 
  successful first year look like?"
- "What is the team structure I would be joining?"
- "What are the learning and development opportunities?"
- "What is the typical career progression for someone 
  in this role?"

Questions to avoid:
- "How many leaves do I get?" (too early)
- "Can I work from home?" (unless it is a remote role)
- "When will I get a promotion?" (presumptuous)
- "What does the company do?" (shows zero research)

Q25: Why should we hire a fresher like you over someone with experience?

What HR evaluates: Confidence without arrogance. They know you lack experience — they want to see what you bring instead.

How to answer: “I bring fresh perspectives, up-to-date knowledge of current technologies, and no legacy habits to unlearn. During my college projects, I demonstrated that I can learn new tools quickly — I picked up Docker in one week for my final year project. I am also willing to start at the ground level and grow with the company.”

Q26: Are you willing to work in shifts or on weekends?

What HR evaluates: Flexibility. For service companies with US/UK clients, night shifts are common. Saying “no” can be a dealbreaker for many roles.

How to answer: If you are genuinely okay with it: “Yes, I understand that client requirements may need flexible hours, and I am comfortable with that.” If you have constraints, be upfront: “I am open to occasional weekend work. For regular night shifts, I would need to understand the rotation schedule.”

Q27: Your percentage/CGPA is low. Why?

What HR evaluates: Honesty and whether you have compensated for it with practical skills. Do not make excuses — own it and redirect.

How to answer: “My academics were not my strongest area, and I take responsibility for that. However, I invested that time in building practical skills — I completed 3 projects, contributed to open source, and earned certifications in [relevant technology]. I believe my practical abilities and project experience demonstrate my capability better than grades alone.”

Q28: What if you do not get this job?

What HR evaluates: Resilience and maturity. They want to see that rejection will not break you — and that you have a plan B.

How to answer: “I would be disappointed because I genuinely want this role. But I would ask for feedback on where I fell short, work on those areas, and continue applying. Every interview is a learning experience.”