Most application forms carry more boxes than the job needs. Past the CV upload and the work history, the red asterisks stop and a long tail begins: cover letter, portfolio link, salary expectations, a demographic section, a free-text box marked additional information. "Optional" there is a user interface label. It tells you what the software will accept before it lets you press submit, and absolutely nothing about who reads the field afterwards.
That gap is where people lose time and, occasionally, jobs. Some optional fields are genuinely filler and skipping them costs you nothing. Some are optional on the label and scored in practice. And a few are optional because the law says they have to be, and your answer is nobody's business. Sorting a form into those three piles takes about twenty seconds and changes how you spend the next twenty minutes.
What a blank field looks like on the recruiter's side
When a recruiter opens your application, they are not looking at the form you filled in. They see a candidate record: fields stacked in a fixed order, usually with the parsed CV pinned to the top of the panel. An unanswered optional field renders as an empty row, or does not render at all. No alert fires. Nobody is told you skipped it.
Two exceptions matter. Some configurations mark an application as incomplete when specific fields are blank, which puts a status flag on your record that a coordinator can act on before a human reads a word of your experience. And many teams build their shortlist view around chosen columns. If the hiring manager's screen shows name, location, notice period, salary expectation and cover letter, your blank is a visible hole in a column, sitting beside eleven people who typed something. Identical data, completely different presentation.
You cannot see which setup you have landed in. What you can do is judge by field type, which is what the buckets below do.
Bucket one: skip these, nothing happens
These fields exist for the company's internal reporting or because the form template shipped with them. They do not feed a score, and a blank one is invisible.
- How did you hear about us. Marketing attribution. Fill it if there's a referral to name, otherwise leave it.
- Preferred pronouns, preferred name, honorific. Fill these if you want them used. There is no penalty either way.
- Secondary phone number, second address line, fax. Yes, some forms still have a fax field.
- Social profiles you don't maintain. An abandoned account with four posts from 2019 is worse than no link. This is different from a portfolio, which is bucket two.
- Willing to relocate, when you already live in the city. Redundant with the address you gave three screens earlier.
- "Anything else we should know" appearing twice. Some forms repeat the free-text box on two pages. One answer is plenty.
The completion-percentage meter belongs here too. That bar is a form-design nudge, an interface trick to keep you going, and its value is almost never carried into the recruiter's view. A record at 78 percent with a strong CV and a sharp cover letter beats a 100 percent record with nothing worth reading in it. Do not chase the bar.
Bucket two: labelled optional, scored in practice
This is the bucket that decides outcomes, and it has a small number of members.
The cover letter box
If there is one argument in this article, it's this one: the optional cover-letter field is the highest-leverage box on any application form, and most people leave it empty. That is exactly what makes it worth filling.
On a competitive role the recruiter is working a list of eighty near-identical records. Three or four of them have something written in that box. Those three get read as people rather than parsed fields, and they get read first, because a human wrote something and a human wants to see what it says. You do not need a page. Six sentences that name the role, connect two things from your CV to two things in the posting, and say why this employer specifically, will out-perform 90 percent of what lands in that field.
The trap is the generic letter. A paragraph that would fit any company at any time is worse than a blank, because it tells the reader you applied in bulk. If you cannot write something specific in six minutes, skip it and spend those minutes on a different application.
The "why this company" field
Same logic, tighter format. Usually a 500-character box, which is roughly four sentences. It is almost always read when it contains text, because it is short and it sits high on the record. Name something real: a product, a market they just entered, the way the team is structured. Anything you could copy into a competitor's form fails.
Portfolio, GitHub, personal site
Optional in the form, mandatory in practice for design, front-end, data, writing and anything creative. A reviewer who cannot see work will assume there isn't any worth seeing. If what you have is thin, link the one thing you're proud of rather than a profile page with nothing on it.
Salary expectations when it appears without an asterisk
An optional salary field is a real choice, and it has been covered here before, so briefly: leaving it blank is safe on a role where you genuinely don't know the band, and costs you nothing at screening stage. It occasionally costs you a callback where the coordinator needs it to route the application. Treat it the way you treat the notice-period and knockout questions further up the form: answer if you have a number you're comfortable defending, otherwise leave it and expect the question by phone.
Bucket three: optional because the law made it optional
Equal-opportunity and demographic sections, ethnicity, gender, disability status, veteran status, sometimes age band. These are optional by statute in most places, they are separated from the hiring record by design, and they are aggregated for reporting rather than read against your name. "Prefer not to say" is a complete answer and carries no penalty. Skip the whole block if you want to. That is what the option is for.
Anything outside that block asking for the same data is a different matter, and a bad sign about the employer.
The additional information box and its one good use
This field is where applications go to get worse. It invites you to restate your CV in prose, and a reviewer who has already read your CV will skim it and move on.
It has exactly one strong use: answering the question the form did not ask. A gap that needs a one-line explanation. A visa status that is better stated than assumed. A job title that undersells what you actually did. An availability date that differs from what the dropdown allowed. Two sentences, factual, no apology. If you do not have one of those, leave it blank.
The rule for every optional field: fill it when it contains information the recruiter cannot get from your CV, skip it when it does not.
The time budget
Here is the practical case for skipping. A thorough application takes between fifteen and forty minutes, most of it in the fields that actually matter. If you fill every optional box on every form, you will manage maybe eight applications in an evening, and half of them will be padded with text nobody reads.
Cut the bucket-one fields and you buy back real time. Put that time into the cover-letter box on the four roles you genuinely want. Ten applications where the optional writing fields are specific will produce more interviews than thirty where they are all filled in generically. This is also why tools that pre-fill the structured parts are worth it. A LinkedIn-to-CV tool like Postulit handles the parsing and the repetitive fields so your attention lands on the boxes that need a person.
Next form you open, do the twenty-second triage before you type anything. Scroll to the bottom, find the optional fields, and mark each one: filler, scored, or none of their business. Then write properly in the two or three that scored, and submit at 74 percent without a second thought.