All levels

HR and Behavioural Interview Prep

Twelve chapters on how HR and managerial rounds work, building a story bank, the STAR method, self-introduction, strengths and weaknesses, conflict, leadership, failure, tricky questions for freshers, negotiation and closing well, with sample answers and common mistakes.

Chapter 5 of 12Core questions · Why This Company, This Role and Your Goals

Why This Company, Why This Role, and Where You Are Headed

Three questions probe your motivation: "Why do you want to join us?", "Why this role?" and "Where do you see yourself in five years?". Interviewers ask them because a candidate who has chosen the company and role deliberately tends to work harder, stay longer and need less persuasion. These questions also reveal whether you did your homework. Generic answers ("it is a reputed company with good growth") tell the interviewer you sent the same application to fifty places. This chapter shows how to research, how to turn research into a specific answer, and how to talk about ambition without sounding either aimless or disloyal.

1. What a good "Why us?" answer contains

A strong answer has three ingredients:

  1. Something specific about the company (a product, a customer base, a technology, a mission, a culture practice, a recent project), not a general description of its size or brand.
  2. A link to your own experience or interest (why that thing matters to you, with evidence).
  3. What you hope to contribute and learn (a two-way exchange, not only a request).

"Two things draw me to your company. First, your logistics platform serves small manufacturers rather than only large retailers, which is the segment I saw up close in my internship at a packaging firm, where late deliveries cost them real money. Second, I read that your engineering teams own their services from design to production support, which is the kind of end-to-end responsibility I want to learn early. I would like to contribute the APIs and tracking work I did in my internship and grow into designing systems that small businesses can rely on."

The answer would not work for any other company. That is the test.

2. How to research

Spend an hour to a few hours on each serious application.

SourceWhat to look for
Company website, About and Careers pagesproducts, mission, values, teams, locations, what they say they look for
Product pages and documentationwhat they actually sell, who uses it
Recent news, press releases, blog postslaunches, funding, acquisitions, expansions, challenges
Annual report or investor presentation (for listed companies)strategy, segments, priorities, financial direction
The job descriptionrequired skills, tools, responsibilities, wording that repeats
Employee profiles and posts on professional networksbackgrounds, career paths, culture
Reviews (with scepticism)recurring themes, not single angry or glowing reviews
People you know who work there or used tothe day-to-day reality
The product itselfuse it, and note one thing you like and one thing you would improve

Then write three facts you can use in conversation and one thoughtful question each fact raises. Treat information from public sources as true only as of the date you read it, and be careful with figures you do not remember exactly; say "as I understand it" rather than quoting a number you are unsure about.

3. Why this role

Answer with three links between the role and you:

  • Skills match: "The role needs X and Y; I have done both in [project/job]."
  • Interest: "The day-to-day work of [what the role actually involves] is what I enjoy most."
  • Direction: "It fits where I want to build my career."

"I am applying for the business analyst role because it combines what I enjoyed most in my coursework: working with data to answer a business question, and then explaining the answer to non-technical people. In my capstone project I analysed a retailer's sales data and recommended a change in stock levels that the owner adopted. The role's mix of analysis and stakeholder work is exactly where I want to start my career."

If you are applying to many roles, adjust the emphasis per role. A common failure is applying to both a sales and a backend job with the same story.

4. Why not the current employer? Why are you leaving?

Experienced candidates are always asked why they are leaving. The rule is simple: talk about what you are moving toward, not what you are running from. Keep it honest and constructive.

ReasonA good way to say it
Limited growth"I have learned a great deal in this role, and I have reached the point where I want broader responsibility. This role offers [specific scope]."
A different kind of work"My work has been mostly [X]. I realised I enjoy [Y] more, and this role is mostly Y."
Company or team change"The company has reorganised, and the project I was most involved in was wound down. I would like to apply my skills to a new problem."
CompensationGenerally avoid leading with it. If it is true and unavoidable, "Compensation is part of it, but the main reason is [growth, scope, learning]."
Bad manager or cultureDo not criticise. "I am looking for a more collaborative environment where I can learn from experienced peers."
LayoffState it calmly and factually: "My team was affected by a reduction in staff. It was not performance-related, and I have been using the time to [upskill]."

