Engineering leadership

Engineering leadership is coaching people who build together — especially when agents join the loop. Mentorship, cross-team collaboration, and clear process around AI and event-driven workflows are how ownership stays real as the tools move.

The work I care about is still people and systems: helping engineers grow, aligning teams that do not share a roadmap by default, and designing the rituals that keep delivery honest. Coaching is not a side channel — it is how judgment compounds when the surface area of the product keeps expanding.

AI changes the tempo, not the responsibility. RAG pipelines, connectors, and event-driven agentic workflows are leverage when teams can see what ran, why it ran, and who owns the outcome. Without that, you get demos. With it, you get a harness people can operate under load.

Leadership, then, is less ceremony and more continuity: hire for ownership, mentor in public, renegotiate process when agents join the workflow, and leave systems that still work when you are not in the room.