AutoFill · coverage

Where AutoFill works, measured

AutoFill reads whatever application form is open in your Chrome tab, so it works on any career site. This page says how well, platform by platform, from a check that fills one public form on each and counts the fields that verified. The same table drives the “Supported / Best effort” badge in the side panel and the “fields at risk” line it shows before a fill.

Loading the latest measurements…

PlatformStatusVerifiedMeasuredOften needs your check
WorkdayTestednot yet measuredset by hand—
GreenhouseTestednot yet measuredset by hand—
AshbyTestednot yet measuredset by hand—
LeverTestednot yet measuredset by hand—
WorkableLimitednot yet measuredset by hand—
SmartRecruitersLimitednot yet measuredset by hand—
BambooHRLimitednot yet measuredset by hand—

What the words mean

tested
A nightly run (or a hand-run of the same check) verified at least 70% of the fields it saw on a public form of this platform, on 8 fields or more.
limited
Measured below that, measured on too few fields, or run only through saved page fixtures. AutoFill still fills; review closely before Submit.
unsupported
The public form could not be reached, or fewer than 40% of the fields verified. AutoFill still tries, and tells you what it could not do.

Known limits

Each of these is a fact about how the extension behaves today, not a policy; the code that makes it true is named beside it.

  • Submit is always your click.
    The extension fills and stops. It never presses the employer’s Submit button; you review every answer and send the application yourself.
    extension/src/lib/engine_flags.ts (submitGuard)
  • A sign-in wall or an account step comes first.
    When the page shows a password box and almost nothing else, the side panel says “Needs you first”. Sign in or create the account, then ask it to fill. Most Workday tenants ask for an account before the form opens.
    common-ground/src/ats/supportTier.ts (tierForPage, sign_in)
  • A CAPTCHA in front of the form stops the fill; one beside it does not.
    A human check that stands where the form should be is yours to complete first. A reCAPTCHA or Turnstile box at the foot of a real form is only a note: the fill proceeds and the check is part of your Submit.
    extension/src/content/page_signals.ts (CAPTCHA_FRAME) · common-ground/src/ats/supportTier.ts
  • The posting is not the form.
    On a job description page with an “Apply” control and no fields, the panel asks you to press Apply first. Some platforms (Workable, SmartRecruiters, Dayforce, Zoho) open the form in a later step or a new tab.
    common-ground/src/ats/supportTier.ts (posting_not_form, no_form_yet)
  • Forms embedded in a company’s own careers site are read inside their frame.
    Many employers embed Greenhouse or Lever inside their own page. When the top page shows no fields, the extension looks into every frame for the form. Coordinates and some reads inside a cross-origin frame are less reliable than on the platform’s own page.
    extension/src/background/panel_task_agent.ts (cross-origin iframe probe)
  • Workday needs real keystrokes.
    Workday rejects values written by script and only keeps what was typed. The extension types through Chrome’s own input path for those fields, which is slower, and a date or month picker there can still need your check.
    extension/src/background/panel_cdp.ts (Input.insertText, Input.dispatchKeyEvent)
  • Date pickers, pop-up menus and type-to-search pickers are the controls most often left for you.
    The extension records every control it could not finish and shows you the kinds it misses most on each platform before a fill starts (“fields at risk”). Those rows are codes only: never a label, a value or a page.
    backend/src/lib/recipeMiss.ts · backend/src/lib/supportTiers.ts (riskKinds)
  • The site’s own résumé import is used when the page offers it.
    When a form has its own “autofill from résumé” button, the extension presses it with your stored résumé first, then checks every value the import wrote against your profile and rewrites what is wrong. Not every platform offers one.
    extension/src/lib/engine_flags.ts (resumeImport)
  • Multi-page flows are filled one page at a time.
    Each page is read, filled and verified before the next. A page that opens a new tab or a browser prompt stops the loop and the panel asks you.
    extension/src/lib/engine_flags.ts (pageSignals)
  • What the numbers are.
    The fill rate is fields verified divided by fields seen on one public demo form per platform, filled once by the same extension you install, against our development server, never submitted. It is a floor for that form on that night, not a promise for every employer’s variant.
    e2e/first_sight/canary.mjs · e2e/first_sight/fill_rate.mjs · docs/CANARIES.md
  • LinkedIn Easy Apply is not supported.
    AutoFill is built for employers’ own application forms and is not built or tested for LinkedIn Easy Apply, whose User Agreement lists bots and other automated methods among its don’ts.
    common-ground/src/ats/termsNotes.ts · extension/manifest.json

Questions people ask

Does “limited” mean AutoFill will not work there?
No. AutoFill reads whatever form is open and fills what it can on any site. “Limited” means we have not yet measured a high verified rate on that platform’s public form, so review more closely before you submit.
How often are these numbers updated?
A nightly check fills one public demo form per platform and compares it with the last baseline; a hand-run of the same check updates this table. The date beside each row is the measurement’s own.
My employer’s form is not on any of these platforms.
AutoFill does not match a list of sites; it reads the form in front of you. Platforms not listed here are filled as “best effort”, and the side panel tells you so before it starts.