The Free-Text Application Question Decoder, Prompt by Prompt

You are filling in a job application form, and before the submit button will work you have to write something in one or more open-ended boxes: "Why this company?", "Describe your experience with X", "What is your greatest weakness?", "Anything else we should know?" This guide is for that exact moment. It is a lookup table: jump to the prompt on your screen, see what it screens for, and write an answer that clears the screen inside the box's word limit. It does not treat these as interview questions to rehearse aloud. It treats them as the written gates they are.

Most existing advice answers "why do you want to work here" as something you say in the first or second interview. That is a different problem. The box on the form is scored or filtered before a person ever meets you, and it has a word budget the interview does not. This decoder covers the whole family of written free-text prompts, prompt by prompt.

The form has two graders, and they fail you differently

An application form grades you in two separate systems, and confusing them is the most expensive mistake on the page. One system rejects; the other ranks. A knockout question is a binary eligibility gate, and a disqualifying answer triggers immediate automated rejection with no scoring and no human review. A selling prompt is a competency question that gets scored and used to build a human-reviewed shortlist. Writing eloquently in a knockout box optimizes at the wrong level entirely.

Knockout questions cover work authorization, licenses, certifications, availability, location, willingness to travel, minimum experience, and language proficiency. Their layer is binary and irreversible: no human ever reviews an eliminated candidate. Selling prompts - the free-text boxes this guide is mostly about - are where your writing actually earns a rank.

The practical consequence: read the whole form before you write a single word. If a question could be checked against a minimum requirement and looks enforceable, treat it as potentially knockout and answer it literally. Everything else is a selling prompt, and the rest of this guide is about writing those well.

Prompt decoder: what each box screens for and what clears it

Here is the core lookup. Find the row that matches the prompt in front of you. Column one names the prompt family, column two is what a recruiter is actually screening for, and column three is what a passing answer contains. This is the table to bookmark.

Each row also has a way it lies to you, which is what the failure-modes section covers. For now, read every prompt on your form against column two. The single most common error is answering the prompt you assume is being asked rather than the one being screened for. "Describe your experience with project management" is not an invitation to narrate your career; it is a check against a stated minimum qualification, and the reviewer is looking for the specific competency, described, with how you gained it.

That volume is why these boxes exist. Supplemental questions let a reviewer identify relevant skills without asking in an interview and screen many applicants at once. A scannable, numbered answer survives triage better than prose does, which is the whole reason structure matters more in the box than it does across a desk.

The word budget is the hidden rubric

The box has a limit, and the limit is a rubric in disguise. Recruiting guidance documents supplemental answers at 50 to about 200 words. That ceiling, combined with MIT's STAR weighting, does the math for you: if Action should be about 60% of the answer and Result about 10%, then in a 200-word box roughly 120 words must describe what you personally did and about 20 must state a quantified outcome. The habit of spending 80% of the answer on Situation and Task mechanically starves the two parts being scored.

Platform limits vary widely, and knowing the real ceiling stops you from either rambling or truncating. These come from each platform's own documentation.

The trap in this table is the gap between the stated norm and the technical ceiling. A prompt may say "100 words or less" while the box physically accepts far more, because many boxes do not hard-stop. That soft limit is an invitation to ramble, and rambling costs you against the actual rubric even when the box lets you do it. Count words before you paste.

The word budget is not a constraint on your answer. It is the scoring rubric printed in miniature.

The describe-experience box, weighted to Action and Result

For any "describe your experience with X" box, use STAR and weight it toward what you did and what happened. STAR is a structured framework describing a specific Situation, Task, Action, and Result, and structured behavioural answers are roughly twice as predictive of job performance as unstructured ones, which is precisely the signal a reviewer rates. Handing them a visibly STAR-shaped box hands them the specifics they score on.

The weighting is the whole trick. MIT puts Action at about 60% of the answer and Result at about 10%, with the remaining 30% split between Situation and Task. Most candidates invert this, spending 80% on setup and rushing the Action and Result. In a 150-word box, that inversion leaves fewer than 30 words for the only two parts being evaluated.

Two rules make a describe-experience box pass. First, the Result must carry a number, because an unquantified result looks complete but is not scorable. Second, the Action must be yours, in the first person singular, not the team's. "We shipped" tells the reviewer nothing they can rate; "I rewrote the intake flow and cut drop-off" does.

Situation: When [team] faced [problem], [one line of context].
Task: I was responsible for [the specific outcome I owned].
Action: I [did this], then [did this], and [did this] - the three concrete moves you made, in the first person. This is 60% of the box.
Result: [Metric] improved by [number] over [timeframe], and [one durable consequence].

