Jason
Thatcher

I architect, build, and program software solutions to data and backend problems — eight years of production software engineering, the last four pointed at data engineering at cloud scale. Before that, a decade in operations and supply chain leadership: Monte Carlo simulations, data mining, and AUC optimization to minimize cost and maximize margin, managing teams of analysts before most people called it data science.

My work lives in the integration layer — the software that makes systems talk to each other and pipelines actually run. I design and build bespoke solutions from scratch: not just configuring connectors, but writing the code that does what connectors can't. If a system has an interface — an API, a database, a file format, a protocol — I can build something to talk to it.

For the past four years, that work has centered on cloud-native lakehouse architecture — designing, operating, and extending medallion pipelines across Microsoft Fabric, Azure Databricks, Azure Data Factory, and dbt.

My expertise is in the plumbing, not the porcelain. I've built APIs, not just called them. I've written API wrappers and bespoke integration software for legacy systems with no REST endpoint, no SOAP service, no modern interface at all. Cloud platforms like Fabric and Databricks are my primary domain — the software engineering depth is the force multiplier I bring when the platform runs out of road.