In technology companies, AI is already going beyond the trend and influencing products, engineering, and daily business processes. Along with opportunities come challenges: working with sensitive data, security requirements, and the complexity of integration into existing systems. In such conditions, it is important to understand where AI really creates value and where it just adds noise. During the discussion, participants share their practical experience: how they implement AI in their products, adapt engineering processes, and restructure operations for new tools. This is a conversation about real pain points, opportunities, and solutions that help teams move forward.

As the team grows, products multiply, and the engineering organization evolves - the CTO role often shifts from a technical leader to a manager staring at spreadsheets and dashboards. And that’s when it becomes truly challenging: to stay in the technical loop, remain close to the architecture and systems, and keep a real sense of what’s happening on the ground. In this talk, I’ll share my experience on how to stay a Hands-on CTO - maintaining deep technical understanding, influencing architecture, and scaling the company at the same time, without losing touch with the code and core systems. Key topics we’ll cover: - How the CTO role evolves as the company grows - from coder to system-level leader. - The most common traps: loss of architectural memory, disconnect between business and engineering, dependency on a few key people. - Healthy habits that help keep technical context: code reviews, architecture stand-ups, "walk the code" sessions, CTO R&D sprints. - Decision-making systems: how ADRs and RFCs help maintain clarity and traceability. - Communication with tech leads: building effective 1:1s, technical syncs, and knowledge-sharing loops. - Tools and platforms that preserve context - dashboards, monitoring systems, and architecture reviews.

Being a team lead is like piloting a spaceship where every crew member has their own temperament and trajectory. The DISC model is your GPS that helps you avoid burning up in the atmosphere of “storming” and guides your team into the stable orbit of “performing.”

In his presentation, Vadym will cover: - Goals of the strategy process - Forecasting and goal setting (Foresight, Top-Down + Bottom-Up) - Lean A3: structuring problems and metrics - Strategy implementation and cascading goals - Tracking results (time cycles, OKRs, monitoring, adaptation) - Practical A3 examples

Real experience of building a team from 1 to 30 people: challenges, solutions, and achieved results. We will discuss the team selection strategy, key tasks, implemented tools, as well as recommendations on how to stay afloat in this challenging industry.

How do you transition from a developer to a successful entrepreneur and build a multimillion-dollar business? The real-life journey of founding an AI company in the U.S., raising $2.5M in investments, and key insights into growing a tech business.

A talk on how to build an effective international team, overcome cultural differences, and the importance of personal branding for leaders. The session covers strategies for combining personal and company brands for mutual growth.

Strong teams are not just about execution - they are the foundation for sustainable business growth. They create a safe space, accelerate decision-making, adapt to change, and solve problems before they become critical. This talk will explore how to develop leaders and leadership circles within an organization, build a culture of accountability, prevent burnout, and protect teams from toxic individuals who can destabilize systems from within. Key points: How to build teams that drive business results, not just complete tasks. What leadership maturity means and how to cultivate it. Delegating responsibility without creating chaos or burnout. How to identify and neutralize toxic players (narcissists, psychopaths) in the system, and why they are important for business success. Managing emotional load during times of crisis. Practical tools for leaders to structure chaos and maintain focus on outcomes.

Ever noticed that one team runs like a well-oiled machine while another keeps getting stuck? Why does one developer thrive on freedom while another panics without clear instructions? And most importantly—how do you handle this when you’re no longer just coding, but leading?