A tech lead who still
reads the execution plans.
Based in Kyiv, working remotely with teams worldwide. I've grown from
hands-on backend engineering into technical leadership — and I'm building
toward the architect role deliberately: ADRs, system design reviews, and
owning decisions end to end, not just writing code that works.
My approach: understand the business problem first, then engineer the
simplest architecture that solves it. No over-engineering, no hype-driven
development. I stay close to the details that decide whether a system
survives — query plans, failure modes, migration strategies — while
keeping the team shipping.
Architecture-first
Hexagonal architecture, DDD, event-driven systems. Decisions written down as ADRs, not tribal knowledge.
Team leadership
Mentoring engineers through code review, pair programming, and design sessions. Coverage gates and review culture that stick.
Database depth
PostgreSQL performance is a specialty: execution plans, indexing, partitioning, zero-downtime migrations on hot tables.
Security-aware
PCI-relevant flows, HMAC-signed webhooks, card-data masking, 3DS. Payments taught me to treat security as a requirement, not a feature.