Data Steward Job Description Pack

What's in the pack

• Role summary that draws the owner / steward / custodian boundary correctly — because a JD that confuses them hires the wrong person.
• Seven core responsibilities, written as doing-work, not committee attendance.
• Qualifications split required vs preferred, weighted toward domain fluency and follow-through over tool checklists.
• Five success metrics with targets and cadence — definitions coverage, issue age, rule coverage, go-live reviews, consumer satisfaction.
• A 30-60-90 plan you can hand the hire on day one.
• Six interview questions with "a strong answer..." guides for consistent scoring.
• Adaptation notes for business vs technical stewards and fractional (25–50%) allocations.

How to adapt it (about 2 hours)

1. Pick the variant. Business steward or technical steward — the notes tell you which sections to reweight. For fractional roles, cut to the first four responsibilities; a fractional steward with a full-time JD fails by design.
2. Replace the brackets — domain, reporting line, metric targets, compensation band (validate against your market).
3. Sanity-check the metrics against what your steward can influence. Holding stewards accountable for source-system quality they can't touch is the fastest way to lose one.
4. Interview with the provided questions and score against the guides, not vibes.

Before you hire

Make sure the role lands inside a working structure: the data steward guide covers the role in depth, steward vs owner vs custodian settles the boundary questions, and the stewardship program guide covers the program the hire plugs into. Pair the JD with the RACI matrix so the accountability structure exists before the person does.