Clinical Data Scientist in 1933: Neyman and Pearson formalize hypothesis testing

The job title is far younger than the craft behind it. 'Data scientist' dates to around 2008, when DJ Patil and Jeff Hammerbacher independently settled on it while building data teams at LinkedIn and Facebook, and statistician William S. Cleveland proposed 'clinical data science' as an academic field only in 2001. The underlying discipline is centuries older, tracing through John Tukey's 1960s-70s push for exploratory data analysis back to Ronald Fisher's 1920s statistics and John Graunt's 1662 study of London's mortality records.

A 2012 Harvard Business Review article calling it 'the sexiest job of the 21st century' triggered a decade-long corporate hiring boom and hundreds of new university programs. That boom has since matured: the generalist title has split into analytics engineering, machine learning engineering and product analytics, and AI tools now handle a growing share of the routine querying, cleaning and charting the original job assumed a person would do by hand.

What does a clinical data scientist actually do day to day? Contrary to the 'building AI models' image, most days split between writing SQL queries and Python code to pull and clean data, running statistical tests or training models, and translating results into a chart or memo a non-technical stakeholder can act on. Practitioner surveys consistently put data cleaning and preparation at roughly half or more of total working time.