Why ApplyBot stops before Submit

Quick answer: ApplyBot will never click Submit for you. It gets an application ready and stops. You open it, read it, and send it yourself. That's not a missing feature — it's a decision.

Adding a real "auto-submit" button would have taken us about an afternoon. The hard part — finding the job, filling in the form — was already done. The button was right there. We just didn't press it, and we want to explain why, because "just apply for me" is a completely reasonable thing to want.

The reason comes down to what happens when something goes wrong.

If the tool stops one step early, you lose maybe fifteen seconds reading it over before you send it. If it sends something it shouldn't have, that mistake has your name on it, permanently: a resume that oversold you, sitting in a company's system forever, or forty applications gone out to jobs you'd never have chosen, from an email address a recruiter now recognizes. There's no taking that back.

Fifteen seconds against that isn't a close call. So there is no setting, anywhere, that lets ApplyBot send an application on its own. It gets everything ready, and finishing the job — opening the real form and clicking the real Submit button — is something only you can do.

What actually keeps it honest

That last step is the most visible guardrail, but it's not the only one. A few plain rules do most of the work underneath it.

It can't invent your experience. It only ever writes with facts you've confirmed yourself — the roles you held, what you actually did, the numbers you can back up. Once it finishes writing, we check the result against those same facts one more time before you ever see it, specifically to catch anything that quietly got oversold along the way. A verb like "led" sneaking in where it should say "contributed to" is the real risk here, not fabricated jobs.

It only works with two application systems. Right now, that's Greenhouse and Lever, which between them cover a big share of the postings you'll actually find. It doesn't touch sites that make you create an account first, or LinkedIn's own one-click apply. That's on purpose — those systems need things (like stored passwords) that we'd rather just not deal with, for your sake as much as ours.

It never gets to see more of your data than it needs. When it has to fill in a field it doesn't recognize, it's told what the field is asking for — not shown any of your actual information. Most fields never even reach that point; they're filled straight from your profile automatically.

It gives up when something's wrong. If it fails three times in a row on the same kind of task, it pauses itself and waits for you to look at it. There's also a daily cap on how much it can do, so a bad night doesn't turn into sixty applications you now have to clean up.

What this actually costs you

Being honest about the trade-off: you're still very much in the loop. This isn't "wake up to twelve applications sent." It's "wake up to twelve applications written and ready" — which is most of the effort, but not the final word. If what you actually wanted was the first one, this isn't the right tool for you, and better you know that now than after paying for it.

What you get instead is simple: nothing with your name on it ever leaves without you reading it first. For a document whose entire job is representing you to a stranger, that seems like the right place to keep a person in charge.