How I lead, run teams, and use AI without lowering quality.

I lead through clarity, context, and high standards. I try to make the goal understandable, the tradeoffs visible, and the next step concrete.

I prefer operating systems that are lightweight but real: clear priorities, useful rituals, honest status, and follow-through on the work that matters.

1:1s are for trust, feedback, growth, and unblocking. I use them to connect current work to long-term development and to catch small issues early.

I coach engineers toward broader ownership: clearer problem framing, better technical communication, stronger risk judgment, and accountable follow-through.

Production issues deserve calm urgency. I care about customer impact, fast containment, clear communication, and durable remediation after the immediate pressure drops.

AI should make engineering more thoughtful, not less reviewed. I keep human accountability, tests, code review, privacy, and maintainability at the center.

I expect ownership, curiosity, direct communication, care for users, and willingness to improve the system around the work, not only the assigned ticket.

Engineers can expect context, candor, support, technical engagement, and a manager who takes both delivery and growth seriously.