Subscribe to DSC Newsletter

Data scientist paid $500k can barely code!

This is not about attacking a guy - a friend of mine - who, at first glance, seems extremely overpaid, like any top executive. Indeed, the question is about whether data scientists should be coders (spending 50% to 100% of their time writing code) or not.

I believe the answer is negative. There are many different types of data scientists, and no real data scientist, in my opinion, spends more than 50% of his/her time coding. But you are welcome to post your point of view. Data scientists spend much of their time producing measurable added value, and many times, it involves intuition, vision, and gut feelings, and stuff that you don't learn at school.

Some interesting comments that I've read include

  • A good data scientist is a bad coder, and conversely
  • Curry spaghetti is to statistical science what new cuisine is to Italian/Indian cuisine

The latter is about the top qualities any data scientist should have: creativity, and the disruptive element to think about products that no one before would ever imagine it would work. And also the fact that data science is a blend of several disciplines.

Here is an example of a data scientist, still writing Perl programs and relying on vision, yet creating bridges (API's) between platforms, to automate growth hacking, lead generation, and everything that comes with it, to the point that it is described as IoT (Internet of Things) for digital media. Almost without coding. Some top automated trading algorithms are just like that, being mostly machine-to-machine communications, involving very little coding.

Data science is not just about coding, and my friend makes money from algorithms that deploy machine-to-machine communications, with very little coding involved: instead, it's about high-level API's and web apps, many times leveraging vendor platforms where much of the code resides. Many top data scientists actually do not code at all: they either manage a startup, or supervise coders. Those who spend their days coding are not real data scientists.

As an hiring manager, if you interview candidates, be aware that the data scientist job title has been abused, and do your due diligence to identify candidates that will make your client happy. Today, someone who can barely write an R program call herself data scientist and demands a $100k salary just out of her training. I think the data scientist job title should not be legalized like doctor or lawyer, but when hiring a so-called data scientist, ask for success stories, coding samples, and references. My 2 cents.

DSC Resources

Additional Reading

Follow us on Twitter: @DataScienceCtrl | @AnalyticBridge

Views: 56648

Comment

You need to be a member of Data Science Central to add comments!

Join Data Science Central

Comment by Ralph Winters on August 1, 2017 at 2:52am

There are many quants or traders in the financial domain , who work with their own tools (no R, no Python, no SAS)  who could easily call themselves data scientists. All they need to do is develop 1 hedging strategy which yield multiples of their 500K.  Some really know their domain inside out, can quickly develop their own ideas, and implement them quickly.

Comment by Bohdan Pavlyshenko on June 26, 2017 at 11:28pm

I work as a data scientist (PhD) in the area of sales forecasting in FMCG, fraud detection, I was a teammate of the team which won the Kaggle competition (our #1st  place solution here). I cannot imagine how I can do my work as a scientist only without programming skills  in Python  and R. If I see some predictive analytics problems,  I understand what approaches can be applied to solve it.  But to get good solutions I need to  analyze distributions, generate a lot of new features, select most effective of them, do a lot of validations of models, build ensembles of models,  etc. I can do all of these things  only using my programming skills. Before I get the final effective model which can be implemented into production, I need to create a lot of prototypes for the analysis and if  I ask some engineers  to do programming work, in my opinion, it will be a very long process.

Comment by Pete Mancini on December 20, 2016 at 7:32pm
50% is about right. However, if your coding skills are garbage I won't hire you. Good vision and math skills are needed, for sure, but you must execute on those visions. For entry level data scientists, any coding skills are fine. I can teach R, Python, and Julia to you. At higher levels you better be able to create robust models for mission critical tasks without needing a lot of support. Most general programmers don't understand what we do to give adequate support, so the burden is on you. I assume the person making $500k is in NYC or LA NYC or la working for a company that has money to burn. If you like that life style, it's one way to go.
Comment by Maksymilian Piechanowski on July 4, 2016 at 11:33pm

This is very inspiring. Thank you!

Comment by Oliver Chikumbo on March 24, 2016 at 12:40pm

Why are folks so hung up about what what a data scientist should be or shouldn't be? As far as I'm concerned, get the individual that will get the job done, and call him whatever you want to call him/her with a salary to match the contributions/expectations. 

Comment by Raja Khongthaw on December 24, 2015 at 8:29pm

In my opinion, no one will attain that title "Scientist" until and unless one is widely recognized with a huge contribution to the Science of Data AND the new method(s) one has invented. So I feel that the organization ,knowingly or unknowingly, gives a wrong title related to job description or expectation,  OR that the candidate applies for the job knowingly or unknowingly because he/she wants to fit in there.

They can be data science engineer as simple as that.

Comment by Vincent Granville on September 8, 2015 at 5:59am

Also, designing a brand new system that leverages various data to deliver high value and beat all competitors, is creativity and craftsmanship: you don't learn that stuff at school. Coming up with the concept might just take 30 minutes while sipping a glass of wine at midnight, but is has far more value than days of coding - coding can be learned at school or on Github, stackexchange, Google etc. And what you can learn for free on the web will one day get outsourced to the cheapest bidder that delivers good enough quality. That's why the $500k, in this case, is by no means overpaid.

Comment by Lucas Finco on September 8, 2015 at 4:53am

If your friend knows his company's business, competitors, and market well, and knows what data to gather, what analyses to run, and what models to build so that he can discover new knowledge, provide strategic advantage, and communicate these results to company executives in a clear and understandable way, then I would say he is under paid.

I have seen many amazing programmers working on the wrong problems.  Being able to code is one thing.  Getting value out of the techniques that Data Scientists wield is another. 

Comment by Stephen Verba on September 5, 2015 at 1:10pm
I posted the following comment elsewhere but it really belongs here:


Data Scientist? What is the science this refers to?

An Astronomer knows math and stats and the science of Astronomy (HR diagram, stellar evolution, cosmology, etc.)

A Marketing Science professional knows math and stats and Marketing theory ( adoption models, segmentation approaches, consumer behavior, etc.).

So what is the subject of "Data Science"?

As for coding, designing creative and insight-generating analysis plans has nothing to do with coding.

Likewise you can be a brilliant developer and know nothing about analytics.

And, you can know how to code, and how to do analytics, and know nothing about business.

Don't get me wrong, I love seeing the data science field emerge and evolve, but some honest self-reflection seems in order before the hype bubble bursts.

This debate over a high salary for someone who does not code just illustrates that this is still an immature field that has not yet clarified its own body of knowledge, core principles, roles and responsibilities, central focus, etc.
Comment by Vincent Granville on September 4, 2015 at 4:51pm

Sione, there are data scientists who can't code, and there are data scientists who don't code. They are two very different species.

Follow Us

Videos

  • Add Videos
  • View All

Resources

© 2017   Data Science Central   Powered by

Badges  |  Report an Issue  |  Privacy Policy  |  Terms of Service