Frontend Reliability: From Alerts to CRO

Boris Chernysh leads T-Bank's web platform development and serves as Chief Reliability Officer for client interfaces, covering web, mobile applications, and APIs. With Alexander Polomodov, he traces a path from mathematics and C++ to platform architecture and leadership of SRE teams.

Boris studied computer security but chose software development. After algorithmic trading, freelance work, a CRM for an eyewear retailer, and municipal parking systems, he joined the Tinkoff project through CSSSR. The move into a large monolith taught him the cost of communication, architectural constraints, and technical debt.

As team lead, Boris tried to preserve engineering depth, moved delivery toward Kanban, and developed a microfrontend-based forms platform. A client-monitoring project expanded from alerts into metrics, on-call rotations, error budgets, and ownership design. The web SRE teams eventually moved under his leadership.

A second thread covers personal-account reliability: resource mistakes in the old Node.js monolith, static fallbacks, and the design of a new platform. A host application, microfrontends, and ready-made pipelines hide Kubernetes from product teams. As CRO, Boris is learning to frame the right questions in unfamiliar domains and move between engineering and management.