Avoid Hiring Data Ninja Rockstars: How To Build Effective Data Teams
summary
Argues against hiring one “data ninja” who does everything and spells out concrete role splits: data scientists do feature engineering, modeling and model metrics; BI analysts build dashboards with SQL and Power BI/Tableau and design business metrics; data engineers handle pipelines, storage (S3, BigQuery), and scaling to samples like 2 million events per second and integrate models into a Scala backend or Python-serving stack. Recommends pre-agreed handoff definitions, separate monitoring responsibilities, and choosing hires by which of engineering, science or domain knowledge the product actually needs.
AI-written summary · about
chapters (8)
- 0:00Introduction to data teams
- 3:01Project case study overview
- 6:18Core data team skill sets
- 8:50The data scientist role
- 13:46The business analyst role
- 16:58The data engineer role
- 21:23Navigating cross-team overlap
- 24:37Summary and audience Q&A
related talks
30mBuilding the best data team is not rocket science
45mA Data Engineer, Scientist and Analyst Walk Into a Bar
01h 05mHow to build your data engineering/data science team?
32mWhat Superpowers Do I Need to Be a Great Data Professional?
39mFoundations of Data Teams
50mBuilding Your Data Analytics Team - live RunAs Radio episode
58mGrowth & change of careers, organizations & responsibility in data science
23mData engineering team leads