Help center
How ApplyPilot works, where it stops, and what to do when a form fights back.
Getting started
- 1Upload a resume. ApplyPilot extracts your history and shows it to you for confirmation — nothing goes into your profile until you approve it.
- 2Fill in the work-authorization block. This is the one section ApplyPilot will never infer, and applications ask about it constantly.
- 3Install the browser extension. Application forms live on the employer’s site, so this is how ApplyPilot reaches them.
- 4Paste a job URL on the Apply page. ApplyPilot reads the posting, detects the platform and recommends a resume.
- 5Open the application and run autofill. Review what it filled, answer what it handed back, and submit yourself.
What ApplyPilot will not do
These are not settings, and no plan changes them.
- It will not submit an applicationApplyPilot fills fields and stops. Submission happens on the employer’s own page, by your own click. There is no submit method anywhere in the adapter layer.
- It will not invent an answerIf your profile does not answer a question, ApplyPilot says so and asks. It will not produce a plausible-sounding answer to fill a gap in your history, your qualifications or your authorization status.
- It will not answer consequential questions on its ownWork authorization, sponsorship, salary, background screening and voluntary demographics always require your explicit confirmation, whatever the confidence score says.
- It will not bypass human verificationA captcha pauses the session and hands the page back to you. ApplyPilot makes no attempt to solve or evade one.
- It will not ask for employer passwordsApplyPilot works inside your own authenticated browser session. It has no place to store a third-party credential and never requests one.
- It will not claim to improve your oddsAutofilling saves typing. Whether an employer calls you back is not something this product can observe, influence or honestly report on.
How confidence works
Every field ApplyPilot considers gets a score out of 100, based on how it was matched: an exact field-name match scores higher than a fuzzy label match, which scores higher than an inference. The score decides what happens.
| Score | What happens |
|---|---|
| 95–100 | Filled automatically. |
| 80–94 | Filled, and flagged so you can check it. |
| 60–79 | Not filled. Shown to you for review. |
| Below 60 | Not filled. ApplyPilot is not confident enough to guess. |
The exception
These categories bypass the scores entirely and always require your confirmation:
When something goes wrong
Every failure ApplyPilot can hit has a message and a next step. This is the complete list.
| Situation | What it means |
|---|---|
| That does not look like a job URL | ApplyPilot could not parse this as a web address. |
| Unknown application platform | ApplyPilot could not identify which application system this page uses. |
| Human verification required | This application is protected by a human verification challenge. ApplyPilot does not attempt to solve or bypass these. |
| Sign in required | This employer requires an account before you can apply. ApplyPilot never stores or asks for employer login credentials. |
| The application session expired | The employer’s site signed you out while the form was open. |
| No resume selected | This application requires a resume and none is selected. |
| Some information is missing | The form asks for details your profile does not contain yet. |
| This posting is closed | The employer is no longer accepting applications for this role. |
| No application form on this page | This looks like a job description rather than the application form itself. |
| The form changed while filling | Fields appeared or moved after ApplyPilot inspected the page, so filling stopped to avoid writing to the wrong field. |
| More fields appeared | Answering one question revealed additional fields. |
| The form is in an embedded frame | The application is inside a frame ApplyPilot cannot read from this page. |
| You may have already applied | This role closely matches an application already in your tracker. |
| Resume upload did not complete | The employer’s site rejected or dropped the file upload. |
| Connection problem | ApplyPilot could not reach the server. |
| Too many requests | ApplyPilot is pacing requests to stay within limits. |
| Monthly application limit reached | You have used all the applications included in your plan this month. |
| Browser extension not connected | ApplyPilot needs the browser extension to read and fill application forms. |
What is stored
Your profile, your resumes, your saved answers, the jobs you analysed and the applications you started. Resume files live in encrypted object storage; the database holds only their metadata.
The autofill engine reads through a fixed allow-list, so the answer to “what could ApplyPilot type into an application?” is finite and auditable. The Privacy dashboard shows that list in full, and exports everything as one JSON file.
Security
- Encrypted in transit and at rest.
- Passwords hashed with scrypt. OAuth available, and preferred.
- Session cookies are httpOnly and SameSite=Lax; extension tokens are short-lived and individually revocable.
- The extension requests host access per domain, on first use — not for every site you visit.
- Password fields are skipped by the field collector, so the extension cannot read one even by accident.
- Every read and write of your candidate data is written to an audit log you can read, recording which fields were touched but never their values.
What we measure
Activity, not outcomes. ApplyPilot reports how many fields it filled, how many it handed back, and an estimate of the typing it avoided — all things it did and can therefore count.
Interview and offer counts come from statuses you set by hand, and are shown separately. Nothing in the product joins the two into a claim that autofilling caused an outcome, because nothing in the product could establish that.