Writing Job Responsibilities: How to Describe What the Role Actually Does
The responsibilities section is the core of any job description. It tells candidates what they will actually do in the role — not the generic duties everyone shares, but the specific work that matters. Well-written responsibilities attract the right candidates and filter out the wrong ones. Poorly written responsibilities attract everyone and filter no one.
All resources Writing Job Responsibilities
Start every responsibility with a strong action verb
The first word of each responsibility sets the tone and communicates ownership. Weak verbs like "assist," "help," or "support" suggest a passive role and attract passive candidates. Strong verbs like "lead," "design," "implement," "own," and "drive" signal ownership and attract candidates who want impact. Match the verb to the actual level of ownership. A junior role might "contribute to" or "participate in" certain activities, while a senior role "leads" or "defines" them. Be honest — if the person will actually be supporting rather than leading, say so. But do not default to weak verbs when the role genuinely involves ownership.
Tie responsibilities to outcomes
The difference between a good and great responsibility description is whether it includes an outcome. Compare: "Manage social media accounts" versus "Develop and execute a social media strategy across LinkedIn and Instagram that increases engagement by 30% within six months." The first is a task. The second is a responsibility with a measurable outcome. Outcomes tell candidates what success looks like. They also attract candidates who are motivated by results rather than just completing tasks. Not every responsibility needs a specific metric, but where possible, connect the work to a business result — revenue, efficiency, user satisfaction, system reliability, or team performance.
Be specific about what the person owns
Vague responsibilities fail because they do not tell candidates anything unique about the role. "Work on various projects" could mean anything. "Own the customer onboarding flow, including email sequences, in-app tutorials, and support documentation, serving 500+ new users monthly" tells a candidate exactly what they will spend their time on. Specificity also helps during interviews — when you can point to the job description and discuss specific responsibilities, conversations are more productive and aligned.
Keep the list focused and prioritized
Most job descriptions list too many responsibilities. When everything is listed, nothing stands out, and candidates cannot identify the 3-4 things that matter most. Limit responsibilities to 6-8 core items. Order them from most to least important — the first few items should represent 70-80% of the role. If you have more than 10 responsibilities, you either have a role that should be split into two positions or you are listing tasks that belong in a training document, not a job description.
Avoid these common responsibility errors
These mistakes appear in the majority of job descriptions and are easy to fix once you recognize them.
- Listing only tasks without outcomes — "Process invoices" tells nothing about volume, accuracy standards, or impact
- Using jargon without explanation — internal acronyms mean nothing to outside candidates
- Listing too many items — more than 10 responsibilities dilute focus and overwhelm readers
- Being too generic — "Handle ad hoc projects" could appear in any role in any company
- Conflating responsibilities with requirements — "Must have experience with Salesforce" is a requirement, not a responsibility
- Using passive language — "Will be involved in" or "Expected to assist" suggests limited ownership
- Listing responsibilities that belong to other roles — include only what this specific person owns
- Forgetting to mention collaboration — who does this person work with and how?
Related resources
Related job descriptions
Frequently asked questions
How many responsibilities should a job description include?
Aim for 6-8 core responsibilities. This is enough to describe the role comprehensively without overwhelming candidates. Research shows that candidates focus on the first 3-4 items in any list, so prioritize accordingly. If you have more than 10 items, either the role should be split into multiple positions or some items are tasks rather than core responsibilities.
Should responsibilities include metrics and numbers?
Where possible, yes. Numbers give candidates concrete context about the scope and impact of the role. Examples include team size managed, revenue targets, user base supported, transaction volumes, or performance metrics. Not every responsibility needs a number — some work is qualitative — but adding metrics to 2-3 key responsibilities helps candidates understand the scale and expectations of the role.
Use InstantJD to create your job description
Generate a scored, editable, hiring-ready job description in minutes — free for verified employers.