Recruit Swipe is a recruiter-only app. It connects to the applicant tracking system or job board you already work in, deals the candidates on an open requisition one at a time, and writes your decisions back to that system.
Three things it deliberately is not: it is not a candidate database, it is not a place candidates sign up, and it is not somewhere you post jobs. Your ATS stays the system of record.
Before you start
You need two things:
- An account on a supported source — an ATS or job board we have built an adapter for.
- Permission to create an API credential in that account. On most systems that means an admin or a recruiting-settings role. If you are not sure, the connect your ATS page says exactly where the key lives in each product.
The first ten minutes
- Create your account. Email and password. You will confirm the address with a six-digit code — there is no magic link to lose in a spam folder.
- Connect a source. Settings → Connect a source, pick your provider, paste the credential. Some providers need one extra detail, like a subdomain or a company id; the form asks for exactly what yours needs.
- Set what a swipe does. Open the connection, go to Settings, and configure right, left, and up. The picker only offers actions your provider supports. If you want to try the app without touching anything real, set every direction to “record only”.
- Pick a requisition and swipe. Open the connection, choose an open req, and the deck fills with its candidates.
Two ways to work a requisition
Swipe deals one candidate at a time. Right saves, left passes, up boosts — or whatever you configured them to mean. There are buttons; gestures are a preference you can turn on in Settings.
Grade shows the whole list, including people you have already swiped, with a 1–100 score per row and per-skill breakdowns. Grades are recorded only and never write to your ATS. Teammates on a shared connection can see each other’s.
Switch between them with the mode dropdown at the top of the deck. Your choice is remembered.
What happens after a swipe
Each swipe runs your configured actions in order and records the outcome of each. If the stage change worked and the tag failed, you will see that on the candidate, with the reason.
Everything you saved or boosted collects in the Candidates tab, newest first, across every connection you have.