Question
An interviewer asks, “Why do you want to work here?” Give a practical answer structure and explain how you would use the job description, public company facts, and your own experience. Do not rely only on brand, pay, technology names, or “great culture,” and do not pretend to know internal information that is not public.
What the interviewer is testing
- Whether you connect motivation to concrete role responsibilities rather than repeating company slogans.
- Whether you use verifiable company or product facts and distinguish facts from assumptions.
- Whether you can show relevant ability, outcomes, and a learning goal as a two-way fit.
- Whether you can honestly name unknowns that need confirmation instead of inventing enthusiasm.
Model answer
Use three parts: role work, company evidence, and personal proof. Start with the two responsibilities that attract you and how they relate to your next development step. Then cite one or two public facts, such as a product direction, customer problem, engineering practice, or constraint the team is addressing. Finish with one real experience showing similar work or the responsibility you could take on after joining.
Keep the answer to one or two minutes. Do not turn “why do you want to join” into a company overview or list every strength. Each fact should answer “why does this matter to you?” and each example should answer “what result did you produce?”
If public information is limited, say so directly: “From public information I understand A, and I would like to confirm B during the interview.” That is more credible than claiming insight into internal culture and naturally turns the answer into a two-way question.
Structure example
The pseudostructure below uses bracketed fields that you replace with your own facts.
I want to join because the [specific problem] in this role is the direction
I want to keep investing in.
Public information shows that the team is working on [verifiable fact], and
the [constraint or user outcome] suggests that [skill or way of working] matters.
In my previous role I owned [similar task] and moved [metric] from [baseline]
to [result] through [key action]. I would apply that experience to [role work]
while developing [specific learning goal].
I would also like to confirm how [unknown public detail] is prioritized in the role.Before the interview, rewrite responsibilities as verbs, turn company facts into “fact—impact—why it matters to me,” and choose one result-based example. This prevents a last-minute pile of adjectives.
Common pitfalls
- Saying only “your company is famous and I have always admired it,” without role work or evidence.
- Making pay, commute, or benefits the only motivation and ignoring why you can do the job well.
- Repeating a website slogan without naming the product, customer, or engineering decision behind it.
- Inventing knowledge of team culture, internal projects, or the interviewer’s history.
- Claiming “I would take any role,” which makes motivation impossible to verify.
Evidence and trade-offs
“Public fact” does not mean “positive review.” You can cite product documentation, technical writing, career pages, public incident reports, or customer cases while stating the source’s time range and uncertainty. Turn unconfirmed points into questions instead of packaging guesses as conclusions.
Role fit does not require claiming complete readiness. A credible answer names one validated strength and one planned growth area, such as: “I have built high-concurrency data exports; I have not owned cross-region compliance yet, and I want to develop that here.”
Record or write the answer and check four questions sentence by sentence: is it a fact, interpretation, evidence, or wish? Does the fact have a source? Does the evidence include your action and result? Is the wish linked to a role responsibility? Delete adjectives that fail these checks.
Then rehearse against the three core responsibilities in the job description. Keep one relevant experience per responsibility, limit the answer to two minutes, and end with one confirmation question grounded in public information.
References
- Amazon Jobs SDM Interview Prep: behavioral answers should explain what you did, why you did it, and use STAR to structure the response.
- LinkedIn Talent Solutions common interview questions guide: candidates evaluate the company, role, and growth opportunity for fit.
- LinkedIn Talent Solutions Interviewing Tips: a Situation, Task, Action, Result answer template.
Follow-up questions
What if I know very little about the company publicly?
State the role facts you could confirm, then turn unknowns into questions about the team’s most important user outcome, success criteria, or collaboration boundary. Do not fill the gap with unverified news or rumors.
What if the interviewer asks, “Why not another company?”
Compare the concrete overlap among the work, user problem, and growth goal without criticizing other companies. You can explain that several opportunities value the same capability, while this role’s public responsibilities fit your current experience most closely.
How can I discuss compensation without sounding purely transactional?
Complete the role-fit and contribution answer first, then discuss total compensation, scope, and level at the appropriate process stage. Pay is a legitimate consideration, but it should not replace an explanation of the work and outcomes.
Can I answer if I lack industry experience?
Yes. Explain transferable tasks, methods, and results, then acknowledge the domain gap and a concrete plan to close it. Do not present “fast learner” as an unsupported conclusion.
How do I avoid sounding scripted?
Remember the three-part structure and two facts, not a complete paragraph. Use your own details, numbers, and trade-offs to answer follow-ups so the response can adapt to the interviewer’s question.