Why do you want to work here generator, by Resume Worded★4.9 on Trustpilot · 5M+ job seekers
Why do you want to work here? A reason only you can give.
Interviewers ask this to find out whether you chose them or they are one of forty open tabs, because motivation predicts how fast you ramp and how long you stay. The answer is built from research, not enthusiasm: one specific thing you found, the product, a recent move, the team, connected honestly to where you want your career to go.
Name the company, pick what genuinely draws you, and paste the specifics from your research. You get a spoken answer in three beats: the draw, the honest connection to your own direction, and where it goes from here. Sized to 45 to 60 seconds. Your first drafts are free.
Why do you want to work here generator
Run the swap test on the first beat: put a competitor's name where theirs is. If the sentence still works, your specifics are not specific enough yet; regenerate with a sharper finding.
The marked beat should read like an admission about you, not a compliment about them. You are explaining what you want next, and that is the part no research can fake.
Interview answers come from knowing your own story.
The research half of this answer takes twenty minutes. The direction half, where you actually want to go, is the part most people have never mapped. Coached, our career coaching platform, builds you a free career read from just your LinkedIn: what you are good at, what you value, and where those two things point.
What you are good atWhat you valueWhere those two point
Get your free career read, from just your LinkedIn. It takes a few minutes, and the read is yours to keep.
Answer with one specific thing you found in your research, the product, a recent move, or the team, connected honestly to the direction you want your career to take. The test for every sentence: if it would still be true with a competitor's name swapped in, it is flattery, not an answer yet.
The research takes about twenty minutes, and it looks in three places. Most candidates look in none of them, which is why a single specific finding immediately separates you: the interviewer hears their actual company in your answer instead of a template with their name pasted in.
The 20 minute research method. Three places to look, one line to keep.
The product: twenty minutes of actually using it
If the product is something you can touch, touch it: sign up, run the core flow, and write down one thing done well and one opinionated choice. "Your CSV importer handles messy files cleanly" is worth more than a paragraph of admiration, because only someone who used the product could say it. If the product is enterprise software you cannot reach, the docs and case studies tell you what it does and who it is for, which is enough.
Recent moves: why this company, right now
Read the last two or three announcements: launches, expansions, a new market, a leadership change. A recent move turns your answer from timeless flattery into a timely observation, because it lets you say why now: "you just expanded from two cities to eleven, and growth like that breaks onboarding first, which is the work I do."
The team: why this seat
The posting itself is research; it tells you what the team owns and what problem created the vacancy. Add a look at who you would work with, and the team's engineering or design blog if one exists. This is where the answer gets its landing: not just why the company, but why this specific chair inside it.
The failure mode
The flattery trap
Compliments are not motives. "You're an industry leader with a great culture" teaches the interviewer exactly one thing: that you did no research, because that sentence works for any company in any industry. There is a mirror version of the same failure, reciting the company's About page back at them, which proves research happened but still says nothing about you. Research is the ingredient. The connection to your own direction is the answer.
The swap test, applied. If a competitor's name fits your sentence, the sentence is not done.
Money, commute, and remote policy fail the same test from a different side: they are real reasons, but they are true of every job at that pay and location, so they distinguish nothing. The interviewer is not asking what you would receive; they are asking what you would do here that you could not do elsewhere, and why that matters to you.
Interactive, try it here
Run the swap test on your own draft
Paste your opening sentence and the company's name. We swap the name for a competitor's and show you the result; your ear does the rest. It runs entirely in your browser, and nothing you type leaves this page.
The swap test
Proof of quality
Why do you want to work here: example answers
Three answers in this generator's format, inputs included, one per kind of draw. The companies are invented; the mechanics are not. Notice that every draw is checkable, every connection is an admission about the candidate, and none of it would survive the swap test with another company's name.
Inputs: Streamline Data · draw: the product itself · specifics: used the free tier for 2 years, the CSV importer handles messy files better than anything else, EU data residency launched in March · connection: I own the ingestion layer at my current company, three years on messy data onboarding, want enterprise scale next · role: Senior Data Engineer
The drawI've used Streamline on the free tier for about two years, and the honest answer is that your CSV importer is the reason I applied. Every tool in this space claims to handle messy files; yours actually does, and that kind of unglamorous correctness says a lot about how the team decides what matters.
The connectionMessy data onboarding is the problem I've spent the last three years on. I own the ingestion layer at my current company, and most of my real wins have been in the ugly edge cases, so I notice who else takes them seriously.
The directionYour EU data residency launch in March says you're going after enterprise data teams, and that is the scale I want next. I want to work on ingestion where the edge cases number in the millions, and here that's the core product rather than a side effect.
Inputs: Harbor Health · draw: a recent move · specifics: expanded from 2 cities to 11 last year, the posting says this is their first dedicated onboarding role · connection: I was the first onboarding hire at my current company after a similar jump, turned an improvised checklist into a process new staff run without me · role: Customer Onboarding Specialist
The drawWhat caught my attention is the expansion: two cities to eleven in a year. Growth like that usually breaks onboarding first, and the fact that you're creating a dedicated onboarding role right now tells me you already know it.
The connectionI've done this exact stage before. I was the first onboarding hire at my current company after a similar jump, and I turned an improvised checklist into a process new staff could run without me. Building the playbook is the part of the job I like most, which is why I want the stage where it doesn't exist yet.
The directionA first-of-its-kind role in a company growing this fast is where that skill compounds. I want my next few years to be building systems that outlast me, and this seat is that job on day one.
Inputs: Fieldnote · draw: the craft bar · specifics: their April design blog post on rebuilding the offline sync UI included the two approaches that failed; designers there run their own field research · connection: I do my best work on utility software, ran about 40 field visits last year for one redesign, want to go deeper into research-led design · role: Product Designer
The drawYour design team's April post on rebuilding the offline sync UI is the most honest design writing I've read this year, because it included the two approaches that failed. Teams don't publish their dead ends unless the internal bar is real.
The connectionI do my best work on utility software, the kind people use in a warehouse or a truck rather than at a desk, and I already work the way your team does: I ran about forty field visits last year for a single redesign, because I don't trust my screens until I've watched someone struggle with them.
The directionDesigners running their own field research is something most companies claim and your blog actually proves. I want the next stretch of my career to go deeper into exactly that kind of work, and I'd rather do it where it's the operating model than keep negotiating for it.
Frequently asked questions
How do you answer why do you want to work here?
With one specific thing you found in your research, connected honestly to your own direction. Spend twenty minutes in three places: the product (use it, note one thing done well), recent moves (the last two or three announcements), and the team (what the posting says this seat owns). Then say what you found, why it connects to the work you want to do next, and what you would do in the role.
What is a good example answer for why do you want to work here?
A working skeleton: "You did X recently, which tells me you're going after Y. That's the problem I've spent my last few years on, and this role owns exactly that work." The specifics carry it. "You expanded from two cities to eleven last year, and growth like that breaks onboarding first; building that playbook is the work I do" is a complete answer in two sentences.
What should you not say when asked why do you want to work here?
Anything a competitor's name would survive: generic praise about culture, leadership, or innovation. Anything about what you would receive rather than do: salary, commute, remote policy, benefits. And do not recite the company's About page back at them; that proves research happened but says nothing about you. Every failing answer shares one root: it contains no information about either the company or you.
How do you answer why do you want to work here if you do not know much about the company?
Do the twenty minutes before the interview; that is the honest fix, and the method is simple: use the product if you can, read the last two or three announcements, and reread the posting for what the team owns. If you do all of that and still cannot find one thing that genuinely draws you, treat that as real information about whether to invest an interview loop in this company at all.
Is it OK to mention salary or benefits as a reason?
Not as the answer to this question. Everyone works for pay, so pay distinguishes nothing about you and this company, and the interviewer knows compensation matters without being told. Salary belongs in the offer conversation, where it has real standing. This question is asking what you would do here that you could not do elsewhere, and why that matters to you specifically.
Why do interviewers ask why do you want to work here?
Because motivation predicts behavior they cannot test any other way: how fast you ramp, how you handle the rough quarters, and whether you stay. A candidate who chose the company deliberately interviews differently from one running a mail merge, and this question separates them in under a minute. It also checks judgment: what you chose to notice about them says something about how you evaluate.
The half of the answer research cannot supply
The specifics take twenty minutes. The direction, what you actually want your next years of work to be, is the half most people have never sat down and mapped, which is why their answers to this question sound borrowed. Coached, our career coaching platform, builds your free career read from just your LinkedIn: what you are good at, what you value, and where those two things point.
