Code of Leadership: How a CTO’s Responsibilities Grow, with Vasiliy Gigauri (Series #Management)

My guest in the new episode on November 17 at 15:00 Moscow time is Vasiliy Gigauri, CTO and board member at Chestny Znak. His experience includes working at Deutsche Bank and BNP Paribas, growing an engineering organization from 200 to 580+ people, and leading technology changes in a national-scale system.

We’ll talk about how leadership changes when you’re responsible for several teams, the resilience of a large platform, and decisions the business depends on. Where does your own technical depth still help? When does the habit of getting into everything yourself start to slow the organization down?

We’ll go through specific decisions: — From engineer to manager: how to delegate work you could do faster yourself and notice when everything is starting to depend on you again. — Moving into a new domain: what carried over from banking to Chestny Znak and which decisions had to wait until he understood the domain better. — Changing a large system: how to agree on shared engineering processes, preserve team autonomy, and check whether the redesign helped. — The CTO on the board: how to weigh technically worthwhile work against other company priorities, discuss risks, and stand by a disagreement. — AI in engineering: how responsibilities change and how to measure the effect, accounting for review, rework, and maintenance.

We’ll also discuss the management principles Vasiliy had to reconsider as his responsibilities grew. What would you ask him? Leave your questions in the comments.

#CodeOfLeadership #Leadership #Management #Engineering #AI