What Makes a Great Job Role Description

Anatomy of an Ideal Job Role

A great job role description is not a job advertisement. It is a precise, structured specification that serves as the single source of truth for compensation, career development, performance evaluation, recruiting, and compliance.

Every role in a well-designed architecture includes these components:

1. General Description

A concise summary (2–4 sentences) of the role's purpose, scope, and organizational impact. This is what someone reads first to understand what the role does.

Example: "Designs, develops, and maintains software systems that process and analyze large-scale data pipelines. Collaborates with data scientists and product teams to deliver production-grade data infrastructure. Reports to the Engineering Manager, Data Platform."

Rules:

• State what the role does, not what the role "is responsible for" — active verbs, not passive responsibility language
• Include the reporting line or organizational context
• Keep it under 50 words

2. Detailed Tasks

The specific activities the role performs. Tasks are the atomic unit of work — they are what gets done, day to day. List 10–20 tasks per role, ordered by importance/time allocation.

Good task writing:

• Start with an action verb: Design, Analyze, Review, Build, Manage, Report
• Be specific: "Reviews pull requests for code quality and architectural compliance" not "Participates in code reviews"
• Include frequency or context where relevant: "Conducts weekly stakeholder alignment meetings"

Tasks are critical for two reasons beyond description: they map to skills (which capabilities are needed), and they map to AI-automatability (which tasks can agents perform).

3. Responsibilities

Broader accountabilities beyond individual tasks. Responsibilities describe what the role is answerable for — outcomes, not activities.

• "Ensures data pipeline uptime of 99.5% or higher"
• "Maintains compliance with GDPR data processing requirements for all pipeline outputs"
• "Manages vendor relationships for cloud infrastructure contracts up to €500K annually"

4. Work Mode

The location and collaboration model: on-site, hybrid, remote, or field-based. Include:

• Required on-site days (if hybrid)
• Time zone expectations for remote roles
• Travel requirements (percentage of time, destinations)
• Physical requirements (if applicable)

Work mode is increasingly relevant for job evaluation — the EU Pay Transparency Directive includes "working conditions" as one of four core evaluation factors.

5. Interactions and Stakeholders

Who the role works with, internally and externally. This defines the collaboration surface and influences skill requirements.

• Internal: Which teams, functions, and leadership levels does the role interact with regularly?
• External: Customers, vendors, regulators, auditors, partners?
• Direction: Does the role direct others, collaborate as peers, or receive direction?

6. Qualifications

The formal requirements for holding the role. Separate into:

• Required: Non-negotiable prerequisites (specific degree, certification, years of experience, security clearance)
• Preferred: Differentiating qualifications that strengthen a candidate but are not mandatory

Keep qualifications objective and defensible. Under EU Pay Transparency rules, qualification requirements that disproportionately exclude a gender may be challenged as indirect discrimination.

7. Equal Pay Criteria

The factors that determine this role's position in the pay structure. Mandated by EU Pay Transparency Directive Article 4, the criteria must be objective and gender-neutral:

• Skills — the capabilities required to perform the role
• Effort — the physical, mental, and emotional effort the role demands
• Responsibility — the scope of decision-making, accountability, and organizational impact
• Working conditions — the environment, hazards, and scheduling demands

These four factors form the basis of gender-neutral job evaluation under the Directive. Every role description should explicitly document how it scores on each factor.

8. Risk and Compliance Categories

Classify the role's exposure to operational, compliance, safety, and financial risk:

• Operational risk — can errors in this role cause service outages, data loss, or process failures?
• Compliance risk — does this role handle regulated data, financial reporting, or audit-relevant processes?
• Safety risk — does this role involve physical hazards, machinery, or field operations?
• Financial risk — does this role have budget authority, procurement power, or revenue responsibility?

Risk categories influence grading frameworks (higher risk typically maps to higher grades) and are relevant for insurance, audit, and regulatory reporting.

9. Required Skills with Proficiency Levels

The skill profile: 15–30 skills, each with a target proficiency level (1–5 scale), grouped into competency clusters. This is the bridge between the role description and every downstream skills-based process.

See the Skills, Competency Clusters, and Proficiency Frameworks article for detailed guidance on skill selection and proficiency definition.

Putting It All Together

A complete role description in Cobrainer includes all nine components in a structured, version-controlled format. Every component is individually editable, trackable, and exportable. Changes create diffs. Rollback is always available.

The result: one source of truth that feeds compensation decisions, recruiting templates, performance reviews, career guidance, and compliance reporting — automatically, without manual synchronization.