Engineering leader with 16+ years of experience managing high-performing teams and building scalable cloud & AI-driven systems. At Diri, I lead 10–12 engineers, modernized infrastructure to achieve 99.99% uptime SLA, enabled zero-downtime deployments, and scaled daily transaction processing capacity 6×.
By integrating AI tools — Copilot, Cline, Claude Code, n8n — I boosted feature delivery output by ~30% and streamlined code reviews, embedding modern developer experience practices across the team.
Passionate about fostering strong engineering culture, driving innovation, and aligning technical excellence with business outcomes. I believe great software is built by great teams — and great teams are grown intentionally.
Lead 10–12 engineers across product and infrastructure. Modernized cloud infrastructure to achieve 99.99% uptime SLA and enabled zero-downtime deployments. Scaled daily transaction processing capacity 6×. Drove AI tooling adoption (Copilot, Cline, Claude Code, n8n) increasing feature delivery by ~30%.
Managed 3 squads of 11–14 engineers each. Improved data processing efficiency by 20% through optimized scoring logic and database handling. Drove cross-squad alignment, delivery cadence, and engineering culture initiatives.
Architected frameworks powering media platforms with over one billion page views. Led migrations to cloud-native microservices and championed CI/CD and TDD adoption across engineering teams.
"Great software is built by great teams — and great teams are grown intentionally."
Weekly structured conversations — not status updates. I use a shared doc with standing topics: blockers, recent wins, career goals. It's a conversation first, follow-up second.
I write job specs with the team, not for them. Structured rubrics, calibrated panel debriefs. Curiosity and ownership weigh more than years on a CV or raw technical depth.
Blameless by default. The write-up focuses on timeline, contributing factors, and system improvements — not who was on-call. I read every postmortem within 24 hours.
I stay hands-on enough to read code and review architecture, but don't write production code. RFC process for cross-team decisions. I ask "why" more than "how".
Open to conversations about engineering leadership, team scaling, and technical strategy. Let's connect on LinkedIn.