The role form has six fields. None of them are optional, but the free-text brief is the only one that takes longer than 30 seconds.
The six fields.
- Title. Plain English. "Senior backend engineer" beats "Software engineer III". The title drives the role family and the default rubric.
- Seniority. One of: associate, mid, senior, staff, principal. Drives the question difficulty in the AI screen and the assessment item set.
- Location policy. Remote, hybrid, or on-site. Where hybrid or on-site, pick the city. Drives candidate eligibility and timezone match.
- Salary band. A range, in your headline currency. Drives the salary-expectation question in the AI screen and the candidate-side filter.
- Must-haves. Up to five short bullets. Drives the deal-breaker check at the start of the screen.
- Free-text brief. A paragraph or two. Drives the rubric proposal and the candidate-facing role page.
What drives what.
The free-text brief is the load-bearing field. Everything downstream (rubric, assessment, interview script, candidate page) starts from the brief. If the brief is vague, the rubric is vague, and the finalists will be too. If the brief is specific, the rubric will be specific, and the finalists will be a better match.
You can edit any field after posting except the role family. Edits to the brief regenerate the rubric proposal; you can accept or keep the prior one.
A good brief is 150 to 300 words. See "Writing a good role brief" for the template we use internally.
What to do next: post the role, then review the proposed rubric before any candidate arrives.