Priya Raghunathan
Senior Platform Engineer
- Based
- Austin, TX · Remote ok
- Track
- 8 years · Stripe, Fastly
- Go
- Kubernetes
- Terraform
- Postgres
Recruiter-only · Bring your own ATS
Swipe through the pipeline you already have.
Recruit Swipe deals your open requisition one candidate at a time and writes every decision straight back to your ATS — stage change, note, tag, rejection. No second database. No candidate-facing anything.
10 sources built · credentials stay server-side · your ATS remains the system of record
Engineering — Requisition 4471
4 left
Marcus Ellery
Staff Backend Engineer
- Based
- Manchester, UK
- Track
- 11 years · Monzo, Sky
- Java
- Kafka
- AWS
- gRPC
Sofia Berglund
Infrastructure Engineer
- Based
- Stockholm, SE
- Track
- 6 years · Klarna
- Rust
- eBPF
- Nomad
Dele Adeyemi
Site Reliability Engineer
- Based
- Lagos, NG · Remote
- Track
- 9 years · Flutterwave
- Python
- Prometheus
- Ansible
That's the demo deck.
In the app the next candidates load from your requisition automatically.
Written back to Greenhouse
- Swipe to see the write-back.
The difference
A swipe is a write.
Most sourcing tools give you a nicer list and leave the actual work where it was: back in the ATS, in another tab, later. The decision and the record drift apart.
Here the gesture is the transaction. Swipe right and the candidate moves to Interview in Greenhouse before your thumb is back. Swipe left and the rejection is filed with the reason you configured. Every action is logged with its outcome, so a failed write is something you can see and retry — not something you find out about in a pipeline review.
Three steps, once
Set it up in an afternoon, then never think about it.
- 01
Connect
Add the ATS or job board you already work in. Paste a key, pick your account. Your credentials are encrypted server-side and never reach the phone.
- 02
Configure
Decide what each direction does. Right might advance the stage in Greenhouse and apply a tag in Ashby. The picker only offers what that provider actually supports.
- 03
Swipe
Pick an open requisition and go. Each swipe runs your action list in order and records what succeeded, so you can see exactly what landed in the ATS.
Sources
Your ATS, not ours.
We do not host the candidate database of record. The system you already pay for stays the source of truth; we cache what we need for speed and record what you decided.
- GreenhouseIntegration built
- AshbyIntegration built
- LeverIntegration built
- WorkableIntegration built
- RecruiteeIntegration built
- SmartRecruitersIntegration built
- TeamtailorIntegration built
- BambooHRIntegration built
- JazzHRIntegration built
- ManatalIntegration built
- iCIMSIn development
- Workday RecruitingIn development
- IndeedPartner access pending
- ZipRecruiterPartner access pending
Adding a source means writing one adapter, not rebuilding the app. If yours is missing, tell us.
Security
Your keys never ship in an app bundle.
Credentials in a vault
API keys and tokens are encrypted at rest and decrypted only inside the server function that makes the call, under your own session.
Every call proxied
The phone talks to us; we talk to your ATS. No ATS endpoint is ever called from the device, so a compromised handset cannot reach your pipeline.
Row-level isolation
Every table is scoped to its owner in the database itself, and cross-account isolation is asserted by tests on every commit.
Share without sharing
A teammate can swipe a connection you own without ever seeing the key behind it.
Two ways in