Announcing o11's backing from Y Combinator.

# AI for Greenhouse

## AI that moves the pipeline inside Greenhouse.

- Move candidates through stages with the agent in the loop.
- Nudge interviewers to fill scorecards without follow-up email.

# Senior Engineer · Platform

Open · 9 candidates

## Stages Interview Plan Job Setup Notes

Stage: All Source: All Sort: Date applied

### Application Review 3

AY  
A. Yusufa.yusuf@mail.com  
LinkedIn · 2d  
0/3 reviews Move

MI  
M. Iverson maya.i@mail.com  
Website · 3d  
0/3 reviews Move

RK  
R. Klein r.klein@mail.com  
Indeed · 4d  
0/3 reviews Move

### Phone Screen 3

EK  
E. Kobayashi eko@mail.com  
Referral · 5d  
1/3 reviews Move

FS  
F. Suri f.suri@mail.com  
LinkedIn · 6d  
1/3 reviews Move

KP  
K. Park k.park@mail.com  
Website · 7d  
1/3 reviews Move

### Onsite 2

DL  
D. Lim d.lim@mail.com  
Referral · 10d  
2/3 reviews Move

JB  
J. Bauer j.bauer@mail.com  
LinkedIn · 12d  
2/3 reviews Move

### Offer 1

MT  
M. Tran m.tran@mail.com  
Referral · 18d  
3/3 reviews Move

### Hired 0

Drag here when offer accepted

## Pipeline review

AT  
Move E. Kobayashi to Onsite and schedule for Thu 4/24.

## o11 for Greenhouse: an AI agent layer for the ATS

o11 is an AI execution layer that runs inside Greenhouse. The agent moves candidates through stages, nudges scorecards, and helps with scheduling — without sending a coordinator into a side spreadsheet to track who still owes what to which req.

If you have searched for **AI for Greenhouse**, a **Greenhouse AI agent**, or an **alternative to Greenhouse’s built-in AI** for actual workflow execution, the question is the same: does the AI summarize candidates or move candidates.

## What teams use o11 for in Greenhouse

- **Candidate stage moves.** Advance candidates through stages with the right tags, fields, and notes attached.
- **Scorecard nudges.** Keep interviewers on time and unblock stuck panels without manual follow-up email.
- **Interview scheduling.** Coordinate panels across calendars and rooms with the agent in the loop.
- **Pipeline reporting.** Generate role-by-role status briefs that recruiters and hiring managers can actually read.

## Why o11 differs from Greenhouse-native AI

Greenhouse’s AI features focus on summaries, drafts, and recommendations. They describe a candidate, but the stage move, scorecard nudge, and scheduling email still end with a human clicking through screens. o11 operates on the pipeline. The chat is the control surface, Greenhouse is where the work lands.

## Built for teams that live across systems

Greenhouse is one part of a much larger recruiting stack — usually paired with calendar, email, an HRIS, sourcing tools, and a careers site. o11 is positioned to act across all of them. A panel debrief becomes a stage move, a scorecard nudge, an HRIS pre-fill for the offer, and a Slack message to the hiring team without the coordinator stitching tools together by hand.

## Where Greenhouse teams typically start with o11

- **Recruiters** with stage moves, candidate notes, and outreach.
- **Coordinators** with scheduling and scorecard chase.
- **Hiring managers** with role-level briefs and decision prep.
- **Talent leadership** with pipeline reporting and audit trails.

## How o11 respects Greenhouse permissions

The agent operates with the user’s own user role. Job-based permissions, EEO and confidentiality 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 site admin.

## FAQ

**Does it screen candidates?**  
Only as configured by the recruiting team and EEO policy.

**Does it touch offers?**  
Yes. It can prepare and route, but humans approve.

## Ready to see o11 inside Greenhouse?

[Book a demo](/content/demo/index.html)