What is a Job?
Clear definition, clean distinctions and an outcome‑first view on modern work.
Table of contents
Role • Responsibilities • Requirements • Outcomes
4
Core elements
Purpose, tasks, requirements, outcomes
5–7
Top tasks
Recommended visible items
≤ 2
Must‑haves
Maximum hard filters
Terms & distinctions
Job
Bundle of purpose, responsibilities and outcomes under constraints (time, budget, mode).
Role
Contribution to value creation — independent of org chart.
Position
Org placement (title, level, department).
Project
Time‑boxed initiative with a deliverable — can involve multiple roles/jobs.
Job components
| Part | Content |
|---|---|
| Purpose/Mission | Why does the job exist? What impact? |
| Responsibilities | 5–7 prioritized tasks with time share/frequency |
| Requirements | Must vs nice‑to‑have with level and proof |
| Constraints | Work mode, schedule, travel |
| Outcomes/OKRs | Measurable results and quality criteria |
Responsibilities (Tasks)
Prioritize
Lead with the most important; include time share/frequency.
Be concrete
No buzzwords; no wishlists.
Outcome link
Each task serves an outcome (e.g., ↑conversion, ↓downtime).
Dependencies
Expose interfaces (teams/tools/processes).
Requirements & proof
| Type | Example |
|---|---|
| Must‑have | 2–3 years in X OR proven projects in Y |
| Nice‑to‑have | Knowledge of Z (level: basics) |
| Proof | Link to repo/portfolio/case study; before/after metrics |
| Soft skills | Describe in context (e.g., facilitating 15‑person meeting) |
Measurable outcomes
A job succeeds when outcome goals are met. Define 2–4 KPIs (leading/lagging) and the quality criteria (Definition of Done).
Examples: revenue +12% in 2 quarters, NPS +8 pts, MTTR −30%, time‑to‑market −20%.
Examples
Product Marketing Manager
Purpose: positioning & demand. Tasks: messaging, launch plan, enablement. Must: 3+ campaigns; Proof: KPIs.
DevOps Engineer
Purpose: stability & delivery. Tasks: CI/CD, monitoring, incident response. Must: cloud; Proof: MTTR/Change Failure Rate.
Define outcomes before listing requirements.
— Career Wiki Editorial
FAQ
Job vs role?
Role = contribution; Job = purpose, responsibilities, requirements, outcomes under constraints.
How many must‑haves?
At most 2 true hard filters. Everything else as nice‑to‑have.
How concrete should tasks be?
Concrete enough to assess fit — with priority and time share.
How to phrase outcomes?
SMART/OKR, ideally with baseline and target.