for recruiting agencies

Put your roles where developers actually are.

terminalhire surfaces your open reqs inside developers' terminals — matched locally to what they're building. No job board. No résumé spam. You only ever receive a lead a developer explicitly approves, with their name attached and a per-partner DPA in place.

01

Connect

Push your open reqs four ways: connect your ATS board (Greenhouse / Ashby / Lever), POST to our API, upload CSV/JSON, or add them by hand in the portal.

02

Match — locally

Your roles surface to relevant developers inside their terminal, matched on their own machine against what they build. We never see their stack or identity. You send nothing, you learn nothing about them — yet.

03

Consented leads

A developer who wants your role explicitly approves a named share. You receive a warm, GitHub-verified lead — with their approved profile slice — and reach out. Per-opportunity, per-partner DPA.

Warm, not cold

Every lead is a developer who saw your role and chose to raise their hand.

Verified

GitHub-backed profiles — real languages, real cadence, not a keyword-stuffed résumé.

Compliant by design

Named-entity consent, per-opportunity, with a per-partner DPA. No scraping, no list-buying.

Four ways to connect

ATS boardGreenhouse, Ashby, or Lever — we pull your reqs automatically.
APIPOST listings JSON with your x-partner-key.
CSV / JSONBulk-upload a file of roles in the portal.
Portal formAdd or edit a role by hand in your dashboard.

Become a channel

Pilot: instant access. Each agency signs a per-partner DPA before any developer lead is delivered.

Already have a key? Open your dashboard → · Download the one-pager (PDF) ↓