TL;DR
A role brief is a rewritten version of your job description, designed to speak clearly to developers. We draft it, you approve or request edits in Slack or Teams, and only then is the role shown on daily.dev.
What a role brief includes
Clear title and level
Core technologies and stack
Location or remote policy
Compensation range
Key context about the team and role scope
Your custom qualification questions (if added)
Steps to approve a role brief
Receive draft
After you post a job in Slack or Teams, our team drafts the brief.
Review content
Check title, stack, comp, and context for accuracy.
Request edits if needed
Share feedback directly in Slack or Teams.
Approve
Confirm when the brief is ready. We then surface it to matched developers.
Important:
Nothing goes live until you approve the role brief. Developers will only see roles that you have confirmed.
FAQs
Q: Why not just use my original job description?
Because most job descriptions are too long or unclear for developers. A role brief highlights what they care about most.
Q: Can I request major changes?
Yes. You can adjust scope, comp, or positioning before approving.
Q: Can I update the brief after launch?
Yes. Post changes in Slack or Teams and we will refresh the live brief.