HR Round Basics: Standard Questions, Story Bank and Red Flags
Every company’s HR page on this site used to repeat the same groundwork. It now lives here once, so each company page can stick to what is different about that company. Read this page first, then open the HR page for the company you are interviewing with.
The ten standard questions
These come up almost everywhere. The framework is the same at every company; what changes is the detail you plug in, which is what the company pages cover.
| Question | Framework |
|---|---|
| Tell me about yourself | Present → Past → Future, 60-90 seconds. End on why this role, at this company, today. |
| Why this company? | One thing about how they hire or train, one thing about their work, one thing about where you fit. Name a product, team or technology you actually know. |
| Why should we hire you? | Three proofs, under 90 seconds: a project result, a hard problem you debugged, a team example. |
| Strengths and weaknesses | Strength with evidence. Weakness that is real, non-fatal, and comes with what you are doing about it. |
| Where do you see yourself in 5 years? | Growth inside the role and the company. No unrealistic title jumps. |
| Tell me about a conflict in a team | Situation → what you did → result. Listening and outcome, not blame. |
| Are you willing to relocate / work shifts? | Answer honestly. If you have a constraint, state it early and calmly. |
| Explain a gap / low score / job hop | Own it in one sentence, then show what changed. |
| What do you know about us? | Three facts: what the business does, what the role works on, one recent public initiative. |
| Do you have any questions for us? | Team rituals, mentoring, success metrics, tech stack. Not salary first. |
Sample answers on the company pages are frames to adapt, not scripts. Map each one to a real project or internship of your own, and keep the details consistent with what you said in the technical rounds - HR often cross-checks your motivation and timeline against earlier answers.
Story bank: five stories to prepare once
Most behavioural questions can be answered from five stories. Write them once and reuse them across companies.
| Story type | Prompt |
|---|---|
| Ownership | Fixed something without being asked |
| Failure | Missed a deadline or shipped a bug in a project |
| Teamwork | Disagreement resolved constructively |
| Learning | Learned a tool or language under time pressure |
| Impact | Measurable project result |
If a story has no clear result, or is all “we” and no “I”, fix it with STAR stories that fail before the interview.
Prep checklist
- Draft a 2-3 minute “Tell me about yourself” tied to why this company, not a resume dump
- Prepare one STAR story each for conflict, failure or learning, deadline pressure, and teamwork
- Know one concrete fact about the company’s products, services, or hiring track for your role
- Decide your relocation, bond and notice-period answers before the interview, not on the spot
- Prepare two thoughtful questions about the first project, the team, or the training path
Red flags at any company
- Badmouthing colleges, teammates, or other companies
- Memorized speeches that ignore the question asked
- Lying about tools or CGPA
- Asking about CTC or WFH in the first breath
- Having zero questions at the end
Generic praise (“great company”) is also weak. Tie every answer to the company’s actual work, the role, and evidence from your own projects.
Next step
Open the HR page for your company from the company list - for example TCS, Infosys, Accenture or HSBC - for the company-specific questions, sample answers and what that panel scores.

