Marcus, 29: the teacher who became an engineer and closed the gap the hard way

The standard disclosure first: Marcus is a placeholder profile, written as the template for the real interviews Happydance will publish before this site launches, because a Sell The Truth company does not print invented testimony as fact. The bootcamp economics, the salary ladder, the neighbourhoods and the shape of the graduate role are all real. The real career changers on this team, and they exist, will be interviewed to exactly this standard.

He is 29, lives in Woolton, and he answers questions like a man who spent five years being asked them by teenagers, which is to say, thoroughly and with zero tolerance for waffle.

Why did you leave teaching?

"I loved the teaching part of teaching and I was being paid to do everything except that part. By year five I was working sixty-hour weeks, most of it admin and behaviour management, and the part of the job I was good at, taking something complicated and building someone's understanding of it step by step, was maybe a fifth of my time. I know exactly when I decided: a Sunday night, marking mock papers at 11pm, watching a YouTube video about programming in the other window like it was contraband.

The honest version of choosing a bootcamp: it was the option that fit a person with a mortgage-sized rent and no ability to stop earning for three years. Fourteen weeks, savings emptied, and a certificate that I quickly learned meant almost nothing by itself. Bootcamps teach you to build things. They do not make you an engineer. Finding out the difference was the next two years of my life."

What was the gap, honestly?

"I want to itemise it, because 'bootcamp grads lack fundamentals' is said constantly and specified never. Here is what I did not have, discovered mostly by hitting it. I could build a working feature but I could not tell you why one approach would fall over at scale. Data structures beyond the obvious ones. What the event loop actually does. Why a database index matters and when it does not. Anything real about networking, memory, or what the machine is doing under my nice TypeScript. And the subtler gap: I had never read code I did not write, and a real codebase is 95% that.

The interview process here caught most of this, and this matters for career changers reading: they saw the gap clearly and hired me anyway, at graduate level, which is around the mid twenties salary-wise, and yes, that was less than my teaching salary. Nobody dressed that up. The bet, said out loud in my final conversation, was trajectory: they had watched me reason through the practical exercise, get things wrong, and correct fast when challenged, and apparently correcting fast is the thing. Teaching, it turns out, trains that muscle for five straight years."

What did closing it actually take?

"Two years, roughly, of treating my own education like a job I was moonlighting. The company's half: a proper graduate structure, a named mentor, one of the seniors, who reviewed my code like it mattered and explained like I was smart, which is rarer than it sounds. Protected learning time that actually stayed protected. Pairing, endless pairing, which for an ex-teacher was the perfect format, apprenticeship is just teaching pointed the other way.

My half: evenings and Saturday mornings with a stack of proper computer science material, working through it like a syllabus, because I am a teacher and building a curriculum for exactly one struggling student was the most natural thing in the world. I filled notebooks. I re-implemented things that already exist to understand them. The imposter weeks were real, month three was the worst, sitting in a review while two engineers debated something I could not even parse, and going home wondering if I had made an enormous mistake. What got me through was embarrassingly teacherly: I tracked my own progress like a mark book, and the evidence said I was moving even when the feeling said I was not. Trust the mark book, not the feeling. I used to tell my year elevens that. Turns out it is true."

What do you actually do all day now?

"Proper product engineering, in a squad, on the analytics dashboards mostly, TypeScript across the frontend and Node services. A normal day is stand-up, a solid morning of building, afternoons of reviews and pairing, and the same boring bits everyone here admits to: refinement, ticket admin, the odd flaky test. Two years in, I review other people's code and my comments get taken seriously, which quietly astonishes me on a regular basis.

And the promotion was real, graduate to engineer in just under two years, which the career progression page says is the normal range for career changers, and I can confirm the process worked exactly as printed: evidence, a written case, the pay moving with the title. The next gap, engineer to senior, is judgement more than knowledge, and I am in the middle of closing it, so ask me again in two years."

Why do you stay?

"Because this place made a bet on me and then actually paid it off, and that buys loyalty no perk ever could. Because the explaining muscle from teaching turned out to be valuable here, I run onboarding sessions for new joiners now, and being good at something visible while you are junior at everything else does wonders for the imposter weeks. And because the honesty is real. I was told the truth about the pay cut, the gap and the two hard years before I signed. Everything hard that happened, I had been warned about. Do you know how rare that is? I taught in schools. I know exactly how rare that is.

Also, Woolton. We rent in the village and are saving to buy, which, unlike my London bootcamp cohort, is a realistic sentence: semis around Liverpool average £249k and Woolton is leafy, villagey, good schools everywhere, which matters because there is a baby coming, which is its own story. Saturday is the farmers' market and Camp Hill woods, and my old teacher colleagues visit and get very quiet about my life now. Twenty-five minutes to the office. A village pub. I am 29 going on retired, and delighted about it."

Marcus's quick answers

Would you recommend a bootcamp to someone in a job like your old one?

"Yes, with the full warning label: the bootcamp is the entry ticket, not the journey, and the two years after it are the actual price. If evenings of deliberate study for two years sounds impossible, wait. If it sounds like relief compared to what you are currently doing on your evenings, you are probably my kind of case. The graduate role is where people like us start."

What should career changers emphasise when applying here?

"Evidence you learn fast and correct faster, because that is the actual bet they are making. Bring a project you understand to the bottom of, not five you can demo shallowly, the interview goes deep and shallow drowns. And name your gaps yourself before they find them. Honesty is the house currency. Spend it."

Was the pay cut worth it?

"Short term it hurt, I will not lie, graduate money after teacher money meant a genuinely careful year. But the ladder here is printed in public and it is real: I am past my old teaching salary already, and the ceiling above me runs to staff level at nearly eighty. Teaching's ceiling required becoming a deputy head, which is to say, leaving teaching. I did my sums with a clear head. They came out right."

---

If you are reading this on a Sunday night with marking, or spreadsheets, or anything else in the other window, Marcus would tell you the gap is real and closable, and the graduate and engineer openings are where the closing starts. The whole ladder he is climbing, numbers included, is on the career progression page.