Why this company / role interview questions
The complete guide to the why this company / role interview archetype: what interviewers are actually testing, how to structure a strong answer, 20 real reported example questions, and the practice loop that makes you better at this pattern. Read it once, then run a session.
What interviewers are really testing
The interviewer is measuring whether you've done your homework, but more importantly, whether your career narrative makes sense. When a hiring manager asks "why us?", they're really asking: "Will you still be here in 18 months, or will you get bored and leave once the novelty wears off?" They've seen too many candidates who were just excited by the brand name or fleeing a bad situation, only to churn out after the company invested in onboarding them. The question is fundamentally about pattern-matching your stated motivations against the actual day-to-day reality of the role.
Beyond retention risk, they're also testing whether you understand what you're signing up for. If you say you want more autonomy but you're interviewing for a role with heavy process and oversight, that's a red flag that you'll be frustrated within months. If you claim to want customer impact but can't name a single customer segment or use case, you're revealing that your interest is shallow. Strong answers demonstrate that you've connected the dots between what shaped you, what you're optimizing for next, and why this specific opportunity—not just this company's reputation—is the logical next step. Hiring managers use this question to separate candidates who are running toward something from those who are just running away.
Three mistakes that lose this question
Listing company perks or reputation instead of role-specific drivers. When you lead with "I've always admired your brand" or "the culture seems great," you're telegraphing that any role at the company would do—which makes the interviewer wonder if you actually want this job or just want the logo on your LinkedIn. The strongest answers connect to the specific problems you'd solve, the team you'd join, or the product area you'd own, not the free lunch or the prestige.
Explaining what you're leaving without explaining what you're moving toward. If your answer focuses on what's wrong with your current company—limited growth, slow pace, lack of resources—you sound like you're fleeing rather than choosing. Even if those frustrations are valid, the interviewer hears "this person will complain about us too once the honeymoon ends." You need to reframe those gaps as positive wants: not "my current role lacks ownership" but "I want to own end-to-end delivery of a product."
Offering a first-90-days plan that's generic or purely learning-focused. Saying "I'd spend the first month learning the codebase and meeting stakeholders" signals that you haven't thought past orientation. Strong candidates propose a falsifiable hypothesis: "I'd focus on reducing the checkout abandonment rate by investigating the mobile flow" or "I'd interview the top five enterprise customers to validate the roadmap priorities." The specificity proves you've researched enough to have a point of view, and the concreteness gives the interviewer something to react to—which often sparks the best part of the conversation.
The frame strong candidates use
The best answers to "why this company" pass what you might call the find-and-replace test: if you could swap in a competitor's name without changing your reasoning, you haven't actually answered the question. This means you need to do asymmetric research—not just read the About page, but find the details that differentiate this opportunity from adjacent ones. Maybe it's that they're the only player in the space using a specific technical architecture you want to learn. Maybe it's a recent pivot announced in a blog post that aligns with where you think the market is headed. Maybe it's that the hiring manager previously built something you admire at another company. The specificity signals genuine interest, but more importantly, it demonstrates the research rigor you'd bring to the job itself.
The second frame is about narrative coherence across time horizons. Weak candidates optimize their answer for sounding enthusiastic in the moment. Strong candidates structure their answer so a hiring manager could explain it to their own boss: "This person spent three years building X, learned Y was the constraint, and now wants to go deeper on Y—which is exactly what we need for this role." When your story has that kind of internal logic, the interviewer becomes an advocate for you in the debrief. They can defend your candidacy with a clear through-line. This is why the STAR-like structure matters: current context (S) establishes credibility, what you want more of (T) shows self-awareness, the company/role mapping (A) proves you've done research, and the 90-day thesis (R) demonstrates you're already thinking like someone on the team. Each element makes the next one more believable.
Quick reference
Why this company? Why this role? Why are you leaving your current job?
Grounded in real company / role specifics (products, values, recent news); avoids trashing current employer; first-90-days is concrete and falsifiable.
The structure of a strong answer
Strong why this company / role answers follow a consistent shape. You can deliver any specific story over this skeleton — and the skeleton is what interviewers are pattern-matching against, even if they don't say so.
S: your current context and what it taught you. T: what you now want more of. A: why this company / role maps to that want. R: a concrete first-90-days thesis.
20 real why this company / role questions from interviews
Drawn from our verified bank — sourced from candidate-reported interviews, paraphrased into archetype form, quality-scored before publication.
- If you were starting a career today and had a choice between the legacy majors with locations not mattering, which company would you go with and why?
- What draws you to infrastructure-focused companies like Stripe rather than application-layer businesses?
- Why are you leaving the bedside after six months to pursue an OR position?
- Tell me about a time you left a job and what led to that decision.
- Why are you interested in Endeavor Air?
- Why do you want to work on payments infrastructure specifically at Stripe?
- Besides good pay why do you want to be a professional pilot?
- Why are you interested in Allegiant?
- Tell me about your compelling story for why you want to work at Frontier.
- Why are you interested in Horizon and how did you come to be interested in them specifically?
- Besides good pay why do you want to be a professional pilot
- Why Propel, and how does it differ from other accelerated pathways?
- Why do you want to become a flight attendant at American Airlines, and what excites you about this role?
- Why do you want to work for SkyWest?
- Why do you want to work for Endeavor?
- Why do you want to work for Southwest?
- Why do you want to move to Panama and work for Copa?
- Could you dive a little bit more about why you want to be here specifically at Morgan Stanley as opposed to other bulge bracket banks, as well as boutique banks?
- What do you know about the Starbucks Rewards Program?
- What appeals to you about perioperative nursing compared to floor nursing?
Common questions about why this company / role questions
What does a why this company / role interview question actually test?
Grounded in real company / role specifics (products, values, recent news); avoids trashing current employer; first-90-days is concrete and falsifiable.
What's the right structure for answering a why this company / role question?
S: your current context and what it taught you. T: what you now want more of. A: why this company / role maps to that want. R: a concrete first-90-days thesis.
How long should my answer be?
Aim for 90–120 seconds. Strong answers are 250–350 words spoken — long enough to land the situation, action, and result, short enough that the interviewer can follow up. Anything past 2 minutes risks losing them.
Can I use the same story for different why this company / role questions?
Often yes — strong stories tend to demonstrate multiple competencies. But you should re-frame the angle each time: when the question is about conflict, lead with how you navigated the disagreement; when it's about leadership, lead with how you set direction. Same story, different opening sentence.
What if I don't have a great example for this?
Use a smaller, real story before reaching for an inflated one. A 3-person team conflict you handled well beats a fabricated 50-person crisis. Interviewers spot embellishment in seconds — concrete details and self-aware framing matter more than scope.
Should my answer mention the outcome even if it was bad?
Yes — even when the outcome wasn't ideal, naming it directly is more credible than a vague 'we learned a lot.' Quantify what you can (timeline, dollars, people affected, downtime), then close with the specific change you carry forward.
How do I practice this pattern?
The fastest way: run a mock session and let an AI interviewer push back on your answer with follow-ups. Reading example questions is helpful, but answering one out loud, getting it scored, and rewriting it is what actually moves your performance.
Reading isn't practicing.
Try answering one why this company / role question right now before checkout, with real Claude-scored feedback in 5 seconds.
Try a sample question →