How it works
Three decisions up front. Then it's just your thumb.
Recruit Swipe is a lens onto the pipeline you already run. Nothing here replaces your ATS, and nothing asks your candidates to sign up for anything.
Connect a source
Pick your ATS, paste an API key, and give the connection a name. Some providers need one extra detail — a subdomain, a company id, an OAuth client id — and the form asks for exactly what that provider needs, nothing more.
The key goes straight into an encrypted vault on the server. It is never stored on the phone, never held in local storage, and never included in the app bundle. When a call has to be made, a server function decrypts it, makes the call, and throws the plaintext away.
You can connect more than one source. A recruiter running Greenhouse for engineering and Workable for sales sees both, separately configured.
Decide what a swipe means
Each direction — right, left, up — maps to an ordered list of actions. Right in Greenhouse might advance the stage and add a note. Right in Ashby might just apply a tag. Same gesture, different meaning per connection, because the systems are different and pretending otherwise breaks things.
advance_stageMove the candidate to a stage you pick.apply_tagTag them in the ATS.add_noteLeave a note, with the date filled in.rejectFile a rejection with your chosen reason.local_onlyRecord it here and write nothing back.
The picker only offers what the provider supports. Ashby has no rejection endpoint we can verify, so Ashby connections do not offer a reject action — rather than offering one that quietly fails.
Swipe a requisition
Open a requisition and the deck fills with its candidates. One card at a time: photo, headline, skills, experience, resume link. Buttons if you prefer them, gestures if you turn them on.
Each swipe runs your action list in order and records what happened to each step. If the stage change succeeded and the tag failed, you see that, on the candidate, with the reason. Candidates you have already swiped do not come back around.
Prefer to assess before you act? Switch the same requisition into Grade mode: a scrollable list, a 1–100 score per candidate, per-skill breakdowns, and a note. Grades are recorded only — they never write to the ATS — and teammates on a shared connection can see each other's.
Afterwards
You can see what landed.
Every swipe is kept with its outcome log. The activity view for a connection shows what you did, when, and what each configured action returned from the ATS.
Positive swipes collect into a shortlist across every connection you have, newest first. Tap one and you get the candidate as we cached them, plus exactly which writes were attempted on their record.