Announcing o11's backing from Y Combinator.

# AI for Lever

## AI that triages the recruiting pipeline.

- Triage active reqs and surface stuck candidates.
- Draft candidate replies grounded in the role context.

## o11 for Lever: an AI agent layer for recruiting

o11 is an AI execution layer that runs inside Lever. The agent triages the pipeline, drafts candidate communications, and updates requisitions — without sending a recruiter into a side spreadsheet to track who is stuck where and which req still needs an owner.

If you have searched for **AI for Lever**, a **Lever AI agent**, or an **alternative to ATS chat tools** for actual workflow execution, the question is the same: does the AI describe the pipeline or move the pipeline.

## What teams use o11 for in Lever

- **Pipeline triage.** Surface stuck candidates by req, stage, and last activity so recruiters can act, not scroll.
- **Candidate communications.** Draft replies grounded in the role, conversation history, and stage context.
- **Requisition updates.** Keep req fields, owners, and approval status accurate as the search evolves.
- **Cross-team handoffs.** Move candidates between recruiters, coordinators, and hiring managers with full context.

## Why o11 differs from Lever-native AI

Lever’s built-in AI features focus on suggestions and summaries. They explain a candidate’s history, but the stage move, the reply, and the requisition update still end with a human clicking through screens. o11 acts on the pipeline. The chat is the control surface, Lever is where the work lands.

## Built for teams that live across systems

Lever is one part of a much larger recruiting stack — usually paired with calendar, email, an HRIS, sourcing tools, and team chat. o11 is positioned to act across all of them. A debrief becomes a stage move in Lever, a scheduling note to the candidate, and an HRIS pre-fill for offer prep without the recruiter stitching tools together by hand.

## Where Lever teams typically start with o11

- **Recruiters** with pipeline triage and candidate replies.
- **Coordinators** with scheduling and chase work.
- **Hiring managers** with weekly role-level status briefs.
- **Talent leadership** with cross-req reporting and audit trails.

## How o11 respects Lever permissions

The agent operates with the user’s own role and access scope. Posting visibility, sensitive information settings, and audit history apply exactly the way they do in the UI. Nothing is bypassed. That is what makes o11 deployable in talent orgs that cannot trust a tool that runs as a single over-privileged super-admin.

## FAQ

### Does it send candidate emails on its own?

Drafts go to recruiters; sending requires human approval by default.

### Multi-team setups?

Yes. Scoped per team, role, and recruiter.