Why Do You Want to Work Here? Answers That Aren't Fake

Almost every interview includes some version of "why do you want to work here," and almost every candidate knows the game: you're supposed to sound like this company has been your dream since childhood. The problem is that most people can't sell that story with a straight face, and experienced interviewers can smell the performance. So you end up stuck between two bad options: gush and get caught, or answer honestly and watch the recruiter's pen stop moving.

There's a better middle path. After studying how this question actually plays out in hundreds of real interviews, the pattern is clear: the answers that win aren't the most enthusiastic ones. They're the most specific and the most honest about where your interest genuinely overlaps with what the company does. This guide breaks down what interviewers really want, why forced passion backfires, and gives you nine copy-ready sample answers you can adapt.

What interviewers really want when they ask this question

The hidden question underneath "why do you want to work here" is not "do you love our logo." It's two practical things: will you fit here, and will you stick around long enough to be worth the hire. Recruiters phrase it as passion, but what they're screening for is whether you understand the role, whether you've thought about it, and whether your reasons will still hold in six months.

Hiring managers who are honest about this say the cult-devotion version actually works against them. As one put it in a recruiting discussion, any place that rewards pure flattery "winds up with bad hires." Another framed the real target well: it isn't about loving the company logo, it's about having an interest and caring about what you do. That distinction matters. You don't need manufactured excitement about the brand. You need a credible, specific reason your skills and goals line up with this particular job.

This is why authenticity tends to beat polish. Career research consistently finds that candidates who connect genuine values and experience to the employer are rated more favorably than those relying on obvious impression management. A grounded answer that names something real about the company reads as competence. A rehearsed passion speech reads as a candidate who is good at rehearsing.

Why forced passion talk backfires

Candidates are increasingly done with the charade, and they're loud about it. In one widely-shared r/jobs thread about "passion talk", the person who started it described being asked what motivates them to wake up every morning for a basic data entry job, and finally answering that they just wanted the paycheck and the health insurance. The room went quiet. They didn't get the job. But the comments underneath were a wall of agreement: nobody has a passion for spreadsheets at nine in the morning, and pretending otherwise feels like joining a cult instead of a workplace.

The most telling detail in these threads isn't the anger, it's how transparent the faking is on both sides. People describe nodding along to mission statements they skimmed thirty seconds before the call, while the job posting said one thing and the hiring manager described something completely different in the actual interview. Everyone is winging it. The "skill" becomes matching the energy and hoping nobody asks a follow-up you didn't prep for. That's a fragile way to interview, because the follow-up almost always comes.

Here's the part that should change how you approach the question. Honesty framed with a little strategy often lands better than canned enthusiasm. One candidate answered "why do you want to work here" with "honestly, the commute and the salary band," watched the interviewer's pen stop, and got the job anyway. The manager later said that answer was the reason he pushed for the hire. The lesson isn't to blurt out your rent situation. It's that a real reason, delivered with confidence, signals a real person who has actually thought about the trade-offs.

The honest-but-strategic formula

You don't have to choose between lying and torpedoing yourself. Use a simple three-part structure that stays true while pointing at what the interviewer needs to hear:

1. Something specific about the company or role. A product, a problem, a way they work, a recent move. Concrete, not "great culture."
2. How it connects to your skills or goals. The honest overlap between what you're good at and what they need.
3. What you'd contribute. Flip it toward them. Robert Half recommends reframing the whole question as "why would this company want to hire me," and building your answer around the value you'd add.

This structure matches what candidates report when they stop performing. In a popular r/jobs thread on dropping the polished act, one person wrote that their offer rate went up noticeably once they answered questions honestly instead of giving textbook responses. A commenter added a sharper version of the same insight: as a new grad, their answers were "abstract and kind of nebulous," and interviews only improved once their responses became concrete and understandable. Specific beats vague every time. Your job is to give the interviewer something they could actually repeat to their boss.

What to research before you answer

Every good answer to this question is built on a few minutes of homework. Company research is the single most cited fix by career experts, and Indeed's guidance is blunt about it: learn the products, services, mission, and workplace culture, then tie those to your own goals. Not knowing enough about the company is one of the fastest ways to sink this question.

Here's a tight checklist to run before any interview:

• Recent news. A product launch, funding round, expansion, or new market. This is your best source of a specific, current talking point.
• The actual job description. Read it against how the recruiter describes the role, because they often diverge. Note the real problems the job is meant to solve.
• Mission and values wording. Not to recite, but to find the one line you can honestly connect to your own experience.
• The product itself. If you can use it, sign up and try it. "I've used it" is worth more than any adjective.
• The team and reviews. Glassdoor, LinkedIn, employee posts. Look for what the work is actually like.
• One problem you could help with. This becomes your contribution point.

Nerves erase all of this in the moment. When your mind blanks, having a company-specific cue in front of you is the difference between a generic answer and a targeted one. This is where MeetAssist helps during a live call: it can surface a relevant, company-specific talking point in real time so you can point at something concrete instead of falling back on "I really admire your culture." It works during the actual interview, so it covers you exactly when the pressure hits.

9 sample answers to "why do you want to work here"

Fill in the brackets with your own research. Keep them short, spoken, and specific. Each note explains why it works.

1. Mission and values fit

I looked into how you [specific thing they do, e.g. handle X for customers], and it lines up with how I like to work. I'd rather spend my time on [value in action] than [the opposite], and that's not true of every company in this space. That fit is a big part of why I applied.

Why it works: it names a real behavior, not a slogan, and shows you compared them to alternatives.

2. Career growth

I'm at the point where I want to go deeper in [skill or area], and this role clearly does more of that than my current one. You're [growing / building X / working on Y], which means there's real room to develop instead of doing the same thing on repeat. That's what I'm looking for next.

