Upload a job description to start a search

A candidate search started from an uploaded job description, with criteria extracted automatically.

CLIENT-ONLY · How-To

Outcome

A search seeded directly from a JD, with criteria pulled from the document.

Open the search dashboard.
Click the paperclip icon at the bottom left of the search input.
Select your JD file. The file name appears in the input.
Wiggli parses it and extracts job title, company (if mentioned), skills, location, industry, and language.
The detected filter chips highlight. Review and click any chip to edit, remove, or accept AI synonyms.
Click Find talents.

[SCREENSHOT: Search dashboard with an uploaded JD and the extracted criteria chips]

Active chips reflect the JD, and results match the role described. The file name stays visible until you clear it or start a new search.

Plain, well-structured JDs parse better than designed PDFs.
The engine reads only the JD. Prompt text typed alongside an uploaded file is ignored, so fine-tune on the filter screen after parsing, not in the search bar.
Strip the JD to must-haves before uploading. The parser treats everything in the document as a requirement, so a JD full of nice-to-haves produces an over-specified search. If the JD is bloated, a Smart Prompt with the three or four real requirements usually beats it.
One JD per search.
For sensitive client roles, redact the company name before uploading.
JD upload also works in the Sourcing Agent, but there the intake conversation is the stronger path: it digs into what actually separates a good candidate. Hand the agent a JD only when it’s well written and truly reflects the target profile.

Still stuck?

Your customer success manager reads faster than any search bar.