Data scientists use statistics and machine learning to answer questions and make predictions that businesses can use. The work mixes exploration, modelling and communication, and the hardest part is often defining the right problem.
Where you start matters less than what you can show you have done. This is what the work is built from.
Core skills
Tools and settings
What the work tends to feel like from one day to the next.
Work alternates between thinking, building and explaining. You spend time understanding a problem with the people who own it, exploring data to see what is possible, and building and testing models. Equally important is testing whether the model really helps and writing up the result so that decision-makers understand what it can and cannot do. Some weeks are mostly experimentation, others mostly handing something to engineers.
The day-to-day tasks behind the job title, in plain terms.
There is rarely one route to becoming a data scientist. These are the two most common.
Statistics, computer science, maths, physics and similar subjects are common starting points.
Many data scientists begin as analysts and add modelling and programming over time.
How people usually show they can do the work, and how employers tend to weigh each route.
Statistics, maths, computing, economics and the sciences all lead here. The common thread is comfort with numbers and uncertainty.
Questions you chose, data you cleaned and findings you explained matter more than course badges.
Short credentials for a platform or method can help, especially when you are changing careers.
As you gain experience the work tends to fork. These are two directions it commonly takes.
Working out what actually causes a change, and what to do about it.
Building models that make predictions inside products.
A typical shape, not a rule: people move at different speeds, and some skip stages.
Statistics, computer science, maths, physics and similar subjects are common starting points.
Get dependable at statistics and probability, python or R and sQL, and learn how your employer's tools and habits work. This is where trust is earned.
Working out what actually causes a change, and what to do about it. Applied machine learning is the other common direction.
Understanding how the organisation earns and spends turns a technically correct answer into a useful one.
What usually separates people who progress from people who stay level.
Say what was decided because of your work. People move up by changing outcomes, not by producing more charts.
Understanding how the organisation earns and spends turns a technically correct answer into a useful one.
Documented, tested pipelines and notebooks that someone else can rerun are what lead roles are trusted with.
Every role has them. Knowing what they are is part of choosing it well.
Test simple rules and plain analysis first; use a model only where it clearly adds value.
Hold back test data, check for leakage, and be sceptical of results that seem too good.
Show ranges, explain what could change the answer, and agree how decisions will be made under uncertainty.
No role suits everyone. These are the traits that help and the things people say they wish they had weighed first.
Meetups, reading groups and online forums are where methods and job openings both circulate.
A short write-up of how you approached a real dataset teaches others and shows your reasoning.
A project that starts from a clear question and ends in a finding reads far better than a tour of a tool.
Describe the data problems you hit and how you handled them; that is the part employers cannot get from a certificate.
The two most common routes are a quantitative degree, often with a postgraduate qualification and moving from analyst work. Statistics, computer science, maths, physics and similar subjects are common starting points. Many data scientists begin as analysts and add modelling and programming over time.
The essentials are statistics and probability, python or R and sQL. Employers also value framing the problem before modelling, communicating uncertainty honestly and working with engineers and product.
Typical tools and settings include a notebook environment, machine learning libraries, sQL databases and version control. The names change with employer and fashion, so understanding what each kind of tool is for matters more than any one product.
Experimentation and causal inference: working out what actually causes a change, and what to do about it. Applied machine learning: building models that make predictions inside products. To move up in this kind of work, tie every analysis to a decision: say what was decided because of your work. People move up by changing outcomes, not by producing more charts.
Interest in data science has matured: employers want people who can show business results and who work well with engineers, rather than only model-building skills. It is worth weighing messy data, explaining, not just analysing and fast-moving methods before you decide.
Read the interview questions for the role, then practise answering out loud. HireMonkey lets you upload your resume and a job description and answer an AI interviewer that follows up, then scores each answer and tells you what to fix.
Upload your resume and the job description, and the AI interviewer builds its questions from both. Every answer is scored against the bar for the role, with notes on what to fix.