Signaller interview questions, with example answers

Signaller recruitment includes a recorded video interview and, later, a competency interview at the assessment centre. Applicants report that the assessment centre interview is built almost entirely on the eight non-technical skills Network Rail uses. This guide lists the kind of questions to prepare for under each skill, with example answers.

These are examples of the type of question to expect, not a list of the actual questions — those are not published and will vary. Preparing real stories against each skill covers whatever you are asked.

How to structure an answer

Use the STAR structure — situation, task, action, result — but keep the situation short. Two sentences of context is enough. Spend most of the answer on what you did and why you chose it, because that is the part being assessed. Finish with the outcome and what you learned.

Questions to prepare, by skill

Conscientiousness

• Tell us about a time you followed a procedure exactly, even though you thought there was a quicker way.
• Describe a time you noticed a mistake in your own work. What did you do?

Relationships with people

• Describe a time you had to work with someone you found difficult.
• Tell us about a time you helped a colleague who was struggling.

Communications

• Tell us about a time you had to make sure an important message was understood correctly.
• Describe a time you told someone more senior that you thought they were wrong.

Willingness and ability to learn

• Tell us about a time you received criticism. How did you respond?
• Describe something new you had to learn quickly.

Planning and decision making

• Describe a time you had to make a decision without all the information you wanted.
• Tell us about a time several urgent things needed doing at once. How did you decide the order?

Multi-tasking capacity

• Describe a time you had to keep track of several tasks at the same time.
• Tell us about a time you were interrupted in the middle of something important.

Controlled under pressure

• Tell us about a time something went wrong and you had to act quickly.
• Describe the most stressful situation you have handled at work.

Attention management

• Describe a time you had to stay focused on a repetitive or quiet task for a long period.
• Tell us about a time you noticed something others had missed.

Example answers

“Describe a time you told someone more senior that you thought they were wrong.”

Situation: In my warehouse job, a shift manager asked us to stack pallets two high in an aisle to clear space before a delivery.

Task: The racking in that aisle had a load sign that I was fairly sure the double stack would exceed.

Action: I did not start stacking. I went to the manager straight away, said I thought the double stack would go over the aisle's limit, and showed them the sign. I suggested moving the overflow into the next aisle instead, which had spare capacity, even though it was a longer walk.

Result: The manager checked, agreed, and we used the other aisle. The delivery was about ten minutes later than planned. What I took from it was that raising it before acting was the right order — once the pallets were up, it would have been much harder to say anything.

Why it works: the candidate acted on a concern rather than staying quiet, raised it with the right person before doing anything, offered a practical alternative, and accepted the delay as the cost of doing it safely.

“Tell us about a time you noticed a mistake in your own work.”

Situation: Working on a supermarket checkout, I cashed up at the end of a shift and my till was £20 over.

Task: Being over is often treated as less serious than being under, and it would have been easy to leave it.

Action: I told the supervisor, and we went back through the day's transactions together. I found a sale I had keyed in as £5 when the customer had paid £25 — so the till held £20 more than the system recorded.

Result: The sale was corrected on the system so the stock and takings matched, and I started reading the amount on the screen back to the customer before taking payment. My supervisor used it at the next team briefing as an example of reporting something even when it went in the shop's favour.

Why it works: it shows the candidate reports errors even when nobody would notice, investigates rather than guesses, and changes their method so it does not happen again.

“Tell us about a time something went wrong and you had to act quickly.”

Situation: At a leisure centre, a child was pulled out of the pool by another parent and was coughing badly while I was the only staff member on that side.

Task: I needed to deal with the child and keep the rest of the pool safe at the same time.

Action: I cleared that end of the pool first, so there was not a second problem, then radioed for the first aider and stayed with the child, keeping the parent calm and giving the first aider clear information when she arrived.

Result: The child recovered, and the incident report I wrote was used in a review of lifeguard positioning.

Why it works: it shows prioritising — making the wider situation safe before the individual one — and communicating clearly under pressure. That order of thinking is exactly what signalling scenarios reward.

What panels tend to look for

• Your own actions, not the team's. Say “I”, not “we”.
• The reasoning. Say why you chose what you did.
• Honesty about outcomes. A story where something went imperfectly and you learned from it is often stronger than a flawless one.
• Real examples. Follow-up questions are hard to answer about something that did not happen.

For the recorded format specifically, see the signaller video interview. For the skills themselves, see the eight non-technical skills.