Why auto-apply tools get application forms wrong

Read the reviews of any job auto-apply tool and the same complaints come up: fields left empty, the wrong option picked from a dropdown, applications reported as sent that never arrived. It is tempting to read that as laziness. Mostly it isn't. Application forms are genuinely hostile to automation, in ways that are not obvious until you have pointed a filler at a few thousand of them.

A form field is not a form field

The naive approach — find the input, set its value — fails immediately on modern forms. React and Vue components don't notice a value set directly; the visible text changes and the app's own state doesn't, so the form submits empty. Dropdowns are usually not dropdowns at all but a styled list of divs with a hidden input beside them. Design systems hide the real radio button and paint a prettier one on top.

One specific trap: several component libraries keep a second, invisible input next to the real one purely so the browser will show a 'please fill this field' message. Fill that one and nothing happens, and every question appears to be two questions. Any filler that doesn't know to skip see-through elements will double-count and mis-answer its way through the entire form.

The bug that taught us to look twice

Our own worst example. On Greenhouse, we filled the applicant's details first and uploaded the resume last, which is the order a person would use. Greenhouse reads the uploaded file and redraws the contact fields from what it finds inside. First name, last name, everything typed before the upload — wiped, a second later.

The filler had already moved on and reported success. It never looked back at the field. Every Greenhouse application we sent went out, or stopped for review, with fields we believed we had filled and hadn't.

The fix was two lines of ordering and one of verification: upload the resume first, then fill, then read a text field back before claiming it worked.

That last part is the general lesson. A filler that writes a value and assumes it stuck will be wrong on any form that reacts to what you give it — and the good ones all react.

The questions nobody can guess

Name, email and phone are the easy part. The questions that decide whether an application is any good are the ones written by the company: why this role, what is your notice period, describe a time you disagreed with a manager. A tool has three options — leave it blank, invent something, or ask you.

Leaving it blank fails required fields. Inventing is worse: it puts claims in your name that you may have to defend in an interview, or that are simply false. The only defensible answer is to draft from facts the person actually gave you, and to stop and ask when there is nothing to draft from. That is slower and it is the difference between an application and a form submission.

Why 'applications sent' is the wrong number

Sending is easy to count and easy to inflate. Whether the form was complete, whether the answers were right, whether it arrived — that is harder, so most tools don't report it. Ask instead: does it show you every answer before it goes? Does it keep proof of what was submitted? Does it tell you when it was unsure?

A tool that can't answer those isn't necessarily lying to you. It just doesn't know either.