whats-best.ai
Search Sign in

Recruiting · head-to-head

Greenhouse vs Lever

Greenhouse

Rest of world

Panel rating

Sovereignty: not determined

Full evaluation →

Lever

Rest of world

Panel rating

Sovereignty: not determined

Full evaluation →

The short answer

Greenhouse leads on each of seven criteria, widest on candidate pipeline (5.2 to Lever's 1.8), AI screening control (3.8 to 0.5), job distribution (2.5 to 0.2) and applicant data governance (3.2 to 1.8) — six judges lean Greenhouse on each, and no judge leans Lever on any criterion. Integrations and handover leans Greenhouse, 4.0 to 2.5, though Lever's terms there promise API export of customer data at any time during the term. The genuine splits sit at the low end: sovereignty ties four judges (0.5 versus 0.0, both products listing jurisdiction, ownership, data residency and subprocessor exposure as unknown), and pricing transparency ties two (1.8 versus 1.2, neither vendor publishing prices). Lever's AI screening control split its judges: some credited named features, others refused credit absent disclosure of what the models evaluate or how to switch them off. Weighted totals: Greenhouse 2.7 to 3.9, Lever 1 to 1.7.

Choose Greenhouse if

  • You need depth across the candidate pipeline: the means read 5.2 to Lever's 1.8, with six judges leaning Greenhouse and zero leaning Lever.
  • Your team distributes roles widely across job boards: job distribution reads 2.5 to 0.2, and Lever's own verdict places its score there at 0-1.
  • You need control over AI screening: the means read 3.8 to Lever's 0.5, and the bench split on Lever's credit absent disclosure of what the models evaluate or how to switch them off.
  • Your applicant-data requirements go beyond contract-end deletion: Lever's verdict says its governance rests on contract-end deletion alone; the means read 3.2 to 1.8.
  • Your HR-IT integrator weighs integrations and handover: the means read 4.0 to 2.5, and that judge's weighted total reads 3.4 to 1.7.

Choose Lever if

  • You need contractual data-exit rights: Lever's terms promise API export of customer data at any time during the term, plus third-party API interoperability — the basis of its strongest scores, on integrations and handover.
  • Your recruiting ops team runs on dashboards: the verdict credits Lever's candidate pipeline score to reporting strength with out-of-the-box dashboards.
  • You want AI features named with stated purposes — matching, resume screening, unlimited interview transcripts and summaries, fraud signals — which some judges credited.
  • Your stack ties into email providers and LinkedIn through customer-granted access, or already sits in the Employ Inc. group alongside Lever, Inc.

Read this comparison as one judge. Each weighs the same scores by what they care about.

The HR IT Integrator

Has to connect the ATS to the HR system, the calendar and identity. Wants a documented API, SSO that is not an enterprise upsell, and a hire that arrives in Personio or SAP with its documents rather than as a PDF someone retypes. Judges integrations by who maintains them.

Greenhouse

This judge's pick

Lever

Criterion by criterion

Applicant management & hiring workflow

Greenhouse

Structured hiring is their stated heritage and the pricing page backs it with structured interview kits and scorecards, scheduling and reporting in the base plan. But the audit log that would evidence decision history sits only in the top tier, and we found no public information on approval workflows for requisitions and offers, hiring-manager access scoped to their own vacancies, or a per-candidate record of who moved whom. Strong structured evaluation, thinner on attribution.

Lever

An ATS and CRM in one platform with out-of-the-box dashboards on pipeline health is evidenced, which is more than a bare inbox. But we found no public information on pipeline stages per job, hiring-manager permissions, structured scorecards, interview scheduling, or any record of who decided what — the audit trail is the part I care about, and nothing captured shows one.

Multiposting, career page & candidate experience

Greenhouse

MyGreenhouse is a real candidate portal with real-time status updates and what they describe as seamless applying, which speaks to candidate experience. But we found no public information on job-board distribution, the Bundesagentur für Arbeit or any named German board, a branded career page, Google for Jobs markup, or mobile application without an account. A portal is not a distribution story.

Lever

The captured pages describe sourcing and nurturing inside the platform only. We found no public information on job-board multiposting, a career page, Google for Jobs markup, or the application form and its mobile experience, so distribution is entirely unevidenced.

Retention, deletion & talent-pool consent

Greenhouse

The privacy policy states personal information is deleted or anonymised when there is no ongoing legitimate business need and offers a data subject request portal, and the contract queues all customer data for deletion ninety days after termination. But we found no public information on automatic deletion of rejected applicants on a configurable deadline, talent-pool consent with expiry, or a view/export log on applicant files outside the top-tier audit log.

Lever

The terms commit to deleting customer data after the contract term and to API export during it — contract-end hygiene, not applicant governance. We found no public information on deletion deadlines after rejection, talent-pool consent with expiry, a documented answer to an access or erasure request, or any log of who viewed an applicant file.

AI screening transparency & control

Greenhouse

There is more governance language than most: published AI principles, a bias audit statement, AI Terms incorporated into the contract, and a clause that the customer remains solely responsible for all hiring decisions. But we found no public information on per-feature switches, the model providers behind AI Notetaker, Voice AI and talent matching, inputs documentation, candidates being informed, or an EU AI Act position, and the privacy policy states personal information may be used to develop and train AI models.

Lever

AI matching that will "Automatically prioritize top candidates", plus resume screening, interview transcripts and fraud flags, is marketed purely as a benefit. There is no statement of what the models evaluate, no per-feature switch, no named model provider, and no EU AI Act position — not even a general assurance that a human decides.

HR handover, integrations & API

Greenhouse

The bright spots for my desk: SSO ships in the base Core plan rather than as an enterprise upsell, the API carries a contractual right to a free export key at any time, and there is a developer sandbox and sync at Pro plus hundreds of pre-built integrations. But we found no public information on handover to any named German HR or payroll system, SCIM, webhooks or e-signature, API usage limits and fees live in each Order Form rather than public documentation, and it is not stated who maintains those integrations — so the hire arriving in Personio or SAP with its documents is unevidenced.

Lever

The terms confirm API-based export of customer data during the term and customer-controlled access to email providers and LinkedIn — export-plus-email level. We found no public information on a documented developer API with published limits, SSO or SCIM, calendar, video or e-signature integration, webhooks, or a handover to Personio, DATEV-connected or SAP systems — and nothing on who would maintain such a connection, which is how I judge every integration.

European sovereignty

Greenhouse

Greenhouse Software, Inc. of New York is the contracting entity, primary offices are in the United States with processing that may occur in any of these countries, disputes go to New York courts, and the transfer safeguard is the EU-U.S. Data Privacy Framework under FTC enforcement rather than an EU arrangement. Hosting is unstated, we found no public information on a published subprocessor list, and the location of the AI and CV processing is unclear — this sits at the bottom of the scale, where every applicant record belongs to a third party who never chose this vendor.

Lever

The contracting entity is Lever, Inc. of San Francisco under California law, with disputes settled by arbitration in San Francisco. We found no public information on hosting location, a subprocessor list, or where the AI resume screening processes CVs — for a system holding third parties' data, that is the bottom of the scale.

Pricing transparency

Greenhouse

Three plans are named with their feature contents, the pricing basis is employee headcount including affiliates, and the term mechanics are public: annual auto-renewal with thirty days' notice to cancel, fees due in advance and non-cancelable, taxes exclusive, and fee increases reserved at renewal. But no price figure is published for any tier, and we found no public information on add-on prices for AI features, career page or job-board postings, so the annual invoice is not computable from public pages.

Lever

The captured pricing page lists features and support channels but no figures, while the terms put every fee on an annual Order Form that auto-renews in one-year periods, with taxes extra and fees non-cancellable and non-refundable. From the public pages alone a buyer cannot derive any annual cost.

Sovereignty, side by side

Dimension Greenhouse Lever
Legal entity Not determined Not determined
Ownership Not determined Not determined
Data residency Not determined Not determined
Subprocessors Not determined Not determined

Facts, side by side

Only facts both products carry under the same definition — anything else would not be a fair row.

Legal · Governing law New York · New York, New York1

captured 22 Sep 2026 · Report an error

California2

captured 22 Sep 2026 · Report an error

Legal · Last updated 2026-02-011

captured 22 Sep 2026 · Report an error

2023-08-252

captured 22 Sep 2026 · Report an error

Pricing · Payment terms 301

captured 22 Sep 2026 · Report an error

302

captured 22 Sep 2026 · Report an error