How to Answer Why Do You Want to Work Here?

Specific–Personal–Forward formula answers why you want to work here by linking one verified employer fact, the role’s work and evidence that you can contribute. Keep the spoken answer under 75 seconds, following InterviewOra’s guidance, and tailor the proof to the Job description.

What should you say when they ask, “Why do you want to work here?”

Answer “why do you want to work here?” with the role priority first, a verified employer fact only if it explains that work, then personal evidence and the contribution you would make. A truthful general answer is stronger than a specific fact you cannot verify or connect to the role.

Use this compact formula:

“I’m interested in this role because [role priority]. I noticed [verified employer fact], which matters to me because [connection to the work]. My experience with [evidence] would let me contribute by [specific contribution].”

Leave out the employer fact if it fails either test. You do not need to invent enthusiasm to sound prepared. Say:

“I’m interested in this role because [role priority]. It fits the work I want to do, especially [specific responsibility]. My experience with [evidence] would let me contribute by [specific contribution].”

For example:

“I’m interested in this role because it combines customer research with product decisions. I noticed that your team recently expanded the service into small-business accounts, which matters to me because I enjoy turning customer evidence into practical improvements. My experience running user interviews and analysing support themes would let me contribute by identifying friction in that new segment.”

Replace every bracketed phrase with something true. Check the job description and current company sources before naming a release, service change or strategic priority. Do not claim to have used a product, admired a culture or shared a value if you have not. TopInterview advises candidates to be truthful about their product use.

This structure also answers “Why this company?”, “Why this role?”, “Why did you apply?” and “Why us rather than our competitors?” Keep the role priority and contribution clear. Change the employer fact when the wording changes.

Use prompts, not a memorised paragraph. InterviewOra recommends keeping the spoken answer under 75 seconds, but that is one source’s ceiling, not a universal hiring rule. Prepare.fyi suggests 45–60 seconds for a full answer. Stop after the contribution sentence and let the interviewer ask for detail.

What is the interviewer really checking?

Interview Copilot frames the answer as Employer Fact–Role Priority–Personal Evidence, a structure for connecting motivation with the vacancy rather than general admiration (Interview Copilot).

The usual advice says to add a concrete employer fact, link it to the role and show your fit. Prepare.fyi calls this Them–The Role–You, while Applystead uses Work–Employer–Fit as alternative answer structures (Prepare.fyi; Applystead). These labels differ. The checks overlap.

The interviewer is testing five things:

• Company understanding: Do you know what this employer actually does?
• Role understanding: Do you understand the work this vacancy owns?
• Durable motivation: Does the work itself interest you beyond getting an offer?
• Retention risk: Is your reason specific enough to suggest considered choice?
• Capability: Do you have evidence that you can contribute?

Treat your answer as a work hypothesis. Say the causal chain aloud:

“The company is doing X; this role owns Y; I have evidence of Z; I would apply it here by doing A.”

That chain gives the interviewer something to examine. “I love your mission” does not. Without a relevant example, it proves only that you read the mission statement. A responsibility from the Job description, linked to a real result, gives the interviewer a testable connection between motivation and capability. NovoResume discusses connecting company knowledge and field interest when explaining your motivation (NovoResume).

A specific fact is not automatically stronger than a truthful general answer. A funding note, mission statement, employee review or earnings call does not prove what the team does day to day. An unverified product claim can damage credibility more than, “I am interested in this work because it matches the problems I have solved.”

Use a company fact only when you can verify it, connect it to the Job description and explain the contribution that follows. Otherwise, choose the plain truth.

How long should the answer be at each interview stage?

InterviewOra recommends keeping the full answer under 75 seconds, so match the amount of evidence to the interview stage rather than forcing one script everywhere. (InterviewOra’s under-75-second guidance)

