Answer-and-remember

A required question nobody could answer — not the rules, not your custom Q&A, not the AI — would otherwise stop the form dead at Submit. Answer-and-remember turns that into a one-time ask.

How it works

flowchart TD
    A[Field on the form] --> B{Rule or saved custom Q&A answers it?}
    B -- Yes --> C[Filled automatically]
    B -- No --> D{Required?}
    D -- No --> E[Left for you — not blocking]
    D -- Yes --> F{AI answers on, Pro/trial?}
    F -- Yes --> G[AI fills it — flagged to check]
    F -- No --> H[Badge asks once, inline]
    H --> I[Saved as custom Q&A: match + answer]
    I -.every future form with the same words.-> B

After a fill, the badge lists up to 8 such questions, each with a control built from the form's own options — a select for radios, selects, button groups and react-select menus; a text box or textarea otherwise — a note saying "Remembered as <keywords>" underneath, and two buttons: Fill these and Skip.

Saving:

1. Fills the fields through the same widget fillers as everything else.
2. Appends { match, answer, from, at } to your custom Q&A, where match is the question's content words — stopwords dropped, first six kept.

The next time any board asks a question containing those same content words — in any order, on any company's form — it's filled without asking again. Matching works as a substring or when every content word from a saved match appears somewhere in the new question.

A question counts as required when it has required/aria-required, a * or "(required)" in its label, or a required class on its container.

In the apply queue

The queue uses the exact same mechanism. When autoApply hits questions like this, it stops before Submit and returns needsAnswers; the entry in your job log is marked Needs answers (amber, like Failed submit) with the questions listed in its notes, and the tab is left open showing the badge in Fill & submit mode. Saving your answers (or skipping) resumes the run: it skips the refill, presses Submit, and watches for confirmation as usual.

A value that exists but doesn't fit still counts as unresolved

Sometimes a rule or a saved custom-Q&A answer exists, but the actual widget won't take it — a searched combobox with no matching live option (a School/Discipline picker that doesn't list what your profile has), or a "buttons" group that wouldn't click. That field flows through the same answer-and-remember, AI and sharing paths as a question nothing could answer at all, rather than silently disappearing.

Form sharing (the next level)

When a fill leaves required questions nothing could answer, jobwhat can share the question — its label and options only, never your answer — under a fingerprint of the specific form. If someone else queues that exact job next, jobwhat asks them the question up front, before the run even starts, instead of them hitting the same wall you did. Turn this off in Settings → Share the questions a form asked that nothing could answer if you'd rather not.

Your Metrics tab shows both directions of this: Questions you shared and Heads-ups from others' forms. See The Metrics tab.

Learning loop: patterns across every form

Separately from per-job sharing, jobwhat also learns from the shape of questions across every form, on every board — never the answers, just how often a given wording shows up and what options it offers. That aggregate feeds a small, human-reviewed set of synonyms and frequent-question hints, refreshed once a day, which helps the built-in rules recognize an oddly-worded question it wouldn't otherwise catch.

The popup's Get set up card surfaces the other side of this: if forms keep asking something your profile and custom Q&A don't cover, it's listed there with an inline answer box — save it once and it's remembered like any other custom Q&A entry.