Why it works: honest self-interest framed as ambition, tied to something specific about their trajectory.

3. You love the product

I've actually used [product] for [context], and [specific thing you liked]. When I saw the role open, it was an easy yes because I already understand what you're building and why people pick it. I'd rather work on something I get than something I'd have to fake interest in.

Why it works: real usage is impossible to fake and instantly credible.

4. The team or people

I talked to [person] / read about how the team works, and the way you [collaborate / review work / handle X] is the kind of environment where I do my best work. I've been on teams where [contrast], so I know what fits me, and this looks like it does.

Why it works: shows you've done real digging and know your own working style.

5. Career changer

I'm moving into [field] from [previous field], and this role is a strong bridge because it needs [transferable skill] that I've spent years building, applied to [new area]. Your team seems set up to [reason it suits a switcher], which is exactly the kind of place I want to make that move.

Why it works: turns a change into an asset and names the overlap directly.

6. Junior or no experience

I'm early in my career, so I'm honest that I'm here to learn and contribute at the same time. What drew me to you specifically is [specific thing, e.g. the kind of projects, the training, the product]. I've already [self-taught / built / done X] to get ready, and I want to keep building that in a place doing real work in [area].

Why it works: honesty about experience level plus proof of initiative. If you're breaking into tech, our guide on the fastest way to get an IT job with no experience covers how to build that proof.

7. Remote or flexibility, framed honestly

I'll be straight that the [remote setup / flexibility] matters to me, because I do focused work best without a commute eating my day. Beyond that, the role itself fits what I'm good at: [specific skill match]. So it's both. The setup lets me show up at my best, and the work is something I actually want to do.

Why it works: names a practical reason without making it the only reason. Honesty plus a fit anchor.

8. Role-specific impact

From the job description, it looks like you're trying to [solve X problem]. I've done [relevant work] before and got [result], so I can see pretty clearly where I'd be able to help here. That's the part that got me interested: it's a problem I know how to move on.

Why it works: pure contribution framing, backed by a past result. This is the version that persuades busy hiring managers.

9. Honest "salary and stability," reframed professionally

I'll be honest that stability and fair pay matter to me at this stage, and this role delivers on both. That's not the whole story though. I looked at what you're building in [area], and it's work I can do well and stay engaged with. I'm looking for somewhere I can commit to for the long run, and this checks the boxes that make that realistic.

Why it works: it says the quiet part out loud without stopping there, signaling a candidate who plans to stay. If pay comes up directly, our guide to answering salary expectations has scripts that won't get you rejected.

Answers that get you rejected

The same handful of mistakes sink this question again and again:

• The flat "just the paycheck." The honest impulse is fine, the blunt delivery isn't. The candidate who said it and got hired paired it with confidence and a real fit. Give the interviewer somewhere to go.
• Generic "great company culture." With no specifics, this signals you researched nothing. Name a behavior, a product, or a piece of news instead.
• Reciting the mission statement. They wrote it. Repeating it back proves you can read a homepage, nothing more.
• Obvious lying that dies on the follow-up. The trap candidates describe is nailing the smiling, confident answer and then getting one question deeper than they prepped for. If your reason is invented, you can't survive "tell me more about that." A true reason lets you keep talking.

You can keep the truth and still protect yourself. The move is selection, not fabrication: pick the honest reasons that also make you look good, lead with those, and skip the ones that don't help. That's putting your best foot forward, not lying.

How to sound natural in the moment

The candidates who improved most didn't memorize better scripts, they stopped scripting. Overpreparation is its own trap: build a perfect performance and any unexpected question shatters the illusion, which is easy to see through. Talking points beat scripts because you can adapt them.

A few things that help:

• Treat it as a two-way conversation. The interview is you deciding whether they're worth your time too. That mindset lowers the pressure to perform and makes your answers sound like a person talking, not a candidate auditioning.
• Match their energy. If the interviewer is calm and direct, a high-energy dream-job speech feels off. Meet them where they are.
• Admit what you don't know. Saying "I don't have experience with that yet" builds trust and makes your real claims more believable.
• Keep one specific cue ready. You need conversational fluency, not memorized paragraphs. Having a single company-specific point on hand, whether from your notes or surfaced live by MeetAssist during the call, lets you stay natural and still say something concrete when nerves hit.

The same relaxed, specific approach carries the rest of the interview too. It's how you handle "tell me about yourself" and it's what makes the questions you ask the interviewer land, since a two-way conversation only works if you actually bring questions.

FAQ

What are good reasons to want a job?

Good reasons combine genuine self-interest with fit: the work uses skills you're strong at, the role helps you grow, the product or mission connects to something you actually care about, and the company is stable enough to commit to. Pay and flexibility are legitimate too, as long as they aren't your only stated reason. The best reasons are specific to this company and could be repeated back by the interviewer.

Why are you interested in this position?

Focus on the role, not just the company. Name a specific responsibility in the job description that matches your experience, explain the overlap with your skills, and point to a problem you could help solve. Something like: "This role centers on [X], I've done [related work] with [result], so I can see where I'd contribute right away." That reads as competence and real interest at once.

How do you answer "why do you want to work here" with no experience?

Be honest that you're early in your career and there to learn, then prove initiative. Name something specific that drew you to this company, mention what you've already done to prepare (self-teaching, projects, certifications), and connect it to the work they do. Enthusiasm plus evidence of effort beats claiming experience you don't have, which collapses on the first follow-up question.

What's the best way to say you want a job?

State it directly and tie it to fit and contribution: "I'd genuinely like this role because [specific reason], and I think I can help with [specific thing]." Avoid framing it around your own hardship or desperation, since that shifts focus away from mutual benefit. Confidence plus a concrete reason signals a candidate who has thought it through, not one who will take anything.