Why pre-screen traffic systems managers before the interview
Retiming a junction almost never removes congestion. It moves it, usually onto a road with houses on it, and the people there find out before anyone reports the improvement. Managers worth hiring measure the surrounding network rather than the junction they changed, and can say where the queue went. A short screen asks that, along with how they weigh pedestrian delay against vehicle flow.
What actually matters when screening Smart Traffic Systems Manager candidates
- 01
Technical depth
Check depth on adaptive control platforms (SCATS, SCOOT, InSync, Centracs), NTCIP 1202 device communication, controller cabinets, detection types (radar, video, loops), and MUTCD signal timing standards.
- 02
Work that shipped
Ask which corridors or citywide systems they retimed, upgraded or connected: number of intersections, fiber or cellular backhaul builds, TSP or preemption deployments, measured delay and travel time gains.
- 03
Diagnosis under uncertainty
Probe how they isolate flashing intersections, conflict monitor trips, detector dropouts and comms failures across a TMC, and what they do when field data contradicts the central system.
- 04
Working across the org
Explore coordination with public works, police, transit agencies, DOT districts and signal technicians, plus handling council or resident complaints about a timing change.
Pre-screening questions to ask Smart Traffic Systems Manager candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Systems they ran
3 questions01Can you describe your experience with intelligent traffic management systems?
Listen forSystems they operated day to day, with the network size and their own responsibilities described.
Experience limited to procurement or specification, or no system they were operationally responsible for.
02Can you provide an example of a project you managed in this area?
Listen forA delivered scheme with the before and after measured across the affected network, not one junction.
Projects described by technology installed, or benefits claimed from modelling rather than measurement.
03How do you approach integrating new technology into existing traffic systems?
Listen forLegacy controllers and mixed equipment handled realistically, with phased change around live operation.
Wholesale replacement assumed, or integration with older equipment not considered.
Measured not modelled
4 questions04What strategies do you use to optimise signal timings?
Listen forChanges validated with measured journey times across the corridor, including the roads that receive displaced traffic.
Timings optimised from a model alone, or effects measured only at the junction that was changed.
05Can you discuss your experience with adaptive traffic control?
Listen forAdaptive systems tuned in practice, with an honest account of where fixed timing performed better.
Adaptive control assumed superior everywhere, or parameters left at supplier defaults.
06Can you describe your experience with real-time data collection and analysis?
Listen forDetector health monitored actively, with faulty data identified rather than fed into control decisions.
Detector data trusted without validation, or failed detectors influencing signal decisions unnoticed.
07What methods do you use to evaluate the efficiency of a traffic system?
Listen forJourney time reliability and delay measured across modes, including buses and pedestrians rather than cars alone.
Efficiency measured by vehicle throughput only, or other modes left out of the assessment.
Incidents handled
2 questions08How do you handle emergencies such as collisions or severe weather?
Listen forRehearsed plans with emergency services coordination, and diversion strategies agreed before they are needed.
Response improvised, or no established coordination with emergency services and neighbouring authorities.
09Describe a time when you identified and resolved a significant traffic flow problem.
Listen forA problem found from data with the cause established, and the effect of the fix measured afterwards.
Problems identified from complaints only, or fixes applied without measuring the result.
Safety weighed properly
3 questions10How have you improved pedestrian and cyclist safety through system management?
Listen forSpecific measures with casualty or conflict data behind them, and vehicle delay accepted as a trade-off.
Vulnerable road users treated as a source of delay, or safety measures dropped to protect flow.
11What is your approach to cybersecurity in traffic control systems?
Listen forControl networks segmented and remote access controlled, with roadside cabinets treated as physical exposure.
Control systems reachable from corporate networks, or roadside equipment access not considered.
12How do you manage communication with the public during disruption?
Listen forAdvance notice given with realistic timescales, and complaints during works answered rather than absorbed.
Disruption communicated after it starts, or optimistic timescales given that are then missed.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical depth
35%5Names specific controller firmware, explains split, cycle and offset tuning logic, and distinguishes where adaptive beats time-of-day plans.
Work that shipped
30%5Cites corridor names, intersection counts, and before-after travel time or stop reductions verified through ATSPM or probe data.
Diagnosis under uncertainty
20%5Walks through a real outage: symptom, cabinet and network checks, root cause, and the permanent fix plus monitoring added afterward.
Working across the org
15%5Describes brokering timing decisions between emergency services, transit priority requests and resident pushback without stalling the project.
Retiming a junction moves the queue onto a road with houses on it. A one-way video screen asks where it went.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish systems they operated, test their measurement practice, and hear how they handle incidents and safety.
How much does local authority experience matter?
Considerably. Procurement, political oversight and public consultation shape what is possible, and someone from a vendor background will underestimate how long a change takes to approve.
Evaluating answers
What is the strongest signal when screening this role?
Knowing where the congestion moved. Managers who measure the network describe the effect on surrounding roads. Anyone reporting only the improved junction has measured the easy thing.
How do I judge their safety judgement?
Ask about a change that increased pedestrian wait times. Real answers acknowledge the trade-off and how it was decided. Anyone optimising purely for vehicle throughput will create casualties.
























