A candidate database that remembers everyone you have met.

A recruitment candidate database is the searchable record of every person a recruiter has met: candidates, applicants and people kept on the bench for later. In RecruiterDesk it is one deduplicated directory, searchable by name, email, phone, role, employer, location, skill and your own tags, and filterable by experience, expected CTC, notice, talent tier and inferred seniority. One person has one profile, so the same candidate is never scattered across sheets, and the people you already know are a search away the next time a role opens.

Two ways. Search and filter the directory directly, by skill, location, experience band, expected CTC, notice, tier or seniority, or open a Bench view of your strongest, four-star-and-up people. Or, once a mandate has a fitment checklist, let RecruiterDesk rank the people already in your pool against that role, with a fit score, the must-haves met and any knockout flagged, so your first shortlist is built from candidates you have already worked.

Yes. A person carries an "open to opportunities" flag that stamps the date you set it, so a fresh signal reads differently from a stale one. When a client asks for a senior person who would move, you filter on open plus seniority plus skill and recall the shortlist on the spot, with no mandate created. It is the reverse-headhunting view your own network has always been worth, finally searchable.

Drop your resumes in bulk as PDF, DOC, DOCX or a ZIP and each is read into a structured record, deduplicated on email and phone. If you are switching from another tool, a guided spreadsheet import maps your old CSV export onto the talent fields, shows a dry-run preview, and loads people with the same dedupe, so a switching desk starts full on day one rather than empty.

Current role and employer, location, total experience, notice period, skills and a seniority band inferred from title, scope and years together, plus a parse confidence. A low-confidence read is flagged and collected in a Needs review queue, where one tap re-parses the resume or marks the record checked, so a weak parse is never trusted silently.

Yes. Consent, withdrawal, export and erasure are tracked per person with an audit trail, and the design follows India's DPDP expectations, with the customer as the data fiduciary and RecruiterDesk as the processor. A bulk CSV export of the whole pool is restricted to the workspace owner and written to the audit log, so the clearest data-out action leaves an accountable trail.