
The sanctioned way to source LinkedIn profiles into Lever is LinkedIn Recruiter System Connect (RSC), which ships free with a LinkedIn Recruiter license and exports a profile into Lever as an opportunity in one click. Without a Recruiter seat, the Lever Hire Chrome extension imports a public profile, and a Simular AI computer agent can read the profile and build the Lever opportunity for you, with the stage and source already filled in.
A recruiter runs one LinkedIn Recruiter search and gets 300 matches. Forty look worth a first conversation. The tedious part starts now: opening each profile, then retyping the name, title, company, and profile link into Lever as a fresh opportunity, forty times over, before anyone has even replied.
Quick answer: the sanctioned way to source LinkedIn profiles into Lever is LinkedIn Recruiter System Connect, which ships free with a Recruiter license and pushes a profile into Lever as an opportunity in one click. Without a Recruiter seat, the Lever Hire Chrome extension imports a public profile, or a Simular AI computer agent reads the profile and builds the Lever opportunity for you, with the stage, owner, and source already set.
| By hand | Simular AI agent | Extension & RSC | |
|---|---|---|---|
| Setup | None | Show it one pass, about 15 minutes | Install extension, or admin sets up RSC |
| Speed per profile | 2 to 3 minutes | Unattended, human-paced batches | One click, one profile at a time |
| Cost | Free, your time | Subscription | RSC free with a paid Recruiter seat |
| Needs Recruiter license | No | No | RSC yes, extension no |
| Fills stage, owner, source | If you remember to | Yes, every record | Partly, you finish the rest |
| Best for | A handful of profiles | Steady sourcing into Lever, hands off | Recruiter teams already on RSC |
A staffing agency sourcing 40 profiles a day, an in-house recruiter filling one hard role, and a founder doing their first ten hires all face the same retyping tax. Only the volume changes.
Open the profile, read the fields, and create the opportunity in Lever yourself. Zero tooling, full control, capped at your own typing speed.
Pros: free, no license, and you can extract the profile data exactly the way your pipeline needs it. Cons: at roughly 2 to 3 minutes per profile, sourcing 40 candidates is well over an hour of pure data entry, and it is the first thing that gets skipped when you are busy.
Sourcing 40 profiles by hand at about 2 to 3 minutes each is roughly 80 to 120 minutes of retyping per search. Run three searches a week and that is 4 to 6 hours you are not spending on candidate conversations. Derived estimate.
Instead of installing anything or buying a seat, you show a Simular agent your sourcing routine once, and it repeats it into Lever for you.
Because the agent operates the real Lever and LinkedIn screens the way a person does, it needs no Lever API key, no Zapier wiring, and no browser extension. It checks for an existing opportunity before creating one, so a bulk run does not flood your pipeline with duplicates. That covers the sourcing even where the official integration cannot reach, such as a public profile you found without a Recruiter seat. See the Sai page for how the agent is set up.
Pros: consistent opportunities on any LinkedIn plan, unattended, no extension footprint. Cons: a subscription, plus about 15 minutes up front to teach it your routine.
Lever ships two sanctioned tools for this, and which one you can use depends on your LinkedIn plan.
Pros: sanctioned, and RSC is included free with a Recruiter license, so there is no scraping risk. Cons: RSC needs a paid Recruiter seat, not free LinkedIn or Sales Navigator; the extension works one profile at a time; and neither fully sets your stage and sourcing note, so the retyping shrinks but does not disappear.
Lever, like LinkedIn, treats sourced candidates as data it governs. RSC exists because LinkedIn wants profile export to go through an authorized channel that respects member privacy, which is why it syncs an in-ATS status and job data rather than letting tools read the page freely. Bulk scrapers skip that channel: they pull public profiles in the background, which LinkedIn's user agreement prohibits, and that is what puts an account at risk, not the act of sourcing itself.
Pro tactics for clean sourcing at volume:
The mistakes that cost recruiters time are consistent: leaving the source blank, creating duplicate opportunities, and trusting a background scraper that risks the account. The approach that holds up is boring on purpose, source through a sanctioned or human-paced path and label every record. The lesson worth pinning up: the bottleneck was never finding the profiles, it was retyping them into Lever.
The winning pattern: source through a sanctioned or human-paced path, label every opportunity with its stage and source, and let a Sai agent do the retyping into Lever on its own VM so your team spends its hours on candidate conversations, not data entry. The same agent can then add LinkedIn candidates to Greenhouse if you run more than one ATS, and you can read how Simular works on the Simular about page.