Never speak badly of your current or former employer, manager or colleagues. Interviewers imagine themselves in that seat next year.

5. "Where do you see yourself in five years?"

The interviewer is checking three things: ambition (do you want to grow), realism (does your ambition make sense for this path), and fit (will the role and company help you get there, and will you stay long enough to be worth hiring and training).

What to say

  • Skill growth: "In five years I would like to be a strong, independent engineer who can own a service end to end and mentor newer team members."
  • Responsibility growth: "I would like to have grown into a role where I lead a small team or a significant area of the product."
  • Contribution: "I want to have delivered work that the business depends on."

"In the first year, I want to learn the codebase, the domain and how your team works, and to be reliable on the tasks I am given. Over the following years I want to take on larger features and own a component, and eventually mentor new joiners. I am still exploring whether I will enjoy technical depth or team leadership more, and I would like the chance to find out here."

What to avoid

  • "I want your job" or similar, which can sound threatening.
  • "I will be a CEO/manager in five years" with no grounding.
  • "I do not know" or "I have not thought about it".
  • A plan that has nothing to do with the company or the field (planning to leave for higher studies abroad in two years, if you are applying for a long-term role). If you do have such a plan, think carefully about how to handle it honestly, since a surprise later helps nobody.
  • Over-precise promises ("I will stay forever").

It is acceptable to say you are not certain of the exact path, so long as you show direction and willingness to learn.

6. "What do you know about our company?"

Prepare a 30-second summary: what the company does, who its customers are, one recent development, and one thing that interests you.

"As I understand it, you build payment infrastructure for small online merchants in India, and over the last year you have expanded into [new capability]. What interested me most was your approach to [specific thing], because in my project I faced a similar problem with [X]."

If the news you read is uncertain, phrase it as your understanding, and use the question as a chance to ask: "Is that still the direction the team is taking?"

7. "Why should we hire you?"

This is a chance to summarise your fit in three parts: what the job needs, what you bring (with evidence), and what you will do for them.

"From the job description, you need someone who can build reliable APIs and work closely with the product team. I have built and deployed two production-style APIs, I debugged real issues in my internship, and I learn quickly. I would also bring a habit of documenting what I build so others can use it. I think I could be useful within the first few weeks and grow from there."

Be confident but not boastful. Do not compare yourself with other candidates, because you do not know them.

8. Other motivation questions

  • "Why did you choose this field/degree?" Tell the true story: a moment, a person, a project that sparked the interest, then what you did to follow it.
  • "Are you applying elsewhere?" Be honest without drama: "Yes, I am speaking with a few companies, but this is one of my top choices because [reason]."
  • "What other companies are you interviewing with?" You do not have to name them. "Similar companies in the same field" is fine.
  • "Why do you want to work in [city]?" Genuine reasons (family, the industry cluster, the team) are fine. Do not claim a love for a city you have never visited.
  • "What would make you leave?" "A role that stopped teaching me anything, or a culture that did not value honesty. I would first try to fix it by talking to my manager."

9. A research-to-answer worksheet

For each company, fill in:

  1. In one sentence, what does the company do and for whom?
  2. Two specific things I find interesting (product, technology, culture, mission).
  3. One recent development.
  4. How my skills or experience link to those things.
  5. What I want to learn from this role.
  6. One question I would ask the interviewer that shows I read about them.

Then compose a 45-second "Why us?" using lines 2, 4 and 5.

10. Common mistakes

  • Generic praise: "reputed company, great brand, good culture".
  • Answers about what the company can give you only (salary, location, learning), with nothing you would give.
  • Mistakes about the company (the wrong product, a competitor's product, outdated news).
  • Criticising your current employer.
  • Ambition answers that are either empty or alarming.
  • Memorised lines that contradict your behaviour (saying you value teamwork, then answering every question with "I").
  • No questions of your own, which suggests no real interest.

11. Practice questions

  1. Why do you want to work for this company? (Answer without using the words "reputed", "brand" or "growth".)
  2. Why this role over other roles you could have applied for?
  3. Where do you see yourself in five years, and how does this role help?
  4. Why are you leaving your current job? (Or, as a fresher: why did you apply for this role?)
  5. What do you know about our products and our competitors?
  6. Why should we hire you instead of other candidates?
Header Logo