About
About.
I came up through computer science at Kent State, then moved into systems and software engineering at Boeing. The through-line is the same one that attracted me to computer science in the first place: take difficult, high-stakes systems seriously, and make careful technical decisions under real constraints.
I gravitate toward work at the seam between engineering depth and practical delivery: hardening brittle hardware-software systems, designing safer operator workflows, and building products that feel considered rather than overbuilt. The part of engineering that holds my attention most is the point where architecture, ownership, and judgment all matter at once.
Outside of Boeing, I spend most of my time building. Ledger is my clearest public software story today as CTO of a civic-tech startup, and my personal projects tend to cluster around truthful systems, strong tooling, and products that solve a very specific problem end to end.
Current focus
Most of my work right now sits at the intersection of applied AI and software engineering. The day-to-day looks like building agentic workflows, shipping LLM-powered features, and helping organizations adopt frontier tools without getting burned by them.
- Applied AI and LLM-powered products.
- Agentic engineering workflows: custom skills, MCP servers, RAG pipelines, tool-using agents.
- Frontier model patterns and how they change what's worth building.
- High-leverage systems where small, careful moves compound.
How I work
-
Systems thinking
Depth before noise: understand the system, then make the smallest high-leverage move.
-
Restrained product judgment
Architecture with a purpose: design for maintainability, operator trust, and real usage.
-
Deep ownership
Stay with the work through the messy middle: design, build, ship, support, and the conversations that hold it all together.
-
Practical experimentation
Hands on the tools, not just opinions about them. Claim less, demonstrate more.
-
Architectural discipline
Clear interfaces, small blast radius, honest failure modes: the discipline that keeps hard systems livable.
Outside the work
Outside of work, I'm usually building side projects, cooking dinner, following Pittsburgh and Cleveland sports, or spending time in Ohio with my wife Sarah and our golden retriever Milo.
Where I'm headed
I'm looking for the next chapter of work where applied AI and product engineering meet under real constraints.
- AI-native companies building frontier-model-shaped products.
- Frontier-model applications across product and tooling.
- Software roles where AI fluency is an edge, not a separate job title.