LinkedIn candidate search
Search LinkedIn straight from the job you're sourcing for, and import the profiles that fit into the same selection flow you already use.
When you’ve worked through every CV in your pipeline and still haven’t found the right person, the next step is to look beyond your applicant pool. For most teams that means a recruiter typing queries into LinkedIn, saving profiles to a spreadsheet, and then transcribing the promising ones into their ATS a few hours later.
We’ve been building something simpler. Starting this week, Selectify can search LinkedIn for you and drop the profiles that fit straight into the job you’re working on.
Why search is part of selection
We didn’t start Selectify to be a sourcing tool. The product exists to help you select candidates — compare them objectively, ask the right questions, share findings with the hiring team. But pilot after pilot hit the same wall: the selection tools are solid and the candidate pool is wrong. You can’t select your way to a great hire if the people applying aren’t the right match to begin with.
So we took the same “selection is a team sport” thinking one step earlier in the funnel. Instead of switching to LinkedIn Recruiter, paying for InMails, and re-entering candidates one at a time, search now lives inside the job you’re sourcing for — and its output becomes the input of everything else Selectify does.
How the search works
Open any job and hit Add from LinkedIn. You get a form that should feel familiar if you’ve ever used LinkedIn Recruiter:
- Keywords and job titles — current and past roles.
- Location and distance — with a radius you control.
- Industries, seniority, years of experience — picked from LinkedIn’s own taxonomy so your filters match LinkedIn’s logic.
- Education, company, profile language — deeper filters for when a role warrants them.
Your job title and location pre-fill from the job you’re viewing, so the common case is “click search, tweak one thing, go”. Every search is team-scoped — one team never sees another’s searches or results.

What comes back
Searches are asynchronous — LinkedIn isn’t instant and we don’t pretend otherwise. A typical search returns in 30 to 90 seconds. When results land you see a table of profiles with:
- name, current role, location, a short bio
- a LinkedIn URL to verify any profile before importing
- a status per profile: new, imported, or dismissed
You pick the profiles that look right and click import. Selectify creates the candidate records, attaches them to your job, and pushes them straight into your normal selection flow — the same pipeline, fit scoring, DISC insights, and team review you already use. Duplicates are detected by LinkedIn URL, so importing the same person twice — or finding someone already in your pool — is a no-op rather than a conflict.

Under the hood
A few things worth being upfront about:
- Quotas. Each subscription has an import allowance per billing period, visible on your subscription page. You won’t pay per search — imports are bundled into the subscription.
- Privacy. Every imported profile is treated as any other candidate — subject to your team’s GDPR defaults, consent flow, and automatic cleanup rules. No separate silo, no separate retention policy.
- Async by design. Because searches take real time, the UI is built for that. Start a search, walk away, come back. You’ll see a notification when results land; meanwhile you can keep reviewing other candidates.
Who gets access
To keep the rollout manageable we’re enabling LinkedIn search tier by tier — Business and Enterprise teams on active subscriptions, plus every pilot team (pilots resolve to Enterprise-level feature access). If you’re on a lower tier and want in, reach out — we’re lining up the next batch.
What’s next
This is the shape we’re shipping now. Near term we’re working on:
- Saved searches — re-run a search later without re-typing every filter.
- Notifications when new profiles match a saved search — continuous sourcing instead of one-shot queries.
- More sources — LinkedIn is one pool. Indeed, Stack Overflow, and GitHub are all on the roadmap.
- Fit scoring alongside results — today the fit score runs after you import; the plan is to surface it next to each search result so you can pick the top 5 instead of skimming 50.
We’re not promising dates. We are promising we’ll ship the next piece once it’s genuinely good enough, not because it showed up on a roadmap slide.
If you’re a Business- or Enterprise-tier team and want to try it today, it’s already live on your job pages.