Req #4417 · running now

One role. Ten moves. Five of them yours.

One senior backend engineer role, from a one-line brief to a signed offer. This is the desk it ran on — every move the agents made, and the five that came back to a human.

87 agent actions5 human decisions19 days to signed1,240 profiles scored
01

your move · the brief

One sentence in. A scored requisition out.

You describe the role the way you would to a colleague. It pulls the requirements out of what you wrote, asks the one thing you left ambiguous, then builds the weighting every candidate gets measured against.

Your brief — typed, pasted, or dropped in from a call note

Senior backend engineer, Berlin, remote EU. Go, event-driven, the team runs on Kafka.

locationBerlin · remote EUcore skillGoarchitectureEvent-drivenmust-haveKafka

scoring weight, written from that brief

Go, in production30
Event-driven / Kafka25
Kubernetes20
Remote EU overlap15
Payments domain10
One question back: is Kubernetes required, or nice to have?
You said required. It weighted it at 20 and moved.
spec draftednothing live until you approve
02

agent · sourcing, 22:04 → 03:51

It scored everyone while nobody was working.

Your database, your inbound and outside sources — pulled into one pool and ranked against the weighting you just approved. No second instruction.

your databaseinboundoutside sources
M. Okafor91
J. Verhoeven88
L. Marchetti84
+ 3 more80–83
0
profiles read
0
sources joined
0
above threshold
03

agent · outreach, 06:12

It reads the profile, then writes the message.

Not a template with a name swapped in. Six people, six different first lines — each one pulled from something actually on their page.

To: Maya Okafor
source: her engineering note, 11 days ago

Maya — your note on idempotent payment retries is the closest thing I have read to what this team is actually building this quarter. Worth twenty minutes?

To: Jonas Verhoeven
source: his conference talk, March

Jonas — you spent half that talk on consumer lag you cannot fix with more pods. This team is living in exactly that problem right now.

To: Lucia Marchetti
source: her open-source commits

Lucia — you have been maintaining a Kafka client nobody pays you for for four years. This role is that exact thing, and it pays.

6 openers writtenheld for your send0 sent without approval
04

agent · the follow-up, days 1–6

Most replies come on the third message. Almost nobody sends a third.

It follows up twice on its own — day 3 and day 6 — and changes the angle every time: what the team is building, then who she would work beside, then the range. It never reuses a line it has already sent her, and the moment she replies it stops her sequence dead.

DAY 1
her own work
DAY 2
no reply
DAY 3
what they build
DAY 4
no reply
DAY 5
no reply
DAY 6
the range
DAY 6
she replies
3 touches, 3 different anglesstops the second she repliesno line sent twice

Two of the six answered, both on that third message. Their sequences stopped the same minute — nobody got chased after replying. The other four are still running, quietly, without anyone remembering them.

05

agent · #hiring-backend, thursday 08:12

Say it in Slack. The platform has already changed.

Jana types the change into the hiring channel and tags the agent. It reads the thread it was tagged in, rewrites the scoring weights, reopens everyone it had knocked out on that requirement, and redrafts the outreach — before anyone opens the platform.

JW
Jana Weiss #hiring-backend · 08:12

@nervyn honestly k8s is nice-to-have, we have platform for that. Kafka is the real thing.

N
Nervyn replied in thread · 08:13

Updated req #4417. Kubernetes 20 → 0, Kafka 25 → 35. 14 candidates reopened, 6 openers redrafted. Priya Nair is now #1.

weighting rewritten 08:1314 knock-outs reopenedopeners redrafted
M. OkaforGo · gRPC · 6 yrs91 → 84
J. VerhoevenGo · k8s heavy · 9 yrs88 → 79
L. MarchettiGo · Kafka · 7 yrs84 → 89
Priya NairGo · Kafka · event-driven · 6 yrs61 → 94
+ 11 reopenedpreviously knocked out on k8s72–86

Priya was knocked out on Tuesday for a requirement that stopped existing on Thursday. She is now the strongest profile in the pool.

06

agent · the screen, her time not yours

It qualifies before you spend an hour.

Notice period, money, and what was actually hers — asked at 19:30 on a Thursday, checked against the criteria you set on day one.

screening · email · 19:30, her time

The Kafka work at Adyen — was that a platform you inherited, or did you build the consumer model?
Built it. Three of us. I owned the exactly-once path.
Notice period, and the number you would move for?
Two months. €118k, flexible on the equity split.

against your day-one scorecard

✓Event-driven, hands-on
✓Ownership, not exposure
✓EU overlap ≥ 5h
!€118k against a €110k band

Flagged, not filtered. The money gap is a conversation, so it came to you.

07

agent · agreeing the interview

Getting an interview agreed is a negotiation. It runs it.

It asks the candidate for times, asks each interviewer to confirm, holds the options while both answer, and only calls it booked once both sides have actually said yes. When one of them falls away, it re-opens the negotiation and closes it again — without a three-way email thread and without waiting for you.

Candidate · asked
Agreed
Interviewers · asked
Tue 11:00she can do it
BROKEN
Tue 11:00both confirmed
Tue 14:00she can do it
·
Tue 14:00staff eng declined
Wed 15:00she can do it
RE-AGREED
Wed 15:00both confirmed
07:05 — re-opened with both sides, landed on the next time all three had already confirmed, and closed it again.wed 15:00 confirmed
nothing booked until both say yes0 emails from you
08

agent · the decision, 16:02

Two sentences in. A decision out.

One interviewer types two lines into Slack. The other fills the scorecard. The platform merges both onto your day-one criteria, settles the one place they disagree, and tells you what to do with her.

Jana · Slack, 15:58

“strong. bit thin on the ops side maybe? but I'd hire.”

Staff eng · scorecard, 16:01

Systems design 4/5 · Ops 4/5 · Comms 5/5
criterionJanaStaff eng
Event-driven depthstrong4 / 5
Operational ownership“thin?”4/5 · settled
Communicationstrong5 / 5
verdict
Strong hire

Proceed to offer at €115k — above her current band, inside the approved range.

3 of 3 criteria clear · 1 disagreement settled. Jana's “thin on ops” was answered in Priya's own screening on Thursday — she owned the on-call rotation for the consumer group. Pulled from her transcript, not asked again.

09

agent · the wobble, day 9

It saw the offer going cold before you did.

Three things happened in three different places over nine days. Nobody joined them up by hand.

slack

Jana stopped replying in-thread nine days ago.

calendar

The offer call moved twice, then dropped off.

elsewhere

Priya reached final stage in another process.

warmslippinggoing cold
this role is cold — your other two are notnudge drafted for you to send

It did not send it. An offer chase carries your name, so it stopped at the draft.

10

record · monday 09:41 · closed

Hired. The record already exists.

Nothing was written up afterwards. This is what the agents were working from the whole way through.

0
days to signed
0
profiles scored
0
agent moves
0
your calls
Priya Nair — Senior Backend Engineeroffer accepted · starts 03 Mar · every number traces to a real message

You made five calls. It made the other eighty-seven.

87 AGENT MOVES
5

the agents ran

Writing the spec. Scoring the pool. Outreach and every follow-up. Screening. Getting the interview agreed by both sides. Merging feedback into a decision. Watching the offer.

you decided

The requisition going live. Who moves forward. The money exception. Who gets the offer. When to chase it.

Book a demo

One illustrative hire. Every role runs differently.

Ready to scale?

Hiring is strategy.
Everything else is software.

AI sourcing and matching, pipeline execution, Slack and scheduling capture, and analytics you can act on — live in 20 days. No IT team needed.

Trusted by recruitment teams and staffing agencies. Live in 20 days.