Building the best data team is not rocket science
summary
Argues that the right data team aligns responsibilities to hires and gives concrete hiring rules: start centralized/decentralized/federated based on company size, build around three pillars analytics strategy governance, and hire for specific skills — SQL + viz for data analysts, Python/R + stats + domain for data scientists, and software/DevOps + ETL for data engineers. Recommends centralized analytics-first for small startups, balance for midsize, federated at scale, and tracks hiring risks like false positives and missed candidates.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 3:22Defining the best data team
- 12:42Company size impact on team structure
- 14:08Scope of the data team
- 15:58Team structure models
- 21:38Core team roles and skills
- 24:50Hiring false positives vs negatives
- 27:20Diversity in data teams
- 28:03Practical hiring tips by company size
- 29:48Conclusion and Q&A
related talks
30mAvoid Hiring Data Ninja Rockstars: How To Build Effective Data Teams
23mData science as a team sport
01h 05mHow to build your data engineering/data science team?
29mBuilding successful data teams in the realities of 2023
38mBuilding Effective Data Teams: Strategies for Success
16mBuilding a Computing Environment to Support Analytics
43mFrom instinct to informed decision: launching data in your startup
23mHow to Build a Data-Intelligence Startup within your Organization