Skip to content
Handbook

Edit requirements and interview questions

Define what counts as evidence before you start collecting it.

Owner · Recruiter2 min readGuided walkthrough
Before you begin

Open the job’s profile editor. Editing requires recruiter or owner access.

On this page
From a requirement to a useful questionSynthetic example

A guided view of the actual product controls. Move step by step or play the walkthrough.

Step 1 of 3

Name a concrete skill

One requirement should describe one relevant capability. The actual profile editor keeps its rubric alongside it.

Fictional data · Local example only · No account changes, messages, payments or device recordings
  1. Name a concrete skill

    One requirement should describe one relevant capability. The actual profile editor keeps its rubric alongside it.

  2. Explain what demonstrates it

    Define observable evidence. An exact task example is more useful than an unqualified claim.

  3. Confirm comparable questions

    Choose the core questions that fit the answer budget. The confirmed selection applies to new interviews.

Read the complete walkthrough
  1. Name a concrete skillOne requirement should describe one relevant capability. The actual profile editor keeps its rubric alongside it.
  2. Explain what demonstrates itDefine observable evidence. An exact task example is more useful than an unqualified claim.
  3. Confirm comparable questionsChoose the core questions that fit the answer budget. The confirmed selection applies to new interviews.

Step by step#

  1. Write the requirement

    Under Requirements & evaluation, use Skill or experience to name one relevant capability. Choose Must have or Nice to have, then a weight from 1 to 10.

  2. Define the evidence

    Use What demonstrates this requirement? to describe the information that would support an assessment. Separate experience claims from independently verified credentials.

  3. Check role context

    Review Experience, Location, Salary, Availability and Languages. Exclusion criteria are for human review; they are not a license for automatic rejection.

  4. Choose comparable core questions

    Check Include in the interview for the questions you intend to ask. Selected questions must be distinct and fit within the configured answer budget.

  5. Confirm changes

    Save the reviewed profile. New interviews use the confirmed selection; existing interview snapshots remain tied to their original version.

Specific questions, useful answers#

A question such as “Tell us about a time you checked an order for errors” can support a concrete evidence review. A generic “Are you detail-oriented?” mainly invites an unsupported yes/no claim.

The question selection cannot be saved#

Select at least one distinct core question and keep the total answer allocation within the interview budget. If someone else has changed the job version, reload and reconcile your changes before saving.

Put it into practice.

Make a requirement specific. Work through the controls with local sample data.

Try the exercise
Explore the handbook

Find an answer, a button or your next step.

Search the complete handbook. Your query stays in this browser.

Something not working? Start here →
Local handbook search↑ ↓ to move · Esc to close