VKT Toolkit · September 25, 2026 · 9 min read

How to Fill Out Job Applications Faster in Chrome (Workday, Greenhouse, Lever)

Ten applications, ten portals, ten accounts, and the same twenty facts typed out again at every one of them. Your name. Your address. Your degree and its start date. Whether you need visa sponsorship. Nobody designed these forms to be pleasant — but most of what they ask for never varies, and that is exactly the part worth automating.

This is the workflow, built around the fact that applicants rarely control which ATS they meet.

Why Job Applications Are the Worst Forms on the Web

• One portal per employer. Company A runs Workday, company B uses Greenhouse, company C uses Lever — with different fields, different validation and a separate account each time.
• Long flows. A single application often runs 40+ fields across five or six steps, with a progress bar that resets if a session expires.
• Repetition with a thin layer of variation. Maybe 80% of the answers are identical between applications; the resume, the cover letter and two free-text answers are the part that actually needs your attention.
• Domains you see twice. The same employer may list three roles on its portal. The second and third applications reuse the same profile, the same work history, the same voluntary disclosures.

What Chrome Autofill Covers on Each ATS

The built-in autofill helps a little and gives up quickly:

The common thread: autofill answers questions it recognizes as identity. An application asks questions that happen to be about you but are not address data — and only one of those two things is what autofill understands.

The Strategy: One Application Profile, Reused Everywhere

Instead of saving answers per employer, save one snapshot that represents your application profile: the constant block you type at every portal. Then replay it onto whichever form you are standing in front of.

Two properties make this work with a form-snapshot tool rather than autofill:

• Matching is descriptor-based, not position-based. VKT Form scores each stored field against each field on the page using name, id, label text, semantic tokens, structure and DOM order. A snapshot built on one employer's portal still fills a different employer's portal, because the tool is matching the question, not the coordinates.
• Coverage beyond the plain document. Field detection reaches shadow-DOM components and iframes, and it also captures the inactive steps of a multi-step flow — which is how a Workday wizard gets filled in one pass instead of one page at a time.

Step by Step: Build Your Application Profile

1. Open the most complete application form you can find — a Workday wizard or a Greenhouse application with many optional fields. The richest form makes the best template.
2. Fill it completely by hand with your constant answers: name, email, phone, city and country, degree and institution, current employer, work authorization, sponsorship requirement, notice period, links to your portfolio and profiles.
3. Leave the tailored parts blank: resume upload, cover letter, the "why this role" box, salary expectations, and anything with today's date.
4. Click Collect and check the field list. Remove anything job-specific that snuck in.
5. Next portal: click Fill. Review the report — every field is read back after writing, and anything that did not land is listed instead of being silently skipped.
6. Calibrate what the heuristics miss. If one stubborn field never fills, bind it once in the snapshot's calibration panel; from then on it always takes priority.

That is the whole setup: one form filled carefully, once.

Per-Employer Snapshots: When They Are Worth It

• Multiple roles at the same employer. After your first application, Colleagues-portal answers such as "how did you hear about us", preferred location or department are already stored — later applications become a two-click review.
• Portal-specific questions. Some employers add long questionnaires (security clearance, shift availability, languages). Save a second snapshot when that block is stable across their roles.
• Referral rounds. If a recruiter sends you back to the same portal for a second interview stage, the answers are waiting.

What You Should Never Save

• Passwords for the application accounts — use a password manager, which is built for exactly that.
• Government identifiers: national ID, passport number, Social Security number, tax file number. Applications ask for them late in the process, if at all, and snapshot storage is plain local storage, not an encrypted vault.
• Bank details and payment cards. Same reason.
• Anything that changes per application: cover letters, tailored summaries, salary figures you adjust per role, the date.

The rule that keeps this simple: store what you would happily read out loud to a recruiter. If an answer should be encrypted, it should not be in a form filler.

A Realistic Ten-Applications Workflow

1. Keep one profile snapshot for the constant block and two or three per-employer snapshots for portals you return to.
2. For each new posting: create the account, open the form, click Fill, read the field report.
3. Type only what is genuinely new: the tailored paragraph, the right resume version, the salary answer.
4. Read the whole form once before submitting. You are the last line of defence against a wrong phone number on a form you already sent nine times today.

In practice this moves the job-application hour from "retyping and re-checking" to "deciding what to say" — which is the part that influences the outcome anyway.

Honest Limits

• It fills, it never submits. No Next, no Apply, no bulk applications. That is deliberate: reviewing each application is also what keeps you out of trouble with sites that forbid automated submission.
• File uploads stay manual. No extension can attach your resume to a file input.
• Long free-text answers are yours to type. A snapshot can hold them, but they should be tailored each time — that is the point of applying to a specific role rather than a category.
• Accounts and logins are still per portal. The snapshot saves the form, not the journey around it.

For that job, VKT Form is a browser extension that stores everything in chrome.storage.local on your own machine — no account, no analytics, no upload. The free tier holds 5 snapshots with unlimited fills, enough for one application profile plus the portals you revisit. Premium lifts the cap and adds JSON export/import so you can carry snapshots between your laptop and desktop, for $9.99 one-time (lifetime) or $2.99/month.

Frequently Asked Questions

More VKT tools live in the extensions catalog, or reach us at [email protected].