Skip to content
all episodes
Code of Leadership · episode 90

How a CTO’s Responsibilities Grow with Vasiliy Gigauri

2:05:34

Episode participants

Conversation

What we discussed on the recording

When Deutsche Bank decided to close its equities business, BNP Paribas had to work out how to preserve the service clients relied on. Vasiliy explained which platforms the buyer would need and why it should bring over the engineers who built them. The hardest conversation was with the engineers themselves. They had jobs at a bank they knew, while the BNP Paribas technology centre in Moscow and St Petersburg had yet to be set up.

To explain his work at Chestny Znak, Vasiliy follows a carton of milk from the dairy to the till. Before bottling, the tracking system checks the batch volume against veterinary records. If that check stalls, milk sitting in tanks can spoil. At the shop, scanning the same carton answers different questions. Is it past its expiry date? Has a product with that code already been sold? Here the customer waiting at the till feels the delay.

Adding a new product category affects both the tracking services and the shopper’s app. Business owners agree on priorities each month so every team can finish its part by the deadline. Teams used to bundle their changes into one release and wait for one another’s fixes during integration testing. Now each team deploys independently. Shared feature flags let them switch on the feature once all the pieces are in place.

A seat on the board helps Vasiliy see what engineering will face two or three years ahead. Conversations with business colleagues showed him that regulators would increasingly ask for changes deep in the core system. When introducing AI, his team could draw on the way its systems analysts already worked. He uses OpenSpec to explain why a new tracking rule deserves a detailed specification and a check against existing rules before anyone starts writing code.

Engineering managementLeadershipArchitectureStrategy