Most of an application form is machine food: dates, titles, location, work authorization, all of it parsed and filtered without a person involved. Then you reach the bottom of the page and find two or three text boxes containing questions somebody at that company sat down and wrote themselves. Those boxes decide more than everything above them combined, and most candidates type forty tired words into them at 11pm.
Someone reads these, and usually first
The parsed fields get filtered by software. A custom open-text answer cannot be filtered by software in any useful way, so it lands in front of a human being. Normally a recruiter or a hiring coordinator, sometimes the manager who wrote the question, and very often before anyone has opened your CV.
I have watched screeners work a pile of 180 applications. They do not read 180 CVs. They read 180 short answers, sort them into yes, no and maybe, then open the CVs only in the yes stack. At that moment your CV is a confirmation document. The answer is the audition.
Which means the effort ratio most people run is upside down. An hour tuning a CV that gets eight seconds of attention, ninety seconds on the answer that gets read line by line. If you have twenty minutes for an application, spend fifteen of them in the text boxes. The same reasoning applies to the cover letter field when a form offers one, and it is why the rest of the form deserves speed rather than craft.
Five different questions wearing the same costume
The right response depends entirely on which one you are actually facing, and they are not hard to tell apart once you know they are different animals.
The knockout in a text box
"Describe your experience with Workday HCM." "What is your familiarity with IFRS 16?" This is a closed question that somebody could not build as a dropdown. There is a fact being checked, and the reader is scanning for it in the first line.
Lead with the fact. Two administered migrations, four years, current. Then one sentence of texture. If you do not have the thing, say what you have that is adjacent and be quick about it, because vagueness here reads as no. These are the text-box cousins of knockout questions, and they reject just as quietly.
The motivation question
"What interests you about this role?" A sibling of the why-are-you-applying field, and the failure mode is identical: the answer is about the candidate. Growth, challenge, a great team, a chance to learn.
The fix is a sentence that could only be written about them. Their pricing model. A product decision you disagreed with and want to argue about. The fact that they run support inside the engineering org, which is unusual and which you happen to have opinions on. One specific observation beats four paragraphs of enthusiasm.
The scenario question
"Tell us about a time you shipped with incomplete information." They are testing judgment, not heroism. Give the decision, the constraint you were under, and what you traded away. Skip the epilogue where everything worked out and the client was delighted.
The values question
"What does good collaboration look like to you?" The trap is that it looks easy, so people agree with the careers page in slightly different words. Say something narrow enough that a reasonable person could disagree with it. "Decisions get written down, even the ones made in a corridor" is an answer. "Open communication and mutual respect" is a screensaver.
The deliberately odd one
"What is something most people in your field believe that you think is wrong?" These exist to cost mass-appliers time. A company that asks this is filtering for people who slowed down, and the answer barely matters compared with the fact that you clearly wrote it for them. Answer honestly and slightly narrowly. Do not perform quirkiness.
Length, and the shape that goes inside it
100 to 150 words. This holds across almost every custom question I have seen, and it holds for a reason: it is long enough to contain a claim plus proof, short enough to be read in full on a phone between meetings.
Two words reads as contempt. Six hundred words does not get read, it gets skimmed for a reason to stop reading, and skimmers find one.
Inside that budget, three moves in order:
- Answer in the first sentence. Not context, not a windup. The actual answer.
- Evidence in the second and third. One concrete thing you did, with a number attached if a number exists.
- Relevance to them in the last. The bridge from your evidence to their situation.
That order survives being read at speed and half-abandoned, which is how these get read.
The rules that actually decide it
- Answer the question asked, not the one you prepared. This is the most common failure by a distance. The reader wrote that sentence deliberately and notices immediately when you answered a neighbouring question instead.
- Never paste your cover letter in. It answers a different question at the wrong length, and the mismatch is visible in the first line.
- Never leave an optional one blank. The blank is itself an answer here, and it says you were doing volume. Optional in this context means optional in the way that showing up on time is optional.
- Mirror their vocabulary. If the posting says "partners" rather than "clients", say partners. This is not keyword stuffing, it is evidence that you read the thing.
- Draft in a text editor, not in the browser tab, and keep the draft. Sessions expire, and forms lose work. The same discipline that keeps autofill from quietly mangling your application applies here.
Generated answers get caught here before anywhere else
This is worth being blunt about. Recruiters have recalibrated fast, and the custom question is exactly where they look hardest for a generic tell, because the entire design intent of a custom question is that a generic answer cannot satisfy it.
The tells are consistent: an opening that restates the question, praise for the company that would fit any competitor, three balanced items where a human would have given one lopsided one, and a closing sentence about being excited to contribute. Read your own draft and ask whether a candidate applying to a direct competitor could send it with two nouns swapped. If they could, you have written nothing.
Using a model to tighten prose you wrote is fine. Using one to produce the substance defeats the only part of the form that was ever going to help you.
Build the bank once, re-cut it forever
Writing from scratch every time is why these answers are bad. It is 11pm and you are on application seven.
So do it once, properly. Write out three or four real stories from your working life in full: a project you saved, a decision you got wrong, something you built that outlived you, a conflict you handled badly and learned from. Four hundred words each, no audience in mind, just the truth of what happened. That is one evening.
After that, every custom question becomes a re-cut rather than a composition. The scenario question takes story two. The values question takes the conflict. The motivation question takes whichever story is closest to their actual problem, plus a fresh sentence about them. Twenty minutes becomes eight, and the eight are better than the twenty were.
Then protect that time on the other end. Generating a clean CV from your LinkedIn profile is a solved problem, and a tool like Postulit does it in a couple of minutes, which is exactly the kind of time you want to redirect toward the two boxes a person is going to read. Start the bank tonight with one story. The next form you open will already be easier.