ANSWER GUIDE
Why do you want to work here?
The interviewer is not asking you to praise the company. They are checking whether your interest is specific enough to survive the boring parts of the job — and whether you understand what you are joining.
What the interviewer is checking
| Signal | What they listen for | What weakens the answer |
|---|---|---|
| Research | A specific product, decision or market position | “You are a great company with a great culture.” |
| Fit | A connection between their work and your evidence | “I want to work for a big company.” |
| Realism | You understand the hard parts of the role | Only perks and brand |
| Retention | A reason that will still matter in a year | “I need a job” or “the salary is good” |
| Motivation | Why this work, not just this industry | A speech that could be pasted into any application |
A four-part answer
- One specific thing. A product, a customer problem, a technical decision, a stage of growth or a public commitment. Not the mission statement.
- Your connection. What have you done, used, studied or observed that makes this relevant? A user experience, a previous project, a domain interest.
- The realistic hard part. Name something you expect to be difficult: the pace, the regulatory environment, the legacy stack, the customer mix. This shows you are choosing the job, not the logo.
- The role connection. Tie it back to the job description and what you want to contribute. Keep it to one sentence.
Example: product company
I have used your scheduling product for two years as a team lead, and the feature that made me switch was the way it handles time zones without asking the user to think about them. I have built internal tools for distributed teams, and the hardest part was always the edge cases around daylight saving and travel. I know this role would also involve support escalations and a lot of customer calls, which is the part I would need to learn. What I want to contribute is the same instinct: find the confusing edge case before the customer does.
Example: healthcare or public service
I am applying because your team runs the community follow-up programme I referred patients into in my previous role. I saw what happened when the handover worked and when it did not, and I want to work on the part that closes that loop. I know the caseload is high and the systems are not always joined up; that is the part I am prepared for. The role description mentions improving the referral pathway, which is exactly the work I have been doing informally.
Example: career changer
I am moving from teaching into instructional design, and I am specifically interested in your team because you build for adult learners who are retraining while working. I have taught adults in evening classes, and the biggest design constraint was not the content but the twenty minutes they had after a shift. I have rebuilt a course around that constraint before. I know I would need to learn your authoring tools and accessibility standards, but the problem — designing for people with no spare time — is familiar.
What to avoid
- Generic praise. “Great culture” and “industry leader” are not reasons; they are adjectives.
- Only perks. Remote work, salary and holiday are legitimate considerations, but they are not why you want this job. Save them for the offer conversation.
- Flattery without evidence. If you admire a recent launch, say what you noticed and why it matters.
- “I need a job.” It may be true, but it tells the interviewer you have not chosen them.
- A long history of the company. They know their own history; spend the time on the connection to you.
Research that produces a specific answer
- Read the last two product launches or annual report and note one decision you find interesting.
- Look at the job description for a problem the team is trying to solve, not just a list of duties.
- Read two or three employee reviews and treat them as hypotheses; do not quote them in the interview.
- Use the questions to ask about the company guide to test what you learned.
Follow-up questions
- “What else would you want to know about us?” — have one specific question ready.
- “What would you change about our product?” — give one thoughtful observation, not a teardown.
- “Why not a competitor?” — compare on the work, not on prestige.
- “Where else are you interviewing?” — be honest but brief; focus on what you are looking for.
These guides are written and maintained by MockInterview as original practice material. They are not leaked employer questions, and no employer has reviewed or endorsed them. Sample answers are illustrative; use your own examples and verify role requirements, licensing and local policy with the employer. Last updated 2026-11-03.