Business function
Data Engineering
Operates pipelines, contracts, and quality with domains — engineering builds, but does not alone decide purpose and grain.
Load-bearing: Quality and Metadata; Ownership is neighbor. Quality, Metadata · Concept · Shared standard · 8 pillars
Download decision card (PDF) Fill first decision Fill deal card Partial scope / service
Kundenschmerz points and controls
Typical business problems
- Transforms without a contract owner
- DQ tickets without business triage
- Breaking changes without a consumer path
Typical controls
- Data contracts and schema tests
- DQ gates in the pipeline
- Release and breaking-change cadence
How we remove it
- Pipeline contract before transform; meaning owner does not sit in DE
- DQ gate with business triage; the ticket tool is Influence
- Breaking-change notice in the contract; consumer path required
Related roles
Recommended learning paths
Recommended tools
- Fill first decision Capture decision question, data product, owner, or vacancy for the first workshop. tool
- Fill deal card Clarify customer situation, value claim, offer package, and handoff for this function. tool
- dbt DQ rules Derive gates from contracts tool
- Architecture fit Choose a viable delivery shape tool
Recommended stories
1 series 9 stories
Not the full catalog — open Stories filtered to this function
Recommended stories for this function
- Governance in Data Engineering story
- Contract gate before transform story
- DQ gate with an owner path story
- Semantics handoff story
- Breaking change with a consumer path story
- First decision: decision question story
- Sales hub: governance as a service story
- Data architect role story
- Across functions story