Fifteen years building the parts of a product that have to keep working: distributed Go backends, media pipelines, and the databases under them. At Ezoic I led Flickify from the first line of code to a shipped product — a Go pipeline that scripts a web page with an LLM, narrates it, and renders it across a fleet of AWS workers. I write Go and PHP, and I am usually the person who goes and reads the spec.
Selected work
All projects →Flickify ↗
2020 — 2026Turning an article into a watchable video was a manual editing job measured in hours, which meant publishers simply did not do it. A Go pipeline that parses the page, scripts it with an LLM behind a three-provider routing layer, assembles scenes from stock, generated and templated assets, then renders through After Effects and FFmpeg across a fleet of AWS workers fed by SQS — spread wide because a single render node was nowhere near fast enough — with a Vue editor over the top for anyone who wants the last word.
e-Freight declaration platform
2013 — 2019Air cargo paperwork moved on paper between airlines, warehouses and the federal customs service — every handoff a place to lose a day. A PHP/PostgreSQL platform speaking IATA CIMP, SITA, ARINC and EDIFly Type B, with GOST-qualified digital signatures through CryptoPro and direct integration into the customs IT system — built with a team of four, then extended to a second country's customs regime.
Publisher platform services
2019 — 2026Ad and content experiments needed backends that stayed available under spiky publisher traffic without degrading response times. Go and PHP microservices with Vue front ends, built around measurable request budgets and backpressure rather than optimistic caching, provisioned in Terraform and watched in Grafana.
Career · 2011–2026
Full history →Tools I reach for
MSc Computer Science — Moscow State Institute of Radio Engineering, Electronics and Automation (now RTU MIREA), 2011
English (professional) · Russian (native)