Expertise · Engineering & architecture
Most data platforms hide their structure inside scattered SQL scripts. I make the design executable: models, rules and metadata in the middle, generating the SQL, control flow, tests and lineage — with governance shifted left, into the model, not bolted on after.
The ideas behind it
ERDs and lineage should not be decoration. When the metadata is executable, the same design generates the SQL, the tests, the docs and the lineage. Design once, generate many.
Business logic should not be scattered across SQL scripts. I design business-oriented transformation layers where the meaning lives in metadata, governed and visible — not buried in pipelines.
Lineage extracted from code alone tells you what connects to what. It cannot tell you why it matters. Business-friendly, semantic lineage — intent, not just wiring — is what teams actually need.
dbt and SQLMesh bring declarative, versioned engineering. I carry bank-grade governance into them — shift-left quality, contracts, metadata diffing — disciplined without being bureaucratic.
From the writing
That is the heart of how I work — let us make your metadata do the building.
Start a conversation