"Why do you want to work here?" on an application form

Short answer: four sentences - what this company does, what this role is, what you have already done that maps onto it, what you want next. And here is the part nobody mentions: in both Greenhouse and Workday, that box cannot reject you by itself. No rule reads it. No score comes out of it. A person does, later, with forty other answers open in the same window.

So the box is not a filter. It is the only field on the form where you get to write a sentence rather than pick one, which is the only reason your application can stop looking like everyone else's.

What the box is actually checking

The wording moves around, but the field is doing one of a very small number of jobs.

In Greenhouse, all of these are the same object: a custom application question attached to the job post. The answers land where you would expect - Greenhouse's help pages put a candidate's responses in the Application section of the candidate's profile - and a recruiter can pull every answer for a single job post into a spreadsheet, which arrives by email as an .xlsx file. Picture your paragraph as a cell in a column, because that is the shape it is read in.

That export is deliberately narrow: it runs one job post at a time, filtered to the post you choose. Which tells you something about the reading. Nobody is comparing your answer to the one you wrote for a different company last Tuesday; they are comparing it to the forty other people who applied to this requisition, in one sitting, in one file. The bar is not "is this a good paragraph." The bar is whether yours is one of the four or five in that column that clearly refer to this job.

What sits on top of those questions is the interesting part. Greenhouse calls them application rules: "automatic actions applied to job post questions," triggered when an applicant's response fulfills the rule's conditions. There are three - Auto-Tag, Auto-Advance and Auto-Reject. Auto-Reject is the one that ends applications on submission, and Greenhouse states which question types it can be built on: Yes/No, Single-select, Multi-select. Auto-Advance names the same three.

Workday reaches the same place from a different direction. A Workday questionnaire supports five question types - Date, Multiple choice, Number, Text and Upload attachment - and scoring attaches to exactly one of them. "You can add a score for each possible answer for multiple choice questions in the questionnaire," after which "Workday calculates the total score for a completed questionnaire." A Text answer carries no score, so it contributes nothing to that total.

What each system can do with a free-text answer

Greenhouse application rules and Workday questionnaire scoring both operate on choice-based questions. The free-text box is stored and read, never matched.

	Greenhouse	Workday
Free-text answer type exists	Yes - a custom application question	Yes - Text, one of five question types
Can auto-reject you on its own	No - rules run on Yes/No, Single-select, Multi-select	No - no score attaches to a Text answer
Can auto-advance you to a later stage	No - same three question types	-
Carries a numeric score	-	Only multiple choice; Workday totals the questionnaire
Feeds branching follow-up questions	-	Only multiple choice, single select - up to six levels
How many questions can sit around it	-	No more than 50 per questionnaire, excluding branching

Every other field on that form is a switch. This one is a note.

Can a bad answer get you auto-rejected?

No. Greenhouse's auto-reject rules can only be configured on Yes/No, Single-select and Multi-select questions, and Workday's scoring only attaches to multiple choice answers, so neither system has anything to match a paragraph against. The rejection this box produces is human, slower, and arrives after someone has read your four sentences next to somebody else's four sentences.

The four sentences that earn the box

There is a shape that works, and it is not a cover letter compressed into a smaller space. A cover letter argues. This answers.

The four-sentence answer

One sentence each. Past about 100 words you have written a cover letter nobody asked for.

1. 1
   What this company does

   Name the product, the market, or the customer - something you could only know from reading the site. Not the mission statement, which is on every site.

2. 2
   What this role is

   Name the part of the job that is actually the job. The posting tells you; most applicants answer the title instead.

3. 3
   What you have done that maps

   One prior responsibility that lines up with sentence two. A number if you have one, no number if you would have to invent it.

4. 4
   What you want next

   The thing this role gives you that your current one does not. This is the sentence that makes the answer specific to this posting rather than to this industry.

Take a Retail Manager applying to a two-store hardware chain. O*NET lists the first task of a First-Line Supervisor of Retail Sales Workers as to "Provide customer service by greeting and assisting customers and responding to customer inquiries and complaints," and the second as to "Direct and supervise employees engaged in sales, inventory-taking, reconciling cash receipts, or in performing services for customers." Those are two fairly different jobs living under one title, and any given posting leans one way. Work out which, then write to it:

Your Riverside store is the only place in the county carrying contractor accounts alongside walk-in trade, which makes it a scheduling problem more than a selling one. I have run a 14-person floor team across a seven-day roster for three years, including the inventory count and the cash reconciliation. What I have done least of is contractor account management, and that is the reason I am applying here rather than to another big-box floor. I would rather run a store where the regulars have names.

Four sentences. One of them admits a gap, which is a large part of why the other three are believable.

The same box, for a Software Engineer

