The signaller assessment centre: presentation and competency interview

Network Rail calls this stage the assessment with the team. As of 2026, applicants describe it as two things: a presentation to a set brief, and a competency interview. It is frequently held virtually.

The presentation

You are given a brief in advance and asked to present to it, typically for around fifteen minutes. Notes and a script are allowed. Bringing copies for the panel is appreciated where the session is in person.

Three things matter more than polish:

Answer the brief that was set. The most common way to lose marks here is to present something adjacent to what was asked — usually because you had an idea you liked better. Read the brief, and structure the presentation so the panel can see it being answered.

Keep to time. Running long is read as poor planning, which is one of the eight skills being assessed. Rehearse it out loud with a timer, because everyone underestimates.

Do not read the script. Having one is fine and encouraged. Reading it aloud is not a presentation. Use it as a safety net and speak from notes.

Slides, if used, should carry very little text. The panel is assessing how you communicate, and a slide full of sentences means they read instead of listening.

The interview

Up to an hour, and built almost entirely on Network Rail's eight non-technical skills: conscientiousness, relationships with people, communications, willingness and ability to learn, planning and decision making, multi-tasking capacity, controlled under pressure, and attention management.

That is not a guess about the shape of the interview — it is the framework Network Rail uses, and preparing an example against each heading is the highest-value thing you can do for this stage.

What a strong answer looks like

Two sentences of context, then what you did and why you chose that, then the outcome and what you took from it. The reasoning is the part being marked; the story is just the vehicle for it.

Panels hear a great many answers that describe what happened and never say what was decided. "It was really busy and I got through it" is not an answer to a question about multi-tasking. "I decided to leave the stock check until after the delivery, because the delivery had a driver waiting and the stock check only had a deadline at the end of the day" is.

Expect follow-ups

Competency panels probe. What would you do differently. What did the other person think. What if it had not worked. These are not traps — they are how the panel distinguishes a real example from a rehearsed one, and they are much easier to answer about something that actually happened to you.

If it is virtual

Applicants describe these being run through a video platform. Treat the setup as part of the preparation: test the link beforehand, sit somewhere quiet with light in front of you and the camera at eye level, and have a phone number for the recruiter in case the connection fails. A dropped call handled calmly is a non-event; a dropped call handled in a panic is the panel's clearest data on controlled under pressure.

Questions to ask them

Have two or three, and make them about the actual job rather than about the company. What the roster looks like at the specific box. What the first six months after training involve. What people find hardest in the first year.

These are useful to you — you are deciding whether to take a shift-working job — and they read as someone who has thought about doing the work rather than about getting the offer.