Job description builder

Copy comes from the standard data. Keep the “not in scope” section — it filters mismatches better than any benefits list.

ROLE: Delivery Engineer (L2 · Intermediate · Independent)

POSITIONING
Owns one scenario end to end: scope, baseline, acceptance, and the system still running afterwards.

SCOPE OF RESPONSIBILITY
Accountable for scenarios.
- Scenario scope: One scenario, full cycle (from requirement to live operation)
- System scope: Data and interfaces across 1–3 systems
- Counterparts: Business owner, front-line staff, IT / data team
- Horizon: Weeks to months
- Budget authority: Single-scenario scale, subject to approval
Reference level range: P5–P6 (public information, not an official mapping).

REQUIREMENTS
- Business literacy: Independent (Completes the standard case without guidance)
- Scenario engineering: Independent (Completes the standard case without guidance)
- AI engineering and debugging: Independent (Completes the standard case without guidance)
- Delivery assurance: Independent (Completes the standard case without guidance)
- Delivery engineering: Independent (Completes the standard case without guidance)

EVIDENCE TO BRING
- A scope sheet: boundaries, baseline numbers, acceptance actions
- A failure sample set (20+ cases) that shows where the system breaks
- A record of one real process running in production, with named users

DELIVERABLES
- A running scenario
- Acceptance sheet
- Failure sample set
- First version of the runbook

NOT IN SCOPE
- Decisions beyond the scope above (common misconception: Treating go-live as delivery complete. Go-live is the start.)
- Go-live is not delivery complete

FAILURE SIGNAL TO WATCH FOR
The scenario works but nobody uses it: acceptance measured features, not outcomes.

—
Generated from the FDE Level Standard (2026), CC-BY-4.0. Not a national qualification; salary ranges are public-source estimates.