I'm a software engineer and tech lead with a path into the craft that didn't start with code. I spent the first decade of my career in financial operations and business analysis before transitioning into engineering, and that background is load-bearing. Understanding how systems serve people before learning how to build them shaped everything about how I approach the work — and it's the direct reason I moved into a technical lead role quickly once I made the switch.

I approach this craft the way a good tradesperson approaches their work: complexity is a tool, not a default. I reach for it only when the problem actually demands it. The measure of a well-built system isn't how impressive it looks on the day it ships — it's whether the engineer who inherits it two years later can understand it, trust it, and extend it without fear. That's the standard I build to.

My day-to-day lives at the intersection of Node.js, TypeScript, and Java services stitched together with event-driven patterns on AWS and Kubernetes. Outside of production work I'm deep in agentic AI — building personal projects with LangGraph and CrewAI and driving adoption of AI-augmented workflows across my team. I care as much about the people using what I build as the engineers maintaining it. Technology that doesn't genuinely serve both groups isn't finished yet.

When I'm not building production systems, I'm exploring the edges of what agentic AI workflows can actually do at scale — which is less "impressive demo" territory and more "will this hold up at 3am on a Tuesday" territory. I'm based in the northern suburbs of Cincinnati, OH and selectively open to remote opportunities where the problem space is genuinely interesting or the mission of the organization is compelling and meaningful.