What the sources say	Practical recommendation
Recruiter or screening call. Applystead recommends a 30-second version for recruiter screens. (Applystead’s recruiter-screen guidance)	Prepare a compressed answer. Name the work, one verified employer fact and the contribution you could make. Stop there.
Phone screen. InterviewOra recommends roughly halving the full answer for this setting. (InterviewOra’s phone-screen advice)	Remove the example and extra context. Keep the role priority, employer fact and contribution.
Hiring manager interview. Prepare.fyi recommends 45–60 seconds, or 110–150 spoken words, for a full answer. InterviewOra recommends staying under 75 seconds. (Prepare.fyi’s answer guidance; InterviewOra’s under-75-second guidance)	Start with your full prepared answer. Stop after the contribution point. Let the hiring manager decide whether to ask for evidence.
Panel interview. The sources do not establish a separate panel duration.	Start with the full answer, then follow the panel’s cues. Invite detail only after you have named the work, employer fact and fit.
Follow-up request for more detail. STAR supplies a structure, not a time target.	Give one relevant example. State the situation and task briefly. Focus on your action. Finish with the result. Do not restart the opening answer.

Source: How to Answer “Why Do You Want to….

Source: How to Answer “Why Do You Want to….

The short versions remove context, not proof. Keep the role, a verified fact and a contribution. Aim to sound conversational rather than memorised.

Treat these timings as practice guidance. Interviewer style, role seniority and the pace of the exchange still matter. Apply Coach’s timing guidance supports treating answer length as a conversational judgement, not a fixed hiring rule.

A hiring manager who asks, “Tell me more about that migration,” has already accepted the opening structure. Answer the follow-up directly: “The situation was a growing message backlog. My task was to move the service from RabbitMQ to Kafka without interrupting customer updates. I introduced dual-writing, tested the cutover and monitored errors. The result was a controlled migration with clearer failure signals.” Then stop.

What are strong example answers for different candidates?

Early-career candidates, experienced candidates, and career changers can each consider pairing one employer fact with one proof point and one forward contribution, using the sample structures in InterviewOra’s guidance. The wording changes with the evidence available. The logic stays speakable.

Early-career candidate

“I’m interested in this product analyst role because it combines customer problems with data-led decisions. I noticed that your team recently added a self-service reporting feature. That stood out because my placement project involved testing how students used dashboards to find information. I mapped the common sticking points and proposed clearer labels. I would bring that same user-focused approach here by helping the team turn customer behaviour into simpler product decisions.”

Replace before speaking: Confirm the reporting feature on the company website, product page or release notes. Replace the placement project with your real coursework, project or product research. Do not imply professional product experience you do not have.

This follows the company, role, and candidate progression illustrated in TopInterview’s 12 sample answer patterns.

Experienced candidate

“I want this engineering role because it owns the reliability problems I enjoy solving. Your job description highlights event-driven systems and dependable service operations. In my previous role, I led a RabbitMQ-to-Kafka migration, including six months of dual-writing, while keeping the change controlled for users. That work taught me to plan migration risk, monitor live behaviour and bring teams with me. I would apply that experience here by strengthening the platform without treating migration as a purely technical exercise.”

Replace before speaking: Verify that the vacancy genuinely involves event-driven systems or migration work. Keep the RabbitMQ-to-Kafka example only if you led or materially contributed to it. Prepare.fyi uses a migration example to illustrate how evidence can connect with the target role.

Career changer

“I’m moving into customer success because I want to solve customer problems beyond the point of sale. Your company’s expansion into small-business accounts interests me because those customers often need clear guidance, not jargon. In retail, I handled difficult requests, identified the real issue and explained practical next steps during busy periods. I would bring that calm, structured service to onboarding and help customers reach value sooner.”

Replace before speaking: Check the small-business expansion against current company information. Replace the retail example with your own customer service, education or other transferable evidence. Applystead’s examples illustrate how practical experience can support a career-change answer.

Each script has one fact, one proof point and one proposed contribution. That discipline prevents a personal history from swallowing the answer. It also leaves room for the interviewer to ask about the evidence rather than forcing you to recite every achievement.

How do you adapt the answer to the role and the employer?

The Job description should control your research order: keep an employer fact only when it is current, attributable and tied to a stated responsibility, using the fact-versus-inference check described by Interview Copilot.

Use a verifiable research workflow

Start with the three-pillar company–role–you method:

1. Company: What verified fact shows what the employer is doing now?
2. Role: Which responsibility in the Job description makes that fact relevant?
3. You: What evidence shows you can contribute to that responsibility?

