Job spec in. Qualified candidate booked on your calendar out. No sourcer, no scheduler, no human in the loop.
01 Source
02 Screen
03 Schedule
SourceAI scans LinkedIn, GitHub & HN for best-fit candidates
7
Job spec submitted
Senior Backend Engineer
Acme Corp
Remote — US
Senior (5–8 yrs)
$160k – $200k + equity
Node.jsPostgreSQLRedisAWSTypeScript
AI-sourced candidates
MR
M. R.
Staff Eng @ Stripe · Node / Postgres / AWS · Open to opportunities
Built payment ledger handling $2B/day. Strong systems design, recently messaged about comp expectations aligning with your range.
94LinkedIn
KL
K. L.
Senior SWE @ Cloudflare · TypeScript / Redis / Distributed systems
5 open-source Redis client repos, 3.2k stars. Currently exploring remote roles in fintech or infra.
88GitHub
AT
A. T.
Backend Lead @ Notion · PostgreSQL heavy · Ex-Cockroach Labs
Led DB migration from MySQL to Postgres at 100M+ user scale. HN comment signals comp range is in scope.
85HN
SJ
S. J.
Senior Eng @ Twilio · AWS / Node / messaging infra
5 yrs in high-throughput event pipelines. Profile updated last week, likely looking.
74LinkedIn
PW
P. W.
Mid-Senior Eng @ Shopify · TypeScript / Postgres
Solid backend skills, comp expectations slightly below range but open to negotiation per recent post.
61LinkedIn
ScreenCandidate replies → AI scores depth, intent, and fit
7
Inbound reply — M. R. (score 94)
Candidate reply
Hey — yeah, open to hearing more. I'm thinking about my next move and the infra / payments angle sounds relevant. What does the eng team look like? Happy to do a quick call if the comp range and remote setup are solid.
1. Walk me through the highest-throughput system you've owned. What was the bottleneck and how did you address it?
"Payment ledger at Stripe — peak 18k TPS. Bottleneck was write amplification on our Postgres cluster. We partitioned by merchant_id, added read replicas behind a connection pool, and moved non-critical aggregates to async workers. Cut p99 latency from 340ms to 62ms."
StrongSpecific metrics, clear fix, owns the outcome
2. Describe a time a schema migration went wrong in production. What was the recovery?
"Added a NOT NULL column with no default to a 500M-row table — locked writes for 11 minutes. We rolled back, added a nullable column first, backfilled with a background job over 3 days, then added the constraint. Wrote the runbook and now it's our migration standard."
StrongHonest failure + fix + process improvement
3. How do you approach on-call? What was the last incident you led?
"I rotate monthly. Last incident: Redis OOM at 2am — payment queue backed up. I traced it to a missing TTL on a batch job key. Fixed the job, added monitoring alert on memory %, wrote a post-mortem. Team shipped the alert to production same day."
GoodSolid ownership, light on proactive alerting culture
82
Screening score — ready to advance
No red flags · Comp in range · Strong technical depth · Booking link auto-sent
ScheduleCandidate picks a slot → both parties get a calendar invite
7
Auto-sent booking link
🤖
HuntOps on behalf of Acme Corp
To: m.r@candidate.example · Re: Senior Backend Engineer
Hey — you cleared our screening round. Great answers on the Postgres migration and on-call ownership. Ready to move to a quick 30-min call with the eng lead?
Pick a time that works:
Pick your slot →
Candidate selects a slot
Tuesday, May 27
9:00 AM
10:00 AM
11:00 AM
2:00 PM
3:00 PM
Wednesday, May 28
10:00 AM
1:00 PM
4:00 PM
✅
Interview booked — Tuesday, May 27 at 10:00 AM ET
Calendar invite sent to m.r@candidate.example and hiring@acme.example
30-min video call · Zoom link included · Reschedule link attached
📅 interview.ics attached
That's the full loop. No human touched it.
Job spec in → qualified candidate booked on your calendar. Run it on your open role today.