The ApprenticeRoute

Going from newest to most experienced in three years

Somewhere in my third year, someone asked me a question about how a process worked, and I answered it without looking anything up, and they went away and did the thing. It took me about an hour to notice what had happened.

I'd been the person asking that question eighteen months earlier. Now I was the person who knew. Nobody had told me the transition had occurred; there'd been no announcement and no promotion. I'd just gradually become the one in the room who'd been there longest.

This happens far faster than anyone expects, and nobody prepares you for it — partly because the mental model you arrive with, from school, is that seniority takes decades.

Why it happens so fast

Two forces, and they compound.

Turnover. In a large organisation, people move constantly — promotions, team changes, new jobs elsewhere, parental leave, reorganisations. Over three years a team can turn over substantially. You, meanwhile, are on a four-year programme and going nowhere. Simply by staying put you climb the tenure rankings without doing anything at all.

New intakes arrive behind you. Apprenticeship cohorts are annual. Twelve months after you start, a fresh group appears who know nothing, and by definition you know more than they do. Two years in, there are two cohorts below you. That's a very unusual position for a twenty-year-old: junior in every conventional sense, and simultaneously the institutional memory for a certain set of things.

The result is that "how long have you been here?" starts producing surprised reactions somewhere in year three. It's the single strangest feature of the back half of an apprenticeship.

What you actually know that others don't

It's worth being precise, because the tendency at 20 is to dismiss it as trivia.

You know where things are, who owns what, why a process has a weird step in it, which system is unreliable on Mondays, who to actually ask rather than who the org chart says. You know what happened two years ago that explains the current arrangement. You know the unwritten conventions — how much detail goes in a particular report, what the tone of a particular meeting is.

None of that is on a CV and all of it is genuinely valuable. It's the difference between a competent new joiner taking three weeks to do something and taking three days. Organisations run on this kind of knowledge and it lives almost entirely in people's heads, which is exactly why the person who's been there longest becomes load-bearing without anyone deciding it.

The corollary, which is the useful bit: write it down as you learn it. The acronym list and the notes I recommended in your first week turn out to be the raw material for this. When you become the person who's asked, having it written means answering takes a minute instead of an afternoon.

Mentoring the intake below you

At some point you'll be asked to buddy, mentor or onboard a new apprentice. Possibly formally, more likely by someone saying "you were in their position, could you look after them for a bit?"

Say yes. It's one of the most useful things you'll do, and not primarily for them.

What actually helps a new apprentice, from having been one very recently:

What it does for you is the part nobody mentions. Explaining something is the fastest way to discover whether you actually understand it. I learned more about how my own job worked in a month of answering an apprentice's questions than in the previous six months of doing it. It also, bluntly, reads extremely well: being the person who develops others is one of the clearest signals of readiness for the next level, and it's available to you at 20 in a way it isn't in most careers.

The moment the apprenticeship stops defining you

For your first eighteen months, "the apprentice" is your identity at work. It's how you're introduced, it's the interesting thing about you, it's the explanation for what you don't know yet.

Then, gradually, it stops. People stop mentioning it in introductions. You get given work with no scaffolding. Somebody asks your opinion in a meeting because they want your opinion rather than because they're being encouraging. Someone joins the team who doesn't know you were an apprentice and nobody tells them.

This is a genuinely good moment and it feels ambiguous when it arrives, because "the apprentice" was also a shield. It explained the gaps. Once it's gone you're just a colleague, assessed like everyone else, and the curve I described in your first performance review — where people soften feedback because you're young — disappears with it.

Two things I'd say about that transition.

Don't cling to it. There's a temptation to keep leading with the apprenticeship because it's distinctive and it's been the frame for everything. At some point it becomes the professional equivalent of talking about your A-levels. It's on your CV; it doesn't need to be in every introduction.

Don't be embarrassed by it either. The over-correction is worse: people who finish and quietly stop mentioning the route, as though it were a lesser version of a degree. It isn't, and what the qualification is worth sets out why. Four years of paid work alongside a Level 6 qualification is a harder thing to have done than three years on campus, and the right posture is neither defensive nor evangelical — just factual.

What actually changes about the work

The trajectory is more predictable than it feels from inside it.

Year one: you're given small, well-defined pieces of work with generous deadlines and someone checking them. You are, honestly, a net cost.

Year two: you're given real work with real deadlines. People stop checking everything. You start noticing problems before anyone tells you about them, which is the actual threshold of competence.

Year three: you own things. You're the one who knows how a particular area works, you get asked rather than told, and your name comes up when something in that area needs doing.

Year four: you're doing a job. The apprenticeship is now paperwork happening around a role you'd hold anyway, and the main event is the assessment and what comes next.

The step that matters is the one between years one and two, and it isn't about knowledge. It's about being someone who follows things through without being chased. That's the entire distinction, and it arrives whenever you decide to start doing it — which can be much earlier than year two if you want it to be.

Two traps in the back half

Becoming the person everyone asks, at the expense of your own work. Being useful is good until it's your entire day. If you find yourself doing three hours of other people's questions and then your own job at 6pm, that's a problem to raise with your manager rather than absorb. The fix is usually writing things down once rather than explaining them eleven times, and being honest about capacity.

Depth without breadth. The risk of staying in one team for four years is that you become excellent at one narrow thing and know nothing about the rest of the organisation. Apprentices who rotated, or who deliberately volunteered for cross-team work, came out considerably better positioned at the end — and better placed for the conversation about what role you land in when the programme finishes.

If your programme has rotations, take the uncomfortable one. If it doesn't, ask in year two or three whether there's a project elsewhere you could contribute to. The question costs nothing and the answer is more often yes than you'd think.

What this is actually worth

Here's the comparison that makes the point.

A graduate joining at 22 spends their first year being new — the confusion, the acronyms, the not-being-useful, all of it. You did that at 18, on someone else's schedule, while also doing a degree. By the time you're 22, you're three or four years past it: you know the organisation, you've onboarded other people, and you have a track record with names attached to it.

That's the compounding advantage of this route, and it's not really about the qualification. It's about having done the hard, disorienting, unglamorous first-year-of-work part at an age when most people are still choosing modules.

The strange bit is that it happens without ceremony. There's no day when you're told you've stopped being the newest person. You just answer a question one afternoon, correctly, without looking it up — and then notice, an hour later, that something has changed.