AppFill

Greenhouse, Lever, Ashby and Workday all want name, email, phone and LinkedIn. Then they ask what Chrome's built-in autofill never touches: are you authorized to work here, will you need sponsorship, how many years of experience, why this company.

Most of my time on each application went to retyping answers I had already given somewhere else. The parts that deserve attention, choosing the right portfolio pieces and writing a note to the hiring team, got whatever time was left.

Autofill is something you reach for in the middle of a page, so it lives in the menu that's already under your hand. There's no toolbar popup to open and nothing to configure per site. The same menu works inside the embedded application frames many company career pages use.

• check_circleFill blanks, never overwrite. A page fill only touches empty fields, so running it twice is harmless and anything I typed stays put.
• check_circleShow the gaps. Fields it can't place get a dashed amber outline instead of a best guess. Green means done, amber means mine to do.
• check_circleDon't agree on my behalf. It never ticks a checkbox from a guess, so consent and privacy boxes stay my decision. Password and file fields are skipped entirely.

Application forms are built by different teams on different platforms, so no single attribute is reliable. A field might have a proper label, only placeholder text, or just a developer name like job_application[first_name]. AppFill collects every clue, turns them into plain words, and checks them against 31 patterns for names, contact details, links, work history and the standard yes-or-no questions.

For each empty field it checks four sources in order and stops at the first answer: answers saved for this site, the field's own autocomplete hint, my custom answers, then the built-in patterns. Dropdowns get one more step, since a profile that says OR has to match a form that says Oregon.

Some questions belong to one platform or one company: work arrangement, pronouns, how you heard about the role. Instead of guessing, AppFill outlines them. I answer them once, right-click and choose Remember my answers on this site.

Answers are saved per host, not per company. Most companies run their applications on the same few platforms, so answers saved on one Greenhouse posting fill the next Greenhouse posting too.

Right-clicking inside a field adds Fill this field with…, a submenu of every saved value with a short preview. It covers fields with labels too odd to match, and it replaces whatever is already there, because pointing at one field is a clear instruction. The submenu rebuilds itself from the profile, so empty entries never show up as choices.

The settings page is itself a form: personal details, address, links, work and education, and four standard yes-or-no questions. Below those come custom answers for anything the profile doesn't cover, a list of remembered sites, and export and import for moving to another computer. It saves as you type.

Custom answers match on a few words the question would contain. "Why do you want, why this company" catches most versions of the question without a rule for each.

I loaded the extension into Chromium and ran it against a Greenhouse-style form with text fields, dropdowns, two radio questions, a long-answer box, a consent checkbox and a password field.

• check_circle13 of 14 fields filled on the first pass, with no saved answers.
• check_circle15 of 15 filled after remembering the site once, including the dropdown and the checkbox.
• check_circle0 password, file or unsaved checkbox fields touched.

An autofill tool holds exactly the details you'd least want leaking. The profile, custom answers and remembered sites live in the browser's local extension storage. Nothing is synced, sent or logged, and export and import cover moving to a new machine.

I built AppFill with Claude in one session. I set the behavior: where the menu lives, what it may and may not touch, how gaps are shown. Claude wrote the code, loaded the extension into a headless browser, and ran it against a sample application form so every rule could be checked against a real page.

Reviewing the screenshots from those test runs is where the one bug turned up, before the extension was ever used on a real application.

Fixes

• buildOn radio questions, the green highlight landed on the first option instead of the one that was selected. It now outlines the checked option.