Use Code PATIMES15 for 15% off a two day pass or combo pass. (Excludes workshops & All Access)
Earlier this year, the White House announced it named Dr. DJ Patil as its very first Chief Data Scientist. With the claim that the U.S. has seen “an acceleration of the power of data to deliver value,” White House CTO Megan Smith (formerly of Google) has further reinforced the notion that making data-driven decisions is becoming pervasive – not just in bleeding edge startups or the biggest technology companies.
Everywhere you turn, companies are hopping on the bandwagon and bringing in someone to be their dedicated in-house “Data Scientist.” People like Jonathan Goldman at LinkedIn have paved the way for this new career, one that Harvard Business Review even called the “Sexiest Job of the 21st Century.”
So – why is this happening now – almost 30 years after the first dot com domain was registered and the floodgates of digital data opened?
It’s no big secret that the amount of data companies are generating is exploding exponentially. As of 2012, about 2.5 exabytes of data (2.5 billion gigabytes) was being created each day, and that number is doubling approximately every 40 months. The volume is growing and it could be argued the speed at which the data is coming in is growing even faster.
At the same time, this exponential increase means the tools and skills needed to make sense of that data has become a specialized skillset, and not just another tool in a developer or marketing analyst’s toolkit.
Enter: the data scientist.
Do I Need A Data Scientist?
Before you get ahead of yourself and start making job posts tomorrow to hire your first data scientist, have a discussion with your team about whether or not you even need a data scientist.
There are three key questions to ask:
If the answer is “no” to any of the above of them, then you’re better off using the right 3rd party analytics platform that your non-technical users can use day-to-day. Even if you’re generating billions of data points a month from hundreds of millions of users, using a 3rd party tool can potentially still lower total cost of ownership and free up valuable time from both your engineering team (who won’t have to support your infrastructure), and your sales, marketing, product, operations, customer success, etc. teams that won’t have to learn on internal teams for support.
However, there are twp cases where you should consider building out your own data science team – 1) if you need to build predictive models, or 2) a significant portion of your business happens offline. If either are true, and you can additionally support building out your own data infrastructure then you should consider building out a data science team.
What Do I Look For When Hiring A Data Scientist?
So, let’s say it is a priority for your company – now what?
I often get asked this question by both startup founders and Fortune 500 CTOs. As the analytics field and data needs have evolved so rapidly, often your best potential hires didn’t have the title “data scientist” previously, or were working in an analytical role in a specific area like marketing or operations.
Based on personal experience and feedback from founders, the top things I’ve found to look for when hiring your first data scientist are:
How Do You Become A Data Scientist?
This excerpt is from Business2community. To view the whole article click here.
Jeremy Levy, CEO, Indicative
Originally published at www.business2community.com