Building a large data science team is hard. It’s still a nascent practice, and there are no models to follow. Much of what works for established departments like engineering, BI/analytics, and other functional areas does not apply to data science. Don’t force this decidedly square peg into a round hole. Instead, take time to understand the nuances of how a data scientist thinks, works, and thrives and design something completely appropriate for them.
Through his unique experiences of building several large data science teams (80+ people) at companies like Stitch Fix and Netflix, Eric Colson has learned a few things. These lessons aren’t obvious and could have only come through experience, trial and error, and iteration. Join Eric as he recounts some valuable lessons learned, including:
Some of these may seem unintuitive, and they may not apply to all cultures or organizations. But understanding the nuances may inspire new thinking that allows you to unlock the potential of your data science team.
Eric Colson is chief algorithms officer at Stitch Fix as well as an advisor to several big data startups. Previously, Eric was vice president of data science and engineering at Netflix. He holds a BA in economics from SFSU, an MS in information systems from GGU, and an MS in management science and engineering from Stanford.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org
Apache Hadoop, Hadoop, Apache Spark, Spark, and Apache are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries, and are used with permission. The Apache Software Foundation has no affiliation with and does not endorse, or review the materials provided at this event, which is managed by O'Reilly Media and/or Cloudera.