Brainner Lever Integration - What It Does and When to Use It

The Brainner integration for Lever automates resume screening by extracting hiring criteria from job descriptions, scoring incoming candidates against those criteria, and syncing results back into Lever. It’s designed to reduce the manual workload of resume review while preserving recruiter control over hiring decisions. This article explains how the integration works, concrete use cases for when to enable it, implementation and data-flow details, measurable outcomes you should expect, and practical configuration and rollout tips.

At a high level, Brainner connects to Lever to automatically import job postings and candidate resumes. Brainner’s model analyzes the job description to produce role-specific criteria, lets recruiters refine those criteria (mandatory vs preferred), scores each candidate in real time, and then updates candidate records and statuses back into Lever.

How the Brainner + Lever flow works (three core steps)

• Import Job Description Brainner pulls the job description from Lever and uses NLP to extract role criteria (skills, experience, education).
• Customize Screening Criteria Recruiters can add, remove, weight, or mark criteria as mandatory/preferred so the scoring matches hiring requirements.
• Real-time Candidate Analysis and Sync As candidates apply, Brainner scores and ranks them, provides per-criterion justifications, and writes scores and status changes back to Lever.

Manual screening vs Brainner + Lever: operational impact

When to enable the Brainner + Lever integration

• High application volume roles If a role receives hundreds or thousands of resumes (e.g., entry-level, bulk hiring), Brainner reduces screening time dramatically.
• Roles with well-defined, repeatable criteria When skills and experience can be codified (certifications, language fluency, specific technologies), automated scoring is highly effective.
• To enforce consistent initial screening Teams that need standardization across multiple sourcers or hiring managers benefit from consistent criteria application.
• When you need auditability Brainner’s per-criterion justifications and scores create a traceable record of why candidates were advanced or screened out.

Prerequisites and data flow: to use the integration you need API access for Lever (typical admin-level credential) and permission to push candidate updates. Once authorized, Brainner polls Lever for open jobs and new candidate submissions, processes resume content in Brainner’s environment, and posts scores and status changes back to Lever. The integration respects Lever’s candidate IDs to ensure updates map correctly.

Typical field mapping between Lever and Brainner

Common questions about accuracy and customization

Best practices for configuring criteria: start by importing the job description and reviewing the auto-generated criteria. Classify items as mandatory only when lacking them should exclude a candidate (e.g., required license). Use preferred flags for differentiators (e.g., familiarity with a specific framework) and assign weights to reflect priority. Example: for a Senior Java Engineer, make Java experience mandatory, JVM tuning preferred, and cloud experience weighted higher if the role is cloud-centric.

KPIs to track after activation

• Screening time per role Measure average time saved from initial resume receipt to shortlist creation; expect dramatic reductions for high-volume roles.
• Candidate throughput Track number of candidates moved to interview per week to verify quality isn’t reduced.
• False negative rate Periodically audit screened-out resumes to ensure qualified candidates are not being filtered incorrectly.
• Time-to-hire Monitor end-to-end cycle time to confirm efficiency gains translate into faster hires.

Limitations and scenarios to avoid: Brainner works best when candidate qualifications are documented in resumes and when the job has definable, measurable criteria. Avoid relying solely on Brainner for roles where fit is primarily assessed through portfolio review, auditions, or subjective presentation (e.g., creative director portfolios). Also be cautious when job descriptions are vague; automated extraction will inherit ambiguity.

Quick activation checklist (practical steps)

• Admin access and API keys Confirm Lever admin permissions and supply required API credentials to Brainner.
• Import and review job definitions Import a sample job and verify Brainner’s extracted criteria for completeness.
• Set mandatory vs preferred Classify critical items as mandatory to avoid false positives.
• Run a backfill audit Analyze a recent batch of filled roles to compare Brainner scores to actual hires and adjust weights.
• Enable live sync Turn on real-time scoring for new applicants and monitor initial KPIs for 2–4 weeks.

Security and compliance questions

Expected ROI and practical outcomes: organizations typically see substantial time savings — Brainner claims up to 90% reduction in screening workload for eligible roles — and improved consistency in initial candidate selection. Practical ROI comes from reduced recruiter hours spent opening resumes, faster time-to-hire, and clearer audit trails for selection decisions. To realize these benefits, pair the integration with a controlled rollout, KPI tracking, and periodic audits to tune criteria weights.