Prepare people and recruiting work

Draft roles, organize evidence and keep personal information in its audience.

Use Artie to prepare work from the sources you are entitled to use. Recruiting and people work needs particularly clear ownership and audience choices.

On this page

Define the role or process

Give the role scope, requirements, approved company information and intended audience. Ask for a job-description or interview-plan draft. Review the criteria rather than accepting a familiar template as your actual hiring standard.

Organize evidence

Provide the permitted candidate or employee materials and request a source-linked summary. Keep observations separate from conclusions. A summary is support for a human decision, not proof that a hiring or employment decision is correct.

Prepare communications deliberately

Specify the recipient, sender account and desired outcome. Review facts and proposed commitments before an outward-facing action that needs approval. A personal inbox remains controlled by its owner.

Reuse the process safely

Save appropriate formats and shared instructions. Keep another person's private information out of wider audiences. For repeating coordination work, set the cadence, delivery destination and accountable person.

Find candidates from work evidence

Ask Artie to find people whose work matches your role criteria. People-focused web search uses Exa People professional profiles; ordinary web research can help find supporting project evidence. Artisan’s people database supplies structured records and work emails, but its search rows aren't evidence of a person's own work.

People-focused web search is billed normally. Artisan’s people database has a shared allowance of 200 request transmissions per workspace per UTC day, including searches, record reads, fallbacks and retries. This is a request allowance, not a candidate count.

If the database allowance is reached, ask Artie to resume database discovery at the reported reset time on the next UTC day, or use available web research sources. If discovery stops at a capacity limit, partial results already saved remain available for review.

  1. Give Artie the role criteria, the work evidence you're looking for and the permitted sources and audience.
  2. Ask for a bounded sourcing batch saved to the task. Request each candidate's source, a summary of discovery counts and examples to review.
  3. Ask Artie to read the saved result pages when you need more detail. To source more people, explicitly ask it to continue the same saved batch.
  • The discovery summary includes records found, distinct records new to that batch, duplicates within the batch, contact-history exclusions and up to five examples.
  • Contact-history exclusions depend on available email addresses and contact-history coverage. A record that's new to the batch isn't confirmation that you've never contacted that person.
  • Review the work evidence before treating a discovered person as qualified. Examples follow source ranking, not a completed qualification assessment.

Find up to 20 potential candidates for a developer-tools engineering role with evidence of building open-source command-line tools. Use people-focused web search and supporting project pages. Save a bounded sourcing batch to this task, show each person's source, and summarize new-to-batch records, duplicates and any contact-history exclusions. I'll review the evidence before qualification or outreach.

Discovery prepares sourcing results. It doesn't complete qualification, write a recruiting tracker or send outreach. Bounded discovery doesn't run a background worker or guarantee a daily number of qualified first contacts.