Why pre-screen smart transportation analysts before the interview
Transport forecasts are frequently wrong, and the useful analysts are the ones who go back and check. Induced demand fills new capacity, a signal change moves congestion rather than removing it, and counts taken in one week describe that week. Analysts worth hiring compare their forecast with what happened. A short screen asks about a forecast that turned out wrong.
What actually matters when screening Smart Transportation Analyst candidates
- 01
Technical proficiency
Check hands-on command of traffic data tooling: Python or R with pandas, SQL against ATSPM or detector archives, ArcGIS or QGIS, Synchro, Vissim, GTFS feeds, INRIX or HERE probe data.
- 02
Systems and trade-offs
Probe how they handle messy field data: failed loop detectors, gaps in Bluetooth re-identification, sample bias in probe coverage, and choosing corridor simulation over simpler before-after analysis.
- 03
Evidence and rigour
Test analytic rigour on signal retiming or safety projects: control corridors, seasonal and weather adjustment, EB crash prediction, confidence in claimed delay or arrival-on-green improvements.
- 04
Collaboration and communication
Assess how they brief traffic engineers, transit operations, city councils, and TMC staff: dashboards in Power BI or Tableau, memos, public Vision Zero or congestion reporting.
Pre-screening questions to ask Smart Transportation Analyst 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.
Analysis that decided
3 questions01Can you describe analysing and solving a complex transportation problem?
Listen forA specific problem with the data used and the decision that followed from the analysis.
Analysis described without an outcome, or work that produced a report nobody acted on.
02Can you describe a transportation modelling project you worked on?
Listen forModel calibrated against observed counts, with validation performance stated rather than assumed.
Models used as delivered without calibration, or validation results not reported.
03Do you have experience developing and implementing transport strategies?
Listen forStrategy work that reached implementation, with their contribution and the result described.
Strategy documents produced with nothing implemented, or outcomes never followed up.
Models handled rigorously
3 questions04What methods do you use in transportation data analysis?
Listen forMethods matched to the question, with sample periods and seasonal variation handled properly.
Conclusions drawn from a single week of counts, or seasonality ignored in comparisons.
05Which analytics tools do you use most often in this work?
Listen forTools used for real analysis with scripting for repeatability, not only spreadsheets and dashboards.
Analysis done manually each time, or no way to reproduce a previous result.
06Which transportation management systems are you proficient with?
Listen forOperational systems used directly, with an understanding of what their data does and does not capture.
Systems named without use, or data quality limitations of detectors not understood.
Faces a wrong forecast
3 questions07How do you handle cases where real results deviate from your analysis?
Listen forPost-implementation comparison performed routinely, with the model revised and the error reported.
Deviation explained away, or no comparison made after a scheme was implemented.
08Describe a time when you had conflicting transportation data.
Listen forSources reconciled by checking collection method, with the disagreement reported not hidden.
The convenient dataset chosen, or conflicts resolved without investigating why they differed.
09Do you have experience analysing the environmental impacts of transport?
Listen forEmissions and noise assessed with real fleet and speed data rather than default assumptions.
Environmental assessment produced from defaults, or impacts on specific communities not examined.
Safety measured too
3 questions10Describe a project where safety was a major concern and what you recommended.
Listen forCollision data and conflicts analysed, with measures recommended for vulnerable road users specifically.
Safety assessed by casualty counts alone, or recommendations that prioritise vehicle throughput.
11Have you presented analysis findings to a non-technical audience?
Listen forFindings explained with uncertainty intact, and questions from residents or members answered honestly.
Certainty overstated for a public audience, or uncertainty removed to strengthen a case.
12What projects have required a working knowledge of transport regulations?
Listen forDesign standards and approval requirements known, with the public consultation process understood too.
Regulation treated as someone else's task, or approval timelines assumed to be short.
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 proficiency
35%5Names specific pipelines they built, joins probe speeds to signal event logs, and explains volume, occupancy, and travel time index calculations without hedging.
Systems and trade-offs
25%5Weighs data cost, coverage, and latency openly; explains when microsimulation was overkill and a split failure metric answered the question faster.
Evidence and rigour
25%5Quantifies impacts with baselines and uncertainty ranges, cites Highway Safety Manual or HCM methods, and flags where results were inconclusive.
Collaboration and communication
15%5Describes a dashboard or memo that actually changed a timing plan or funding decision, translating detector-level detail into plain corridor outcomes.
Transport forecasts are often wrong and rarely revisited. A one-way video screen asks about one that was.
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 analysis that was used, test their modelling method, and hear how they handle conflicting data.
Does local experience matter for this role?
It helps considerably. Data availability, governance and funding routes differ by region, and an analyst who knows where the counts come from will be productive far sooner.
Evaluating answers
What is the strongest signal when screening this role?
A forecast that was wrong and what they learned. Analysts who check their own work have one. Anyone whose models were always right has not compared them against what happened afterwards.
How do I judge their safety thinking?
Ask what they measure besides delay. Sound answers include conflicts, speeds and vulnerable road users. Anyone optimising throughput alone will recommend changes that make streets less safe.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
