HR Round: 20 Questions That Are 100% Asked

You Cleared Technical. Now the HR Round Will Decide If You Get the Offer or Go Home.#

Here's a stat that will surprise you: 15-20% of candidates who clear the technical interview get rejected in the HR round.

Think about that. You prepared DSA for months, cracked the coding questions, explained OOPS perfectly, and then lost the job because you said the wrong thing when HR asked "Where do you see yourself in 5 years?"

The HR round isn't a formality. It's an elimination round disguised as a casual conversation.

I've compiled the 20 most frequently asked HR questions across TCS, Infosys, Wipro, Cognizant, Accenture, and mid-tier IT companies. For each question, I'm giving you:

• Why HR asks this (the hidden test)
• What NOT to say (instant rejection triggers)
• A sample answer you can customize

Before the Questions: 3 Rules for Every HR Round#

Rule 1: HR is testing attitude, not knowledge. Technical round tests what you know. HR round tests who you are. Are you a team player? Will you stay for 2+ years? Can you handle pressure? Will you fit the company culture?

Rule 2: There are wrong answers. "Where do you see yourself in 5 years?" If you say "doing an MBA" or "at a better company," you're done. HR rounds have landmine answers that instantly disqualify you.

Rule 3: Enthusiasm matters more than perfection. HR evaluates energy and attitude. A candidate who says "I'm really excited about this role because..." with genuine energy will beat a candidate who gives technically perfect but monotone answers.

The 20 Questions (With Answers)#

Question 1: "Tell me about yourself."

Why they ask: This is your 90-second elevator pitch. HR uses this to see if you can communicate clearly, if you've prepared, and to set the direction of the conversation.

What NOT to say:

• Don't recite your resume line by line
• Don't start with "I was born in..." (nobody cares about your birthplace)
• Don't talk for more than 2 minutes

Sample answer: "I'm [Name], a 2026 B.Tech Computer Science graduate from [College]. During college, I focused on web development and built three projects, including a food delivery app for our campus that 200+ students used. My strongest skills are Java and React, and I recently completed an internship at [Company/Startup] where I worked on their customer dashboard. I'm looking for a role where I can write production code and grow as a full-stack developer. [Company Name]'s work in [specific area] really interests me."

Structure: Education (10 sec) + Key skills/projects (30 sec) + Recent achievement (20 sec) + Why this company (15 sec) = 75 seconds total.

Question 2: "Why do you want to join [Company Name]?"

Why they ask: To check if you've done research or just mass-applied everywhere.

What NOT to say:

• "Good salary" or "good brand name"
• "My friend works here"
• "I applied everywhere, you called me first"
• "Esteemed organization" (HR hears this 500 times a day)

Sample answer (for TCS): "Two things about TCS interest me. First, the scale. TCS works with clients across 40+ countries, and as a fresher, getting exposure to global projects early in my career is valuable. Second, the initial learning program. I've heard from seniors that TCS ILP in Trivandrum gives a strong foundation, and I want to start my career with solid training before jumping into projects."

Sample answer (for Infosys): "I've been using InfyTQ for the last 3 months and the structured way Infosys approaches fresher development impressed me. Also, the Mysore training campus is something unique. I want to join a company that invests in making freshers production-ready, not just throws them into projects."

The key: mention something SPECIFIC about the company. Not generic praise.

Question 3: "What are your strengths?"

Why they ask: To see if you're self-aware and if your strengths match the role.

What NOT to say:

• "I'm a hard worker" (everyone says this)
• "I'm a perfectionist" (this is a disguised weakness, HR knows)
• Listing 10 strengths (pick 2-3 max)

Sample answer: "My biggest strength is that I learn new things quickly. When our college switched from Java to Python for a course midway, I picked it up in two weeks and ended up helping my classmates. Second, I'm good at breaking down complex problems. During my project, when we faced a database performance issue, I broke it into smaller parts, identified the bottleneck was in query design, and fixed it. These two abilities, quick learning and problem decomposition, I think are useful for any software role."

Pro tip: Always back up each strength with a SPECIFIC example. "I'm a quick learner" means nothing without proof.

Question 4: "What are your weaknesses?"

Why they ask: The ultimate trap question. They want honesty and self-awareness, but they also want to see if your weakness is a dealbreaker.

What NOT to say:

• "I don't have any weaknesses" (arrogant and dishonest)
• "I'm a perfectionist" or "I work too hard" (HR rolls their eyes)
• A real dealbreaker like "I can't work in teams" or "I get angry easily"

Sample answer: "I sometimes spend too much time trying to solve a problem on my own before asking for help. During my final year project, I spent 3 days stuck on a bug that my senior fixed in 20 minutes once I asked. I've been working on this by setting a personal rule: if I'm stuck for more than 2 hours, I reach out to someone. It's been helping me be more efficient."

The formula: Real weakness + Specific example + What you're doing to fix it. This shows self-awareness and growth mindset.

