What to learn when you're already a senior DS
There comes a point in a data science career when learning becomes harder to define.
At the beginning, the path is obvious.
Learn SQL. Learn statistics. Get comfortable with Python. Understand experiments, models, data pipelines and production systems.
Then you become senior.
You can still find gaps.
In fact, you can find an unlimited number of them:
causal inference
LLM evaluation
Bayesian methods
Spark
Kubernetes
a new vector database released last Tuesday
another LLM framework
There is always another subject that can make you feel slightly behind.
But another technical course or simulator rarely change the kind of work you are trusted with.
Obviously abmarks.io is an exception and it will change the kind of work you are trusted with
It might make you better at solving a particular problem. It will not necessarily make you better at finding the right problem, getting people to act on your work or helping your company make better decisions.
That is the real shift after senior.
6 month ago, a colleague asked me:
“I am senior now. Great. What is left to study?”
I have been thinking about that question ever since. Here is what I think matters next.
Learn to choose the problem
A competent data scientist can answer a question.
A strong senior data scientist notices that the question is wrong.
“Can we predict which users will churn?” sounds reasonable. But the useful question might be:
Which users can we realistically retain, with which intervention, and at what cost?
The second question changes everything. It affects the target, the evaluation metric, the data you need and whether a model is useful at all.
At this level, the work is no longer just about choosing methods, validating data, and defining metrics. It is about judgment, priorities, and making decisions when the answer is not obvious.
A simple habit helps: before starting an analysis, write down five things.
What decision will this work support?
Who will make it?
What are the available choices?
What evidence could change the decision?
What happens if we are wrong?
When these questions have vague answers, better modelling will not save the project.
Understand the whole system
Senior data scientists usually understand models.
The next step is understanding everything around the model.
Where did the data come from?
What behaviour generated it?
How does the output enter a product or workflow?
Who monitors it?
What happens when it fails quietly?
The model is only one part of the work. Often, it is not even the most important part.
Choose one important metric or model in your company and trace it from beginning to end:
how the raw event is produced;
how it is transformed;
where assumptions enter;
how the result is presented;
which action follows;
who notices when it is wrong.
You will probably learn more from that exercise than from a general course on “advanced machine learning”.
Learn to make decisions with incomplete information
Earlier in a career, ambiguity often feels like a problem that someone else should remove.
Later, ambiguity is the work.
You will rarely have the sample size you wanted, a perfectly stable metric and six months to investigate. You will have three imperfect sources, a deadline on Friday and a stakeholder asking what you recommend.
The skill is not creating certainty. It is making uncertainty clear.
A useful senior answer often sounds like this:
Here is what we know. Here is what we are assuming. Here is the risk in each option. Given that, this is what I would do.
Keep an assumption log for important projects. Separate reversible decisions from expensive ones. Agree on failure criteria before seeing the results. Say what additional information is worth collecting, and what is unlikely to change the decision.
Knowing when to stop analysing is part of statistical judgment too.
Learn to influence without becoming unbearable
Data does not speak for itself.
Good analysis is not enough. Someone still has to explain why it matters.
Many technically strong data scientists discover this late. They produce correct work and assume that correctness should be enough. Then a weaker analysis wins because it is attached to a clearer story, a trusted person or a decision people already understand.
The most valuable learning rarely comes from a famous person giving a broad lecture. It usually comes from two experienced people discussing a real problem and being honest about what happened..
Influence does not have to mean manipulation. Usually it means doing the unglamorous work:
