I build data systems that are clean, reliable, and actually used.
Rather than just moving data from A to B, I focus on why pipelines break, why data gets messy, and how to design systems that teams can trust.
- I care about data quality, not just data volume
- I think in schemas, flows, and dependencies
- I believe observable pipelines beat black-box ones
- I design for the engineer who maintains it next
π Model data β βοΈ Build pipelines β π Serve insights β π Monitor & iterate
My goal is to build data infrastructure that analysts can rely on and engineers can extend.
Languages & Query
Data Engineering
Cloud & Storage
(Swap in only the tools you've actually used β recruiters check.)
- Understand the business question first
- Model the data to answer it clearly
- Build pipelines that are tested and monitored
- Make the output consumable β dashboards, APIs, or clean tables
- Document it so the next person isn't lost
- Building end-to-end batch & streaming pipelines
- Learning data modeling best practices (Kimball, Data Vault)
- Exploring dbt and modern data stack tooling
Good data is invisible. Bad data is everywhere.
Building pipelines that don't wake you up at 3am βοΈ