Hiring nowDataset curation and stewardship

Data Provenance Specialist

Also called Dataset Provenance Analyst

A Data Provenance Specialist traces where every dataset record came from and what was done to it, so the company can show it has the right to use its data and can defend that claim.

What they do

They follow data from source to release. They record where each batch came from, under what terms, and with what consent. They log every transformation, such as filtering, merging, deduplication and relabelling of fields, so a release can be rebuilt and explained. They maintain dataset catalogues and consent registers, and check new sources against licence terms before anything is added. When a source is challenged or a person withdraws consent, they find the affected records and say what must change. They work with data engineers, legal counsel and researchers, and write records that others can read without asking them.

What a strong hire delivers

In the first months, a strong hire gives the company a clear picture of what it holds and what it may do with it. Expect a lineage record for current dataset releases, a consent and licence register that people actually use, a repeatable intake check for new sources, and a measured share of records with verifiable origin and permitted use, with gaps listed and ranked.

How you can tell they are good

Ask them to walk through a dataset they traced end to end. Good candidates show the record format, explain how they handled missing or disputed origins, and say what they refused to include. Ask how they would prove a record's permitted use to an outside auditor. Be wary of answers that rely on trust, memory or spreadsheets nobody else can read.

Why it is hard to fill

Almost nobody has this exact title. The work sits between data science, archives, information science, governance and licensing, and most candidates are strong in only one of these. Those who combine technical lineage skills with a firm grasp of rights are scarce. Job titles vary widely, so searching on title alone misses most of them. We look at what people have actually traced and documented.

Where to find them

Look in data governance and data stewardship teams, library and archive services, information management, and data science groups that have run audits. Some come from licensing or rights clearance roles in publishing, media and research bodies. Regulated sectors such as health, finance and the public sector often produce people used to evidence, consent and audit.

Indicative pay

Not enough published evidence yet to give a fair range for this role, which is common for work this new. We benchmark it for you as part of a search.

Interview questions for a Data Provenance Specialist

  1. Describe a dataset where you traced origin and transformations. What did the lineage record contain, and who used it?

    A strong answer names concrete fields: source, terms, date of acquisition, each transformation and its owner. It shows real users such as legal or engineering. Worry if the record was a one-off document or no one relied on it.

  2. A source turns out to have unclear licence terms after its data is already in a release. What do you do?

    They isolate affected records using lineage, pause further use, involve legal, and decide on removal or retraining impact. They document the decision. Worry about answers that ignore the release already shipped or treat it as someone else's problem.

4 more questions, with what a strong answer covers, are in the Role Kit.

Job description you can post

We are hiring a Data Provenance Specialist to make sure we know where our data came from, what has happened to it, and what we are permitted to do with it. You will build records that stand up to scrutiny and help our teams build on data with confidence.

What you will do

  • Record the source, terms and consent status of every dataset we acquire or create
  • Log transformations across dataset releases so each can be traced and rebuilt
  • Maintain our dataset catalogue and consent register
  • Review new sources against licence terms before use
  • Trace affected records when a source or consent is challenged
  • Report the share of records with verifiable origin and permitted use
  • Work with engineering, research and legal to close gaps

What you will bring

  • Shown work tracing lineage for real datasets
  • Working knowledge of licensing and data rights
  • Experience with consent and data stewardship practices
  • Clear writing that non-specialists can follow
  • Comfort using catalogues, deduplication tools and scripting to check records
  • Good judgement on risk and when to escalate

Nice to have

  • Experience with audits or regulatory review
  • Background in archives or information science
  • Experience designing quality checks or sampling plans

Free to use and adapt. If it saves you time, a link back to this page is appreciated.

Skills that matter

  • Data quality and provenanceAdvancedTrack dataset origin, validity and transformations
  • Data stewardship and consentAdvancedMaintain permissions, retention and responsible data access
  • Experimental designWorkingChoose comparisons that identify credible effects
  • Intellectual property and licensingWorkingAssess rights in training inputs and generated outputs

Other roles in dataset curation and stewardship

Related roles in other families

How we wrote this

Role definitions are our own editorial work, checked against occupational classifications, standards, research and employer pages. Titles vary by company, and this is a description of the work, not a job advert.

← Dataset curation and stewardshipAll new job families

Start a search

Hiring a Data Provenance Specialist?

Tell us the work. We find the people already doing it, whatever their job title says, and you meet them already interviewed for your role.