Data architect career path: from data architect to head of data
Each step up from data architect: to senior data architect, then to principal data architect or head of data architecture, and on to head of data. What changes in the job, the gap to close, how to show it on your CV and in interviews, and a plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Data architect to senior data architect | Several domains and the platform as one design | 2 to 4 years |
| Senior data architect to principal data architect | The data landscape of the whole company | After several large designs |
| Senior data architect to head of data architecture | A team of architects and their standards | After leading people |
| Head of data architecture to head of data | Data, analytics and their budget | Several years |
Most people reach this ladder from data work below it. Data engineers and database administrators arrive at data architect by their own steps, set out on the data engineer career paths and the database administrator career paths. At the top, head of data is also where the analytics road leads; the step beyond it, chief data officer, is on the data analyst career paths. Architects who widen from data to all systems follow the software architect career paths towards enterprise architect.
BI developers who move from reports to the models underneath them reach data architect too; how they get there from lead BI developer is described in the BI developer career paths.
The rules, owners and quality of the data the architecture holds are run by data governance; its ladder, from data steward to chief data officer, is on the data governance manager career paths.
From data architect to senior
Data architect to senior data architect
What changes: you stop designing one domain at a time and answer for how the domains fit: shared dimensions, master data, the layers of the platform and the standards every team follows. Engineers bring their designs to you for review.
The gap: modellingConceptual, logical and physical models; dimensional models for reporting; naming and keys that last for years. across domains, governanceOwners and stewards for each domain, agreed definitions, access rules and a catalogue people actually use. with real owners, the cost model of the platform, and agreementBring departments to one definition, agree priorities with their heads and keep them informed. between departments that disagree.
On the CV and in interviews: a landscape you designed and how many teams build on it, a standard you wrote, and a definition dispute you settled. Expect a case with two conflicting departments and a fixed budget.
Plan (12 to 24 months): own the model of a second domain; write the modelling standard and run its reviews; lead the platform's cost review with finance; mentor an engineer through their first logical model.
Principal data architect, head of data architecture and head of data
Senior data architect to principal data architect
What changes: your view is the whole company's data: which platforms, which domains own what, how data is shared with partners, and how the landscape changes over five years. You lead other architects without managing them.
The gap: a written data strategy, influence on budgets you do not hold, and enough breadth to judge platformsWarehouses, storage and compute kept apart, roles, data sharing and the cost of each query. depends on the provider, streams and AI uses of data fairly.
On the CV and in interviews: a target landscape you wrote and what was built from it, and a large migration or consolidation you led. Expect to defend a platform choice to the board's technology question.
Plan (several years): own the target data landscape; lead the architecture of one large programme; run a review group where architects check each other's designs.
Senior data architect to head of data architecture
What changes: you lead the architects: hiring, reviews, the standards and the architecture board for data. You report to the head of data, the CIO or the CTO.
The gap: leading peopleExplain a model, a trade-off and its cost to managers, analysts and engineers in their own words. and their growth, a roadmap leadership can read, and the habit of measuring the effect of standards, not their number.
On the CV and in interviews: the team you built, the standards it set and what they changed in cost, speed or quality. Expect a case: three teams ignore the standards; what do you do in the first ninety days?
Plan (12 to 24 months): line-manage two architects; run the data architecture board for a year; publish the roadmap and report against it each quarter.
Head of data architecture to head of data
What changes: you run data as a function: engineering, architecture, analytics and governance, with their people and budget, and the company's data goals with the executive team.
The gap: analytics and data science you did not do yourself, budgets and suppliers, and goals in business terms, such as decisions made faster or regulatory findings avoided.
On the CV and in interviews: a function you led across disciplines, its budget and its results. Expect a case on priorities when every department wants its data first.
Plan (several years): take over the analytics or engineering team next to yours; own a budget for a year; find a mentor who runs a data function.
Two roads continue from here on other pages: the steps from head of data to chief data officer, and the general architecture steps towards enterprise architect and CTO. Both pages are linked at the top of this one.
Your CV for the next step
Moving up in data architecture shows on a CV as a wider reach: from a domain's model, to the landscape many teams build on, to the strategy a company runs on. Three rules:
- Leave every past title exactly as it was. Let the lines below it show the size of what you designed.
- Speak the next level's language. Senior ads say "standards", "reviews", "domains"; principal ads say "target landscape", "data strategy"; head ads say "team", "budget", "roadmap".
- Tie a figure to every line. Systems integrated, teams served, cost, time to a new data source.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| Modelling standard | Defined modelling standards. | Wrote the modelling standard and review for 8 delivery teams; rework after review fell to a few cases a quarter. |
| Target landscape | Worked on the data strategy. | Wrote the three-year target data landscape adopted by the executive board; two warehouses retired on plan. |
| Architecture teamExplain a model, a trade-off and its cost to managers, analysts and engineers in their own words. | Led architects. | Built a team of 4 data architects and an architecture board; every new data product now passes one review. |
| Consolidation | Merged data platforms. | Led the consolidation of the platforms of two acquired companies into one; one revenue figure for the group within a year. |
Key takeaways
- The ladder runs data architect, senior, then principal or head of data architecture, and head of data.
- Senior means the domains fit together; principal means the whole company's landscape.
- Data engineers, DBAs and BI developers reach data architect by their own roads; the pages link both ways.
- Enterprise architecture and chief data officer continue on the software architect and data analyst pages.
- Show each step with a wider reach and a figure, under the job where it happened.
Frequently asked questions
- What comes after senior data architect?
- Principal data architect for the company's whole landscape without a team, or head of data architecture to lead the architects.
- Can a data architect become head of data?
- Yes. It means taking on analytics and engineering, people and a budget, not only architecture.
- Do I need a certification to move up?
- No law asks for one. Ads for senior architects ask mostly for landscapes you designed and decisions you defended.
- How is a data architect different from an enterprise architect?
- The data architect designs the data; the enterprise architect designs all systems and how they serve the business. The enterprise steps are on the software architect page.
- What should my CV show for a principal role?
- A target landscape you wrote, what was built from it, and the cost, risk or speed it changed.