AWS, GCP, Terraform, Python, SQL, PySpark, dbt, Airflow
Tools are part of the story, but the more important part is how they fit together into one operating platform.
About
Platforms that are useful, understandable, and built with discipline.
I work across data engineering, analytics engineering, and cloud platform design. The thread that ties the work together is a strong interest in full systems: infrastructure, ingestion, transformation, orchestration, serving, and the habits that keep them healthy.
Professional profile
What I tend to build.
I like work that moves beyond isolated ETL jobs. The systems I care about most are the ones where storage, orchestration, identity, documentation, and the final user experience all matter together. That is why the core platform work on this site is a full data platform instead of a single pipeline script.
The site itself follows the same idea. It is not meant to be a noisy showcase. It is meant to help another developer understand what was built, why the repos are split the way they are, and which parts are worth studying first.
CDC, medallion layers, orchestration, analytics serving
The strongest work here follows the full path from raw events to stakeholder-ready answers.
Principles
What I want the engineering work to reflect.
Clear data boundaries
Bronze, Silver, and Gold should mean something real in storage, quality expectations, and consumer trust.
Enterprise workflows
Issue-first work, feature branches, clean `main`, and least privilege are part of the normal shape of delivery.
No casual hardcoding
Write the logic once, parameterize carefully, and let the environments differ through controlled inputs.
Documentation that lowers confusion
If a teammate still cannot follow the system after reading, the implementation is not finished yet.
Why this site matters
A long-term engineering base, not just a profile page.
It organizes the public work.
The AWS repos are already substantial. This site helps developers see the whole picture faster.
It carries the GCP learning journey properly.
The GCP rebuild is private, but the architectural lessons and platform reasoning deserve a clean home.
It gives the writing a stable place to grow.
Some of the strongest explanations already live in repo READMEs. Over time this site will add more focused writing around them.