Technical leadership for automotive platforms
Backend architecture, engineering governance, technical-debt planning, hiring, and an active AI-assisted SDLC/PDLC pilot.
Role and outcomes →Engineering systems that survive real operations
Tech Lead and staff-level backend/platform engineer working across distributed systems, delivery platforms, and technical leadership. I stay close to the code while building engineering practices that can scale.
Current work
My strongest work happens where product pressure, technical complexity, and organizational change meet. I combine hands-on engineering with explicit ownership of architecture, hiring, technical debt, and delivery practices.
Backend architecture, engineering governance, technical-debt planning, hiring, and an active AI-assisted SDLC/PDLC pilot.
Role and outcomes →Part-time Co-founder and CTO: product vision, architecture, code, DevOps, and the path from early product iterations to live use and growth.
Explore HZProtocol →High-performance Python identifiers, typed SDKs, authentication starters, authorization patterns, and delivery automation.
View GitHub →Selected engineering
These projects represent the kind of systems I enjoy: narrow interfaces, explicit operating constraints, measurable performance, and documentation that helps another engineer run the thing.
A fork-safe, CSPRNG-backed UUIDv7 implementation with typed scalar and native batch APIs for Python 3.9–3.14.
Repository →Typed Python clients and infrastructure for building products across Polymarket, Kalshi, and Opinion market data.
Repository →A production-oriented sidecar reference for fine-grained policy enforcement in API and microservice environments.
Repository →A maintained Dash + Flask authentication starter with Nginx, Docker Compose, responsive UI, and secure password reset.
Repository →The unusual advantage
Before becoming a software engineer, I owned and operated businesses in logistics, supply, and trade — including complex deliveries to Russia's Far North.
That background changed how I see software. Architecture is an operating model. Reliability is a business property. Ownership, handoffs, lead time, and constraints matter as much in a codebase as they do in a supply chain.
I also hold an MBA in Logistics and Supply Chain Management from HSE University.
Read the full backgroundWriting
Architecture, technical debt, platform engineering, AI-native delivery, product work, and the lessons that connect software to real-world operations.
A practical operating model for risks, ownership, treatment, and recurring investment.
Bounded agent roles, explicit delivery contracts, review evidence, and human authority.
Queues, handoffs, retries, buffers, observability, and recovery across real operating systems.