Here at Twitch, we’ve been working hard to make evidence-driven decision-making a central part of how we build great products. Data scientists play a critical role in that process. They manage experimentation, contribute to product strategy, design data products, and do deep exploratory data analyses. As the leader of that team, it’s my responsibility to try to create a place where data scientists can be successful and satisfied with the impact of their work at Twitch.
I shared what I’ve learned so far in a talk at Mixpanel’s Office Hours series in May. I present a collection of ten questions that I think you should ask of a team you’re thinking about joining (if you’re looking for a job) or of your own team if you’re looking for ways to diagnose potential problems.
Do you spend the vast majority of your time on projects that take longer than a day?
Do people in the organization have ways to access basic data without asking a data scientist?
Do you spend more time doing analysis than waiting for data?
Is there documentation for major schemas?
Do you have a process for detecting and fixing bugs in data collection?
Is past research work documented and available in a central location?
Does the team have a regular process for reviewing work before sharing it?
Do you run randomized and controlled experiments?
Can you report negative results without major political pressure?
Can the CEO (or other leader) name at least one way the team contributed that quarter?
You can learn more about data science work at Twitch at our team homepage. If you’d like to read more about these questions, check out a longer version of the list. We are hiring data scientists and data science managers, so if you’re interested in working with us, we’d love to hear from you! We’re also hiring user experience researchers, a head analyst, and an analytics product manager.