Requirements
Write clear, verifiable requirements
Each requirement should express one clear idea and be verifiable from a professional profile.
Avoid requirements that cannot normally be verified from a professional profile, such as willingness to accept a salary, availability to start on a specific date, or being a “team player.”
- Must-haves and preferences: Use 2–6 must-haves. A criterion is mandatory only if the customer would reject a candidate without it. Keep preferences as nice-to-haves so they improve ranking without excluding relevant candidates.
- Connected context: Keep a skill and how it was used together, or a company and the required period. These connected conditions belong in the same requirement.
- Exclusions: State exclusions directly and only when truly disqualifying. Do not repeat the same rule as both a requirement and a strict filter.
Examples of good requirements
| Type | Example |
|---|---|
| Position and seniority | Current or recent experience as a Senior Backend Engineer. |
| Location | Based in London or Berlin. |
| Hard skill | Hands-on experience building production applications with Python. |
| Domain experience | Built payment processing systems for B2B products. |
| Leadership | Managed a team of at least five engineers. |
| Company and timing | Worked at Stripe before its Series B. |
| Skill in context | Used Python to build fraud detection systems. |
| Related skills | Backend development experience with Python and Go. |
| Exclusion | Must not currently work at Stripe. |
Request example
{
"search_requirements": [
{
"search_requirement": "Built production APIs in Python",
"must_have": true
},
{
"search_requirement": "Worked on B2B payments",
"must_have": false
}
]
}Updated about 4 hours ago
Did this page help you?
