Hiring A Data Scientist: The Good, The Bad And The Ugly

I recently came across this job description for a data scientist (anonymized to protect the innocent): Responsibilities: Translate business requirements into machine learning product. Architect and Build machine learning software products for our core business.
Communicate with business owners the strategy and rationale, define and execute project plan

Lead all aspects of ML automation including model training and development, feature selection and model tuning. Develop production ML and data pipelines. Develop production code and ship to production environments. While it is very clear why such a person would be hugely valuable to an organization, I know of very few individuals who would meet these requirements. It brings to mind an analogy between a software developer and a software architect.

Author: Nisha Talagala

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s