To answer "why do you want to work here", say three things in order: what about this company drew you, what about this role fits what you have done, and what you would contribute, with one specific piece of evidence. Three or four sentences is enough. The question shows up in two places, the interview and a text box on the application form, and the second one is more common than most guides admit: when we read 126 public application forms on Greenhouse, Lever and Ashby in October 2026, one in six asked it in writing. Below are the formula, a 15 minute research checklist, ten sample answers and a template for the written version.
Why interviewers ask
The interviewer is checking two things. The first is whether you want this job or any job. Robert Half says employers want to know that new hires are serious about the opportunity and plan to stay, and suggests reframing the question as "Why would this company want to hire me?" The second is whether you understand what the job is. Big Interview's advice, reposted by MIT Sloan's career development office, says the answer gives recruiters "a sense of how you'll perform in the future", and warns that they "can smell a stuffy answer from a mile away."
On a form, the stakes are similar but the reader is earlier in the process. The applicant tracking system Greenhouse explains that some companies filter applicants first on the answers they gave to "custom questions in the application form." A thin answer in that box can end an application before anyone opens the resume.
The three part answer
1. The company. One specific thing that sets it apart for you: a product you use, a problem it works on, a decision it made recently. "Your mission" does not count unless you can say which part of it and why.
2. The role. Which part of the posting matches what you have done or want to do next. Use the posting's own words for the work.
3. The contribution. What you would bring, with one piece of evidence: a project, a result, a number, a skill you have used for real.
A useful test: if you could send the same answer to a competitor by changing the name, part one is not specific enough. If the answer would fit any role at the company, part two is missing.
A 15 minute research checklist
Set a timer. This is enough for a first round interview or a form question. Save the notes, because the same facts feed the cover letter and the questions you ask the interviewer.
| Minutes | Look at | Write down |
|---|---|---|
| 0 to 3 | The posting | The team name, the problem the role exists to solve, the top three requirements in the posting's words |
| 3 to 6 | The product | One thing you used, read or tried yourself, and one thing you noticed about it |
| 6 to 9 | Recent news | One item from the company's blog, newsroom or engineering blog in the last six months |
| 9 to 11 | The team | Who leads it, what they have written or presented, how big it looks |
| 11 to 13 | Values or mission page | One value you can back with something you have done, not just agree with |
| 13 to 15 | Your answer | Three sentences: company, role, contribution |
If you cannot find anything specific in 15 minutes, that is information too. Lead with the role and the contribution, which you can always speak to, and keep the company part short and honest.
Ten sample answers
These are samples written for this post. Every person, company and number is invented. Read them for structure, then write your own from your notes.
1. New grad, large tech company
I've used Larkspur Maps on every trip since college, and when I read your engineering post on cutting tile load times on slow networks, I recognized the problem from my capstone, where I built an offline caching layer for a transit app in Kotlin. This new grad role sits on the mobile performance team, which is the work I most want to do. I'd bring that caching experience and a habit of measuring before I optimize.
2. New grad, startup
I want to be somewhere small enough that what I ship reaches customers in weeks. Fernhill has twelve engineers and two products, and the posting says new hires own a feature in their first month. In my internship I built and shipped a billing settings page end to end in React and Node, so I've done a small version of that. I'd like to do the full version here.
3. International student, focused on the work
Your fraud team's work on real-time transaction scoring is what I studied in my master's thesis, where I compared streaming and batch models on a public card dataset. The posting asks for Python and experience with imbalanced data, which is most of what that project was. I'd bring a researcher's patience with evaluation and a lot of practice explaining model errors to nontechnical people.
Notice what is missing: the visa. Application forms ask about work authorization and sponsorship in their own questions, and that is where to answer honestly. Spend this answer on the work.
4. Career changer
I taught high school chemistry for seven years, and the part I loved was designing labs that made an abstract idea concrete. Brightpath builds exactly that kind of material for adult learners, and this instructional designer role works with subject matter experts, which is what I did with my department every term. I've built eight e-learning modules in Articulate 360 for our district, and I'd like to do that full time.
5. Honest reframe of "I mainly need a job"
Robert Half lists "Honestly, I just need a job, and this one looked interesting" among the answers to avoid. The fix is not to fake passion. It is to say the true thing that makes this job a good fit.
I'm looking for a steady operations role where I can be good at the work from day one, and this one matches what I've done. I ran inventory counts and vendor orders at a grocery store for three years, and your posting is mostly that, at a larger scale. I also live twenty minutes away, so I can be reliable about shifts.
6. Internship
I'm applying because your summer data internship works on the subscriber retention model, and I've spent this semester on a churn project for my statistics course. I'd like to see how a real team handles the parts a class project skips, like messy data and deciding what to ship. I can bring solid SQL and Python and a lot of willingness to do the unglamorous cleaning work.
7. Experienced hire, same industry
I've spent four years building payroll integrations at a competitor, so I know how painful the multi-state tax piece is for customers. Your product is the one our customers kept asking us to integrate with, and this role owns that integration layer. I'd bring the edge cases I've already been burned by, and a working relationship with most of the payroll providers' API teams.
8. Customer-facing role, little experience
I've eaten at Saltmarsh since it opened, and what I notice every time is how the staff remember regulars. That's the kind of place I want to work. I haven't worked in a restaurant yet, but I've spent two years at a busy pharmacy counter, so I'm used to staying friendly and accurate when there's a line.
9. Mission-driven organization
My grandmother's care after her stroke depended on whether the right paperwork got to the right clinic, so the referral coordination problem you work on is personal to me. This analyst role measures where referrals stall, and I've built similar reporting in Excel and Tableau for a regional food bank's delivery routes. I'd like to bring that to a problem I care about this much.
A personal reason works if you keep it to one sentence and spend the rest on the job.
10. When a recruiter contacted you
I wasn't looking until your recruiter reached out, so I did my homework before this call. What changed my mind was the posting's focus on migrating the platform to event-driven services, because I led a similar migration at my current company last year. I'm interested in doing it again with a larger team and learning what I'd do differently.
You can be honest that you were not looking. Then show you did the research anyway.
The written version on application forms
The interview version gets most of the attention, but plenty of employers ask the question before any interview, in a text box on the form. To see how often, on October 18, 2026 we read the application forms of 126 public job postings at 42 employers through each platform's public job board data: 78 on Greenhouse (26 employers), 24 on Lever (8 employers) and 24 on Ashby (8 employers), taking the first, middle and last posting on each board.
| Greenhouse | Lever | Ashby | Total | |
|---|---|---|---|---|
| Postings read | 78 | 24 | 24 | 126 |
| Asked a "why us" or "why this role" question | 9 | 6 | 6 | 21 |
| Employers asking it | 5 of 26 | 3 of 8 | 2 of 8 | 10 of 42 |
| Required when asked | 8 of 9 | 3 of 6 | 6 of 6 | 17 of 21 |
Three things stood out.
It is an employer setting, not a posting quirk. Employers that asked tended to ask on every posting we read. Figma asked on 3 of 3 postings, as did Discord, Wealthfront and ClickUp. If one posting at a company asks, expect the others to.
It is always a free-text box, and the wording varies. Every one was a long text field. The wording ranged from "Why do you want to work at Discord?" to "Why did you decide to apply to this role at ClickUp?" to Datadog's "Tell us why you are interested in building a product management career at Datadog." Some focus on the company and some on the role, so answer the one that is asked.
Length guidance, when given, is short. Figma's forms add "Please share 3-4 sentences on why you want to join Figma." One Match Group form on Lever asks, "In one sentence, tell us why you are interested in this position." Nobody asked for an essay.
This was a small sample of well-known employers, mostly in tech, and not a random one. Read it as a sign of how the question appears, not as a rate for all employers. The Figma, Discord and Datadog forms also ask about work authorization in a question of their own, which is why the visa does not belong in this answer.
A 50 to 150 word template
[Company] stands out to me because [one specific thing from your research]. The [role title] role focuses on [the work, in the posting's words], which is what I did when [one piece of evidence with a result]. I'd bring [one or two skills the posting names that you have] and [one quality backed by the evidence above].
Two samples, written for this post:
Short (one sentence, 31 words)
I'm interested in this backend role because it owns the payments retry logic, and I spent my internship rebuilding a retry queue in Go that cut failed charges by a third.
Full (three sentences, 73 words)
I've used Copperline's budgeting app for two years, and your recent post about moving categorization on device is the kind of privacy decision I want to be part of. This Android role builds those offline features, which is what I did in my capstone, a Kotlin app that syncs local data after long disconnects. I'd bring Jetpack Compose experience, careful testing habits and a real user's opinion of what the app gets right.
A few mechanics for the box:
- Write it in a separate document first. Forms can time out and lose text.
- Change the company name and the specific detail every time. A pasted answer that names the last employer you applied to ends the application.
- Do not write "see cover letter". If the form asks, it wants the answer in the box.
- Plain text only. Bullets and bold usually do not survive the paste. Our guide to filling out a job application covers the rest of the form.
What not to say
- Only pay, benefits or perks. Robert Half lists "I've heard this company offers good pay and benefits" as a weak answer. Pay matters, but it is not a reason to choose this employer over the next one with the same pay.
- "It's a stepping stone." Robert Half also flags "I see this as a step to bigger and better things." Talk about what you want to do here.
- Praise that fits any company. "Innovative", "great culture", "industry leader". If a competitor could receive the same sentence, it is not an answer.
- Things you did not check. If you mention a product launch or a value, get it right. Interviewers notice.
- A rehearsed paragraph. Know your three points, not your exact words. This answer often follows tell me about yourself, and the two should not repeat each other: that one covers your story, this one covers your reasons.
If you apply to many jobs, ApplyEze, which publishes this blog, writes a tailored resume for each posting, plus a cover letter when the form asks for one, and completes applications on 12 platforms, including Greenhouse, Lever and Ashby. Whatever tool you use, write the "why us" answer yourself from your 15 minutes of notes. It is the one part of the application that only you can make specific.
