Hiring

Hire without re-arguing the bar every round.

A hiring loop runs for weeks, across interviewers who rarely compare notes in real time. The bar — the scorecard, the comp band, the must-haves — gets decided once, early, in a conversation with your assistant. Then it re-drifts anyway, because nobody wrote it down where the next interviewer would actually see it.

You keep working in ChatGPT or Claude the way you do now. Giraffe is where the bar stays put.

Why the bar drifts round to round

You work out the shape of a role with your assistant — how many, what band, what actually matters versus what’s nice to have. That reasoning is good the day you have it. But a loop has several interviewers, spread across weeks, and the version each of them is working from is whatever they remember from the kickoff, or whatever the last candidate happened to ask.

So the band creeps between rounds, the scorecard changes shape, and a strong candidate gets a different bar than a weak one got the week before — not because anyone decided that, but because nobody had the original conversation in front of them.

What Giraffe does instead

You keep working out the plan the way you already do. When the shape is set, you say so — “Save the hiring plan — roles, bands and the scorecard.” — and it lands sorted: what’s current, what you decided, what’s still open. Every interviewer can open the same project before their round instead of asking you or guessing.

When a band moves, you say that too — “Update the backend band — it’s $150 to 175k now.” — and the number every interviewer sees updates with it, dated.

What that looks like

Say you’re running two backend hires and a design hire this quarter. You worked out the bands, the must-haves and the scorecard across a few conversations. Here’s the project every interviewer opens before their round:

Q3 hiring plan

Two backend, one design

Updated 3 days ago
Current
Roles open
2 backend, 1 design
Backend band
$150k–175k
Design band
$130k–150k
Target start
Early Q4
Decisions
  • Comp bands set before the first interview, not after a candidate asks.
  • Same scorecard for every backend candidate: system design, then a paired debugging round.
Open questions
  • Open the design req now, or wait until a backend hire lands?
Notes
  • Two of the last three backend candidates asked about the band before round two. Leading with it saves a round.
Recent changes

3 days ago · Claude

Backend band$145k–170k$150k–175k

1 week ago · You

Roles open2 backend, 1 design

Nothing is captured automatically. Giraffe has no view of your conversations — only what you ask your assistant to save, or type in yourself.

A candidate in round three gets the same bar a candidate in round one did, because the bar is written down and dated, not carried in whoever’s memory happens to be freshest. When it does move, everyone sees the same new number at the same time.

Most rounds, reading the project is all an interviewer needs. When the plan itself needs rework — the design req, a band that’s not landing offers — you can pick it up in ChatGPT or Claude with the whole plan already in front of it, which is exactly how Giraffe works.

Set the bar once. Every round reads the same one.

Free while we’re in beta. An email code gets you in — no password to invent, no card, nothing to install.

Works on every Claude plan — Free allows one custom connector at a time, and on Team or Enterprise an owner has to add it first. ChatGPT needs a paid plan, on the web, with Developer mode turned on, and it won’t work inside a ChatGPT Project. Reading works there; whether saving does depends on your plan and your workspace, and ChatGPT asks you to approve each save. Gemini isn’t supported yet — its app doesn’t allow outside connections. See the setup guides.

Related: keep the decisions you make with AI · keep a round moving without re-briefing every meeting · all use cases.