# Terminalhire

> Developer jobs and paid bounties, matched in the terminal. Your code is your résumé: roles and scoped bounties are matched from what you are actually building, and a claimed bounty pays out when the poster accepts the merged work. Matching runs on the developer's machine against a profile that never crosses the wire.

Terminalhire has three audiences: developers (install the CLI, get matched, claim bounties), founders (post a scoped bounty on their own repo and pay on acceptance), and recruiters (reach developers through work they already shipped).

## Docs

- [Getting started](https://terminalhire.com/docs/getting-started): install, init, first match
- [How matching works](https://terminalhire.com/docs/how-matching-works): the on-device matcher and what it reads
- [Proof of Work](https://terminalhire.com/docs/proof-of-work): the public credential built from merges other teams accepted
- [Claims](https://terminalhire.com/docs/bounties-and-claims): taking an issue to a merged PR and getting paid
- [Post a bounty](https://terminalhire.com/docs/post-a-bounty): for the person paying
- [CLI reference](https://terminalhire.com/docs/cli-reference): every command
- [MCP](https://terminalhire.com/docs/mcp): use terminalhire from any AI editor
- [Privacy architecture](https://terminalhire.com/docs/privacy): what crosses the wire and what never does

## Key pages

- [Install](https://terminalhire.com/install): one-command install, requirements, tiers
- [For developers](https://terminalhire.com/developers)
- [For founders](https://terminalhire.com/founders)
- [For recruiters](https://terminalhire.com/recruiters)
- [Proof](https://terminalhire.com/proof): count your merges into repos that do not publicly belong to you
- [Changelog](https://terminalhire.com/changelog)

## Optional

- [Explore](https://terminalhire.com/explore): live sample of matched roles and bounties
- [Projects](https://terminalhire.com/projects): open repos with claimable work