Try this: "I read your engineering blog post on rebuilding your checkout flow, and the trade-offs you described match the problem I solved at my last job. This account executive role would let me use that experience from week one, and I'm ready to bring it somewhere it'll compound." That's the whole shape: company fact, personal connection, career payoff, said in about 60 seconds, built on something checkable.
TL;DR:
- A deep research fact should be specific, sourced, and reveal an insight that differentiates the company from competitors.
- Connecting that fact to the role must demonstrate how you will directly contribute based on that unique knowledge.
- Explaining why now is the right time should focus on personal career or market shifts that align with taking this role.
- Generic praise or overly enthusiastic statements fail because they lack a deliberate connection to the company's specific circumstances.
- Practicing the answer aloud, focusing on authenticity over memorization, helps convey confidence and sincerity.
Table of Contents
- The three-beat structure: this company, this role, this time
- A 30-minute research routine that finds something real
- Two strong answers and one weak one, annotated
- A fill-in-the-blank template and a pre-interview checklist
- A coaching note on finding the honest answer
- Where most advice on this question gets it wrong
- How MT Coaching can help you get this answer right
- Sources
- FAQ
The three-beat structure: this company, this role, this time
Every strong answer to "why this company" follows the same rhythm, and once you see it, you can't unsee it. MIT CDO recommends a three-part answer covering the company, the position, and the timing, and each beat does a different job.
The first beat, this company, needs one fact you couldn't have said about a competitor. Not "you're a market leader" (everyone says that), but something like a specific product decision, a stated value you've seen in practice, or a technical trade-off they wrote about publicly. The second beat, this role, connects that fact to what you'd actually do in the job, not just what excites you about the mission. The third beat, this time, explains why now: what's changed in your career or the market that makes this the right moment.
Sequence matters. Start with the company because it proves you chose them deliberately. End with timing because it shows self-awareness, not desperation.
- Pick one fact from your research that passes the swap test (more on that below).
- Link it to a specific part of the role, not the company as a whole.
- Close with a one-sentence reason this move makes sense for you right now.
Pro Tip: Write your three beats as three separate sentences first, then join them. It stops the answer turning into one breathless run-on.
A 30-minute research routine that finds something real
Most candidates skim the About page and call it research. That's surface research, and interviewers can spot it in a sentence. Deep research means finding something you couldn't have guessed, and it takes less time than people assume.
- Read the first three bullets of the job description again, they usually reveal what's actually urgent for the team.
- Check the company's engineering or careers blog for a recent post about a decision, a launch, or a problem they solved.
- Scan recent press releases or news coverage from the last few months.
- Look at what employees are posting on LinkedIn, particularly anything about culture or projects.
- Glance at Glassdoor trends for patterns, not individual complaints.
CodeSnatch's swap test is the fastest way to check your fact is good enough: if your sentence still makes sense with a competitor's name-dropped in, it's too generic and needs sharpening.
Pro Tip: Spend your last five minutes writing down one fact and one sentence about why it matters to you, before you forget which detail felt honest.
Two strong answers and one weak one, annotated
Here's what separates an answer that lands from one that blends into every other candidate's.
Strong example 1, early career: "Your blog post on redesigning the onboarding flow for new sellers mentioned cutting drop-off by simplifying the first three steps. I did something similar shrinking a support queue at my last internship, and I want to keep doing that kind of work somewhere it's core to the product, not a side project." This works because the fact is specific, sourced, and tied to a real personal outcome.
Strong example 2, senior or technical: "You've clearly bet on event-driven architecture over a monolith, and that's a hard call given your team size. I've made that same trade-off twice, once well and once badly, and I'd rather bring that judgement here than watch someone else learn it the expensive way." ProductInterview's guidance for senior candidates backs this approach: name a real tension, take a position, connect it to your experience.
Weak example: "I've always admired your commitment to innovation and your amazing culture. I want to grow with a company that values its people." Every phrase here fails the swap test. "Commitment to innovation" and "amazing culture" could describe almost any company on the shortlist, and an interviewer hears dozens of versions a week.
The question isn't whether you sound enthusiastic. It's whether you sound like you chose them on purpose.
A fill-in-the-blank template and a pre-interview checklist
Use this the night before:
"I noticed [specific company fact], which tells me [what it means about how they work]. In this role, I'd get to [connect fact to actual responsibilities]. Right now, I'm looking for [reason this timing makes sense for you]."
- Confirm you have one deep research fact, sourced and specific.
- Write two bullet points connecting that fact to the role's actual duties.
- Rehearse out loud until it lands close to 60 seconds.
- Prepare one question to ask that builds on the same fact.
- Note one honest reason this move matters to you right now.
- Record yourself saying the answer once, then listen back for filler words.
- Time it, aim for 45 to 75 seconds rather than a strict cutoff.
- Ask a friend or peer to react honestly, not just tell you it sounded fine.
A coaching note on finding the honest answer
Most clients I work with already know the fact that would make their answer strong, they just haven't said it out loud yet. I ask three questions: what did you notice about this company that you haven't mentioned to anyone else? What part of the role would you miss if you didn't get it? What's true about your timing that you're tempted to leave out? The answers usually write the script themselves.
— Ruairi
Where most advice on this question gets it wrong
Most guidance tells candidates to sound enthusiastic. That's the wrong target. Harvard Business Review's framing gets closer: interviewers are checking for evidence of a deliberate choice, not the volume of your excitement. Enthusiasm without specifics reads as desperation, or worse, as a copy-paste answer used for every application that week.
The overrated piece of conventional advice is memorising a polished paragraph. Polish reads as rehearsed, and rehearsed reads as insincere, even when the content is true. What matters more is having one real fact and being willing to say something slightly unfinished around it. Strengths-based interviewing guidance from CIPD points at something useful here too: interviewers are also listening for what genuinely energises you, not just your competence. If you skip that and lead only with achievements, you'll sound qualified but forgettable.
Prioritise the research over the delivery. A rough answer built on a real fact beats a smooth answer built on nothing.
How MT Coaching can help you get this answer right
If you'd rather talk it through than write it alone, professional career coaching services can offer one to one interview preparation built around exactly this kind of scripting and rehearsal, pairing practical structure with honest feedback on how you actually sound.
We help you find the fact worth using, shape it into an answer, and rehearse it until the timing feels natural rather than memorised. You can see the full range of coaching and book a session through the main site whenever you're ready.
Sources
- How to Answer “Why Do You Want to Work Here?” — Harvard Business Review
- Why This Company? — CodeSnatch
- How to conduct a strengths-based interview — CIPD
- 3 Tips for Answering “Why Do You Want to Work Here” (+ Examples) — MIT CDO
FAQ
Why this company answer example?
A strong example names one specific, sourced fact (a blog post, a product decision, a recent launch), connects it to the actual duties of the role, and ends with a reason the timing makes sense for you. Avoid generic praise like "great culture" or "industry leader" that could apply to any employer.
How to answer a why company question?
Use the three-beat structure recommended by MIT CDO: this company, this role, this time. Lead with a checkable fact, link it to the job's real responsibilities, then close with why now is the right moment for you.
Why do I want to work for this company?
The honest version of this answer usually comes from something you noticed in your own research, not from the company's marketing copy. Ask yourself what detail about the role or the company genuinely changed how you see it, and build your answer around that.
What is your 3 strength best answer?
This question is really about self-awareness paired with relevance to the role, not a fixed list of three traits. CIPD's strengths-based interviewing guidance suggests picking strengths tied to what energises you at work, then showing how each one matches something the job actually demands.