Engineer by foundation. Leader by responsibility. Builder by instinct.

The path

1. 2013 to 2018

   The foundation

   I started in IT support and infrastructure while studying Informatics at Indiana University, and stayed long enough to run the systems I had been fixing. Web development ran alongside it. Neither was glamorous, and both taught the same lesson: the people using a system are the only reliable measure of whether it works.

2. 2018 to 2026

   The integration years

   Then Workday, across Appirio, Alight Solutions, and Kainos. Integrations for HCM and Financials, implementations and long-running managed services, mergers that compressed timelines and multiplied source systems. At Kainos I was the first AMS integration consultant in the Americas, then led the team, then ran staffing, forecasting, and escalation for it, then took on product ownership and technical leadership across the global Workday services practice.

3. 2026 onward

   AI engineering

   Since July 2026 I lead AI engineering at Kainos: development accelerators that turn specifications into working code, and the MCP servers and agent skills they run on. The goal is to take the repetitive eighty percent off an engineer's plate so the interesting twenty percent gets their full attention.

The full record, role by role, is on the résumé.

Technical leadership is four kinds of understanding.

The technology

Enough depth to tell a real constraint from a preference, and to know when an estimate is fiction.

The business

Why the work is funded, who it serves, and what it costs when it is late or wrong.

The people

What each engineer is good at, what they want to get better at, and what is getting in their way.

The operating environment

Contracts, compliance, support models, and the downstream systems nobody mentioned in the kickoff.

How I work

Clarity first

If the team cannot explain the system, the team does not own it yet.

Ownership is explicit

Every system, decision, and escalation path has a name next to it.

Reliability is a feature

Nobody notices an integration until it fails. Design for the failure.

Tradeoffs are written down

A decision without its alternatives is an opinion with a deadline.

Developer time is the budget

Automate the repetitive work so judgment goes where it matters.

Stay close to the craft

Leaders who stop building lose the ability to tell good work from plausible work.

Outside the day job

Family

Husband and dad. Everything else on this page exists because of what I'm building at home.

Independent development

collect. for iPhone and iPad, Stagger for one weekend a year, and zckr.dev for everything in between.

Music

A minor in Music Theory and Production from the Jacobs School of Music, and a long habit of listening closely.

Experimentation

A homelab of Proxmox nodes, RAID arrays, and enterprise networking. Where I break things on purpose.