How to answer "why do you want to work here" in an interview

The interviewer leans back and asks the one you saw coming: "So, why do you want to work here?" You have the company's About page open in a browser tab, and you start handing it back to them: great reputation, strong culture, a leader in the field. It sounds fine. It also sounds like the last four people they interviewed, because every one of them read the same About page.

That is the trap in this question. It feels like an invitation to praise the company, so most people do, and praise is the one answer that proves nothing. Here is what the interviewer is really checking, and how to give a reason only you could give.

The takeaways

• They are checking two things. Whether you understand what this job actually involves, and whether you are likely to stay. Flattery about the brand answers neither.
• Praise is interchangeable; a specific fit is not. "Great company" fits their competitor too. Tie one concrete thing about this role to what you want to do next, and the answer becomes yours alone.
• No script fakes wanting a job. If your only reason is that you need any paycheck, interviewers hear it. Find the one true reason you would pick this role, and if there isn't one, that is worth knowing before you accept.

What is the interviewer really asking when they say "why do you want to work here"?

Two hidden questions at once. First, did you understand what this role does day to day, or are you just impressed by the logo. Second, are you likely to stay and stay motivated, or will you leave the moment something else pays more. Your answer has to reassure both.

The question is a fit test dressed up as a compliment. A hiring manager who fills a role and watches the person quit in four months has failed twice, so they screen hard for people who want this role in particular and can say why. This runs under most of the interview questions that keep coming back: each one is really asking whether you understood the job.

Why do generic "great company" answers fall flat?

Because they are interchangeable. "You have a great reputation and I admire your culture" is true of half the companies in the industry, so it tells the interviewer nothing about you or your fit. Anything a rival could say back word for word is filler.

Use the swap test. Before you commit to a reason, ask whether it would work, unchanged, in an interview at this company's closest competitor. If it would, cut it. "You're a leader in fintech" passes to every fintech firm. "Your onboarding flow is the one I point to when I explain what good looks like" passes to exactly one company. The second reason could only come from someone who has used the product and thought about it, which is the signal the interviewer wants.

How do I build an answer only I could give?

Start from something specific about this company or role, then connect it to your own direction. Four steps:

1. Dig past the careers page. The mission statement is written for everyone. Spend fifteen minutes on the actual work: the product, a recent launch, the engineering blog, the way the posting describes the day to day. You are hunting for one concrete detail.
2. Pick the detail that connects to you. Not the most impressive fact, the one that overlaps what you want to do next or are good at: a tool they use, a problem they are clearly solving, a way of working you have been looking for.
3. State the two-way fit. Say what draws you to that detail and what you would bring to it. "You're rebuilding your onboarding, and untangling messy first-run flows is the part of the job I like most" connects their reality to yours.
4. Keep it to two or three sentences. One real reason, said plainly, beats a paragraph of enthusiasm. You are giving them something they can believe, not writing an essay.

What if I just need the job and don't have a burning reason?

Be honest with yourself first. If the only true reason is that rent is due, no script will manufacture passion an interviewer can't sense. But "any job" is rarely the whole truth. There is usually one thing that made you apply to this posting over the other ten: the team is small enough that you would own real work, the role is a step toward something you want, the hours finally let you eat dinner at home. Find that reason and say the professional half of it out loud.

When I was applying during my own job search, the answers that landed were never about the company being great. They were the ones where I could point to a specific thing the team had built and say why it matched what I wanted to do next. This note is not for someone applying to a company they actively don't want to join and hoping to bluff through. If you cannot find one honest reason to pick this role, the useful move is to notice that before you accept, not after.

Is "why do you want to work here" the same as "why should we hire you"?

No. They point in opposite directions. "Why do you want to work here" is about your motivation, what draws you to them. "Why should we hire you" is about their return, what they get by picking you. You can prepare both from the same job posting, but this one has to land on genuine interest and fit, while the other lands on proof and value. If the conversation swings to your value instead of your motivation, that is a different answer, covered in how to answer "why should we hire you".

Where Jobscalr fits

The hard part is finding the one specific reason that is also true. Jobscalr is a mobile app that runs a match analysis between a job posting and your profile, scoring the fit from 0 to 100 and explaining where you overlap the role and where you fall short. That overlap is often the honest reason you want the job: the part of the role that matches what you already do well. It drafts cover letters from a company-research step for the same purpose, and its interview prep lets you rehearse this answer as spaced-repetition practice, so it comes out sounding like you. It will not invent enthusiasm you don't have, which is the point.

Common questions about "why do you want to work here"

How long should my answer to "why do you want to work here" be?

Around thirty to sixty seconds, or two to three sentences. Long enough for one specific reason and the fit behind it, short enough that you are not padding. If you catch yourself listing three reasons, you probably don't trust any single one of them yet, so pick the strongest and cut the rest.

Should I mention salary or benefits when they ask why I want to work here?

No, not here. The question is about fit and motivation, and leading with pay or perks signals that the work itself is secondary to you. Compensation is a fair topic later in the process. Save this answer for something about the role or company that connects to what you want to do.

What if I'm applying to a company I don't know much about?

Do the fifteen minutes of research before the interview, because "I don't know much about you" is the one answer that sinks this question. Read the product, a recent announcement, or the role description closely and find one concrete hook. You need one real detail, not an encyclopedia.

Can I reuse the same answer for every company?

No. A reusable answer is generic by definition, and generic is exactly what this question screens out. The structure can repeat (one specific detail, tied to what you want), but the detail has to change for each employer, or the interviewer will hear a template.