Role roadmaps / Data Architect Role flowchart
Choose contracts: grain, ownership, lake vs warehouse, and what you will not build. You still need to have shipped.
Also called: Analytics Architect, Platform Architect
You ship: A platform sketch the org can fund, plus the standards that keep it from rotting.
Years of shipping first. This is not an entry role.
Roadmap Coding Interview Question bank Switch roleData Analyst BI Analyst Data Engineer Analytics Engineer Data Scientist ML Engineer MLOps Engineer AI Engineer Data Architect Nearby roles:Data Engineer , MLOps Engineer , Analytics Engineer
Checked skills
0% · click a node for concepts, stacks, access, and what to produce · drag to pan · Ctrl-scroll to zoom
− Fit + Clear checks
Start · Data Architect Foundations Enterprise modeling Domains, contracts, and why one big lake is not a model. Still SQL You cannot review a mart you cannot query. Unit economics of data Credits, slots, storage, and failed jobs as a line item. Daily craft Warehouse vs lakehouse Iceberg as a contract. When two engines are worth it. Governance that people use Catalog, lineage, and masking that does not block the analyst. SLAs and ownership Who pages, who pays, who may publish gold. How you ship Paved roads A default ingest, a default transform, a default BI path. Exceptions are written down. Migrations without heroics Hive to Iceberg, Synapse to Fabric — dual-run, then cut. Career moves Architect interview A platform sketch, a cost story, and a time you said no. Stay sharp Keep a pipeline in production. Architecture without on-call rot. Keep practicing Study this node
Enterprise modeling Domains, contracts, and why one big lake is not a model.
Domains, contracts, and why one big lake is not a model.
Domains, contracts, and why one big lake is not a model.
Time to learn Domains, contracts, not one big lake.
What you need Contracts article Glossary A domain map Concepts to study Bounded contexts / data domains Contracts as the architectural primitive Canonical vs serving models Avoiding the “enterprise data model” that nobody ships Tech stacks dbt + catalogs — ImplementationData contracts article — The ideaHow to study Contracts article. Sketch three domains and the events between them. What to produce Three domains and the events between them Named contract owners Pitfalls One lake to rule them all with no owners A 400-entity ERD as the delivery plan Interview prompts What is a domain here, and who owns the contract? Links
Mark as done All Articles Stacks Practice Learn Pages
No results. Try analyst, numpy, snowflake, or roadmap.
↑↓ navigate↵ openesc closeAliases: sf, numpy, analyst, mlops
