Leadership Philosophy
Engineering leadership is not a management role — it’s a force multiplier role. My job is to make the ten engineers around me collectively more capable than any ten engineers I could hire. That means building systems, culture, and clarity, not just shipping features.
I’ve spent 15 years inside high-growth environments — from building the infrastructure that ran six media properties at 1B+ monthly page views, to scaling a healthtech platform through 12× transaction volume growth while holding 99.99% uptime. What that history taught me is that sustainable speed comes from investment in fundamentals: CI/CD discipline, TDD culture, clean architecture, and deployment confidence. Not as checkboxes — as deeply held engineering values. Teams that treat these as optional will eventually slow down or break in production. Teams that internalize them ship fearlessly.
I care about measurable outcomes, not activity metrics. When I led the backend optimization at Mamikos across 30+ engineers, the measure that mattered wasn’t story points delivered — it was the 20% reduction in data processing time that unblocked product teams. When I drove AI adoption at Diri, the measure wasn’t tool adoption rate — it was the ~30% increase in feature delivery velocity that engineering and business both felt. I ask my teams: “What would change for the user or the business if we shipped this?” If the answer is vague, we haven’t thought hard enough.
The transition from monolith to microservices at KapanLagi Youniverse didn’t succeed because of the technical architecture. It succeeded because the engineers who built it understood the problem deeply and had the confidence to make consequential decisions. That’s what I try to build in every team: the judgment to act autonomously without waiting for permission, and the ownership to see things through to the outcome, not just the PR merge.
AI changes the ceiling on what a small team can do — but only if the team knows how to leverage it. I’ve integrated AI-assisted workflows across engineering organizations and built early ML models for business prediction. The pattern I’ve learned: AI amplifies good engineers and reveals weak foundations in bad ones. Invest in the engineering fundamentals first. Then AI gives you back time to think bigger.