The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
From Data Steward / Data Governance Analyst (L2)
2-3 years at L2Skills to master
- Moving from owning a specific data domain to leading cross-functional projects. This means developing stronger influencing skills, project management, and a broader understanding of data architecture beyond your immediate domain.
You're ready to move on when
- You've successfully defined and implemented data quality rules for multiple critical data elements.
- You're regularly sought out by business teams for advice on data definitions and usage.
- You've informally mentored new team members and helped them get up to speed.
- You've presented on data governance topics to small groups and handled questions confidently.
- 2
From Data Architect / Senior Data Engineer (L3 equivalent)
5-7 years in engineering, then 1-2 years focused on strategySkills to master
- Transitioning from building data pipelines to defining the 'what' and 'why' of data. This means developing a stronger commercial acumen, stakeholder management, and the ability to articulate business value, rather than just technical feasibility.
You're ready to move on when
- You've designed and implemented complex data pipelines and understand the 'data flow' intimately.
- You're frustrated by poor data quality or inconsistent definitions and want to fix it at a strategic level.
- You've started to get involved in pre-project discussions, advising on data requirements and governance.
- You enjoy translating technical concepts into business language and vice versa.
- 3
From Senior Business Analyst / Product Owner (with strong data focus)
6-8 years in BA/PO, then 1-2 years specialising in dataSkills to master
- Deepening your technical understanding of data architecture, governance tools, and cloud platforms. You'll need to move beyond just consuming data to understanding how it's built, managed, and secured. This means getting more hands-on with SQL and data modelling.
You're ready to move on when
- You've consistently worked on projects with a heavy data component and understand data challenges firsthand.
- You're known for your ability to define clear data requirements and bridge the gap between business and tech.
- You've actively sought out opportunities to learn about data warehousing, ETL, and data governance concepts.
- You're passionate about improving data quality and trustworthiness across the organisation.