Skip to content

Rolero / Platform

One programmable layer instead of 14 fragmented sourcing tools.

Rolero is recruitment infrastructure. A single API and UI that identifies, contacts, and qualifies candidates across fourteen channels — compressing engineering time-to-hire from 47 days to 14, with the same sourcer headcount.

Currently routing 38,412 candidate touches / hour / 612 accounts online
pipeline.rolero.dev / routing-engine Live
# 14 channels · 1 orchestrator
POST /v1/sequences/route
channels: [github, linkedin, wellfound, hackernews, …]
role: "staff-engineer-platform"
dedup: true
daily_touches: 4,200
→ 38,412 touches/hour · 612 accounts
↑ throughput +312% duplicate outreach −81%

§ 01 — Platform

The orchestration layer between your ATS and the open candidate market.

Rolero isn't another sourcing tool. It is the layer your Greenhouse, Lever, Workday, or Ashby instance writes into — and the single surface your sourcers run from. One schema, one queue, one audit log, fourteen channels.

  1. 01 / 04

    A programmable sourcing layer

    Define roles, channels, sequences, and qualification criteria as code or in the UI. Rolero executes that contract across every channel you license — the same role definition produces a GitHub digest, a LinkedIn touches, and a Reddit/Dribbble post in one deployment cycle.

  2. 02 / 04

    One API, one queue, one audit log

    Every candidate touch — outbound message, reply, qualification event, calendar hold — is written to a single event stream your analytics warehouse can subscribe to. Stop reconciling four vendor dashboards. Read one ledger.

  3. 03 / 04

    ATS-agnostic by design

    Rolero is the only platform shipping native, first-party integrations with Greenhouse, Lever, Workday, and Ashby from a single deployment cycle. Your hires, your pipeline stages, your reqs — written back to the system of record without middleware.

  4. 04 / 04

    Built for engineering-first TA teams

    Rolero is engineered by the same team that built talent infrastructure at Google, Stripe, and LinkedIn. Webhooks on every event, a documented REST and GraphQL surface, and a CLI for the recruiters who live in terminals.

§ 02 — Channels

14 sourcing channels. One deployment.

The published baseline. Every customer license ships with the same fourteen channels wired into the same orchestration layer — turn a channel up or throttle it without leaving the Rolero console.

  1. 01

    GitHub

    Code-event triggers, repo affinity, contribution graphs.

  2. 02

    LinkedIn

    Multi-step sequences with reply classification.

  3. 03

    Wellfound

    Startup-talent signal and intent events.

  4. 04

    Hacker News

    Threading, comment graph, hiring-keyword monitors.

  5. 05

    Stack Overflow Talent

    Tag affinity, reputation signals, in-mail routing.

  6. 06

    Dribbble

    Design portfolio parse, role-fit taxonomy.

  7. 07

    Behance

    Project-level hiring signals, Adobe ID bridge.

  8. 08

    Reddit

    Subreddit monitors, threaded reply routing.

  9. 09

    Blind

    Anonymous industry-specific intent streams.

  10. 10

    Twitter / X

    Bio parse, follower-graph signals, mention monitors.

  11. 11

    Slack communities

    Workspace-gated sourcing with consent capture.

  12. 12

    Discord

    Server-thread monitors, role and skills taxonomy.

  13. 13

    Open-source events

    Commit, issue, and maintainer-intent signals.

  14. 14

    Inbound career site

    Application-intake, qualifying forms, ATS write-back.

Configured per customer license, governed by a single policy layer, deduplicated by a single engine.

§ 03 — Dedup engine

Multi-threading is the win. Duplicate outreach is the tax.

When the same candidate is reachable on GitHub, LinkedIn, Wellfound, and the inbound form, the naive approach is to message them on every surface. The enterprise approach is to respect a candidate's inbox. Rolero's patent-pending candidate deduplication engine collapses every alias, email, social handle, and resume-id a candidate is reachable under — across all 14 channels — into a single canonical person record. Your sequence respects that record.

Duplicate outreach reduction
−81%
Identity confidence per match
0.94
Median resolution latency
38ms

Rolero's deduplication pipeline is filed under patent-pending status with the European Patent Office.

Engineer reviewing the Rolero deduplication dashboard on a dark-themed terminal
The deduplication engine, rendered inside the Rolero operator console.

§ 04 — By the numbers

Independently verified. Sourced from public reporting or the platform itself.

94.6%

Candidate response rate

Highest independently verified benchmark in programmatic outreach — Source Global Hiring Index, Q3 2024.

11.7M

Candidates processed in 2024

Across all customer pipelines, deduplicated before sequencing.

612

Active employer accounts

Spanning 23 countries. Average time-to-first-pipeline: 6 days from onboarding.

47 → 14

Engineering time-to-hire, days

Same sourcer headcount. Median across customers hiring 30+ engineers per quarter.

§ 05 — Integrations

Natively integrated. ATS-agnostic. One deployment cycle.

Rolero is the only programmatic sourcing platform shipping first-party integrations with Greenhouse, Lever, Workday, and Ashby in a single deployment. No middleware, no Zapier bridge, no field-mapping spreadsheet — your system of record stays your system of record.

Greenhouse

Bi-directional sync of reqs, candidates, stages, and offers. Custom field support, scorecard write-back, and on-platform interview kit routing.

  • Single-cycle OAuth install
  • Requisition + candidate mirrors
  • EEOC and GDPR audit fields

Lever

Native posting, pipeline stage mirror, archive reconciliation. Archive-state events from Lever surface in Rolero's audit log within 200 ms median.

  • Single-cycle OAuth install
  • Pipeline stage parity
  • Archive and offer sync

Workday

Recruiting-module write-back via Workday's SOAP and REST tenants. Supports tenant-scoped tokens and consent capture for cross-region operations.

  • Single-cycle SOAP + REST
  • Tenant-scoped tokens
  • Cross-region consent capture

Ashby

Direct integration with Ashby's analytics-grade schema. Pipeline-stage writes, custom field support, and feedback survey routing.

  • Single-cycle API install
  • Custom field parity
  • Feedback and survey routing

Compliance posture

SOC 2 Type II · GDPR-DPA · CCPA — certified across all 14 channels.

Book a Pipeline Demo