The pattern most careers follow
Year one you learn the tools and feel permanently behind. Year two you become useful and the panic subsides. Year three you either deepen, broaden, or quietly stall.
The stall is the dangerous one because it feels like competence. Work is easy, you are respected, nothing is difficult. From the inside it is indistinguishable from having arrived.
Diagnosing a plateau, concretely
Three questions, asked honestly once a year:
- Could I have done last quarter’s work eighteen months ago? If yes, you have been paid to repeat yourself.
- Is there anybody here I am learning from? If the answer is no, no amount of effort fixes it, because skill at this level is mostly absorbed from people.
- Has anything I built been used by more people this year than last? Scope growing is the clearest external signal that you are.
Three noes is not a crisis. It is a year’s notice.
The three moves, and what each costs
Deeper. A specialism: data platform engineering, ML systems, a regulated domain. Costs: narrower job market, higher pay within it, and a real risk if the specialism fades.
Wider. Product, management, solutions work. Costs: your technical depth erodes within about two years and going back is hard. Worth doing when you want it, not as an escape from a technical problem.
Out. Contracting, a small consultancy, your own product. Costs: income variance, the selling half of the job, and no colleagues. Freedom that people romanticise and then find lonely.
Doing nothing is a fourth option, chosen by default rather than decided. Money and comfort compound, the cost of the plateau is invisible, and it presents its bill at the next interview, when you discover what your market rate actually is.
Gaps, caring years and non-linear paths
If you took two years out (for a child, a parent, illness, a country change) the advice is one plain sentence with no apology, then talk about the work. ”I was out of work for two years caring for my father. I kept my SQL current on a project for a local charity.” No elaboration, no defensiveness.
Employers who dwell disproportionately on a gap are telling you how they will treat any future human circumstance of yours. That is worth learning during the interview rather than after.
Burnout, in this field specifically
Data and AI work has three ingredients that produce it reliably. Pages at three in the morning, because pipelines run at night. A permanent, manufactured sense of being behind, from the previous lesson. And no natural end state: the data is never clean, the model is never finished, and there is always one more thing to check.
Two guards that actually work, both structural rather than attitudinal:
- An on-call arrangement that is written down, with a rota and a definition of what warrants waking someone. An informal expectation that you are always reachable is the most common cause of people leaving this work altogether.
- A definition of done for your own projects. Written before you start. Without one, every project expands until you stop from exhaustion rather than completion.
The asset almost nobody builds deliberately
Three months of expenses saved changes which jobs you can refuse, which requests you can decline, and how a negotiation feels. It is the most useful career asset available to most people and it is never described as one, because it is boring and it is not a skill.
If you are early and underpaid, this is hard, and it is still worth naming as the goal rather than pretending the choice is only about learning.
What survives ten years
Not the tools. Every framework named in this course will be replaced, and the replacements will be replaced.
What survives:
- A domain. Ten years of understanding how hospitals, freight, lending or agriculture actually work is not reproducible by anyone in a hurry.
- About thirty people who have seen you work and would take your call. This is what a network is, stripped of its unpleasant connotations, and it is built by being useful to people one step behind you, for years.
- A written record of what you built and decided. The habit from the case study lesson, kept up for a decade, is a career’s evidence that no employer owns.
- The habit of finishing. Rarer than talent and more valuable.
The limitation
None of this is a guarantee. Markets contract, sectors are hit, well-run companies fail, and a good decision can still end badly through nothing you did. Career advice that promises otherwise is describing survivors.
What the evidence habit actually buys is not immunity. It is that your work is legible to somebody else when you need it to be, which is the difference between a bad year and a lost one.
Every lesson here is open. Your progress is recorded once you pass the AI at Work exam.
Check your understanding
Three years into a data job, Sofia is respected, comfortable, and cannot remember the last time work was difficult. Her manager is pleased with her. What is the most accurate reading?
Pick the one you would defend. Your answer stays private.
Stuck on something?Ask Rukmini, your AI tutor
