AI job applications on Ashby: what it takes to auto apply
Ashby is an applicant tracking system, and it is one of the harder ATS platforms for an AI job application tool to fill correctly. The form looks simple, but it saves your answers as you go, uses button toggles instead of ordinary checkboxes, sets up its location field differently on every posting, and filters out most automated traffic that comes from datacenters. This guide explains what an Ashby application actually needs, how Reach handles each part, and where it still hands the application back to you. It is written by the Reach team, so we have stuck to behavior we have measured in production and named the limits plainly.
Why Ashby is hard for automation
Every answer is saved to the server as you fill. On most application forms nothing is recorded until you press Submit, so a tool can fill, check and correct fields freely. Ashby is different: each interaction is written to Ashby's server the moment it happens, and what the server has accumulated is the application. A filler that clicks a field twice, or clicks one option and then another to "settle" it, is not tidying up a page; it is sending extra answers that race each other.
Yes/no questions are toggle buttons. Ashby renders many screening questions as a pair of Yes and No buttons rather than a radio button or checkbox. Clicking the button that is already chosen unselects it. So a tool has to click each toggle exactly once, and not at all when the right answer is already selected. A generic filler that clicks to be safe can submit the opposite of what it meant.
The location field is configured per posting. One employer asks for a city, another only a country, and the field only accepts what its suggestion list offers. A tool that types a full street address or a city into a country-only field gets nothing accepted.
There is a resume-first autofill slot. Ashby offers a slot that reads an uploaded resume and fills the form from it. It sits alongside the ordinary fields, and a filler has to recognize it for what it is rather than treat it as one more upload box.
Bot filtering walls datacenter traffic. Ashby filters automated traffic, and most automation running from datacenter servers gets walled. This is why datacenter automation struggles on Ashby, regardless of how well it fills the form.
What an Ashby application needs, and how Reach handles it
| What an Ashby application needs | How Reach handles it |
|---|---|
| Answers saved one interaction at a time | The filler clicks each control exactly once and never "re-sets" a field by clicking through other options first |
| Yes/no toggle buttons | Modeled as Ashby's own button pair: an option already chosen is left alone, an unchosen one is clicked once |
| Location field that varies by posting | Tries a ladder of city, then state, then country until the field accepts one of its own suggestions |
| Resume-first autofill slot | Recognized as Ashby's autofill slot and handled separately from the regular resume upload |
| Traffic that passes bot filtering | Fills run in your own browser through the Reach Autofill extension, or over a residential network path, instead of from a datacenter |
| hCaptcha | Never solved by automation; the application parks for you to finish |
| Screening questions | Answered from your saved answers, your resume and your persona; career-history questions with no evidence are left for you rather than guessed |
| A resume and cover letter | Written for that posting from your real history, checked against it for invented claims, and editable before anything is sent |
Why Ashby fills go through your browser or a residential path
Because Ashby walls most datacenter automation, Reach does not rely on its server-side headless browser for Ashby the way it can on some other ATS platforms. Ashby fills are routed through one of two paths.
Your own browser, via the extension. The Reach Autofill extension (Chrome, Edge, Brave, Opera and Firefox) fills the Ashby form in the browser you already use, on your own network. By default the extension fills and stops; you read the form and press Submit yourself. If you turn on hands-off mode, it submits only a clean fill, meaning nothing unanswered, no fill errors and no visible captcha. An optional unattended queue can walk your approved applications on a schedule in your browser, with per-run and per-day caps.
A residential path. When Reach fills a form for you without the extension, Reach can route it through a residential network path.
On either path, Ashby fills succeed far more often than they do from datacenter automation. That is the practical answer to Ashby bot detection on a job application: the fix is not a cleverer bot, it is filling from a normal browser on a normal network.
What Reach does not do on Ashby
It never solves hCaptcha. Captchas are never solved by automation, on Ashby or anywhere else. If one appears, the application parks.
It does not fight a wall. When Ashby shows a wall, the application moves to the Needs attention list in the Applications tab, and the Finish live list lets you complete it in your own browser with the extension, which fills what it can and leaves Submit to you.
It does not guess at your history. Questions such as whether you have worked at a startup or led a particular kind of project are answered only from saved answers or a resume that states it. Otherwise the question is left for you, so you answer it once.
Review mode is the default
Every application Reach prepares, on Ashby or any other ATS, is held for your approval unless you change that. Auto-apply is opt in per persona, runs under a daily cap you set, and can be paused at any time. Before Reach ever reads an Ashby posting with a model, deterministic gates remove what you cannot take: location eligibility, salary floor, seniority, work type, schedule, direct employer versus staffing agency, your company blocklist and title words you want to skip. Reach also applies only once per employer and title, so a role posted in several cities does not produce several applications.
Replies come back to a private apply address Reach gives you, so Ashby's confirmation email, a rejection, a recruiter reply or an interview invitation shows up in the Reach Inbox tab next to the application it belongs to.
How this compares with other tools
As of October 2026, Tools that fill from datacenter servers and treat every ATS the same way run into the bot filtering described above, and a generic filler that does not know about Ashby's toggles or server-side saving can submit answers that disagree with what it intended. Check any tool's own site for what it currently supports, and ask specifically how it handles Ashby before relying on it for startup roles.
What Reach gets wrong
Ashby applications are not fully hands-free. The best results come from the extension running in your own browser, which means having that browser open; a wall or an hCaptcha still parks the application for you. Reach's inventory is US centric, and coverage outside the US is thinner. The company was founded in 2026, has a small user base and no independent review record yet. Auto-apply volume is capped on purpose, so if you want hundreds of Ashby applications a day this is the wrong tool.
Who this is for
- You apply to employers that use Ashby: a tool that fills Ashby correctly matters.
- You have tried an auto-apply bot that kept getting blocked on Ashby: Reach's browser and residential paths exist for exactly that problem.
- You want a resume and cover letter written for each posting: Reach writes both from your real history and lets you edit them before anything goes out.
- You are comfortable finishing the occasional application yourself: captchas and walls park for you, and the extension helps you finish live.
- You want to try it without paying: the free tier is $0 forever, with unlimited matches, 3 auto-applies a day and 5 tailored packages a month, and no card. Basic is $7.50 a month (25 percent off the $10 list) and Pro is $15 a month (25 percent off the $20 list) with unlimited applies and packages.
Whatever tool fills your Ashby forms, it works from your base resume, so check that first: our free resume checker needs no account.