Lever and External Candidate Sourcing: Increasing Pipeline Volume Without Replacing LeverTRM

Lever built its ATS around relationship-driven recruiting — pipelines, nurture stages, and CRM-style candidate tracking that suit companies doing a lot of proactive, ongoing recruiter outreach. That design assumes recruiters already have a reasonable flow of candidates to build relationships with. For companies scaling quickly across multiple roles, that assumption is often the actual bottleneck.

Where Lever's design creates a sourcing dependency

Lever's pipeline and nurture-stage model works best when there's a steady stream of candidates entering at the top to be organized, tracked, and moved through relationship stages. When that top-of-funnel flow is thin, even a well-configured Lever instance produces the same result: recruiters spending their time hunting for candidates instead of managing relationships with them.

Connecting an external sourcing layer

Lever exposes a documented API that supports adding candidates to specific postings with structured data and notes attached. A sourcing layer that pre-qualifies candidates externally — through social campaigns and automated screening against your criteria — can deliver them straight into the correct Lever pipeline stage, already tagged and screened.

What it means for recruiter time

• Less time spent cold-sourcing on LinkedIn or job boards to fill a thin pipeline
• More time available for the relationship-building and nurture work Lever is designed for
• Pipeline stages stay populated continuously instead of emptying out between postings
• Existing nurture campaigns and CRM workflows remain fully intact

When this is worth setting up

The signal is usually a pipeline stage that's technically well organized but consistently thin — recruiters have somewhere to put candidates, they just don't have enough of them. That's a sourcing problem, not a Lever configuration problem, and it's worth fixing before considering a platform change.

What SmartHire adds above Lever

SmartHire runs the sourcing and pre-screening work upstream of Lever, then delivers qualified candidates directly into your existing pipeline structure via API. Your nurture stages, CRM workflows, and recruiter processes stay exactly as built — the only change is a steadier stream of qualified candidates for your team to actually build relationships with.

Checklist before connecting to Lever

• Which jobs or regions in Lever have the thinnest candidate flow today?
• Which fields should come with each candidate, such as contact details, screening answers and source?
• Who owns access, permissions and the integration user?
• How will duplicates be detected, and how long are records kept?
• Which numbers will you compare before and after: cost per qualified candidate, time to first candidate, recruiter hours?

A simple way to pilot it

Start with one role in one location, ideally roles where the pipeline dries up between campaigns. Run the sourcing layer for a few weeks alongside your normal process, and compare it with the same role's inbound results. If the numbers hold, extend to more roles. This is a pilot, so the results depend on the role and market, and you should treat any published benchmark as a guide only.

Candidate data is personal data. Check that consent, data-processing terms and storage locations meet your rules before you go live, and confirm what your plan and version of the system allow.

Does Lever need to be replaced or changed?

No. The sourcing layer runs alongside it, and your team keeps working in Lever exactly as before. It is a good fit for mid-size teams that manage candidate relationships in one place.

How long does setup take?

It depends on which fields you connect and what your IT team needs to approve. Starting with a single role keeps the first setup short and makes problems easy to spot.

How do we know it is working?

Compare cost per qualified candidate, time to first qualified candidate and recruiter hours on screening against your existing baseline for the same type of role.