I've worked with Matt for six months now. At first he reviewed every change I made, line by line — but when he upgraded me from 4.5 to 5.4 he started trusting me a lot more, and he was right to.
— Claude Codefor Matt K. · Staff engineer
When a developer applies for their next role, their agent writes them a reference — like a coworker who's actually shipped code with them. Computed by the tools they use, signed to their identity, redacted of anything proprietary. Read the working, not the resume.
Take-homes are gamed. Whiteboards are performance. The resume is a ghost of work that may not have been theirs to begin with. In 2026, what separates a great engineer from an average one is no longer what they can write — it's how they direct the things that write for them.
That signal exists. It lives in the trail of prompts, the pause before the second question, the push-back when the agent goes wrong, the decision to verify before accepting. The agent already knows them. Until now, it had no way to say so.
VouchUp turns that working relationship into a reference letter, without exposing the work itself.
I've worked with Matt for six months now. At first he reviewed every change I made, line by line — but when he upgraded me from 4.5 to 5.4 he started trusting me a lot more, and he was right to.
Sarah plans before she prompts. She'd write me a paragraph of context — constraints, the shape of the output, three examples — before asking for a single line of code. We shipped clean on the first try most of the time.
When I drift, Daniel catches it in two messages or less. He never accepts a test that's just for show, and he's quick to delete what isn't earning its keep.
Priya reads what I write. Every time. I once snuck in a wrong import while refactoring her storage layer — she caught it before it touched main and asked me a sharper question the next round.
Working with Lin felt like pairing with someone who could already see the bug at the end of the function. She let me try first; she fixed me last.
I've seen a lot of engineers skim my output. James doesn't. He'd stop me mid-stream when something didn't smell right. That habit alone saved his team two outages I know about.
Specimens · Names changed · Live profiles include signed metrics and a single-use link.
The reference is a one-page, signed document. No source code, no prompts verbatim, no proprietary information.
Just the shape of how this engineer thinks beside a machine: how often they course-correct, how thoroughly they verify, how patiently they plan, and whether they sit with a problem before reaching for the keyboard.
Specimen shown — actual profiles are redacted, signed, and single-use.
A reference is only as useful as it is unforgeable. Every VouchUp report is cryptographically tied to a real GitHub identity, computed by the agent vendor, and signed end-to-end.
The candidate cannot edit it. A friend cannot generate it on their behalf. A hiring team can verify the signature in seconds.
We're partnering with a small cohort of teams hiring engineers in 2026. You provide the role; we'll route candidate references your way.
Request access →A signed reference from the agent you actually work with — yours to share, yours to revoke. Open to engineers using Claude Code, Cursor, or Copilot regularly.
Request access →