Find people
Six ways in. One record at the end of all of them.
The routes
Where candidates actually come from.
Most applicant trackers optimise for job boards and inbound, because that is the tidy story. Real desks run on database search, referrals, a browser extension and messaging, with boards as one channel among several. What matters is that every one of them terminates on the same person record.
Candidate-database search
Search a resume database and import the profile you found, inside the product — not posting with a logo on it. Naukri Resdex is the first one connected.
Ten job boards
Configured and audited, with a self-maintaining feed for the one that takes it. The publishing log is the honest part — see the board page.
Your careers page
Branded, with a form you build and knock-out rules that ask the disqualifying question first.
Email intake
Naukri alerts and a capture address, parsed into candidate records rather than left in a mailbox.
Browser extension
One-click capture from LinkedIn into candidates, contacts or accounts. It reads what you are looking at; it stores no credentials.
Referrals
With weighted attribution across more than one degree, so the person who introduced the person who referred the hire is credited too.
- Careers pagewaits in the inboxmatches
- Email intakecreated as a recordmatches
- Browser extensioncreated or linkedmatches
- Database searchimported on demandmatches
- Partner firm submissionclaimed for a windowmatches
- A CV you upload yourselfcreated after reviewnot yet
- De-duplicated on arrival —
Someone you placed two years ago who applies again lands on the record you already have, with the history still on it.
- Source is recorded, and so is its return —
Source ROI is a standing analytics card, not a spreadsheet exercise.
Choosing where to spend the week
Route questions, answered honestly.
›Which route actually produces hires?
That is the question the source data exists to answer — hires per source, not applications per source, with the origin stamped at arrival so nobody has to tag anything. What it cannot tell you yet is what each route costs.
›Do all these routes create duplicates?
Most check first. The careers page, email intake, the extension and a database import all resolve against people you already hold. The exception is a CV you upload by hand, which does not check — worth knowing on a bulk day.
›Can we publish a job to every board in one action?
No. Boards are configured and audited; the honest state of publishing is on the job-boards page, including which adapters can and cannot post. We would rather you read that before planning a channel strategy.
›Is the browser extension safe to use?
It reads the page already open in your browser. No credentials are stored, requested or transmitted, and it tells you whether a capture will link to somebody you have or create a new person before it writes.
›What about referrals?
Recorded as a chain — who introduced whom, walked back as far as it goes. Employee referrals pay today; a hop through a candidate is recorded and does not currently produce a bounty.
Book a demo
Bring the channel you rely on most.
We will run it end to end and show you where the duplicate would have been created.