This is one of the most common moves out of teaching in the UK, and one of the most misrepresented. The bootcamp version says twelve weeks and a career. The honest version is six to twelve months of real work, a genuinely good chance of getting there, and a set of advantages you already have that most career-changers into data do not.
What actually transfers
- Explaining something complicated to someone who does not want to hear it. This is not a soft skill in data work, it is most of the job. The recurring failure of analysts is producing a technically correct answer nobody acts on. You have spent years making difficult material land with a hostile audience at nine on a Monday morning. That is rarer than SQL.
- Assessment data. If you have tracked a class or a cohort, set targets against prior attainment, or sat in a data drop meeting arguing about progress measures, you have already done analysis under scrutiny. Most teachers do not count this as experience. It is experience, and it is the single most underused item on a teaching CV.
- Working to a fixed cadence with no slack. Reporting cycles are term structure with different names.
- Holding a line on a number. Defending a grade to a parent is defending a figure to a stakeholder. The emotional register is identical.
What does not transfer, and what you will need
Be honest about the gap, because employers will be. You need SQL — genuinely, not superficially; it is the actual daily tool and the thing most interviews test. You need a BI tool, in practice Power BI or Tableau, and Power BI is the more common ask in UK job adverts outside London. Excel to a real standard — beyond what school use requires. And usually Python or R at a basic level, though plenty of analyst roles never need it.
What you also need, and what people underestimate: a portfolio. Two or three projects using real public data, with the analysis written up so a non-analyst can follow the reasoning. Education data is a legitimate and slightly distinctive choice here — you understand the domain, and it makes your background an asset rather than a thing to explain away.
The route people actually take
- SQL first, properly, before anything else. It is the gate. Free and cheap courses are plentiful; the constraint is doing enough exercises to be fluent rather than familiar.
- One BI tool to a demonstrable standard. Power BI unless you have a reason.
- Two or three portfolio projects, each written up with the reasoning visible. One should answer a question someone would actually ask.
- Apply widely to junior and "analyst" titles, including data-adjacent roles — reporting analyst, insight analyst, MI analyst, performance analyst. These are frequently less contested than anything with "data scientist" in the title and are the same work.
- Look hard at the sectors that will credit your background: MATs and academy chains, universities, local authorities, the Department for Education, exam boards, and edtech. Your domain knowledge is a genuine differentiator there and nowhere else.
How the CV has to change
A teaching CV describes duties to a school audience. An analyst CV has to show evidence to a commercial one, and the same history can be written either way.
"Responsible for tracking pupil progress across KS3" is a duty. "Built and maintained the department's attainment tracking, identifying an intervention group of 40 pupils whose results moved from below to in line with target across two years" is evidence — same work, and the second version is legible to someone who has never set foot in a school. Strip the acronyms ruthlessly; nobody outside education knows what KS3, SLT or PP means, and every one you leave in makes the reader work.
Put the portfolio and the technical skills at the top, above the teaching history. The reader is scanning for whether you can do the job, not for where you have been.
The honest part
The first role is the hard one. You are competing with graduates who have the technical grounding and no domain advantage, and with career changers from more obviously numerical fields. What gets teachers through is usually not out-teching those people — it is being visibly better at the part of the job that involves persuading someone to act on a finding, and being credible in a sector that values understanding the data's origin. Aim at those sectors first and the move gets considerably easier.
The hard part is seeing which of your experience counts.
Everyone making this move hits the same wall: you know you can do the work, and you cannot tell which parts of teaching a data employer will actually credit. Valiown reads your CV, works through guided questions to build an honest picture of how you actually work, then matches you against real current UK vacancies and shows the reasoning behind every match — including where the fit is weak. For each role worth going for it rewrites your CV and cover letter in the target field's language, grounded in what you have genuinely done. That reframing is the whole job of a career change, and it is the part almost nobody can do for themselves. Free preview on Google Play.
Common questions
Do I need a degree in data science to become a data analyst?
No. Analyst hiring is unusually portfolio-driven — most UK employers care whether you can do the work, shown through projects, far more than which degree you hold. A relevant degree helps at the graduate-scheme end and matters much less elsewhere.
How long does the move from teaching to data analysis take?
Realistically six to twelve months of deliberate part-time work before you are competitive, and longer if you are teaching full-time while doing it. Anyone promising twelve weeks is selling a bootcamp.
Will I take a pay cut?
Often yes at the entry point, and the trajectory afterwards is usually steeper than teaching. Check live adverts for junior and mid analyst roles in your region rather than trusting any single figure, including this page.