Episode Materials: Product Engineering with Gleb Mikheev (Category #Leadership)

I have collected the materials from my conversation with Gleb Mikheev, CPO of GigaAgent at Sber. The Code of Leadership livestream took place on September 8, 2026. We discussed what happens to engineering work when several working implementations are easy to produce, yet someone still has to decide which was worth building.

Gleb described spending six months back in an individual engineering role after management, working with agents every day. That experience led into a discussion of product ownership, team structure, and learning.

We discussed: - Product engineering. Understanding a user problem, proposing a solution, shipping it, and collecting feedback. How to give someone that responsibility without piling several previous roles and their full workloads onto one person. - The queue after development speeds up. One useful thought experiment from the conversation: making development five times faster does not make the bottom four-fifths of an old backlog more valuable. The next constraints are choosing hypotheses, verifying results, and operating the system. - Team size and specialist boundaries. Gleb expects agents to let smaller teams cover more work. He qualifies that prediction for payment systems and other critical software, where the cost of failure calls for stricter verification and continued specialization. - Junior development. A finished pull request tells us little about what its author learned. How can we check whether someone can explain the design, spot a mistake, and respond when the requirements change? - Experienced developers learning a new practice. How to move beyond doing everything by hand, retain engineering judgment, and avoid the endless loop of “one more task for the agent, then bed.”

Episode materials: 📌 Episode page with timestamps 🎬 YouTube, VK Video 🎧 Podster, Yandex Music, Apple Podcasts 📝 Text recap

#CodeOfLeadership #AI4SDLC #Engineering #Product #Leadership #Career