The competency interview and role play

Every process ends here

Whatever tests an operator runs, a competency interview follows. Transport for Wales, Greater Anglia and ScotRail name the STAR format explicitly; West Midlands Trains runs its competency interview after the tests; GWR runs its interview after the assessment day rather than before it. ScotRail also asks about its values, not only your competencies.

Tests get you into the room. The interview is usually what decides the order of the queue.

The competencies behind the questions

Safety before schedule

Can you describe a time you slowed something down or stopped it because it was not safe, and hold that position under pressure to get moving?

Customer service under pressure

Dealing with people who are angry about something that is not your fault, and who are not going to be made happy.

Conflict and aggression

Revenue disputes, intoxication, antisocial behaviour — de-escalation first, and knowing when to stop trying and call for help.

Working alone

You are often the only member of staff on the train. Decisions get made by you, without a supervisor to ask.

Reliability and attendance

Shift work, early starts, weekends, rest-day working. Operators ask about this directly and they mean it.

Rules and procedure

Following a process exactly even when a shortcut would be faster — and reporting it when you or somebody else gets it wrong.

Structuring an answer

Use STAR and keep the proportions right: a sentence of situation, a sentence of task, most of your time on the action — what you personally did, in order — and a clear result including anything you would do differently.

The most common failure is a story where the action is “we”. Assessors are scoring you, not your former team. The second most common is an answer with no result, which leaves the assessor unable to score it at all.

• Prepare six to eight real examples, not six to eight answers — good examples flex across several questions.
• Draw from outside the railway freely. Retail, hospitality, care, security and the armed forces all produce strong on-board examples.
• Use an example where something went wrong and you fixed it. Flawless stories are less convincing than repaired ones.
• Do not invent. A follow-up question destroys a fabricated example within thirty seconds.
• Say the safety answer out loud in practice. Under lights, people hedge on the one question they cannot afford to hedge on.

The role play

Southeastern runs a live customer-service role play at the assessment centre, and the same skill turns up inside other operators’ assessment days. An assessor plays a passenger with a problem — a ticket they think is valid, a missed connection, a complaint about something you did not cause — and you handle it.

It is not a test of whether you can make the passenger happy. Often you cannot. It is a test of whether you stay calm, listen properly, explain the position plainly, offer what you actually can offer, and do not either capitulate or harden up.

• Acknowledge the problem before you explain the rule. People will not hear the rule until they feel heard.
• Be specific about what you can do, and honest about what you cannot. Never invent a refund or a policy.
• Keep your voice and pace level, especially if theirs rises — tone is most of de-escalation.
• Stay in role until the assessor ends it, and do not break to explain what you were doing.
• Know your exit: at what point do you stop negotiating and involve someone else? Say so.

If there is a presentation

Applicant accounts describe a presentation at GWR Train Manager assessment days. No operator publishes that it sets one, so treat it as a possibility rather than a certainty — but where one is set, keep it to the brief and to time, structure it in three visible parts, and rehearse it standing up and out loud. Assessors are watching whether you can hold a room, which is, after all, what an announcement to a full train is.