The Journey of a Systems Thinker
For 14+ years I've worked at the seam between business intent and integration architecture — translating ambiguous operational reality into requirements, data models, API contracts, and process flows that delivery teams can build against.
"The bridge between a business problem and a technical solution isn't a document; it's a shared understanding of possibility — versioned, reviewed, and testable."
Professional Evolution
My track record spans large-scale retail and banking environments. At Metro I learned the scale of logistics and led a single integration landscape across 20+ system interfaces. At MediaMarkt I ran a multi-year legacy replacement (200+ legacy processes documented; 25% rework reduction). Alfa-Bank brought 30+ APIs integrating call-center to core banking, serving 40M+ customers and 7,000+ agents. Axioma sharpened the craft into formalized requirements engineering — a 6× drop in defect rate and 2× faster feature delivery.
Across all of it, my role oscillated between Business Analysis (what to build) and Systems Analysis (how to build it). I've come to read those labels as increasingly artificial.
The Thesis: Dissolving the BA/SA Role
The line between "what" and "how" is dissolving. A modern analyst cannot afford to be one without the other — and AI-assisted tooling makes the middle layer of pure translation work obsolete faster than most teams realize.
Technical Depth
Reading code, modeling data, and reasoning about APIs and microservices is no longer optional for senior analysts.
Business Empathy
Market context and user psychology have to inform every technical decision for it to hold real-world value.
How I Work
Documentation-first. Docs-as-code where it fits. Requirements engineering treated as engineering: versioned, reviewed, testable. Methods chosen for the problem — BPMN where flows matter, C4 where boundaries matter, ERD/UML where data matters — rather than for ceremony.
Languages
Russian (native) · English (B2)