How to write a job description that finds the right candidates

Yes. Paste the job description into the JD tab on ResumeDB and search from it directly — there is no need to reduce it to keywords first. The description is read for the role, skills, experience, location and salary it implies, and those become the search.

No. A JD as written for candidates — responsibilities, requirements, nice-to-haves and all — is what the search expects. Trimming it to a keyword string generally makes results worse, not better, because it discards the context that distinguishes two candidates with the same job title.

Five things, because those are what the search reads: the role in a title people outside your company would recognise, the required skills named the way a candidate would name them (Tally, GST returns, Excel — not 'strong fundamentals'), an experience range or a level, the work locality rather than just the city, and what the role pays. A normal job description written for candidates usually contains all five already. If one is missing, add a line stating it rather than rewriting the description.

Keyword search only finds the exact words you type, so a resume saying 'reconciliation and ledgers' never turns up in a search for 'accounting'. ResumeDB reads what you meant instead. That is why pasting a whole job description beats picking four keywords out of it.

The same as any other search — 10 credits — and new accounts start with 1000 free credits, enough for 100 searches. You pay 50 credits only when you unlock a candidate's contact details.

Yes. If the job description names a work location — an office in Andheri, a warehouse near Bhiwandi — that location is read as part of the search and results are restricted to candidates near it.

Describe the hire in a sentence in the Quick tab, or fill the Guided form field by field. All three run the same search — the JD tab is just quickest when the description already exists.