I build data systems that survive contact with production.

I never quite settled on calling myself just an engineer. Pipelines are the craft, but what pulls me in is the question sitting underneath them: why a report arrives a day late, why a number won't reconcile, why the same wall keeps stopping the same team. Six years spent in telecom and financial services taught me something I still hold to, that the code is rarely where the real difficulty lives. The harder task is understanding what the business is actually asking for.

I trust systems the way a good risk manager trusts a forecast: carefully, and only after asking what it's quietly assuming. Before a number reaches someone who has to make a decision on it, I want to know it can survive the question "does this actually hold up." I've never been comfortable handing a problem off in pieces. I would rather own it from the messy first draft to the moment it works, and clear whatever is standing in the way along the route.

These days that means Berlin, an M.Sc. in Analytics at Georgia Tech running alongside the day job, and a fairly stubborn refusal to stop being curious about the field. I like being proven wrong if it means I learn something properly. What I'm looking for next is a place willing to hand me a real problem and let me actually own the outcome, not just the ticket.