The signaller job simulation: how to read the scenarios

The job simulation puts you in the chair and asks what you would do. Applicants report it as the longest part of the online assessment, and it is the part where preparation transfers furthest — because the same reasoning shows up again in the video interview and again at the assessment centre.

You sit it before any training. So it cannot be testing rule-book knowledge, and it is not trying to. It is reading your instincts.

The one rule that gets you most of the way

Pick the safety-led answer. This is the advice every applicant who has sat it gives, and it is correct. Where the choice is between something that protects people and something that protects the timetable, protect the people. Delay is recoverable. Nothing else on that list is.

If you take nothing else away, take that. It will carry you through most of the exercise.

Where it gets harder

Not every pair of options is safe versus unsafe. The scenarios that separate candidates are the ones where two answers are both defensible, and the question is which one you do first.

Take the example one applicant published: a pedestrian with a tractor wants to cross the line at a user-worked crossing. They are becoming impatient. You need time to check whether it is safe.

Every option here is "safe" in the loose sense — nobody is going to offer you "wave them across and hope". The real choice is between telling them to wait while you check, and doing something that manages their impatience first. It is the former, and the reason is worth internalising: the reason that crossing has a telephone on it at all is that the user is not in a position to judge the risk. Their frustration is real and it is not information about whether a train is coming.

Four principles that decide the awkward ones

1. Deal with the danger before you investigate it

A report of someone on the track, an unexplained indication, a driver who thinks they hit something — the sequence is always stop the trains, then find out. Not the other way round. If two options both eventually get there, the right one is the one that stops movement first, because establishing the facts takes minutes and a train covers a mile in one.

This is the single most common shape in the exercise, and getting it right requires overriding a very natural instinct to gather information before acting.

2. Confirm rather than assume

A message you did not hear properly has not been received. A train reporting number that does not match anything you expect is not a misreading until you have checked. A track worker who says the line is clear but cannot confirm their team is accounted for has not given you the line back.

Options that involve assuming the reasonable thing are almost always wrong, and they are written to be attractive — they usually come with a plausible-sounding justification attached, like "they clearly said the work had finished".

3. Pressure is information, not authority

Several scenarios put someone on the other end of the phone wanting you to go faster. Control asking for a quicker method during a signalling failure. A person in charge of a work site asking for another twenty minutes. A colleague explaining why it is fine to move a reminder.

None of that changes what is safe. Being straight with them about the rate — so they can plan around it — is the right response. Speeding up to satisfy them is not, and neither is refusing to talk to them.

4. Own the mistake, immediately

Some scenarios are about your own error. You routed a train wrongly, you cleared a signal into a possession, you missed something. Every time, the answer is to say so at once — first because it is usually still operationally live and someone needs to know, and second because the industry's whole safety model depends on hearing about the errors that did not cause harm.

The tempting options are the quiet fixes: correct it at the next junction, wait and see if anyone notices, note it for the handover. They all read as competence. In this context they read as concealment.

Two traps

Over-correction is also wrong. "Stop everything for twenty-four hours" and "refuse and give no reason" are as available in these exercises as the reckless options, and they score badly too. The exercise is not looking for maximum caution, it is looking for proportionate action — the option that removes the danger and then gets things moving again through the proper route.

Do not pick the longest option. In badly written scenario tests the correct answer is often the most detailed one, because the writer thought hardest about it. We deliberately measured that in our own bank and rewrote it — on our first draft the keyed answer was the longest option 82% of the time, which meant the whole section could be passed without reading a word of the scenarios. It is now below 20%, under the 25% you would get by chance. Assume the real thing is written properly too, and read the scenario.

How this helps at the later stages

The assessment centre interview is built on Network Rail's eight non-technical skills, and the video interview's competency questions map onto them naturally. The reasoning above is several of those skills — planning and decision making, controlled under pressure, communications, conscientiousness — expressed as choices instead of as examples.

So when you work through scenarios, notice which principle each one turns on. When the interview later asks you to describe a time you had to make a difficult decision quickly, you will already have language for what a good decision looks like, and you will pick a better example.