Find candidates from a job description

Keyword search only finds the exact words you type. Say a resume reads “handled reconciliation and ledgers” but never uses the word “accounting” — a search for “accounting” misses that person, even though they are exactly who you wanted.

ResumeDB reads what you mean, not just the words you used. Paste the whole job description and it works out the role, the skills, the seniority and the location from it — so you get people who fit the job, not people who happened to use your keywords.

The role behind the title

“Executive — Accounts Payable” at one company is “Accounts Assistant” at another. The duties you listed say which job you actually mean.

Which skills are actually required

Your JD says which skills are essential and which are a bonus. A keyword list treats them all the same and returns anyone who mentioned any of them.

The seniority you are describing

“Will own the monthly close” and “will assist with the monthly close” are different levels of experience, even though neither one names a number of years.

The work location

If the JD names an office or site, that becomes a location filter, so you only see candidates who can get there.

A title someone would recognise

Internal grades — “Executive, Band II” — mean nothing outside your own company. If that is what the JD says, put the ordinary name of the job in the first line too: Accounts Assistant, Warehouse Supervisor, Android Developer.

The tools, by name

“Strong accounting fundamentals” is not something anyone writes on a resume. Tally, GST returns, TDS, Excel are. Name the skills the way a candidate would have named them.

A range, or a level

Two to four years. Five years and above. Fresher. A number range and a level word are both read, so you do not have to settle on an exact figure — but “experienced professional” on its own gives the search nothing to narrow on.

The locality, not just the city

Andheri, Lower Parel, Vashi, Bhiwandi — name the place the person will travel to every day. “Our Mumbai office” leaves the whole city in scope, and commute is what this search filters on best.

What the role pays

Most job descriptions leave this out, and it is the omission that costs you the most time: without it you will read profiles of people already earning more than the role can pay. A range is enough.

Adding a line is quicker than rewriting anything. The whole description is read, so a note at the top of it — “Accounts Assistant, 2–4 years, Andheri East office, ₹30,000–40,000 a month, must know Tally and GST returns.” — is enough to fill in whatever the rest of the JD left unsaid.

There are two other ways in, and all three run the same search. Describe the hire in a sentence in the Quick tab, or fill the Guided form field by field — role, skills, experience, location, salary. The JD tab is just the quickest route when you already have the description written. Every search costs 10 credits either way.