Data Architect Jobs

Data architect jobs on carbon.talent, for senior people who design how an organisation's data is stored, integrated, governed and used. Architects set direction rather than build every pipeline, but the best ones stay close enough to the work to make realistic decisions. Roles include enterprise, cloud and solution architecture, on full-time, contract and fractional terms. This guide covers the skills architecture interviews test and how to evidence design decisions.

Open roles

A data architect's main output is decisions and the documents that explain them: target architectures, data models, integration patterns, standards, and roadmaps that move an organisation from where it is to where it needs to be. The job is as much about trade-offs and persuasion as technology. A design that the engineering team cannot build, or that finance cannot afford, is not a good design.

Listings typically cover cloud platforms and their data services, warehouse and lakehouse design, data modelling at conceptual, logical and physical levels, integration through batch, streaming and APIs, master data and governance, security and privacy. Enterprise architects add alignment with business capabilities; solution architects focus on a specific system or programme. Cloud architects are often expected to know cost management in depth.

Interviews are scenario-driven. You might be asked to design a data platform for a company merging three legacy systems, or to choose between a lakehouse and a warehouse for a given workload. Strong answers start with requirements and constraints, compare options openly, state what you would decide and why, and describe how you would phase the change. Expect follow-up questions that change a constraint to test how your design adapts.

Evidence matters. Bring examples of architecture decision records, diagrams and roadmaps you produced, with sensitive details removed. Describe a decision you would make differently today and why. Interviewers are wary of architects who have only drawn diagrams; show that you followed designs through delivery and learned from what happened.

Data architecture is commonly offered on contract and fractionally. Organisations bring in an architect to design a migration, set standards before a platform build, or review a design before a large investment. Fractional architects often work with several companies at once, providing direction a few days a month. These roles reward people who can produce clear written recommendations quickly.

Regulation shapes architecture in many sectors. Financial services, healthcare and the public sector require attention to data residency, retention, lineage and access controls. Experience with frameworks such as GDPR and sector-specific rules is often expected. Mention the regulatory environments you have designed for and how they influenced your decisions.

Questions to ask an employer: who owns architecture decisions and how they are recorded; how much budget authority the role has; how architecture relates to engineering teams; and what the biggest current constraint is. An architect without influence over delivery tends to produce documents nobody follows.

Paths into architecture usually run through senior data engineering, database administration or BI leadership. If you are making that move, start writing decision records for the systems you already work on. They are good practice and good evidence.

Common mistakes for data architects include designing for imagined future scale instead of current needs, choosing tools before understanding the organisation's skills, and writing architecture documents nobody reads. Strong architects produce short decision records, explain trade-offs plainly and revisit decisions when circumstances change. Interviewers look for humility about past choices as much as confidence about new ones.

Questions to ask an employer include who makes final platform decisions, how architecture is reviewed, what the current pain points are and how much budget exists for change. An architect role without decision rights or budget can be frustrating, so understanding these early helps you judge the opportunity.

Data architects increasingly need to plan for AI workloads. Retrieval systems, feature stores and model training all place new demands on storage, governance and access control. Being able to explain how an existing platform should change to support these uses, without rebuilding everything, is a strong signal in senior interviews.

carbon.talent lists data architect roles with employment type and locations. Signing up, building a profile and applying are free.

How carbon.talent works for candidates

  • Free signup, profile and applying.
  • Contract, fractional and full-time data and AI roles.
  • carbon.talent takes no cut of a contractor's rate.
Create your free profile

Join the Data Architect talent pool

Questions

What does a data architect do?

Designs how data is stored, integrated, governed and used across an organisation, producing target architectures, models, standards and roadmaps.

How do I become a data architect?

Most architects come from senior data engineering, database or BI roles. Start documenting design decisions and trade-offs in your current work.

Are data architect roles available on contract or fractionally?

Yes. Migrations, platform designs and design reviews are often contract work, and fractional architects provide ongoing direction for smaller companies.

What is asked in a data architect interview?

Design scenarios with constraints, trade-off discussions, and examples of past architecture decisions and how they played out.