Do not collect facts for their own sake. Select the fact that explains why this exact work interests you. Then check whether the job description supports your interpretation. Interview Copilot separates an employer fact from the candidate’s inference, while Apply Coach pairs a company fact with motivating responsibilities and career evidence.

Source	What it can confirm	How to verify it is current
Job description	Responsibilities, required tools, outcomes, seniority and location	Compare it with the recruiter’s wording. Ask about contradictions before repeating a claim.
Company website and careers page	Published products, services, mission statements, company values and hiring priorities	Check the page date, current vacancy and newsroom. Treat undated copy as context, not proof of a recent change.
Engineering blog	Technical systems, engineering problems and architectural decisions	Check the publication date and whether the same technology appears in the current role or team material.
Company changelog and release notes	Features or product changes that the company says it shipped	Check the latest entry and the live product. Do not turn a release into a claim about the team’s daily work without further evidence.
Funding notes and earnings calls	Publicly stated growth priorities, market direction and investment themes	Use the latest company or investor record. Separate management’s stated plan from your prediction about the role.
Annual reports, sustainability reports and public filings	Formal strategy, risks, workforce information and reported business priorities	Check the reporting period and later company updates. Older filings can explain context but not prove a current team priority.
Press releases	Official launches, partnerships, contracts, awards or expansions	Check the publication date and look for a later update, correction or change in status.
Product or service research	The current customer workflow, features and problem the employer addresses	Use the product or service yourself where possible. If you have not used it, say so rather than claiming personal enthusiasm.
Customer experience research	Repeated customer needs, friction points and service expectations	Compare several current sources. A single review is an experience, not proof of a company-wide condition.
Employee profiles and review sites	Employee-reported work patterns, team signals and possible concerns	Check dates, roles and repeated themes. Treat this as context, not official evidence.
Informational interviews and professional networks	First-hand views of team practices, decision-making and role scope	Record who supplied the view and when. Corroborate it with the Job description or an official source.

Official evidence includes the Job description, Company website and careers page, Engineering blog, Company changelog and release notes, Funding notes and earnings calls, Annual reports, sustainability reports and public filings, and Press releases. These sources confirm what the employer has published. They do not prove what your future manager does each day.

Employee profiles and review sites, Customer experience research, Informational interviews and professional networks provide useful context. They also carry sampling and timing risks. Label them as reported experience. Do not present one employee’s view as the company’s policy.

Career guidance from UC Davis career guidance, UCF career guidance, University of Michigan career center, San José State University iSchool career blog and the Harvard career office belongs in the guidance layer, not the employer-fact layer. Cite the exact page used for any claim. An institution’s name alone does not verify a company fact or support a claim about interview practice.

Match the research to the vacancy

For a technical vacancy, use the Job description to decide whether RabbitMQ/Rabbit-to-Kafka migration, distributed inventory systems, real-time field data or on-call practices belong in your answer. If the role says nothing about those areas, do not force them into the script because they sound impressive.

For a values-led vacancy, use mission statements and company values as context. Then connect the value to the work. “Your mission inspires me” is thin. “Your focus on access matters to me because this role would improve the service for customers who currently struggle to use it” gives the interviewer a work-based reason to explore.

Compensation, benefits, remote work and location can be truthful secondary motivations. Do not invent a deeper reason. Use this line:

“The location and working pattern matter to me. I am also interested in this role because the work involves [responsibility], and my experience with [evidence] would let me contribute to [outcome].”

That answer stays honest without making practical factors the entire case. TIME advises researching the company and hiring manager while avoiding an oversold interview performance.

1. Primary employer evidence

Start with the Job description. Mark the work the role must deliver. Then verify one matching fact through the Company website and careers page, Engineering blog, Company changelog and release notes, Press releases, Funding notes and earnings calls, Annual reports, sustainability reports and public filings, or Product or service research.

A product launch is useful only if it still exists and connects to the vacancy. A funding announcement does not prove what your team does each day. A mission statement does not prove that the role lives those values.

For a technical role, use RabbitMQ/Rabbit-to-Kafka migration, distributed inventory systems, real-time field data or on-call practices only when the Job description requires related work. Your answer should explain the link:

“The role involves improving real-time field data. I have worked on distributed inventory systems, so I understand the reliability issues this work creates.”

