About
I design and evolve data platforms that are reliable, governed, and built to scale — with a hands-on approach and long-term thinking.
Who I am professionally
I work at the intersection of data engineering, platform architecture, and technical leadership. I currently operate as a Lead / Principal Data Engineer while acting as Head of Data, owning the evolution of cloud-native data platforms end-to-end.
My background combines deep hands-on engineering with architectural ownership and platform strategy, particularly in AWS-based lakehouse and streaming environments.
I focus on building platforms that are not only technically sound, but also trusted by the business — through strong data modeling, governance, observability, and automation.
What I optimize for
The principles I use to make platforms resilient and useful over time.
Reliability by design
Pipelines and datasets should be predictable, testable, and operable — not fragile workflows that require heroics.
Governance as a platform capability
Quality checks, metadata, lineage, and access control must be built-in, not bolted-on after incidents.
Models that serve real decisions
I treat data modeling as the bridge between raw data and trusted analytics, enabling clarity and consistent metrics.
Observability & operational excellence
If we can’t see it, we can’t trust it. Monitoring, alerting, and clear ownership are essential.
Pragmatic automation
Infrastructure as code and CI/CD reduce risk and improve speed, without turning the platform into a science project.
Strengths
How I operate
- I’m comfortable owning systems from ingestion to analytics consumption.
- I make architectural decisions with reliability and long-term maintainability in mind.
- I stay close to delivery: I lead, but I also build and debug.
- I value pragmatic engineering quality over flashy complexity.