Role
Backend & systems engineer
I keep backends running inside other people's constraints.
Availability: Open to a conversation
6
years in backend
3
systems in production
99.95
uptime over 12 months
Local time
Dushanbe, Tajikistan · UTC+5
About
Six years of server-side work in places where the stack is not a choice: shared hosting at a regulator, customs registries without documentation, NGOs with no infrastructure budget.
I work with what is already in production rather than what I would rather deploy. Architecture, to me, is the list of constraints you agreed not to route around.
Mostly Go and PHP on the server, PostgreSQL and MySQL for data, Prometheus for observability. I work in Tajik, Russian and English.
I add observability
I come into systems that have logs but no metrics, and make incidents readable from a dashboard rather than from whoever was on call.
I work inside given limits
Shared hosting, no new services allowed, an undocumented registry — I design for the constraint instead of routing around it.
I hold the contract
I reduce mismatched sources to a single response and keep it from going stale when those sources change without warning.
I write down what failed
Every case study has a "what I would do differently" section. Not modesty — a way of not repeating myself.
Stack
Level is not self-assessment but fact: where the code reached production, where it stayed in day-to-day work, and where I only read and patch what others wrote.
Work
Financial regulator
A public API that folds deposit terms from every bank in the country into a single response. The constraint came from the client: shared hosting, PHP 7.4 with no framework, no composer, and no cron more often than every fifteen minutes.
p95 of 82 ms on shared hosting
Customs clearance
A Go service that parses goods declarations and matches them against the customs registry. A thirty-two goroutine worker pool, a circuit breaker in front of the external registry, metrics in Prometheus.
1,400 declarations per minute
Non-profit sector
Fundraising for verified non-profits: recipient vetting, payment intake, public reporting on every campaign. No infrastructure budget — the whole thing runs on a single server.
Beta: 11 organisations onboarded
Experience
Mar 2025 — now
Backend lead
Jan 2024 — Feb 2025
Backend engineer
Jan 2023 — Dec 2023
Backend engineer (contract)
Apr 2021 — Dec 2022
Server-side developer
Sep 2019 — Mar 2021
PHP developer
Lab
No client here and no SLA. Every demo runs right on the page.
Visualization
Rendering distributed-trace spans with no external library — CSS grid and transforms only. The thing this site’s hero screen grew out of.
Tool
A script that measures ӣ ӯ қ ғ ҳ ҷ via canvas.measureText, comparing "font, fallback" against fallback alone. Identical widths mean the glyph is missing from the file.
Algorithm
Damerau–Levenshtein distance over a trie of tariff positions. Extracted from a client project and stripped of anything client-specific.
Shader
A modular lattice with mirror symmetry computed in a fragment shader. The same geometry that sets the site grid — without treating ornament as an image.
Contact
I reply within a day. Telegram is fastest.
Or use the form