Because this weighting is the same on every posting but the competency changes each time, the drafting itself is where per-application effort piles up. Refolk writes your resume from your own history and tailors it to each posting, so the STAR raw material - the actions and the numbers - is already assembled and scored against the requirement before you start filling boxes.

The why-us and weakness boxes, decoded

The why-us box screens for one thing: that you researched this specific company and role and are not applying blankly. Hiring managers look for assurance that you are familiar with the company and role. A passing written answer ties one verifiable specific to your own experience, and the test is whether the answer is reusable. If you could paste it into another company's form unchanged, it is flattery, not an answer, and it fails.

Build the specific from what you can verify: the job description, the product page, customer stories, the company profile, or public interviews. One concrete fact, connected to something you have actually done, beats three sentences of admiration.

[Specific fact about the company, product, or role that you verified from a named source] is what pulls me here, because [the thing you have done that connects to it]. I want to [contribute the specific thing] to [the specific team or problem named in the posting].

The greatest-weakness box screens for self-awareness, honesty and integrity, and a growth mindset. Recruiters are looking for two things at once: your weakness, and the steps you are taking to improve it. An answer with only the first half reads as a red flag; an answer with only the second half reads as evasion. Both halves must be present. Pick a real, non-critical weakness - one that is not a core requirement of the job - and pair it with a concrete improvement step you are already taking.

Run the form in order

Work the form in this sequence. It moves from the irreversible gates to the scored boxes to the optional field, so you never waste a good paragraph on a box that only needed a checkbox.

How this goes wrong: eight failure modes

Every prompt in the decoder has a way it lies to you - an answer that looks right and fails anyway. These are the false positives to check against before you submit. This is the section to reread when a box feels done.

1. Treating a knockout as a selling prompt. The tell is a polished paragraph in a work-authorization or relocation box. Check: is the field binary or dropdown and eligibility-worded? If so, a disqualifying answer removes you with no person opening your resume, and prose changes nothing.

2. Front-loading Situation and Task in a describe-experience box. This wastes a 200-word budget on setup. Check: Action plus Result should be about 70% of the words. Spending 80% on setup is the documented common miss.

3. A Result with no number. The answer looks complete but is not scorable. Check: the Result carries a quantified outcome, since it is important to highlight quantifiable results.

4. A weakness with no recovery. A genuinely real weakness stated alone reads as a red flag. Check: both halves are present, because you should not list a weakness without the steps you are taking to improve.

5. A reusable why-us answer. Flattery that would fit any employer. Check: the answer is specific enough that you could not reuse it at another company.

6. Guessing on a changing eligibility fact. Incorrect or incomplete entries on authorization, licensing, or availability can trigger automatic screening outcomes. Check: confirm the current fact rather than assuming last year's answer still holds.

7. Assuming the box hard-stops. A soft limit invites rambling. Check: count your words before pasting, because the box may accept more than the stated limit.

8. Over-writing the optional box. Padding the additional-information field with a resume restatement. Check: fill it only to add new evidence or explain an edge case; otherwise leave it blank.

Who reads your boxes, and where they sit

The people scoring these boxes are recruiters and technical recruiters, and their concentration tells you how standardized this screening is. In Refolk's index of professional profiles, there are 109,785 recruiters and technical recruiters in the United States and 6,978 in the United Kingdom.

The US recruiter pool is about 15.7 times the UK pool, which means the free-text box in front of you was almost certainly designed and rated by someone whose whole job is triaging supplemental answers at volume. That is an argument for structure, not eloquence. The reviewer is fast, and a STAR-shaped box with a number in the Result is built to be read fast.

If you want to see who actually reads these forms in a sector you are targeting, that is a people search, and it is a different kind of task from writing the box.

Verify before you submit

Run this checklist against the form before you click submit. It catches the failures that pass a casual read.

Keeping this current

The prompt families in the decoder are stable, but two things drift, so re-check them per application rather than trusting a saved answer. First, eligibility facts change: your work authorization, license status, or availability may not match last year's answer, and a stale entry in a knockout box auto-rejects you. Confirm the current fact each time. Second, the word limit is set by the specific form, and the technical ceiling often differs from the stated one. Read the limit on the box in front of you and count against it, because a box that says "100 words" while accepting 500 will not warn you when you overrun the rubric.

The deeper thing to keep current is your raw material. The STAR content - your actions and their quantified results - is what every describe-experience box draws on, and it is the same across postings even though the competency asked for changes. Keep that inventory of actions and numbers fresh, and each form becomes a matter of selecting and trimming rather than writing from scratch. Refolk tailors your materials to each posting and scores how well you fit, which turns the box-filling from a blank-page problem into an editing one.