Writing clearer AI job briefs

Lead with the business or product outcome the hire will own, then list the technical surface area. Candidates scan for scope before they care about stack keywords.

Replace vague “AI experience” with concrete artifacts: datasets, evaluation harnesses, latency budgets, safety constraints, or production traffic.

Must-haves should be binary and observable in a portfolio or interview. Nice-to-haves belong in a short secondary list so strong generalists still apply.

If the role is research-heavy, say so. If it is shipping-heavy, say what “done” looks like in your release cycle.