Hi.
I'm Alex.
I love when complex becomes simple. Found myself in backend development and architecture. Since 2007 on one vector: development — systems — architecture.
I'm alive. I hear you. I can help with a heavy system, a team deadlock, or an idea with no one to build it. No upfront promises — just an individual approach and a deep dive into your specific situation.
I reply myself within a day
Aleksei Zorin
Solution Architect
15+ years in IT · high-load · 80+ services · 50+ engineers
Backend Engineering·Message Brokers·Structured & Unstructured Storage·Deployment Strategies·Event Sourcing·Observability
PDF · 2 pages · updated 22.06.2026
- 200714 y.o.
First PHP book
Dmitry Koterov's already outdated book on PHP 4 at the time. Picked up the rest from online docs.
- 201118 y.o.
First internship in IT
Invited without a resume.
- 201320 y.o.
First IT job
Krasnodar, web-dev studio. First office, first deadlines.
- 201421 y.o.
First public code
Created a GitHub account.
- 201522 y.o.
First serious experience
3 years as Backend Engineer in an outsource team — CRM for Shell, online schools, promos for L’Oréal, Pandora, Sber, bots, diaries. Learned to build backend I'm not ashamed to ship.
- 201724 y.o.
First year outside the usual context
A year in the Philippines. Different country, different pace.
- 201825 y.o.
First experience with microservices
Backend Engineer, Prague. Big legacy monolith on yii1. Integrations, queues, decomposition. Saw where it breaks.
- 201926 y.o.
First lines of Go
Tried Go — love at first sight.
- 202027 y.o.
First management experience
Since then built 4 teams.
- 202330 y.o.
First architect role
Solution Architect with a fast track to Lead — took ownership of a complex system and built a team.
- Dec 202330 y.o.
First AI subscription
Paid for ChatGPT Plus on Dec 26.
- 202431 y.o.
First real achievement
A crisis project became a turning point.
- 202532 y.o.
First scale — 50+ engineers
Lead Architect in FinTech. 80+ services, 7 teams, 50+ engineers, 20+ integrations, ADR, reviews, standards, dev committee, architect team.
- 202633 y.o.
What's next?
I realized the skills I've built — design, simplification, alignment — work anywhere in IT. After me things became clearer, simpler, more efficient, not more complex.
But the further I go, the sharper the questions of meaning become. I no longer want to do IT for IT's sake, RPS and complexity for complexity's sake. I want to do things with meaning.