2. Reputable external evidence

Interview Copilot’s fact-versus-inference method distinguishes employer information you have verified from your interpretation (Interview Copilot). Apply Coach suggests pairing one company fact with the responsibilities that motivate you (Apply Coach). Use both methods as checks, not as substitutes for the employer’s own material.

Career guidance from reputable university and career-office sources supports the same practical discipline: connect the work, the employer and your evidence. Present that as a method, not as proof that an employer operates in a particular way.

3. Informal context

Customer experience research, Employee profiles and review sites, Informational interviews and professional networks can reveal useful patterns. Treat them as context. Label the source honestly:

“Two employees described strong on-call ownership.”

Do not turn that impression into “Your team has excellent on-call practices.”

Salary, benefits, remote work and location can remain truthful secondary motives:

“Those factors matter to me, but the work I want to do is…”

TIME advises researching the company and hiring manager before the interview (TIME). A plain, truthful motivation is safer than a specific claim you cannot verify. A precise error damages credibility more than honest general interest.

What should you avoid saying, and what replies should you prepare?

TopInterview advises replacing unsupported praise and inaccurate product claims with evidence you can verify and explain. TopInterview’s guidance treats honesty as a credibility safeguard.

Avoid: “You are a market leader.”
Say: “Your work in [verified market] interests me because this role would let me apply my experience in [relevant work].”

Avoid: “I need a job.”
Say: “I am looking for work where I can use [skill] to solve [relevant problem], and this vacancy offers that scope.”

Avoid: “I want the benefits.”
Say: “Location and flexibility matter to me, but the work I want to do is [specific responsibility].”

An unverified company fact can be weaker than a plain, truthful explanation of why the work is worth doing. Interview Copilot recommends separating verified facts from personal inference. Replace any claim you cannot confirm on the interview date.

Use STAR when the interviewer asks for proof: situation, task, action and result. Give one relevant example. Do not add another paragraph of praise about the employer. Practise the follow-up with these interview follow-up questions after STAR answers.

TIME advises researching the company and hiring manager and avoiding inadequate preparation or overselling. TopInterview also discusses examining potential toxic-workplace signals rather than ignoring them.

FAQ

Why this role?
Name the work before naming the employer. Say: “This role interests me because it involves [responsibility]. I have evidence from [project or result], and I would apply that experience to [likely contribution].” Add one verified employer fact only when it explains why this work matters. A specific fact is not automatically stronger than a truthful role-based answer.

Why not our competitor?
Keep the comparison factual and respectful. Say: “I considered [competitor], but this role’s focus on [verified difference] fits the work I want to do. My experience in [proof] is relevant here.” Do not claim a competitor is weaker without evidence. Do not criticise its people, product or culture.

What if salary or benefits are my main motivation?
Do not invent enthusiasm for the mission. Say: “Compensation and [benefit, location or flexibility] matter to me. I am also interested in this role because it involves [specific work], where I can use [skill].” Practical needs are legitimate. Present them honestly, then show why the work itself is a credible fit.

What if I have not used the product?
Say so plainly. “I have not used the product personally, so I would not claim that. I researched [verified product fact], and the role interests me because [specific responsibility]. My experience with [relevant evidence] would help me contribute to [task].” Product research supports your answer. It does not prove personal enthusiasm.

What if public information is limited?
Use the Job description, recruiter information and any official Company website and careers page material available. Say: “Public information is limited, so I have focused on the responsibilities in the vacancy and what you explained about the team. The work that interests me is [responsibility], supported by my experience in [proof].” Do not fill gaps with assumptions.

What might disappoint you here?
Name a question, not an accusation. Say: “I would want clarity about [role condition], such as how priorities are set or how success is measured. I would raise that early and assess it against the role’s actual responsibilities.” This shows judgement without pretending every part of the job will suit you.

How can you practise the answer out loud in two minutes?

A two-minute rapid drill gives you one verified fact, one role priority, one proof point, one spoken answer and one follow-up response.

0:00–0:30 — Write three prompts (How to Answer “Why Do You Want to…).

• verified employer fact
• role priority
• proof you bring

