Autofill Job Applications Safely: The JJ-JobHunter Extension

The most tedious minutes of any job application are the ones spent re-typing your own CV into a form that is holding a copy of it. Our browser extension exists to delete those minutes — and this article explains exactly how it works, because for a tool that types into job applications on your screen, "trust us" is not documentation. We will cover what it fills, what it deliberately refuses to touch, how the token security model works, and where the beta honestly stands.

What it is, in one paragraph

The JJ-JobHunter extension is an autofill tool for job application forms. You install it, connect it to your account with a token, open a job application, and it types your details — name, contact information, work history fields — from your confirmed CV profile: the structured data the platform extracted from your real CV and you verified. Currently, in beta, it ships with field mappings for Personio and Workday application forms, two systems you meet constantly when applying in the DACH region and at larger companies. That is the whole product. Everything else in this article is the design decisions around it.

What it fills — and what it will never touch

The extension's fill logic is deliberately narrow, and the boundaries are hard-coded, not configurable:

• It fills text fields and text areas. Nothing else. The mechanical fields where autofill genuinely helps — names, email, phone, city, work history text — are exactly where typing is boring and correctness is easy to verify at a glance.
• It never presses submit. The extension never clicks buttons, never triggers a form submission, never selects a submit control — the code contains no path that does. This is the never-submit principle we have argued for as an industry norm; in our extension it is an architectural rule, not a policy that could be toggled.
• It never touches file uploads. Attaching the right CV — which tailored version, for which job — is a decision, and decisions are yours. The extension will not select files or interact with upload controls at all.
• It never touches checkboxes, radio buttons or consent controls. Consent boxes are legal declarations; demographic and personal-choice questions are yours to answer or decline. Software should not tick a box that says "I confirm" on a human's behalf, so ours cannot.
• It never touches hidden or password fields. Hidden fields belong to the site's plumbing; credentials belong to you.

The honest consequence of these boundaries: the extension does not complete applications for you. It clears the typing, and leaves you a form where everything that remains — the CV attachment, the dropdowns, the consent boxes, the salary question, the final click — is judgment, and deliberately so. Our measure of success is the boring part disappearing, not the human part.

The one-token security model

A browser extension that can read your CV data needs a security story better than a password pasted into a config file. Ours works like this.

You generate an extension token in your account settings. The platform shows you the raw token exactly once — it is never stored on our side; only a cryptographic hash (SHA-256) of it is kept, which means nobody, including us, can retrieve your token later. You paste the token into the extension, and from then on the extension authenticates with it to fetch your fillable profile.

Three properties make this model easy to reason about:

• One active token per user. Generating a new token automatically revokes the previous one. There is never a drawer of forgotten credentials that all still work — at most one token is alive, and you know which.
• Revocable in one click. Settings shows whether a token is active, when it was created and when it was last used; revoke it and the extension stops working immediately until you issue a new one. Lost laptop, shared machine, simple caution — the kill switch is yours.
• Least data. The token grants access to the curated, fillable profile fields — not your account, not your applications, not the raw CV file. The extension receives what a form needs and nothing more.

Honest beta notes

The extension is in beta, and beta means concrete things here rather than a marketing adjective. Installation is currently the developer flow: you download the extension package from Settings and load it unpacked in your browser — a process with more steps than a store install. Field coverage is Personio and Workday; forms on other systems, and unusually customised forms on those two, may fill partially or not at all — the extension errs toward leaving a field empty rather than guessing wrong. When a form lives inside certain embedded frames the browser walls off, some fields are technically unreachable for any extension, and ours logs that honestly instead of pretending.

Two practical habits make it work best: keep your CV profile current on the platform (autofill from stale data looks correct and is not — the most dangerous kind of wrong), and treat the filled form as a draft for the review pass every application deserves: check the judgment fields, attach the right CV, read the free-text answers, then click submit yourself.

Why we built it this narrow

It would have been easy to demo a more spectacular extension — one that attaches files, answers dropdowns, maybe even submits. Every one of those capabilities fails the same test: would you want software doing this in your name, unreviewed, on a legal document addressed to your potential employer? Autofill that stops at text fields, holds one revocable token, and structurally cannot press submit is less impressive on a landing page and much easier to trust on a Tuesday night with a real application open.

The typing was never the valuable part of your application. It was just the part that took longest. That is the part we automated — and, deliberately, nothing else.