What a degree apprenticeship assessment centre is actually like
I did my assessment centre from my parents' kitchen, in a school shirt, because I applied in the year when everything moved onto video calls. The wifi held, mostly. Four years later I'd finished a Level 6 degree apprenticeship at a large financial services employer in the South West, and since then I've helped out on the other side of a couple of assessment days, lanyard on, watching nervous seventeen-year-olds do the thing I did. So this is both sides of the table.
One scope note before we start. This piece is about the selection process itself, and mostly about the final day. If you're still at the searching stage, read how to find degree apprenticeships first. For when schemes open, close, and what order everything happens in, there's the application timeline. This article starts after you press submit.
The funnel, stage by stage
Most large employers run some version of the same four stages:
- Online application. A form, sometimes a CV, sometimes a short "why us" question.
- Online tests. Usually a situational judgement test plus numerical or logical reasoning. Increasingly these are dressed up as games: sorting shapes, inflating balloons, that sort of thing.
- A recorded video interview. You answer pre-set questions to a camera, alone, with a timer running. It is exactly as unnatural as it sounds, for everyone.
- The assessment centre. Group exercise, interview, usually a presentation, plus lunch and a look round. Sometimes in person, sometimes virtual.
Numbers vary a lot by scheme, so treat what follows as a shape rather than a statistic. A well-known scheme can get thousands of applications for a few dozen places. The online tests do most of the culling, the video interview thins it further, and by assessment centre day it's typically a small number of candidates per place. That sounds brutal until you flip it round: if you've been invited to the final day, the employer already thinks you're hireable. At many centres you're scored against criteria rather than ranked against the room, so someone else having a brilliant day doesn't automatically wreck yours.
Quick advice on the earlier stages, because they're where most people go out. The tests are practisable, and free practice versions exist online; do a few so the format isn't a shock. On situational judgement tests, pick the boringly responsible option, not the heroic one. On the video interview, say your answers out loud beforehand at least once, look at the lens rather than your own face, and don't read from a script on a second screen. Recruiters can see your eyes tracking.
And the obvious modern one: don't get AI to do it for you. Employers are actively looking for this now. In the Institute of Student Employers' 2025 survey, the share of employers frequently encountering suspected cheating roughly doubled in a year, and undisclosed AI use in interviews was the thing they flagged most. Beyond the ethics, a chatbot answer makes you sound like everyone else's chatbot, and you still have to survive a live interview later as yourself.
What the group exercise is really assessing
The setup is usually six to eight of you around a table, a brief, half an hour to forty minutes, and observers sitting round the edge with clipboards, saying nothing. The task is deliberately a bit silly: rank ten items for a desert island, plan an event on a budget, decide which fictional project to fund. Nobody cares what your group concludes. There is no right answer, and the observers aren't marking the answer.
What they are marking, roughly:
- the quality of what you contribute, not the volume
- whether you bring other people in
- timekeeping, and whether you help the group actually reach an output
- listening, and building on other people's points instead of restating your own
The person who talks the most usually believes they've won. From the observer side, I can tell you they very often haven't. Steamrolling reads as steamrolling, and it's marked accordingly.
The easy wins are almost embarrassingly simple. Keep half an eye on the clock and say so out loud: "we've got ten minutes left, shall we pick our top three?" Notice the person who hasn't spoken and ask what they think. Summarise where the group has got to. Each of those takes one sentence and each one reads as leadership without you having to dominate anything.
And don't perform a personality. If you're naturally quiet, be quiet with three genuinely good moments. That beats being loud badly, which is what most people default to under pressure.
The interview questions that come up every time
Somewhere in the day you'll get a one-to-one or two-to-one interview, mostly competency questions. Four come up almost every time, in some wording:
- a time you worked in a team, ideally where something went wrong
- a time you dealt with a setback
- why this employer
- a time you had to learn something difficult
Prepare these with STAR: situation, task, action, result. One or two sentences of setup, then spend the time on what you specifically did, then finish with what happened and what you'd do differently. The classic failure is spending ninety seconds describing the situation and ten on your part in it.
Here's the bit that stresses school-age applicants unnecessarily: you do not need corporate material. Nobody expects it, and faking it lands terribly. A seventeen-year-old saying "I managed stakeholder expectations" about a bake sale is worse than the plain version. Your raw material is your part-time job, your DofE expedition going sideways in the rain, the sports team, the group coursework where someone didn't pull their weight, the thing you organised at school. A Saturday job story told plainly, with a concrete result at the end, is exactly what they're after, because it's evidence of how you behave rather than a rehearsed abstraction.
Rather than scripting thirty answers, write down five or six good stories. Stories are reusable; the same shift-from-hell can serve the teamwork question, the setback question and the learning question depending on which bit you emphasise.
"Why this employer" needs real research: something specific about the scheme structure, the qualification, or what the business does, not "prestige" or "your values". And be ready for "why an apprenticeship instead of university", because it came up in mine and it comes up in most. Have an honest answer of your own; if you want to see the shape of one, mine is written up in why I chose an apprenticeship over university.
The mark scheme is public
This is the tip almost nobody uses. Every degree apprenticeship in England is built on a published standard, which includes a list of the knowledge, skills and behaviours the apprentice has to develop. Competency questions get written from the behaviours list. If the standard says "works collaboratively" and "responds positively to change", you will be asked about teamwork and about handling change. It's about as close to seeing the mark scheme in advance as recruitment gets.
There are currently 172 Level 6 and 7 standards approved for delivery, and the course pages on this site list what each one requires. Find the standard behind the vacancy you're applying for, read the behaviours, and build a story for each one. Twenty minutes of reading, and you'll walk in knowing roughly what's coming.
Presentations
Formats vary. Some employers email you a topic a week ahead; others hand you a brief on the day with twenty or thirty minutes to prepare. Either way, what's being marked is structure, timing and how you handle the follow-up questions, not production values. Say what you're going to cover, cover it, finish inside the time limit. Under time is fine; over time never is.
The follow-up questions are half the point. If you don't know something, say so and say how you'd find out. That answer scores; bluffing doesn't, and the person asking can always tell.
Lunch is not a break
Somewhere in the middle there's lunch, maybe an office tour, and some current apprentices to chat to. It's usually not formally scored, but it isn't nothing either. When I helped out, we were asked afterwards whether anything had stood out over lunch, good or bad. People talk.
The instruction here is simply: be normal. Talk to the other candidates, since some of them may end up being your cohort. Ask the current apprentices real questions, like what a study day actually looks like or what they wish they'd known before starting, because they're the best intelligence source in the building and they were in your seat very recently. Don't spend lunch performing networking at the hiring manager, and don't disappear into your phone in the corner. Either extreme gets noticed.
Being visibly seventeen
Look around the room and you may find gap-year people, career changers in their twenties, sometimes graduates. This spooks a lot of Year 13 applicants. It shouldn't.
Employers running school-leaver schemes calibrate for age. They are assessing you against the standard and against your potential, not against a 24-year-old's CV. Nobody expects you to have office experience, know the industry jargon, or produce a ten-year plan. What being young does mean is that the basics carry more weight: turning up on time, having clearly prepared, asking questions, listening. Those are things a seventeen-year-old can do exactly as well as anyone else in the room, and they're most of what's on the scoring sheet anyway.
I was visibly the youngest at mine and felt like a child for most of the day. I still got the offer. What they're looking for is trajectory, not polish.
One practical note if you're in Year 13: an offer will usually be conditional on your A-level grades, as a condition of the job as well as the linked university place. The assessment centre isn't quite the finish line, so keep revising.
Logistics, briefly
If the centre is far away and it's an in-person day, travel the night before if you can manage it; arriving frazzled off a 6am train is a self-inflicted handicap. Many large employers reimburse standard-class travel for assessment days, but not all, so ask the recruiter and keep your receipts.
Wear the smartest thing you own. At a bank that means a suit or the nearest thing you've got to one. Nobody has ever been marked down for overdressing at a financial services assessment centre, and if you're genuinely unsure, email and ask; it's a normal question, not a trick.
Bring the joining instructions saved offline, ID if they've asked for it, and a couple of questions for the end of your interview. Ask about the scheme, not the salary: how study time is arranged in practice, what first-year work actually involves. Having no questions at all reads as indifference. It's a small mark against you, but it's a free one to avoid.
One last thing
Assessment centres are long, strange days and everybody in the room is nervous, including the ones who look like they were born in a suit. It helps to remember that the employer has spent serious money getting you to this stage and wants to fill the places. The assessors are not hunting for reasons to reject you; they're hoping you'll give them reasons to say yes.
So give them the boring, solid reasons. Turn up prepared, contribute properly, bring someone else into the conversation, tell true stories about the life you've actually had. That's the whole trick.
And if you're reading all this still not sure whether the apprenticeship route is right for you in the first place, start with degree apprenticeship vs university, which is the honest comparison I wish I'd had at seventeen.