What Are Job Duties and Responsibilities?

What are job duties and responsibilities? Duties are the recurring tasks a role performs: run the payroll, review pull requests, answer tickets. Responsibilities are the outcomes the role is accountable for: payroll accuracy, code quality, customer retention. Job postings list both, usually under one heading, and the distinction matters when you write them or extract them at scale.

What job duties and responsibilities mean, and how to write them

1. Task, duty, responsibility. A task is one unit of work. A duty is a task the role performs regularly. A responsibility is the result the person is answerable for. “Process supplier invoices weekly” is a duty; “keep accounts payable current” is the responsibility it serves. A job description is the set of responsibilities plus the duties that discharge them.
2. How they appear in postings. Most postings carry a heading such as Responsibilities, What you will do or Duties, followed by bullets that mix the two. Postings published through an applicant tracking system tend to keep a stable section order: about the company, responsibilities, requirements, benefits. Postings pasted into an aggregator vary more, from a single paragraph to a full HR document.
3. Write duties as verbs with objects. Start each bullet with an action verb, name the object, and add frequency or scale when it changes the job. “Maintain CI pipelines for three services” tells a candidate more than “DevOps tasks”.
4. Write responsibilities as outcomes. State what good looks like and who depends on it. Five to eight bullets is enough; a list of twenty reads as a role nobody has defined. The fuller method is in how do you write a job description.
5. Keep requirements separate. Skills, years of experience and credentials belong under a requirements heading. Mixing them into the duties list makes the posting harder to read and harder to parse, for people and for software.
6. Keep them current. Duties drift as teams change. A posting copied from a two-year-old requisition describes a job nobody does, and candidates notice at the first interview.

Across the boards JobsPipe collects, phrasing follows the publisher more than the industry. Startup boards on Ashby and Lever favour short verb-led bullets. Large employers on Workday and SmartRecruiters often add physical requirements, compliance language and an equal opportunity statement to the same section. Aggregator postings on Indeed and LinkedIn cover the whole range. The definition and its parts are in what is a job description, and the dataset view is in job description dataset.

Where JobsPipe fits

JobsPipe is a jobs data API that collects live postings from LinkedIn, Indeed, Y Combinator, Naukri, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity, returns them as one schema with closure tracking and a ghost score, and includes a free tier of 1,000 jobs a month. Every row carries the full description text, so extracting duties at scale is a two-step job: pull the postings whose text names the duty you care about with description_or, then split the responsibilities section from each description in your own code.

curl -X POST https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer $JOBSPIPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "description_or": ["month-end close", "accounts payable"], "job_title_or": ["accountant", "accounts payable specialist"], "posted_at_max_age_days": 30, "limit": 50 }'

Narrow with job_country_code_or or job_seniority_or when the phrasing differs by market or level, and page with cursor for the full set.