Documentation

Best practices

Practical tips for candidate data hygiene, job descriptions, AI matching, and pipeline discipline.

What it is

Practical habits that make Talynce work better for your team — most of these come from patterns that produce noticeably better AI match quality and cleaner reporting.

Candidate database hygiene

  • Upload resumes in PDF, DOC, or DOCX for the most reliable parsing — see Bulk resume upload.
  • Upload regularly rather than in huge rare batches, so your database (and AI Match results) stay current.
  • Use tags to organize candidates by skill, source, or event (e.g., a job fair) — tag at upload time to save cleanup later.
  • Periodically review for duplicates; bulk upload already deduplicates by contact info, but manually merged data can still drift.

Writing effective job descriptions

  • Be specific about required skills and technologies — Auto-Fill from JD works best on detailed source text.
  • Separate must-have from nice-to-have requirements explicitly.
  • State experience range and whether remote work is acceptable — these feed directly into AI Match filters.

Job management

  • Keep only genuinely open roles Active; close or pause filled/stale roles so they stop appearing in matching and public listings — see Manage jobs.
  • Review your job list periodically rather than letting old postings accumulate.

Getting better AI matches

  • List the most important skills first in a job description — extraction and matching weight earlier, more prominent skills more heavily.
  • Don't stop at the top 1–2 results — review a spread of match scores, especially anything above roughly 70%, before ruling candidates out.
  • Shortlist a strong candidate to multiple relevant open jobs rather than just one, when appropriate.

Pipeline discipline

  • Agree on what each pipeline status means for your team before turning on status update emails — candidates will see those labels indirectly through email tone/timing.
  • Move candidates promptly rather than batching pipeline updates — stale pipelines make Hiring Intelligence reports less useful for your whole team.
  • Use Notes in the pipeline drawer liberally — they're the shared memory for why a decision was made.

Related articles

Last updated: 9/17/20264 views