DocsGenerating ResumesJob description input

Job description input

The job description is the other half of the equation. What you give it here determines which modules get selected and how the output resume is framed.

Paste vs. URL

The input screen has two tabs: Paste and URL. Paste is always available — copy the job description from wherever you found it and drop it in. The URL tab fetches the page content directly, which is faster if you're working from a job board link.

More is better. Include the full JD — responsibilities, qualifications, the company blurb, all of it. The more text the system has, the more accurately it can extract themes and phrases. Don't trim it down before pasting.

What gets extracted

After you submit the JD, the system runs an analysis pass that extracts:

Company name — Used in the output resume header and for your records.

Role type — The closest match from the role type vocabulary (e.g. director-community, developer-relations). This influences which modules score highest.

Seniority — IC, manager, senior-manager, director, VP, or C-suite. Affects module scoring — VP-appropriate modules score higher on VP-level JDs.

Themes — The 5–8 most prominent themes from the JD vocabulary. These drive the bulk of the module matching.

Key phrases — 5–10 exact phrases from the JD text. These are mirrored into the generated resume to help with ATS matching and to signal alignment to the hiring team.

Reviewing the extraction

After analysis, you'll see a summary of the extracted profile before matching runs. Review it — the AI is generally accurate, but occasionally misclassifies seniority or misses a dominant theme. You can edit any field before proceeding.

Check the phrases. The extracted phrases are used verbatim in the output. If any of them are boilerplate ("competitive salary," "equal opportunity employer") rather than role-specific language, remove them before generating.

Saving JDs

Every job description you submit is saved to your account. You can re-run a generation against a saved JD at any time — useful if you add new modules to your library and want to regenerate with the updated set. Access saved JDs from the Generate screen under the History tab.