This follows Interview Copilot’s sequence: find the fact, identify the priority, then select your evidence (Interview Copilot). Keep each prompt short. Do not write a paragraph.

0:30–1:15 — Speak once (How to Answer “Why Do You Want to…).

Answer without reading a script. Aim for the 45–60-second range recommended by Prepare.fyi (Prepare.fyi). Use this order:

“I’m interested in this role because [role priority]. I noticed [verified employer fact], which matters to me because [reason]. My experience with [proof] would help me contribute by [specific action].”

Stop after the contribution point.

1:15–2:00 — Answer one follow-up (How to Answer “Why Do You Want to…).

Choose one question and answer it aloud:

• “Why this role rather than another?”
• “What would you contribute first?”
• “What did you learn from the product?”
• “Tell me about the example you mentioned.”

Use one specific example. Do not restart the opening answer. If the interviewer asks for evidence, use STAR: situation, task, action and result. Aim to leave the listener with the employer fact, role priority and proof.

The fuller routine is separate. InterviewOra recommends saying the answer aloud three times without reading it, recording it once and then running it through an AI mock interview (InterviewOra). Use that routine when you have more preparation time. The two-minute drill is for the Friday morning recruiter call or the lift ride before the interview. It is not a substitute for a longer rehearsal.

Razen Rehearsal Sandbox: The 60-Second “Why Us?” Panel Answer

It is Tuesday morning, and you are interviewing for a senior product marketing role at Northstar Analytics. The job description makes you responsible for launching its new audit-reporting dashboard, while the panel has only 60 seconds before moving to follow-up questions. You need to show genuine interest without claiming product experience you do not have.

Setting. A video interview with Maya, Daniel and Priya. Daniel is the hiring manager; Priya leads product and joined to test whether Maya understands the work.

Cast

• Maya, Senior product marketing candidate. At stake: She needs the role but must protect her credibility.
• Daniel, Hiring manager for the role. At stake: He needs evidence that Maya understands the job and will stay engaged.
• Priya, Product lead on the panel. At stake: She needs someone who will market the dashboard accurately, not repeat claims.

The Wrong Way

Maya: I want to work here because Northstar is the market leader in analytics, and I’ve actually used the platform every week in my current role.

(Starts quickly, smiles too broadly, and glances at the notes below the camera.)

Daniel: Which part of the platform have you used most?

(Leans towards the camera and waits without rescuing her.)

Maya: The reporting suite, mainly. I love how simple it is for customers to get those audit reports out.

(Nods repeatedly, then tightens her jaw on “love.”)

Priya: The audit-reporting dashboard is still in development. What are you referring to?

(Tilts her head and keeps her voice level.)

Maya: Right, yes, I mean the current reporting tools. But the culture is also a huge reason. Everyone seems very mission-driven.

(Talks over the end of Priya’s question and folds her hands tightly.)

Daniel: What about this role interests you beyond the culture?

(Looks down at his score sheet and gives her two seconds.)

Maya: I’ve led launches before, so I’d be able to bring that experience and help the company grow faster.

(Uses a polished tone but gives no example or specific contribution.)

Priya: What would you focus on first?

(Raises one eyebrow and waits for a concrete answer.)

Why it fails. Maya’s first line creates the failure: she claims weekly product use, then Priya shows that the named dashboard does not exist yet. Her later references to market leadership, culture and growth stay broad, so the panel cannot test whether she understands the role or what she would do.

The Right Way

Maya: I’m interested in this role because it owns the launch of the audit-reporting dashboard, not just the promotion after launch.

(Sits forward, speaks at a measured pace, and keeps both feet flat.)

Maya: I saw in Northstar’s March release note that the platform added audit-log controls. That matters to me because it points to a real customer problem: proving who changed what.

(Pauses briefly after “release note” and looks at Priya.)

Daniel: Have you used Northstar’s platform yourself?

(Interrupts gently, testing whether the answer rests on a false claim.)

Maya: Not personally, so I wouldn’t claim that. I researched the release note and the job description instead.

(Stops, exhales through her nose, and answers without looking at her notes.)

Priya: What evidence suggests you could handle that launch?

(Relaxes her shoulders slightly and turns fully towards Maya.)