Question 5: "Where do you see yourself in 5 years?"

Why they ask: To check if you'll stay. Companies spend 2-5 lakhs training each fresher. If you leave in 1 year, that's a loss.

What NOT to say:

• "Doing an MBA" (HR hears: you'll leave in 2 years for MBA entrance prep)
• "At Google/Microsoft" (HR hears: we're your backup plan)
• "In a managerial position" (too ambitious for a fresher, sounds unrealistic)
• "I haven't thought about it" (sounds directionless)

Sample answer: "In 5 years, I want to be a solid full-stack developer who can independently handle end-to-end development of a feature or module. I want to have worked on at least 2-3 different projects to get breadth of experience. Eventually, I'd like to mentor junior developers the way my seniors mentored me. I see [Company Name] as a place where this kind of growth is possible because of the project variety and scale."

Keep it at the same company. Show growth within the company, not outside it.

Question 6: "Why should we hire you?"

Why they ask: To see if you can sell yourself. Also to see if you understand what the company needs.

What NOT to say:

• "Because I need a job" (desperation)
• "Because I'm the best candidate" (arrogant without proof)
• A generic answer that could apply to anyone

Sample answer: "Three reasons. First, I have practical coding skills. I've built 3 projects from scratch, not tutorials, original projects that solve real problems. Second, I learn fast. I picked up React in 3 weeks for my last project with zero prior frontend experience. Third, I genuinely want to be here. I've researched [Company Name]'s recent work in [area], and I want to contribute to projects at that scale. I know I'm a fresher and I have a lot to learn, but I bring the work ethic and curiosity to learn quickly."

Question 7: "Tell me about a challenge you faced and how you overcame it."

Why they ask: Problem-solving ability and resilience.

Sample answer: "During my final year project, two weeks before submission, our database crashed and we lost 3 weeks of data. We didn't have proper backups. I stayed up for 2 nights, recovered partial data from API logs, rebuilt the database schema, and implemented daily automated backups so it wouldn't happen again. We submitted on time. The lesson: always have backups, and don't just rely on 'it probably won't crash.'"

Use the STAR format: Situation, Task, Action, Result.

Question 8: "Are you willing to relocate?"

Why they ask: Service companies assign you to projects anywhere in India. If you refuse relocation, you're limiting your options.

The answer: "Yes, absolutely. I'm open to working from any location."

Even if you have a preference, say yes first. You can discuss preferred locations AFTER getting the offer. Saying "only Bangalore" or "not Chennai" in the HR round is a rejection trigger.

Question 9: "Are you okay with working in shifts/night shifts?"

The answer: "Yes, I'm flexible with timings."

Same logic as relocation. Say yes now, negotiate later. Many projects require US/UK client interaction, which means Indian night shifts. If you say no, you're immediately disqualified for 40% of projects.

Question 10: "Do you have any backlogs?"

If no backlogs: "No, I've cleared all subjects on time."

If cleared backlogs: "I had [X] backlogs in [semester], which I've cleared. The reason was [honest reason]. After that, I improved my study approach and maintained consistent grades."

If active backlogs: Be honest. They will verify. "I have [X] active backlogs which I'm scheduled to clear by [date]. I've been preparing for them alongside interview preparation."

Lying about backlogs = automatic termination if caught during background verification.

Question 11: "What is your expected salary?"

For fresher roles at service companies: Don't negotiate. The package is fixed.

Sample answer: "I'm aware that [Company Name] offers [X LPA] for this role, and I'm comfortable with that. At this stage of my career, learning and growth matter more to me than the salary figure."

For startups or product companies where salary is negotiable, research the market rate first. Say: "Based on my research, this role typically pays between [X] and [Y] LPA. I'm flexible within that range and open to discussion."

Question 12: "Do you have any other offers?"

If yes: "Yes, I have an offer from [Company]. But I'm more interested in [Current Company] because [specific reason]."

If no: "I'm currently in the process with a few companies. This role is my priority because [specific reason]."

Having other offers shows you're employable. It doesn't hurt you. Don't lie about having offers you don't have though, they might ask for details.

Question 13: "How do you handle pressure?"

Sample answer: "I handle pressure by breaking the problem into smaller tasks. During my semester exams, I had to prepare for 6 subjects in 2 weeks. I made a daily schedule, allocated time to each subject based on difficulty, and stuck to it strictly. I ended up scoring above 75% in all subjects. I think the key is not to panic and just focus on what you can control."

Question 14: "What do you know about our company?"

This is a research test. Before every interview, spend 15 minutes reading about:

• What the company does (revenue, clients, employees)
• Recent news (acquisitions, new products, quarterly results)
• CEO name
• Company values/mission (from their website)

Sample answer (for Wipro): "Wipro is one of India's largest IT services companies with over 250,000 employees. The company has been focusing heavily on cloud transformation and AI services under CEO Thierry Delaporte... actually, I believe Srini Pallia is the current CEO since early 2024. Wipro recently won a large deal with [recent client win you read about]. I'm impressed by the focus on newer technology practices and the WILP program for freshers."

Question 15: "Are you comfortable with a bond/agreement?"

Many service companies have 1-2 year service agreements. TCS has a 1-year bond. Infosys has an 18-month agreement.

The answer: "Yes, I'm comfortable with it. I plan to stay and grow with the company, so the bond duration aligns with my plans."

Even if you're not sure about staying, say yes. The bond is standard and almost every fresher accepts it.

Question 16: "What do your parents do?"

Why they ask: Not to judge your family background (at least not supposed to). It's a rapport-building question and sometimes to assess your stability and communication.

Sample answer: Short and factual. "My father is [profession] and my mother is [profession/homemaker]." Don't over-explain or get emotional.

Question 17: "Why did you choose engineering/CSE?"

What NOT to say:

• "My parents forced me" (even if true, don't say it)
• "Everyone was choosing it"
• "CSE has the best placements" (mercenary)

Sample answer: "I've been interested in computers since school. When I was in 11th, I wrote my first program in C and the feeling of making the computer do what I wanted was exciting. I chose CSE because I wanted to understand how software systems work at a deeper level. Four years later, I'm glad I made this choice because I've built projects that real people use."

Question 18: "Do you prefer working alone or in a team?"

The answer: Always say both, with emphasis on team.

"I enjoy both. For focused tasks like coding or debugging, I prefer working alone because I can concentrate better. But for project planning, brainstorming, and problem-solving, I prefer teams because different perspectives lead to better solutions. Most of my college projects were team-based, and I've learned that collaboration produces better results than solo work."

Question 19: "What will you do if you're not selected?"

Why they ask: To test emotional maturity and resilience.

What NOT to say:

• "I'll be very disappointed" (too emotional)
• "I'll keep trying until I get in" (sounds desperate)

Sample answer: "If I'm not selected, I'd take the feedback, work on whatever areas I need to improve, and keep applying. I believe every interview teaches me something. I'd also continue building my skills through projects and courses. My goal is to become a good developer, and whether that starts here or somewhere else, I'll keep working toward it."

Question 20: "Do you have any questions for us?"

What NOT to say: "No, everything is clear." (Worst answer. Shows zero interest.)

Ask any 2 of these:

1. "What does a typical first 6 months look like for a fresher here?"
2. "What technologies is the team currently working with?"
3. "Is there a mentorship program for new joiners?"
4. "What's the team size I'd be working with?"
5. "How often do freshers get to work on client-facing projects?"

Never ask about salary, leaves, work-from-home policy, or bond breakage in the HR round. Those are post-offer discussions.

5 Body Language Tips for HR Rounds#

1. Maintain eye contact. In virtual interviews, look at the camera, not the screen. In person, look at the interviewer's nose bridge if direct eye contact feels uncomfortable.

2. Smile naturally. Not a permanent grin. Just a warm, natural smile when greeting, when they crack a light comment, and when saying goodbye.

3. Sit upright. Don't slouch. Don't lean too far back (looks too casual). Slight forward lean shows interest.

4. Don't cross arms. Open posture signals openness and confidence.

5. Pause before answering. Take 2 seconds before each answer. It shows you're thoughtful, not rehearsed.

What Happens After the HR Round?#

Three outcomes:

1. Selected: You'll get a call or email within 1-4 weeks with an offer letter. Celebrate.

2. On hold / Waitlisted: Some companies waitlist candidates. You might get selected later if others decline. Don't count on it, keep applying elsewhere.

3. Rejected: You'll either get a rejection email or just silence (many companies don't bother sending rejections). If rejected, move on. Apply to the next company. Every interview makes you better.

How to Prepare: The 24-Hour Plan#

If your HR interview is tomorrow, here's what to do tonight:

6 PM: Research the company. CEO, recent news, revenue, number of employees, what they do.

7 PM: Write down answers to the top 10 questions from this list. Don't memorize word-for-word, know the key points.

8 PM: Practice out loud. Stand in front of a mirror and answer each question. 2 times each.

9 PM: Pick your outfit. Formal shirt, clean and ironed. Neat appearance.

10 PM: Sleep. Seriously. A well-rested brain performs 3x better than a sleep-deprived one. Don't stay up until 3 AM "preparing."

Morning of interview: Arrive 15 minutes early (or log in 5 minutes early for virtual). Carry 2 printed copies of your resume. Bring a pen and notepad.

Polish Your Answers Before the Interview#

You know the questions now. You have sample answers. But every person's story is different. Your answers need to reflect YOUR experience, YOUR projects, YOUR career goals.

That's where polishing helps. Take your draft answer and make it specific, concise, and compelling.

JobRise Answer Polish takes your rough interview answers and turns them into polished, professional responses. Paste your answer, it gives you an improved version that keeps your story but makes it clearer and more impactful.

20 questions. 20 answers. One HR round between you and the offer letter. Prepare like it matters, because it does."