Specificity is harder in software, because the titles are identical everywhere and the businesses underneath them are not. The Bureau of Labor Statistics counted 1,717,800 software developers in 2025 and projects the occupation growing 10 percent through 2035, adding 174,700 jobs on the 2025–35 projections. More than 1.7 million people share one job title. Not one of them is distinguishable from another by the title alone, which is exactly the problem this box exists to solve.

The Bureau also puts the median annual wage for software developers at $135,980 as of May 2025 - and inside that same figure, the median in software publishing is $164,550 while the median in computer systems design and related services is $132,050. Those are not one employer wearing two hats. They are different products, different customers, different reasons the code is hard. "I want to work in tech" tells a recruiter you have not yet noticed which of them you are applying to.

You sell scheduling software to independent pharmacies, so the hard part is integrating with systems the customer did not choose and cannot replace. I spent the last two years on billing integrations - six vendor APIs, four of them undocumented - which is why I know how much of this job is reading someone else's error codes at 11pm. I have never built for a customer who is also the person paying, and I would like to. If that is what this role is, I am interested in it specifically.

How long should the answer be?

Sixty to a hundred words. Neither Greenhouse nor Workday publishes a character maximum on the free-text answer type, and that gap is worth naming rather than filling with a guess: vendor documentation describes what a field can hold, not what a recruiter will read, and those are different limits. What the documentation does tell you is how crowded the form around it is. Workday caps a questionnaire at 50 questions, excluding branching ones; a requisition can carry one primary and one secondary questionnaire for career sites; and each initial answer choice on a multiple choice, single-select question can hang up to six levels of follow-ups underneath it. Your paragraph may well be question 31 of 50.

There is a physical tell, too. If the box renders two lines tall, it was built for two lines; if it renders as a half-page textarea, somebody is expecting a paragraph.

If the form asks for a cover letter as well

Then the box is not a summary of the letter, and writing it as one is the most common way people waste both.

On a Greenhouse job post these are two separate custom application questions, and they are stored differently. The letter arrives as a file - Greenhouse's Attachment answer type accepts candidate uploads up to a file size of 500 MB, which no cover letter has ever come close to and which tells you the field was built to hold anything rather than to be read closely. The box is text typed into the form, and it sits in the Application section of your profile next to every other answer you gave.

So divide the material rather than duplicating it. The Software Engineer above should put the billing-integration work in the letter, where there is room for what broke and what it cost, and keep the box for the two sentences about pharmacies and about wanting a customer who pays. The Retail Manager should let the letter carry the roster and the shrink numbers, and use the box for the contractor-accounts sentence. If you can paste your first paragraph of the letter into the box and lose nothing, one of them is not doing any work.

If you have no real reason to want this company

Then give the role-level reason instead of the company-level one, and stop trying to manufacture affection. This is the most common situation on any application form and the usual advice for it is useless.

A Retail Manager applying to whichever chain is hiring within a commutable distance has a genuine answer available: the format of the store, the size of the team, the shift pattern, the product category they already know. O*NET puts median pay for that occupation at $48,520 a year, or $23.33 an hour, in 2025, against employment of 1,432,600 in 2024 and a projected decline of one percent or lower through 2034 on the 2024–34 projections. In an occupation that is not growing, "I want to run a floor this size, in this category" is a real preference and not a polite one. It is how people actually choose between two nearly identical jobs, and a recruiter who has hired for the role knows it.

What does not work is the sentence about the company's values that would survive a find-and-replace of the company name. Recruiters read this field in a spreadsheet column, forty rows at a time. In that view, interchangeable answers are visibly interchangeable.

If the same box shows up on twenty forms

It will. There is a great deal of hiring going on underneath the vacancy numbers.

The volume behind the form, July 2026

7.3MJob openings, last business day of July 2026

5.1MHires during July 2026

Seven point three million openings and five point one million hires in a single month, per the BLS release of 1 September 2026. Whatever share of those postings sit behind a form carrying this box, you are not writing the answer once, and the figures do not tell you that share - no public series counts how many applications include a free-text screening question, or how many of those answers a human opens.

So build a chassis. Sentences three and four - what you have done, what you want next - barely move between applications in the same field, and you should write them properly once and then leave them alone. Sentences one and two change every time, because they are the only two that name this company and this role. That split is also the honest explanation for why a generic answer reads as generic: half the paragraph was always going to be reusable, and the applicant reused the wrong half.

For the fields that genuinely repeat - the dropdowns, the address, the work authorization question, the previous employer dates - the platform answers the screening questions from your resume, which leaves the text box as the one thing on the form still worth your own attention.

The one thing to get right

Write sentence two before sentence one. Naming the company is easy and proves nothing; naming the part of the job that is actually the job proves you read the posting, and it is the sentence a recruiter uses to sort your answer from the one above it in the column. If you cannot write that sentence about a role, you have learned something useful before you spent an hour on the rest of the form.