Maya: At Lumen, I turned support-call themes into a launch brief, tested the message with five customers, and cut confused trial sign-ups by 18 percent.

(Uses one hand to mark each step, then lets it rest.)

Maya: Here, I’d use customer evidence to explain the audit problem clearly, then give sales proof they could use in the first conversations.

(Slows on “customer evidence” and holds eye contact with both interviewers.)

Daniel: Why Northstar rather than another analytics company?

(Leans back, inviting a comparison rather than a slogan.)

Maya: Because this role connects product understanding with adoption. That combination is the work I want to do next, and I can support it with evidence rather than pretend I’m already a user.

(Finishes under a minute, then stays silent with her hands open.)

Why it lands. Maya gives up the easy shine of claiming product experience, but gains credibility by naming the limit plainly. She uses one verified fact, links it to the role’s stated work, and supplies a measurable example that shows what she would contribute. Priya changes from fact-checker to evaluator because Maya gives her something concrete to examine.

<aside class="razen-coach-card" data-razen-scenario="the-60-second-why-us-panel-answer"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=the-60-second-why-us-panel-answer&amp;article=how-to-answer-why-do-you-want-to-work-here&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=how-to-answer-why-do-you-want-to-work-here">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Begin warm but matter-of-fact when naming the dashboard; shift to direct and unhurried after Daniel asks whether you have used the product.
• When saying “I wouldn’t claim that,” drop the sales tone and use a lower, steadier voice; return to energy only when describing the Lumen result.
• Finish with a firm downward inflection on “evidence,” not an upward inflection that sounds like you are asking permission.

Pause placement

• Pause for 1 second after “audit-reporting dashboard” so the role priority lands before the employer fact.
• Pause for 2 seconds after Priya says the dashboard is still in development; use the silence to avoid defending the false claim.
• Pause for 1 second after “Not personally” before explaining what you researched.
• Pause for 2 seconds after the final contribution point, then stop instead of adding another company compliment.

Physiological cues

• Before answering, press both feet into the floor and release your jaw; this prevents the rushed opening that made the false claim sound rehearsed.
• Keep your gaze on the person who asks the challenge, then include the other panelist when naming your contribution.
• Hold one hand open on the desk while giving the Lumen result; suppress note-shuffling and repeated nodding.
• Take one quiet nasal breath before saying “I wouldn’t claim that,” and do not smile through the admission.

Recovery moves

• If you have already claimed product use, say: “Let me correct that. I haven’t used it personally, so I shouldn’t have said that. I researched the release note and the role instead.”
• If you start praising the culture, say: “That’s too broad. The work that interests me is the audit-dashboard launch, and my relevant evidence is…”
• If Daniel asks for more detail and you start rambling, say: “The short version is: I found the customer problem, tested the message, and reduced confused trial sign-ups by 18 percent.”

Watch it explained

Frequently asked questions

What is the best structure for answering “Why do you want to work here?”

Use three parts: name the work that interests you, connect it to one verified employer fact, then show evidence that you can contribute. The Specific–Personal–Forward, Them–The Role–You, and Work–Employer–Fit formulas each offer a structure for this sequence. Keep the answer conversational and avoid claims you cannot verify.

How long should my answer be?

Aim for under 75 seconds as a practical default, then prepare a shorter recruiter version. Applystead recommends 30 seconds for recruiter screens, while Prepare.fyi recommends 45–60 seconds for a full answer. Stop after your contribution point and let the interviewer ask for detail.

What if salary, benefits or remote work are my main motivations?

Do not invent a passion for the employer. Acknowledge practical factors honestly, but connect them to the work and role: “Those conditions matter to me, and I am also interested in this role because…” Keep compensation details for the appropriate stage unless the interviewer asks directly.

What should I say if I have not used the company’s product?

Say so plainly. Use verified research instead: “I have not used it personally, so I would not claim that. I looked at [specific product fact], and the role interests me because…” Then connect a real project, skill or customer problem to the vacancy.

How can I practise this answer without sounding memorised?

Write three prompts, not a full script: employer fact, role priority and proof. Say the answer aloud three times without reading it, record it once and practise one follow-up question. Remove phrases that sound unlike your normal speech, then test the answer again at the target length.