Hi, I’m Aleksandr, a Lead Solution Architect designing mission-critical fintech and data platforms at scale.
Greenfield builds, legacy monoliths, vendor platforms: from requirements to production
Greenfield builds, legacy monoliths, vendor platforms: from requirements to production

I design distributed systems, own the full engineering lifecycle, stay hands-on with PoCs and research, and use AI across the SDLC. Outside work, I mentor engineers (500+ one-to-one sessions since 2024), write about system design and have co-authored a Java developer course (opens in a new tab).
Architecture and technical leadershipEngineeringSystems administration
Sep 2024 - Present
GITMAX IT Services, Budapest (remote from Spain)
Bank-wide real-time pricing and billing platform for a top-tier universal bank: ~40 microservices, 99.99% availability, 3 data centres. One of two architects, covering 3 in-house teams and overseeing 2 vendor teams
Feb 2024 - Aug 2024
Self-employed, Montenegro
Offline-first media delivery platform for a railway operator: tens of TB of content replicated to onboard train servers. The product’s first architect, in a 12-person team with no technical lead
Apr 2019 - Jan 2024
Sberbank, Moscow
Federated data-access platform for a 175+ PB data estate: 100 GB/s peaks, 99.99% availability. Proposed the architecture, wrote the MVP and owned the platform end to end as technical lead of a 14-engineer team
Apr 2018 - Apr 2019
Ingram Micro Cloud (now CloudBlue), Moscow
B2B cloud-commerce platform for 200+ marketplaces in 45+ countries, built on a Java/C++ monolith being decomposed into microservices. Technical lead of the 7-engineer team that extracted user and account management into one of the first microservices
Jun 2014 - Apr 2018
SberTech, Moscow
Credit risk assessment platform automating decisions for nearly all of Sberbank’s lending: up to 80k applications a day. Grew it from a 3-engineer service as lead architect and technical lead, working through 4 team leads (25 engineers)
Nov 2011 - May 2014
Neoflex, Moscow
Credit origination platforms for 4 banks, built on the Neoflex FrontOffice product: mortgage, car and consumer lending. Developer across backend, workflows and integrations; stood in for the team lead on production rollouts
Sep 2010 - Oct 2011
Akzia.Apps, Moscow
4 cross-platform consumer mobile apps, including an XMPP-based messenger: one backend per app for iOS, Android and Java ME clients. Backend developer in a 5-engineer team, owning the server side of all four
Mar 2008 - Jun 2010
Media Mir (RBC media group), Moscow
Server estate behind the group’s consumer internet services (QIP, Smotri.com, LovePlanet): ~400 FreeBSD and Linux servers, millions of users. System administrator in a 6-engineer operations team on a 24/7 rota
2005 - 2011
Specialist degree (Master’s level), Computer-Aided Design Systems
Design strategies, ER notations, design patterns from normalisation to versioning, plus replication, sharding and federation
Types of caching, five read and write strategies, eviction and invalidation, and popular solutions
Messaging models and exchanges, the main protocols and APIs (AMQP, MQTT, JMS, STOMP) and how four brokers compare
Six API styles side by side: key concepts, use cases and an example of each
Network types and topologies, common protocols, the OSI and TCP/IP models and network security basics
What each of the four does, how they differ, global and local load balancing and the common algorithms
What a backend engineer is expected to know today, beyond a single language