AyHire
Hire developers

Getting started

AyHire finds developers from the work they have done in public, judges it against what your role needs, and tells you who to talk to first, with a link behind every claim. Use it on the website or from your AI agent: they share the same roles and the same shortlist.

1. Set up (five minutes)

  • Sign in at ayhire.com/auth/sign-in with your work email. AyHire emails you a link; there is no password.
  • Make a workspace for the company you are hiring for. You start with a personal one. The switcher at the top of the sidebar has New workspace and Members and invites: teammates you invite see the same roles, decisions and shortlist.
  • Connect your agent (optional). Integrations has one line to paste into Claude Code, Codex, Cursor or any agent that can run commands. It installs AyHire, signs you in through the browser and keeps the key on your computer; the key never appears in the chat. Any agent that speaks MCP can also connect with an API key from the same page.

2. Run your first role

Describe the role the way you would brief a recruiter. On the website, that is the form on Home; with an agent, just ask. AyHire then:

  • suggests what the role needs (criteria marked must, important or nice). Edit them on the role page: they are what everyone is judged against;
  • finds the people behind the code that matches the role. Your agent can also search profiles and commits, and the contributors of projects you name;
  • reads each person's public work and gives a verdict per criterion (strong, some, unknown or none), each with the links it rests on;
  • checks who looks open to a move;
  • makes a call on each person (a pick, set aside, or not looked at yet), with one line of why and one thing to check.

You decide: Shortlist or Not now. AyHire never contacts anyone.

Things to ask your agent

  • “We need a senior Rust engineer who has worked on database internals: storage engines, transactions, query execution. Europe or US time zones. Find me 5 people worth contacting, with evidence I can check for each.”
  • “I'm hiring a client-facing AI deployment strategist, about 80% sales and 20% technical. What can GitHub show for that, and who is worth a call?”
  • “Who builds the most-used open-source vector databases? Which of them look open to a move?”
  • “Compare these three GitHub profiles for our GTM engineer role: …”
  • “Score the new people you found for the Rust role, then show me who to talk to first.”

A brief that works

  • Say what the person will build, not just a title.
  • Separate must-haves from nice-to-haves.
  • Name the projects, communities or kinds of companies where people like this work.
  • Partly technical roles work too (sales engineers, developer advocates, deployment strategists). AyHire judges the technical part and tells you what GitHub can't show.
  • Leave out personal traits such as age, gender or nationality: AyHire does not use them. Location works only as a filter you ask for. It matches what people wrote on their profile, and people who list none show as unknown, never as a mismatch.

3. What AyHire can't see

  • Private work. Most engineers' best work sits in private company repos. AyHire reads public GitHub only, so a quiet profile is unknown, not weak. Ask candidates about the work you can't see.
  • Work outside GitHub, such as GitLab, papers or talks, unless their GitHub links to it.
  • People skills. Selling, leading, how someone comes across in a room: check these in a conversation.
  • Location and time zone, unless people state them on their profile. AyHire doesn't guess.
  • Whether someone is really looking. Availability is a best reading of public signals, such as a recent job change or “open to work”, always shown with its evidence. Employers on profiles can be out of date.
  • Contact details beyond what people made public, or what an email lookup you ask for finds (marked as likely, or a guess).

4. Costs and limits

Searching GitHub and reading someone's evidence are free. An analysis (reading someone's work in depth), a judgement against a role, availability checks and email lookups use paid services, so each account has an hourly allowance: 20 new analyses, 40 judgements and 30 lookups. A saved analysis from the last 30 days is free and instant. The sidebar shows the analyses left this hour, and when you reach a limit, AyHire says which one and when it resets.

5. Your data, and theirs

The Privacy Policy lists what AyHire keeps about you and about the developers it reads. It never reads private repos or full source code.