Building data systems that are reliable by design,
maintainable in practice, and useful to the business.
I approach data infrastructure as a systems problem, not a scripting task. A pipeline that runs once is not the same as one that runs reliably every day, and the gap between those two things is where most engineering decisions live: schema contracts, failure handling, execution logging, partition strategy, layer separation.
My work spans the full data stack, from raw ingestion to governed, analytics-ready outputs. SQL Server warehouses with stored-procedure transformation layers. Databricks lakehouses built on the Medallion architecture with Unity Catalog for lineage. FastAPI retrieval systems backed by vector stores. Each system is designed to be debuggable, reproducible, and maintainable, not just functional.
Certified in Huawei HCIA-Big Data (best trainee across 30+ participants, first attempt) and AWS Cloud Practitioner. Computer Science degree, GPA 3.4/4.0.
Increasingly focused on DE for AI workflows: building and benchmarking vector store pipelines, embedding systems, and retrieval APIs that run in production. Same reliability principles apply, schema contracts at ingestion, measurable latency, and clean separation between indexing and serving. Retrieval quality is measured with an offline evaluation harness, not assumed.
Get In TouchA business question becomes a reliable data product through deliberate stages. Select any stage to see the reasoning, goal, principles, and projects that prove it in practice.
Actively looking for Data Engineering, Big Data, and Cloud Data Engineering roles. If you're building data infrastructure, pipelines, or lakehouses, reach out. I respond within 24 hours.