You are twenty-two minutes into an application for a job you actually want. Steps one and two took your address history and your notice period. Step three took four paragraphs of original writing: why this employer, a time you handled a difficult stakeholder, what you would do in the first ninety days. Step four asks for referee details. You press Continue and a red banner appears at the top of the page: please correct the errors below. The error is that your phone number needs a country code. You scroll up to fix it, and every free-text box you filled is empty.
That is the whole article. Everything below exists to stop that happening, because the second version of a good paragraph is never as good as the first.
The second attempt is always worse
The first version took eighteen minutes because you were thinking: you tried a sentence, cut it, remembered the specific project, put a number in it. The second takes six minutes because you are furious and want to be finished, and it reads like it. Nobody reconstructs the good version from memory, and the recruiter has no idea they are reading draft two.
The cost of losing the work is not twenty-two minutes. It is twenty-two minutes plus a measurably weaker application.
What the form is actually doing with your text
Systems fall into three rough patterns. Vendors change behaviour between releases and between customers, so treat these as shapes to recognise, not brand names to trust.
The account-based system that saves per step. You created a candidate profile before you could see any questions. Each Continue writes that step to a record attached to your login, so if the browser dies you log back in and the completed steps are there. Note the limit: it saves when you press Continue, not while you type, so everything on the step you are on is unsaved.
The single-page form that saves nothing. One long page, no login, a submit button at the bottom. Nothing exists on the server until you submit. Some of these wrap your text in browser storage, which survives an accidental refresh and nothing else.
The resume-later link. You give an email address early and the system sends a long link that reopens your partial application. Good when it works, and it fails quietly: the email lands in spam, the link expires, or it opens an empty form because the record was tied to a dead session.
The tell: if the employer made you log in before showing you any questions, there is probably a saved record. If you clicked from an ad straight into a form, assume nothing is kept.
Create the candidate account before you write a word
The single highest-value habit in this article, and it costs ninety seconds.
Many systems let you fill in half a form as a guest and only ask you to register at the end. Everything you typed before registering exists only in the page you are looking at. Create the account first, confirm the email, log in, and then start answering. Now every Continue writes to something that survives a dead laptop battery.
Save the login properly the moment you create it. A generated set of credentials your browser stored once and never offered again is an irritating way to lose an application.
The actual answer: compose somewhere else and paste
Do not write original prose inside a browser form. Write it in a notes app or a plain text editor and paste it in.
You get autosave you can rely on, a word count, a spellchecker that is not the browser's, and you still have the text afterwards. Losing the form becomes thirty seconds of pasting rather than a disaster.
The catch is that pasting into a plain textarea breaks things in predictable ways.
- Smart quotes and long dashes. Word processors convert straight quotes into curly ones and double hyphens into long dashes, and some fields render these as question marks or a three-character mess. Run the text through a plain text editor first.
- Bullet characters. A bulleted list pastes either as literal dot characters at the start of each line or as nothing at all, the list flattened into one paragraph. Build lists with hyphens.
- Line breaks collapsing. Many fields strip blank lines. Your three tidy paragraphs arrive as one wall. Check how it looks in the field, not in your document.
- Hidden formatting. Text copied from a word processor or a web page carries style markup that some fields reject outright and others display raw.
- Character limits counted differently than you counted. A field capped at 2000 characters may count spaces and line breaks, may count them differently from your word processor, and may truncate silently on paste. Check the limit before writing, and after pasting, click to the end of the field and confirm your last sentence is there.
Keep one reusable answer file
Roughly eight questions recur across almost every employer: notice period, salary expectation, right to work, relocation, why this employer, a conflict or failure example, interview availability, referee details.
Keep one file with a heading per question and two versions of each answer, a short one around sixty words and a longer one around a hundred and fifty, because field limits vary wildly. Build it once, improve it whenever you write something you like, and stop starting from a blank box at nine in the evening.
One warning that has cost people interviews: when you reuse the why-this-employer answer, change the employer name and read the pasted paragraph out loud before moving on. A paragraph enthusing about a competitor is the fastest rejection available.
Session timeouts, and what actually triggers them
Server-side inactivity clocks are commonly fifteen to thirty minutes. What catches people out is the definition of activity. Typing into a textarea usually does not count, because nothing is being sent anywhere. From the server's point of view, someone who spent twenty-five minutes writing a careful answer looks identical to someone who walked away.
Other session killers: an authentication token expiring on a fixed clock regardless of what you are doing, switching from home wifi to phone tethering mid-form, the laptop sleeping when you shut the lid, and a phone browser discarding a background page to free memory while you check a date in another app.
So press Save Draft or Continue every few minutes, do not leave a half-finished application open overnight, and do the writing offline, which removes the timeout from the equation entirely.
Autofill will overwrite a field you already fixed
Browser autofill and password managers operate on field names, not on your intentions. You corrected your postcode by hand, clicked back into the street field, and autofill re-ran and restored the old stored value in the field you just fixed. You will not notice, because you already checked that field. Separately, a box labelled something like Additional Information sometimes matches an autofill heuristic and quietly receives your street address, which looks absurd on the review screen.
The fix is not glamorous: after you finish the last step, go back and re-read step one. Sixty seconds.
The moment you see a validation error
Before you touch anything, copy your work out.
Do not press back. Do not refresh. Do not click the error message. Go to each free-text box, select all, copy, and paste it into your notes file, box by box. Only then fix the validation error. The error page you are looking at may still hold your text in the browser, while the next page render will not, so once you navigate it is a coin flip.
Two related habits. Do not open the same application in a second browser window, because many systems maintain one active record and the second window can invalidate the first. And if a step has a Save Draft button, press it before Continue. Save Draft usually skips validation, Continue does not, and it is Continue that discards your work.
Copy the whole form before you submit
On the final review screen, take a copy: screenshot the whole thing, or select the page text and save it to a file named after the employer.
Five weeks later in an interview, someone says you indicated you could start in four weeks, and you need to know whether you did. Salary figures get quoted back at offer stage. And next time this employer posts a role, you already have your answers.
The checklist
- Create the candidate account before answering anything.
- Check the character limit of each long field before writing.
- Write every paragraph over forty words outside the browser.
- Strip smart quotes and bullet characters before pasting.
- After pasting, read the text inside the field, not in your document.
- Press Save Draft or Continue every few minutes to keep the session alive.
- Never leave a part-finished form open overnight.
- Re-read step one after finishing the last step, to catch autofill overwrites.
- On a validation error, copy every free-text box out before fixing anything.
- Screenshot the review screen before submitting, and save it under the employer name.
None of this is difficult. It is all compensating for software that decided, some time around 2008, that a person writing four paragraphs was idle. Until that changes, keep your own copy.