About This Talk
At Data Fest 2021, I introduced the concept of the “Data Partner” — a role that emerged at Yandex Go (formerly Yandex.Taxi) and sits at the intersection of technology, analytics, and business. The talk covered what this role is, why it exists, and how it differs from adjacent positions like system analyst, data engineer, or engineering manager.
The Problem
As data teams grow beyond 10-15 people, a gap emerges. Data engineers build infrastructure but aren’t close enough to business problems. Analysts understand business questions but can’t influence the data platform. Managers coordinate but don’t have the technical depth to make architectural decisions. Someone needs to bridge these worlds — and that’s the Data Partner.
Key Ideas
What Is a Data Partner? — A hybrid role that combines deep technical understanding of data infrastructure with business domain expertise. The Data Partner translates business needs into data requirements, ensures data consumers get what they need, and prevents the data platform from diverging from actual use cases.
How It Emerged — At Yandex Go, the role evolved organically. As the data platform grew, we noticed that the most effective team members were those who could speak both “engineer” and “analyst.” We formalized this into a dedicated role with clear responsibilities and career growth path.
How It Differs — Unlike a system analyst, the Data Partner has hands-on technical skills and can prototype solutions. Unlike a data engineer, they spend significant time understanding business processes and stakeholder needs. Unlike a manager, they’re an individual contributor focused on bridging gaps rather than managing people.
When You Need One — Organizations with 10-15+ person data teams, multiple data consumers with competing priorities, and a growing disconnect between data infrastructure builders and data consumers.
Why It Matters
As data teams scale, the organizational design becomes as important as the technical architecture. The Data Partner role is one solution to a common scaling challenge — and even if you don’t adopt the exact role, the principles behind it (bridging technical and business worlds, ensuring alignment between infrastructure and consumption) are universally valuable.
