Metix Lists JD to boolean
Pull titles, must-haves and locations from a job description. No model, no invented terms and no candidate search.
Start with the job description
Your example only fills the form. You decide when to run.
A useful next step, right here
Two search strings will appear here. Add your job description or load an example to get started.
Keep the momentum.
Bring your recruiting workflow together with Metix AI.
14-day trial · 1 AI Agent and 500 Credits · Plans $99–$499/mo.A little more clarity.
What to expect from these tools.
Examples, methodology & reference
How this works
A boolean string from a job description uses the title, requirements section, and location the posting states. No synonyms, no model, no candidate search.
A complete example
A complete example
This job description is fictional. It is here so the strings below can be read without running anything.
Title: Staff backend engineer
Location: Berlin, Germany (hybrid, two days on-site)
Experience: 7+ years building production backend services
Requirements: Go, PostgreSQL, KubernetesLinkedIn boolean. Example. Not a search result.
"Staff backend engineer" AND Go AND PostgreSQL AND KubernetesGoogle X-ray. Example. Not a search result.
site:linkedin.com/in "Staff backend engineer" Go PostgreSQL Kubernetes (Berlin OR Germany)Note what is absent. Staff is already in the title, so it is not repeated as its own term, and 7+ years is shown on the page but never put in a keyword string. Berlin and Germany are only in the X-ray string: on LinkedIn, set them in the Location filter. The posting lists no nice-to-haves, so the string has no OR group of optional skills; one would have to be invented.
- Paste the posting, or load the example and press Build the strings.
- The page finds the Requirements section (also What you'll bring, Qualifications, 任职要求) and reads skills from it, not from the duties list.
- Copy a LinkedIn string and an X-ray string. "Python or R" stays an OR group. A weak read is said plainly.
Limits
Only terms found in the posting are extracted. Nice-to-haves remain optional when opening the manual generator. Review ambiguous requirements before using either string.
Before running the search
- Compare “Where each term came from” with the original requirements. For
Python, Django / Flask, check forPython AND (Django OR Flask). If the posting is ambiguous, clarify it and rebuild. - Open the fields in the Boolean generator to adjust the search. Keep optional skills optional. Set LinkedIn’s location filter separately; the X-ray string includes location words.
- Inspect the source profiles returned by your search. A matching word can describe past work or an incidental mention. Confirm relevant experience and dates before treating a result as a match. For interviews, review the toolkit’s evidence guidance.
Who uses it
Who uses it
- Recruiters who have been handed a requisition and want a search string without retyping the whole thing into six boxes.
- Founders checking whether the job description they wrote is specific enough to search against at all.
- Hiring managers who want to see how narrow their must-have list really is once it becomes a query.
Choose the next step
Product facts & pricing
Metix AI covers 860M+ public profiles.
95% of roles get a first interview scheduled within 24 hours — a confirmed calendar slot, not a same-day meeting.
Plans cost $99–$499/mo. The 14-day trial includes 1 AI Agent and 500 Credits.
Talent moves and People Router can show public LinkedIn profile URLs, with no contact details. Other tools omit profile URLs and contact details. Start the 14-day trial.
Named people on Metix Lists
Public US lists with a name, title, company, and location. JSON, CSV, and Markdown sit on each list. These rows are a sample, not a search result from this tool.