Building pipelines that businesses can actually trust.
Started in consultancy. Stayed on merit. Promoted to senior in two years. I design and build robust data infrastructure — from ETL pipelines and streaming ingestion to Unity Catalog migrations and modernising legacy workflows.
I started my career in consultancy, but on my first client deployment I never left — retained as a junior data engineer and promoted to senior within two years. That story says a lot about how I work.
I take ownership of problems end-to-end. I don't just write notebooks — I think about maintainability, observability, and what happens six months after I've shipped something. My manager's words: hardest working, best engineer on the team.
I'm language-agnostic and cloud-comfortable. Give me a messy legacy process and I'll give you something clean, documented, and built to last.
Led the first production Unity Catalog migration at enterprise scale — with no internal blueprint to follow. Converted critical pipelines from legacy to UC, establishing the pattern used by the team going forward.
Built an end-to-end ingestion framework on a newly released third-party API. Hourly jobs resolve download endpoints, ingest data, and log every run to a central audit table — providing full pipeline observability across all downstream consumers.
Designed a YAML-configured notebook that allows tables to be added or removed from audit pipelines without touching code. Built to support post-acquisition data integration — a single config file drives the entire process.
Consolidating a fragmented redaction and retention process — previously spread across ADF, multiple notebooks and SSMS lookup tables — into a single, seamless Databricks workflow. Replacing complexity with clarity.
If you have a project or role that you think might be a good fit, feel free to reach out and we can have a conversation.