How to answer "Why do you want to work here?" in writing

"Why do you want to work here?" looks like a question about them. It is mostly a question about you. Prospects, the UK graduate careers service, puts it plainly: the employer is trying to figure out your motivations and whether you have given serious consideration to your application.^[3] San José State's career advisers add the second half: the reader wants to see how the position fits your career, and that your interest is sincere.^[2]

So the box is a filter for two things. Did you choose this employer, or did you paste? And does this job make sense as your next step?

It is also the question people prepare least. A Harvard Business Review piece on the topic opens by noting that the most obvious questions sometimes get the least attention.^[5] On a written application that shows, because the reader can see a generic answer in a few seconds.

Most guidance is written for interviews, but the structure carries over to a text box. A guide republished by MIT Sloan's Career Development Office breaks the answer into three parts: why this company, why this position, and why you will be successful in the role.^[1] A guide shared by Pomona College's career office uses nearly the same split: why this job, and why this company.^[4]

In writing, that becomes three short moves:

1. One specific thing about the employer. A product you have used, a problem they are working on, something from the posting itself. Specific enough that it could not be pasted into another application.
2. Why this role. What in the day-to-day work you want to do, and how it follows from what you have done.
3. Why you will be good at it. One achievement, with a number if you have one, that matches what the posting asks for. Prospects advises relating your skills directly to those in the job description.^[3]

If the form gives a word or character limit, that is your answer. If it does not, a short paragraph is usually enough: three to six sentences, one for each move above and a line to connect them. There is no rule here, only the reader's patience. Someone reviewing many applications will read a tight paragraph and skim a long one.

Write it in a plain document first, not in the form. Forms time out, and you will want the text again.

You do not need an afternoon. The Pomona-shared guide suggests the company's website, blog, news and case studies, and looking for its values and its short- and long-term objectives.^[4] The MIT-shared guide lists what to look for: the industry focus, the reputation, the values and recent strategic moves.^[1]

A fifteen-minute version you can do today:

• Read the posting twice. Mark the three things it asks for most.
• Read the About page and one recent announcement or blog post.
• Use the product, or read how a customer describes it.
• Write down one detail you did not know before. That detail is your first sentence.

If you cannot find a single thing that interests you, take that seriously. It may be a posting to skip.

The same guide lists the typical mistakes: vague compliments, answers that do not relate to the job, and saying you are only interested in the pay.^[4] On a written form, a few more belong on the list:

• Their own mission statement, repeated back. They wrote it. They know.
• Praise with nothing behind it. "An innovative industry leader" fits every employer, so it says nothing about this one.
• Only what you would get. Remote work, benefits and stability are fair reasons to apply. They are weak reasons to be chosen.
• Another company's name. It happens when answers are pasted. Read it once more before you submit.

Prospects is blunt about the general rule: tailor your responses, and never send generic ones.^[3]

Here is an illustration, written for an imaginary support-engineer posting at a company that makes scheduling software for clinics:

I used your scheduling tool for two years from the other side, as the person at a twelve-doctor practice who called support when it broke. Your team fixed things quickly and explained why. I want to do that work. For the last three years I have handled technical support for a billing product, where I closed about forty tickets a week and wrote the internal guide new hires now start with. The posting asks for someone who can troubleshoot integrations and write clear documentation. That is what I do now, and I would like to do it for a product I already know from the customer's chair.

It names something specific, says why the role, and offers evidence. It also skips enthusiasm words entirely. San José State's advice is to be able to articulate what excites you about the position.^[2] Saying what, exactly, does more than saying how much.

Partly. The third move, your evidence, changes little between similar roles. Keep two or three versions of it and reuse them freely. The first move has to be written fresh each time, because it is the part that proves you looked.

A drafting tool can help with the middle. If something prepares a first version from your resume and the posting, as Final Resume's Prefill does, treat it as a draft: read it, replace the first sentence with your own detail, and check every fact against what you actually did. You are the one who presses Submit, and the one who will be asked about it in the interview.