© Anton Dolganin 2025
My name is Anton Dolganin. I'm an engineer. I don't "just write code" — I solve problems through architecture, systems thinking, and the right tools. For me, language or framework is just that — a tool, chosen based on the goal, the constraints, and the realities of production.
I have over 15 years of experience — from building custom websites to designing distributed systems. I've worked solo and in teams, delivered full-cycle projects, set up CI/CD pipelines, built infrastructure, and written code that runs reliably in production for millions of users.
My focus is production. Code that works, updates cleanly, scales predictably, and doesn’t fall apart under real-world load.
Over the years, I've worked with a broad stack:
Java, PHP, Python, TypeScript, React, C++, C#, Docker, Kubernetes, PostgreSQL, Redis, Kafka, RabbitMQ, gRPC, AWS — and more.
And I keep learning, always.
Today, I focus on systems architecture and helping teams build solutions that are stable, maintainable, and production-ready. I'm also exploring GameDev on the side — revisiting what originally got me into tech.
I build, scale, and stabilize systems under real-world load.
production projects
daily users
lines of code
panic deploys
Pragmatic development. Resilient systems. Built for real-world load.
I start with the purpose — not “which language to use,” but “what needs to be solved and why.” Architecture is a trade-off, and I know how to balance it.
Code should live long. Scale calmly. Survive growth. Microservices — only when they actually solve a problem.
CI/CD, monitoring, testing, deployment — not “nice to have,” but the default. If it doesn’t work in prod, it doesn’t work.
Faced a choice: GameDev or web. Chose the latter — and made it count. Quickly gained traction in web development and became one of the early active developers on the Bitrix24 platform, earning MVP status for my contributions and solutions.
Deepened my expertise in corporate (B2B/B2C) development. Bitrix24 offered me a lead developer role — a recognition of both technical skills and responsibility. It was a phase of mastering large-scale production code and working across teams.
Led a team of 5 developers, owned architecture and delivery processes, and formalized DevOps practices. This phase marked the shift from “writing code” to “building systems.” By the end of it, I realized I had grown beyond the company.
Fully focused on architectural decisions, infrastructure, and production-grade reliability. Designing scalable systems, working with CI/CD, and improving long-term maintainability is now part of the daily routine. At the same time, I’ve returned — on a limited basis — to my original passion: game development. Exploring engine design, systems architecture, and component interaction from a serious engineering perspective.
Not sure where to start? Just describe your task — I’ll help you figure it out and suggest the best way forward.
© Anton Dolganin 2025