To answer “Why do you want to work here?” without sounding generic, name two or three specific things about the company and role that match what you want and what you have done, then say what you would contribute. Specifics are the whole difference: an answer that could be pasted into any other company’s interview will sound like it.
Interviewers ask this to learn whether you did any homework and whether you are likely to stay engaged. A vague answer such as “You’re a great company with a great culture” suggests you applied broadly and chose none on purpose. A specific one shows real interest and makes it easier for them to picture you in the job.
What a generic answer sounds like
Generic answers use words that could describe nearly any employer (“innovative,” “fast-growing,” “passionate team”), talk only about what you will get (“a chance to grow”), and show no evidence of research.
| Generic | Specific |
|---|---|
| “You’re an industry leader and I want to grow my career.” | “I saw you recently expanded the customer onboarding team, and that’s the area I’ve worked in for four years.” |
| “I love your mission.” | “Your focus on making [product type] accessible to small clinics matches my work supporting small practices.” |
| “The culture seems amazing.” | “The job post mentions weekly team demos, and I do my best work when I see my results used by others.” |
The examples are invented. Each specific version points to something real and ties it to the candidate’s experience, which is only possible after research.
The three-part formula
- Something specific about the company or role (a product, a challenge, a way of working).
- How it connects to your experience or interests (evidence, not adjectives).
- What you would bring (a short, concrete value statement).
“What stood out to me is [specific thing]. In my work at [past role], I [relevant experience], so I’m drawn to [what the company is doing]. I think I could contribute by [specific contribution].”
An invented example:
“What stood out to me is that you’re building scheduling software for in-home care providers rather than every industry. I spent three years coordinating caregiver schedules at a home-care agency, so I know how painful last-minute changes are. I think I could help your customer team because I understand the daily problems your users face.”
About 30 to 45 seconds is a sensible target. Your version needs your own real experience.
How to research in about an hour
You do not need a deep dive. Aim for five or six usable facts.
- The job posting. Highlight the top three responsibilities and any phrases about the team’s goals. Repeated words often signal priorities.
- The company’s own site. Read the product or service pages, the about page and any news section: what they sell, to whom, and what they say they care about.
- Recent announcements. A new product, an expansion or a public report. Use only what you can confirm.
- Public professional profiles of the people you will meet. Look at career paths and what they write about, and skip anything personal.
- Customer-facing material. Reviews, case studies and help pages show what customers value and struggle with.
- One or two competitors. A quick look helps you say what is distinctive.
Keep short notes with the date you found each fact, so you can check it is still current on the day. A product in the news last month may have changed by the time you interview.
Choosing the angles that fit you
Pick two or three from this list and match them to your background: the work itself (problems, product, customers); the role’s scope; the team’s way of working, if stated publicly; the company’s direction; or a past project of yours that connects naturally. Do not stack more than three, because a long list sounds read from a page. One strong reason plus one supporting reason is often enough.
Worked examples for different situations
These are invented samples, not lines to copy.
Career changer:
“I’ve spent six years in teaching, and what I enjoy most is turning complicated material into something people can use. Your training team builds exactly that for new hires, and this role would let me use that skill in a business setting. I also completed an instructional design course last year, so the tools you list are familiar.”
Recent graduate:
“In my capstone project I built a small inventory tracker for a campus club, and I realized I enjoy making everyday operations easier. Your focus on logistics software lines up with that, and the associate program you describe would let me learn from experienced engineers while contributing.”
Internal move:
“I’ve worked on the support side for two years and seen which product issues come up most. I’d like to move to product operations so I can use that customer insight earlier in the process.”
All three give a reason, a link to the person’s history, and a contribution.
Expect a follow-up
A good answer often draws a follow-up such as “What do you know about our team?” or “What would you want to work on first?” Prepare one sentence for each from your research notes. If you do not know something, say so and say what you would want to learn, which is better than guessing about the company’s plans. It also helps to separate what the company says about itself (its website and job post) from what you can verify elsewhere, and to word your claims accordingly: “Your site describes…” is accurate, while “Everyone knows you are the market leader” is not.
What to avoid saying
- Pay, benefits or perks as the lead reason. They are valid factors, but leading with them can sound uninterested in the work.
- “I need a job” or “I just want to leave.” If leaving is part of your story, see explaining why you are leaving your current job.
- Flattery with no content. “You’re the best in the industry” is empty.
- Facts you cannot support. If you cite a launch, be sure it is accurate.
- Overclaiming loyalty. “I want to be here for 20 years” is hard to believe; “I want to build something here” is easier.
If the company is not your first choice, find the genuine parts, such as the responsibilities or a skill you will gain, and talk about those. Do not invent enthusiasm you do not have.
Tie it to the rest of the interview
A consistent theme helps. If your reason for applying is “more customer-facing problem-solving,” your examples, your questions and your follow-up should reinforce it. Your opening answer can end on the same point, and the research you did here also feeds the questions you ask at the end.
The swap test is the best final check: if a sentence would still make sense with another company’s name in it, delete it or add detail until it fails.
To organize your research, use the interview research checklist.
Where this comes from
This is common-sense interview preparation, drawn from widely repeated career-coaching advice and from what job postings and company websites typically publish; no study sets a best answer or length. All example answers are invented. Company details change quickly, so verify anything you plan to mention against the employer’s own current materials on the day.