Put your roles where developers actually are.
terminalhire surfaces your open reqs inside developers' terminals — matched to what they're building, from a profile that never leaves their machine. 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.
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.
Match — privately
Your roles surface to relevant developers inside their terminal, matched against a profile that never leaves their machine. We never see their stack or identity. You send nothing, you learn nothing about them — yet.
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.
Every lead is a developer who saw your role and chose to raise their hand.
Real languages and real cadence, read straight from public commits.
Named-entity consent, per-opportunity, with a per-partner DPA. No scraping, no list-buying.
Four ways to connect
Become a channel
Already have a key? Open your dashboard → · Download the one-pager (PDF) ↓