Data Engineer

I’ve worked as a data engineer for about three years, building and maintaining data systems that move and transform large datasets. In that time, I’ve worked with databases containing millions of rows, built batch processing pipelines, and designed BI systems that help both internal teams and external stakeholders make sense of their data. I’ve also set up end-to-end data pipelines that move data from source systems to analytical destinations, using tools like Python, Airflow, dbt, and queue systems such as Kafka and Celery to keep data flowing reliably.

Along the way, I’ve learned that good data engineering isn’t just about writing pipelines—it’s about making systems easier for people to work with. One example of that was containerizing our data stack with Docker so new engineers could spin up a mirror of the production environment on their machines much faster. It removed a lot of the friction that usually comes with onboarding or reproducing production issues.

What sets me apart is that I naturally look for ways to standardize and simplify processes. If something is being done repeatedly, I try to design a structure around it so it becomes predictable, less error-prone, and easier for the team to maintain. That mindset has shaped how I build pipelines, manage data transformations, and structure systems so they are not just functional, but reliable and repeatable.