In Get on Board job postings, as a company or recruiter, the functions section is where candidates decide whether the role matches what they want to do day to day.
What to include
- Day-to-day work: what the person will do each week.
- Team and context: who they will work with and what the team builds.
- Outcomes: how success will be measured in the first months.
What to keep out of the functions section
- Skill lists and tools. Those belong in the requirements field.
- Vague statements like “responsible for everything”.
- Unrelated tasks that do not match the role title.
Quick example
Good: “You will build and maintain APIs for the payments team, collaborate with product to define milestones, and improve performance for high-traffic services.”
Not enough: “Must know Ruby, React, and SQL.”
For full structure guidance, see How to write a clear job posting.
More from Job posting setup
