Why Do You Want to Work Here? How to Answer + Examples
A strong answer to “Why do you want to work here?” connects something specific about the employer or the role with your own experience, strengths or career direction. It is not a compliment contest. The interviewer is trying to find out whether you understand the job, whether your reasons are real, and whether what motivates you lines up with the work they actually need done. That means the useful ingredients are specificity and honesty, not flattery.
Quick answer
Build the answer in three moves:
- 1. Mention something specific that genuinely interests you about the company or the role.
- 2. Explain why it connects with your experience, strengths or career direction.
- 3. Show, briefly, how you could contribute.
Keep it conversational and roughly a minute long. One real reason explained well beats three vague ones.
Key takeaways
- • Be specific: name something about this employer or job that you could not copy into another interview.
- • Connect that interest to your own experience so it sounds credible rather than rehearsed.
- • You do not need an emotional attachment to the company — interest in the work is a legitimate answer.
- • Pay, benefits and remote work are reasonable priorities, but they rarely make a complete answer to this question.
- • Keep the contribution part short so you do not turn this into “Why should we hire you?”
- • Truthful and slightly plain beats polished and invented; interviewers ask follow-up questions.
1. Why interviewers ask this question
No one can tell you exactly what a particular interviewer is thinking, and different companies use this question for different reasons. Still, the question usually exists because the employer wants information that a résumé does not provide. Your work history shows what you have done. This question is about what you are looking for now and whether this particular job is a plausible match for it.
In practice, an interviewer may be trying to understand several things at once:
- • Whether you researched the company at all, or applied to everything with the same cover letter.
- • Whether you understand what the role actually involves, rather than the title alone.
- • What motivates you — the work itself, the problems, the customers, the scope, the learning.
- • Whether your interests line up with the work that genuinely needs doing on their team.
- • Whether you can give a thoughtful, specific answer instead of a generic one.
There is also a quieter reason. Hiring someone who leaves in four months is expensive and disruptive. If your reasons for wanting the job are concrete and connected to the day-to-day work, it is easier for the interviewer to picture you still being interested a year in. You do not need to promise loyalty or claim you will stay forever. You just need your reasons to be grounded in something real about this job.
One thing the question is almost never about: how much you admire the company. Praise is easy to produce and impossible to verify, so it carries very little information. An interviewer who hears “you're an industry leader with a great culture” has learned nothing about you. An interviewer who hears “I've spent two years doing claims intake and this role moves that work upstream into prevention, which is the part I keep wanting to get to” has learned quite a lot.
2. How to answer “Why do you want to work here?”
Work through five steps. Do this once in writing, then practice it out loud until you can say it without reading.
STEP 1
Identify one or two genuine reasons
Ask yourself why you actually applied. The honest answer might be the product, the industry, the type of customer, the size of the team, the technical problem, or simply that the responsibilities are a step you want to take. Pick the one or two you could defend in a follow-up question. Two reasons are usually enough; five becomes a list.
STEP 2
Connect them to the actual job
Reread the job description and find the responsibility that matches your reason. If you are interested in the company but cannot tie it to the work, your answer will float. “I like your product” becomes much stronger as “I like your product, and this role owns the onboarding flow, which is where most of my work has been.”
STEP 3
Connect the role to your background
Explain why that responsibility is a credible fit. This can be direct experience, transferable skills from another field, or a deliberate career direction you have been working toward. This is the step that turns interest into something an interviewer can believe.
STEP 4
Add brief evidence
One sentence of proof. A project, a responsibility you held, a result you can describe accurately. Keep it short — this is a supporting detail, not the story. If the interviewer wants the full version, they will ask.
STEP 5
Finish with what you would contribute or learn
Close forward-looking, in a sentence. Something you could help with, or something you want to get better at in this environment. Then stop talking and let the conversation continue.
WEAK
“I've heard this is a great company and I think it would be a great opportunity for me.”
BETTER
“Two things drew me in. You work almost entirely with small independent clinics, and that's the customer I've supported for the last three years — I know how differently they buy compared with hospital groups. And the posting describes this role as owning the whole implementation, not just the handoff. I've been doing the handoff half and I want the whole thing.”
The second version is not more eloquent. It is more specific. It names the customer type, names the responsibility from the posting, and explains the personal reason in one line. Notice that it makes no claims about the company that could turn out to be wrong.
“I'm interested in this role because [specific reason about the company or the work]. In my experience with [relevant experience or skill], I've [brief, concrete evidence]. What stands out to me about this position is [specific responsibility or opportunity], and I'd be glad to contribute by [realistic contribution].”
Use the template as scaffolding, then rewrite it in your own words. Read it aloud once; if any phrase feels like something you would never say in conversation, change it. A slightly imperfect sentence in your own voice sounds far better than a polished one that clearly came from a template.
3. The Company → Role → Fit → Contribution framework
If you remember nothing else, remember this order. It naturally moves from them, to the job, to you, to what happens next — which is roughly how a good answer feels when you hear it.
COMPANY
What specifically interests you about this employer?
Question to ask yourself: “What specifically about this employer caught my attention?”
ROLE
What specifically interests you about the position?
Question to ask yourself: “What part of the job actually interests me?”
FIT
Why does this connect to your background?
Question to ask yourself: “What experience makes that interest credible?”
CONTRIBUTION
What could you realistically bring?
Question to ask yourself: “What could I contribute in the first months?”
Company. Something concrete: the product or service, the business model, the market they serve, a reputation for a particular kind of work, a recent public announcement, the customers, the direction the company appears to be heading, or the specific team. A mission statement counts only when it genuinely matters to you and you can say why. Generic praise — innovative, industry-leading, great culture — is filler.
Role. Name a responsibility, a problem, a skill, a level of ownership, a customer group, a technical challenge or a scope of leadership from the job description. This is the part most candidates skip, and it is the part that shows you read the posting properly.
Fit. Relevant experience, transferable skills, an accomplishment, a career direction, or a strength you can back up. The fit sentence is what makes the interest believable rather than polite.
Contribution. One sentence, deliberately short. You are signalling that you thought about what you would actually do, not making your full case for being hired. The full case belongs in “Why should we hire you?”
4. How to research the company before answering
You need material, and thirty focused minutes is usually enough. Everything you need is normally published by the employer itself.
- • The official company website, especially the product or service pages.
- • The job description — read it twice, slowly.
- • The careers page and how the company describes working there.
- • Recent official announcements, press releases or a company blog.
- • Published values or mission, where they are relevant to your reasons.
- • Anything the recruiter told you in the screening call or the invitation email.
- • Publicly available team or department information, such as an about page.
As you read, look for:
- • What the company actually does, described in plain language you could repeat.
- • Who its customers are and what those customers need.
- • Current priorities — what the company keeps mentioning.
- • The role's real responsibilities, not just the title.
- • Projects, products or initiatives the role would touch.
- • Skills that appear repeatedly in the posting; repetition is a signal.
- • Problems this role probably exists to solve.
Two limits worth respecting. First, do not manufacture enthusiasm from your research. The goal is to find something you honestly find interesting, not to build a case for feelings you do not have. If thirty minutes of reading turns up nothing that interests you at all, that is useful information about the job. Second, keep research professional. Reading a hiring manager's public professional profile is normal; digging through employees' personal social accounts is not, and mentioning it in an interview makes people uncomfortable.
Write your findings into three or four bullets, not paragraphs. Bullets keep you flexible when the question arrives in an unexpected form — “what attracted you to us?”, “why this role?”, “what do you know about what we do?”. For the wider preparation routine around this, see our job interview preparation guide.
5. What to say if you genuinely like the company
Real enthusiasm is an advantage, but only if you keep it concrete. The trap is that admiration tends to come out as adjectives, and adjectives sound like flattery. “I've always dreamed of working here” gives the interviewer nothing and, if it is not strictly true, invites an awkward follow-up.
Instead, name the specific thing and attach it to the work. Good sources of genuine interest include:
- • Using or knowing the product. Say what you use it for and what you noticed.
- • Interest in the industry. Explain what pulled you into it and what keeps you there.
- • The company's direction. Reference something the company has publicly said, accurately.
- • Mission. Only if it genuinely matters to you, and say why in a personal sentence rather than repeating their wording.
- • The customers served. Often the strongest option if you have worked with that group before.
- • The professional or technical challenge. Scale, complexity, regulation, craft.
Compare: “I love this company” versus “I've used your scheduling tool at two previous employers, and the thing I noticed both times was that the front-desk staff actually stuck with it — which is rare. That's the kind of product I'd like to be closer to building.” The second is enthusiasm with a fact attached.
One caution: do not claim a long-standing admiration you do not have. Saying you have followed a company for years invites the follow-up “what changes have you seen?” — and a blank answer is worse than never having made the claim. Recent interest is completely acceptable. “I hadn't come across you before this posting, but the more I read the more the customer focus stood out” is an honest and perfectly strong opening.
6. What to say if you mainly want the role
Most candidates do not have an emotional connection to the employer, and that is completely normal. Plenty of good hires apply because the job looked like the right work at the right time. You do not need to pretend the company is your dream employer, and pretending usually shows.
When the company is not the draw, put the weight on the work. Honest, respectable reasons include the responsibilities, the skills you would use or build, the type of work, the problems you would solve, the customers you would deal with, the scope of the team, a leadership opportunity, a clear path forward in your field, or the chance to learn something specific. Then anchor at least one reason to something real about this employer — the size, the market, the setup, the customer base — so the answer is not one you could give to any company in the industry.
Realistic example: no personal attachment to the employer
“I'll be straight with you — I didn't know the company before I saw the posting. What made me apply is the shape of the role. Right now I handle scheduling for one site, and this position covers four, with responsibility for the coverage plan rather than just filling gaps. That's the move I've been trying to make. And from what I've read, you run those sites quite independently, which suits how I like to work. I'd want to spend the first month understanding how each site currently operates before changing anything.”
Why it works: it is honest about the starting point, then gets specific fast about the role and the employer's structure, and ends with a realistic first step rather than a promise.
Honesty here is not a weakness. Interviewers hear invented devotion constantly, and a candidate who is clear-eyed about why the job fits is usually easier to trust than one who claims a lifelong passion for enterprise logistics software.
7. Entry-level answer examples
With little work history, lean on coursework, part-time jobs, volunteering and genuine curiosity about the work. The examples below are fictional, and any numbers in them are illustrative sample figures, not real results.
Recent graduate
“I studied environmental science, and most of my classmates went into fieldwork. What interested me more was the reporting side — making the data usable for people who have to act on it. This role sits exactly there: pulling site data together into the quarterly compliance reports. I did something similar on a smaller scale for my final-year project, where I cleaned up three years of monitoring data for a local water group so they could actually see the trend. I'd be coming in needing to learn your systems, but the type of work is the part I already know I like.”
Why it works: It explains a genuine preference, ties it to a named responsibility from the posting, offers one piece of real evidence and is honest about what still needs learning.
Limited experience, changing from unrelated work
“I've spent the last two years in a call centre, and the part of that job I was best at was untangling billing problems — the ones where three different systems disagreed. This role is basically that, full time, for accounts rather than individual customers. I applied here specifically because you handle the billing in-house rather than outsourcing it, so the person doing the work can actually see the whole picture. I know I'd have a lot to learn on the accounting side, but I'm coming in with the customer half already.”
Why it works: It turns limited experience into a relevant strength, names a specific and verifiable fact about how the employer operates, and sets a credible expectation about the learning curve.
First professional job after part-time work
“I've worked in retail since I was seventeen, mostly in stock and inventory, and I got quite interested in why the forecasts were always wrong in December. This is my first office role, and I picked this one because your team handles planning for a chain about the size of the one I worked for — so I've seen the problem from the shop floor. On a sample basis I rebuilt our store's reorder sheet and it cut our weekend stockouts noticeably over one quarter. I'd like to do that with real tools instead of a spreadsheet I made myself.”
Why it works: It uses non-professional experience as legitimate evidence, frames the result as a sample achievement rather than a precise claim, and connects the employer's scale to the candidate's own.
8. Experienced-candidate answer examples
With more experience, the emphasis shifts. Interviewers expect you to be specific about scope and accomplishments, and they expect your reasons to be more considered. Not every answer should be about growth — at this level, doing work you are good at is a perfectly strong reason.
Experienced individual contributor
“I've been doing integration work for about six years, mostly for retail clients, and the thing I keep running into is being handed a spec someone else wrote after the client conversation is over. Your posting describes this role as sitting in the discovery calls as well as building — that's the difference that made me apply. I've built roughly twenty client integrations, and the ones that went well were always the ones where I'd heard the client describe the problem myself. I'd expect to be useful on the harder migrations fairly quickly, and I'd want to be in those early conversations.”
Why it works: It names a concrete frustration, connects it to a specific line in the job description, gives scope as evidence and keeps the contribution sentence brief and realistic.
Senior candidate
“Two reasons. The first is the customer base — you sell to mid-sized manufacturers, and I've spent most of my career in that segment, so I know how long their buying cycles run and why. The second is that this role owns the technical side of renewals, which most companies split off. I've seen both models and the combined one works better. In my current role I've handled the renewal architecture for our fifteen largest accounts. What I'd bring first is probably pattern recognition on where those renewals quietly go wrong.”
Why it works: It gives two distinct, specific reasons, uses segment expertise rather than generic seniority, and offers a contribution that is modest and concrete.
Manager / leadership candidate
“I looked at this one carefully because the team is being rebuilt rather than expanded, and that's a particular kind of job. I've done it once before — took over a support team of nine after two people had left and the queue had backed up badly, and spent the first three months mostly listening before changing the rota. I'd rather do that than inherit something already running smoothly. What interests me about your setup specifically is that support sits with product rather than under sales, which is unusual and, in my view, the right way round.”
Why it works: It shows the candidate understood the real situation, provides directly relevant leadership experience, and names a genuine structural observation about the employer instead of praise.
9. Career-change and internship examples
Career changes, internships and employment gaps do not need apologies. Explain the direction you are moving in and show the transferable skills that make the interest credible.
Career changer
“I taught secondary school for eight years and I'm moving into instructional design. The overlap is bigger than it looks — I spent most of my planning time working out why a particular explanation wasn't landing and rebuilding it. This role is corporate compliance training, which people often find dull, and honestly that's part of the appeal: it's a design problem. Over the last year I've completed a certificate and built three sample modules. I'm not going to pretend I know your industry yet, but I know how to find out where learners get stuck.”
Why it works: It states the change plainly, makes the transferable skill specific rather than abstract, shows deliberate preparation and sets an honest boundary on current knowledge.
Internship candidate
“I'm in my third year of civil engineering, and the module I got most out of was water infrastructure — partly because the lecturer kept bringing in real project constraints. Your firm does a lot of municipal water work, which is why I applied here rather than more generally. I've done a group design project on a stormwater scheme, so I've at least seen the shape of the work. What I'd want out of the internship is time on real drawings and an understanding of how the decisions actually get made.”
Why it works: It explains a genuine academic interest, gives a specific reason for this employer, and describes realistic internship expectations rather than overclaiming.
Returning after a career break
“I was out of work for two years caring for a family member, and I've spent the last few months getting current again — refreshing my certification and doing some part-time bookkeeping. I'm looking for a payroll role, and I applied here because you process in-house for around four hundred employees, which is a scale I've worked at before and know well. I ran payroll for a similar-sized organisation for five years before the break. I'd need a short run-in on your software, but the underlying work hasn't changed much.”
Why it works: It addresses the gap in one factual sentence without apology, shows recent steps taken, and matches prior scope directly to the employer's.
10. Role-specific answer examples
The framework holds across fields; the specifics change. These are condensed versions — enough to show the shape without repeating the same structure at full length.
Customer service
“I like the work more than most people expect. The part I'm good at is the second contact — when someone's already annoyed because the first answer didn't fix it. You handle your support in-house and the posting mentions case ownership rather than ticket handoffs, which is the main reason I applied; handoffs are where those cases fall apart. I've been handling escalations for about two years. I'd probably be most useful on the repeat-contact cases early on.”
Why it works: It identifies a specific strength, ties it to a concrete operational detail of the employer, and offers a narrow, believable contribution.
Sales
“You sell a technical product to a technical buyer, and that's the sale I'm best at — I'd rather spend an hour on a specification than on a pitch. My background is in industrial components, so I'm used to a long cycle with several people involved. Last year I carried a territory with about thirty active accounts. What appeals about this role specifically is that reps stay with the account after close, which isn't how my current company does it, and I think it's the better model.”
Why it works: It matches selling style to the actual sale, gives territory scope as evidence, and names a structural preference rather than flattering the company.
Software / technical
“The honest draw is the problem. You're running scheduling for a fleet, and constraint-heavy scheduling is the kind of thing I've spent my own time on — I built a small rota solver for a friend's restaurant that's still in use. Professionally I've been on backend services for four years, mostly payments, so I'm comfortable with systems where being wrong is expensive. I'd want to spend time understanding the existing constraints before suggesting anything, because those are usually there for a reason.”
Why it works: It shows genuine interest in the specific technical problem, backs it with both personal and professional evidence, and signals sensible judgment about legacy systems.
Healthcare
“I've worked in a large hospital system for five years and I'm looking to move to a smaller setting. You run three outpatient clinics, which means a nurse is part of the whole patient pathway rather than one shift of it — that continuity is what I've been missing. I've worked in post-operative care throughout, so I'm used to the follow-up side. I'd expect the first weeks to be about learning your protocols rather than changing anything.”
Why it works: It gives a clear and legitimate reason for the move, names a specific feature of the employer's setup, and shows appropriate professional humility.
Administrative / operations
“I'm good at the invisible work — the processes that only get noticed when they break. This role covers scheduling, supplier coordination and the monthly reporting, which are normally split across three people, and I'd rather hold all three because they affect each other. I've done exactly that combination for a team of about forty. What made me apply here was that you've grown fast recently, and the messy-process stage is the one I actually enjoy.”
Why it works: It frames operational work positively, explains why the combined scope is a draw, and connects the employer's stage of growth to a real preference.
Remote role
“I've worked remotely for three years and I know what makes it work — mostly writing things down properly. What caught my attention in your posting was that the whole team is remote rather than one or two people dialling in, because the hybrid version tends to leave remote staff out of the real conversations. The role itself is content operations, which is what I've been doing, just with a bigger publishing volume than I've handled. I'd want to understand your review process before I touched the workflow.”
Why it works: It treats remote work as a working-style match rather than a perk, distinguishes fully-remote from hybrid credibly, and still leads with the role.
11. Answers that sound weak — and how to improve them
Before the table, an important clarification. Salary, benefits, remote work and career advancement are entirely legitimate reasons to take a job. Anyone who tells you that you should not care about pay is not giving you useful advice. The issue is narrower than that: this particular question is asking about fit with the company and the role, so an answer built only on compensation does not address what was asked. Those topics have their own place in the conversation, usually later and often with the recruiter.
| Weak answer | Why it falls short | Better direction |
|---|---|---|
| “I need a job.” | True for most candidates, so it distinguishes nothing and answers a different question. | Keep the honesty but add the choice: why this job among the ones you could apply for. |
| “The salary is good.” | Pay is a fair priority, but alone it tells the interviewer nothing about the work fit they asked about. | Lead with the role and scope; handle pay as its own conversation later. |
| “I heard you have great benefits.” | Reasonable to value, but it describes the package rather than the job. | Mention something about how the company works, then the responsibility that interests you. |
| “This company is prestigious.” | Focuses on reputation rather than the work, and can suggest the name matters more than the role. | Say what the reputation is built on — the client type, the standard, the craft — and why that suits you. |
| “I want to work from home.” | A legitimate requirement, but on its own it is about the arrangement, not the job. | Frame remote as a working style you are effective in, then move to the role itself. |
| “It seems like an easy job.” | Suggests low investment and often misreads the role, which is rarely as simple as the posting looks. | If you want a sustainable workload, say you are looking for a role you can do well consistently — and mean it. |
| “I just want experience.” | Positions the job as a stepping stone and says nothing about contributing. | Name the specific skill you want to build and what you would give back while building it. |
| “You're an industry leader with a great culture.” | Generic praise that could be pasted into any interview, and unverifiable from outside. | Replace with one specific, accurate observation about the product, customers or structure. |
The common thread: each weak answer is about the candidate's circumstances or about adjectives, and none of them connect to the actual work. The fix is almost always the same — find the sentence in the job description that genuinely interests you and build outward from there.
“Why do you want to work here?” vs. “Why should we hire you?”
WHY DO YOU WANT TO WORK HERE?
Focus: why this company and this role appeal to you. The subject is your motivation and whether it matches the work.
WHY SHOULD WE HIRE YOU?
Focus: why your experience and skills make you a strong choice. The subject is your evidence and the employer's need.
Keep them separate. If your answer here turns into a list of qualifications, you have answered the other question — and you will have nothing new to say when it arrives. See how to answer “Why should we hire you?” and, for the opening question, “Tell me about yourself”.
12. How long your answer should be
There is no universal correct duration, and nobody is timing you. As a practical guide, something in the range of roughly 45 to 90 seconds tends to work conversationally — long enough to be specific, short enough to leave room for a follow-up. Treat that as a rough sense of scale, not a rule.
What matters more is what the answer contains. A good one makes the reason clear, offers enough specificity that it could not be recycled for another employer, includes a line of supporting evidence, and stops before it becomes a monologue. If you find yourself starting a second story, you have gone past the end.
Read the room as well. In a brief phone screen, a tighter answer is usually better. In a longer conversation with a hiring manager who is clearly interested, you can expand — but let them pull the detail out of you with follow-up questions rather than delivering it all unprompted. Finishing and pausing is a strong move; it signals you are having a conversation, not performing. Practising out loud once or twice is the fastest way to discover that your written answer is twice as long as it felt.
13. Final answer checklist
Run through this the day before the interview, not while you are waiting in reception.
- □ I can name a specific reason this employer interests me.
- □ I understand what the role actually involves day to day.
- □ My answer connects the company to the position.
- □ My answer connects the position to my own background.
- □ I include brief evidence rather than generic claims.
- □ Everything I say is truthful.
- □ I don't rely entirely on salary, benefits or location.
- □ I avoid generic praise that could apply to any employer.
- □ I don't repeat my whole résumé.
- □ I say something about what I could contribute.
- □ My answer sounds natural when I say it out loud.
- □ I can deliver it without memorizing every word.
- □ I have checked that any company-specific claim I make is accurate.
- □ I have a shorter version ready if the interviewer seems pressed for time.
There is no answer that guarantees an offer. Hiring decisions involve the whole conversation, the other candidates, the budget and factors you will never see. A specific, honest answer to this question removes a common reason for being ruled out and lets the rest of your interview do its work. That is the realistic goal. Once your answer is ready, spend your remaining preparation time on your examples, your questions for the interviewer and the practical details, including what to wear.
Frequently asked questions
What is the best answer to “Why do you want to work here?”
There is no single best answer. The strongest ones name something specific about the employer or role, connect it to your own experience or direction, and end with a brief note on what you could contribute.
How do I answer if I don't know much about the company?
Spend thirty minutes on the website and the job description before the interview. If your knowledge is still limited, lead honestly with what drew you to the role and name one accurate thing you learned about the company.
Can I say I want the job because of the salary?
Pay is a legitimate reason to want a job, but it does not answer what this question is asking. Lead with the work and handle compensation as its own conversation.
Can I mention remote work?
Yes, especially if you can describe why you work well remotely. Just make sure the arrangement is not the whole answer; follow it with the role itself.
What if I don't have experience?
Use coursework, part-time work, volunteering or personal projects as evidence. Genuine interest in the specific work, plus one concrete example, is enough at entry level.
Should I mention the company's mission?
Only if it genuinely matters to you and you can explain why in your own words. Repeating a mission statement back tends to sound rehearsed.
How long should my answer be?
Roughly 45 to 90 seconds usually works, though there is no fixed rule. Be specific, give one piece of evidence, and stop before it turns into a speech.
How do I answer without sounding fake?
Use reasons that are actually true for you, avoid adjectives about the company, and say it out loud a few times in your own words rather than memorizing a script.
What if this isn't my dream company?
That is normal and you do not need to pretend otherwise. Focus on the role, the type of work and one real observation about the employer.
Is “Why do you want to work here?” the same as “Why should we hire you?”
No. This question is about why the company and role appeal to you; the other is about why your skills make you the right choice. Prepare both separately.
Next: be ready for the pay conversation
Once you can explain why you want the role, prepare for the question that follows it in most processes — what you expect to be paid.
This guide offers general interview guidance; every employer and interviewer is different. All example answers are fictional and any figures in them are illustrative. Browse all career guides or start at FindMySalary. Before you talk numbers, check what salary you should ask for.