Spirit: An Internal Platform Run as a Product

Dima Gaevsky leads the strategy and evolution of Spirit, Tinkoff's internal developer platform. The conversation traces his path from engineering and infrastructure architecture to the role of technical product architect, connecting developer needs with the platform's overall direction.

Spirit is presented not as a single portal or tool but as a portfolio of products spanning infrastructure, cloud services, databases, and shared delivery capabilities. The episode also examines a contribution model in which platform features can be built by engineering groups outside the central platform team.

A substantial part of the episode focuses on decomposing ownership. Dima explains why individual platform products need dedicated owners, how his time is split among design, strategy, and communication, and why the outcome of technical leadership is less immediately visible than an engineer shipping a specific feature.

In product work, a short feedback loop matters more than a flawless process. Context holders should speak directly before work turns into tickets, while a technical product manager must understand both engineering and internal customers. The closing advice is to know the user, seek unfamiliar problems, and step deliberately beyond the comfort zone.