Browser-only recruiting workbench
Free candidate sourcing workbench for recruiters
Build channel-aware search strings, make role evidence explicit, and draft outreach from facts you have checked. The workbench does not rank candidates or send messages.
- Generated locally in this browser
- Manual review required
- No candidate ranking
01. Build a title-and-evidence search
Use job criteria only: titles, aliases, skills, seniority language, and exclusions. The workbench generates text in your browser; avoid pasting unnecessary personal data.
LinkedIn / Recruiter syntax
("Backend Engineer" OR "Back-end Engineer" OR "Software Engineer" OR "Platform Engineer") AND (Java OR Kotlin) AND "Spring Boot"Google syntax for public pages
site:linkedin.com/in ("Backend Engineer" OR "Back-end Engineer" OR "Software Engineer" OR "Platform Engineer") AND (Java OR Kotlin) AND "Spring Boot"Method: LinkedIn supports uppercase AND, OR, NOT, quotation marks, and parentheses. Google handles quoted phrases, site: filters, and minus exclusions differently, so the two outputs are intentionally not identical. LinkedIn Help · Google Search Help
Limit: Search syntax and result coverage can change by account, product, region, and index. This is a starting query, not a completeness or validity guarantee. Review results yourself.
02. A hard-role pack: backend engineer
A compact example for a role where the technology evidence matters more than a single title. Treat it as a starting brief, not a candidate score.
Role
Backend Engineer
Useful title aliases
- ↳ Back-end Engineer
- ↳ Software Engineer
- ↳ Platform Engineer
Evidence to verify
- ✓ Java or Kotlin in recent work
- ✓ Spring Boot or a comparable JVM framework
- ✓ Production API or distributed-systems ownership
Example search output
LinkedIn / Recruiter syntax:
("Backend Engineer" OR "Back-end Engineer" OR "Software Engineer" OR "Platform Engineer") AND (Java OR Kotlin) AND "Spring Boot"
Google syntax for public pages:
site:linkedin.com/in ("Backend Engineer" OR "Back-end Engineer" OR "Software Engineer" OR "Platform Engineer") AND (Java OR Kotlin) AND "Spring Boot"03. Calibrate the search before reviewing profiles
Write down what must be present, what is acceptable evidence, and what needs a human check. This worksheet records criteria; it never ranks people.
Use observable job evidence and keep interpretation separate from the evidence. A recruiter makes the decision; this worksheet simply makes the decision easier to explain.
04. Draft outreach from verified facts
Paste only facts you have checked and a template you control. This workbench fills placeholders in your browser; it does not discover facts, call an API, or send a message.
Add a verified fact and a template to create a draft.
Limit: Keep personal data to the minimum needed for a relevant, lawful message. Check consent and channel rules before using any outreach tool. Nothing here sends or logs the message for you.
Questions recruiters ask about this workbench
Does this tool search LinkedIn or rank candidates?
No. It produces text you can review and paste into a search. It never opens a search, fetches a profile, scores a person, or makes a shortlist.
Why are the Google and LinkedIn strings different?
The services support different operators. LinkedIn documents AND, OR, NOT, quotes, and parentheses; Google supports quotes, site: filters, and minus exclusions. The workbench keeps those conventions separate.
What should I verify before outreach?
Verify the person, the relevant work evidence, the date and source, the opportunity, and whether the channel is appropriate. The tool only combines facts you provide.
Start a free 10-day Yena trial
When you are ready to turn a search plan into candidate discovery and managed outreach, test Yena on a real mandate for 10 days. Keep human review in control; no hiring outcome is promised.
Start a free 10-day Yena trial