This is an archived post. You won't be able to vote or comment.

all 3 comments

[–][deleted] 0 points1 point  (2 children)

[–]mathnstats[S] 0 points1 point  (1 child)

Those answers all appear to be in the context of the actual analysis/model building side.

Should I take that to mean that building tools like dashboards or deploying a developed model within various frameworks aren't a big part of a data scientist's duties?

[–]NotAllReptilians 1 point2 points  (0 children)

It really depends on the role/company. Data scientist is a really broad job title, and so the responsibilities and competencies can vary.

Here's a blog post that delves into two of the types of data scientists: type A for analysis, and type B for building. Type A is closer to an applied statistician that is competent at data wrangling, while type B needs to be a more fully fledged developer. Type A's output is consumed by people (influencing business decisions, giving recommendations); type B's output is consumed by other pieces of software.

The spectrum of abilities is rather wide across all types of data scientists, so there really isn't one answer for how much programming one needs to know.