Why pre-screen operations research analysts before the interview
The classic failure in this discipline is a schedule that is optimal on paper and impossible on the floor, because a constraint nobody wrote down turned out to matter. Analysts worth hiring spend time where the work happens before they build anything, and can point at something that was actually implemented. A short screen asks what changed in operations rather than what the model recommended.
What actually matters when screening Operations Research Analyst candidates
- 01
Technical proficiency
Probe formulation depth: mixed integer programming, LP relaxations, queueing or discrete event simulation, and hands-on use of Gurobi, CPLEX, OR-Tools, AnyLogic or Python with Pyomo.
- 02
Systems and trade-offs
Assess how they handled model scale and tractability: decomposition, heuristics versus exact solutions, data quality limits, and when a simple rule beat a full optimization.
- 03
Evidence and rigour
Test validation habits: sensitivity analysis, scenario stress tests, backtesting against historical demand or routing data, and how they proved savings were real not modeled.
- 04
Collaboration and communication
Look for evidence they moved planners, supply chain leads or finance to adopt a model, including dashboards, Tableau or Power BI handoffs, and documented assumptions.
Pre-screening questions to ask Operations Research 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 implemented
3 questions01Tell me about a project where your analysis significantly contributed to the business.
Listen forA change that was implemented, with the measured effect stated and evidence it held over time.
Recommendations described with no implementation, or benefits claimed from the model rather than measured.
02Have you conducted cost-benefit analysis in previous roles?
Listen forCosts and benefits built from real figures with the assumptions listed and tested for sensitivity.
Benefits estimated optimistically, or assumptions not stated anywhere in the analysis.
03Have you overseen the implementation of a solution in a business setting?
Listen forInvolvement through rollout, with the operational problems that emerged and how they were resolved.
Handover at recommendation stage, or no involvement once implementation began.
Method fits the problem
3 questions04How familiar are you with mathematical optimisation techniques?
Listen forFormulation skill with a clear view of when an exact method is impractical and a heuristic is better.
One technique applied to every problem, or solver runtime never considered for the real instance size.
05Can you explain your understanding of predictive modelling?
Listen forPrediction distinguished from optimisation, with an understanding of how forecast error propagates downstream.
Forecasts treated as certain inputs, or uncertainty not carried into the decision model.
06Do you use methods such as process mapping and root cause analysis?
Listen forTime spent observing the actual process, with constraints found that nobody had documented anywhere.
Processes modelled from documentation, or no time spent where the work is actually done.
Assumptions checked
3 questions07Do you have experience collecting and analysing data to identify trends?
Listen forData quality checked at source, with an understanding of how operational systems record events.
Data accepted as recorded, or systematic recording errors not investigated before modelling.
08What experience do you have using statistical analysis to support business decisions?
Listen forDistributions checked rather than assumed, with variability modelled instead of using averages throughout.
Averages used for planning variable processes, or distribution assumptions never tested.
09What measures have you used to assess operational performance?
Listen forMeasures that reflect the constraint rather than utilisation alone, with the trade-offs between them understood.
Utilisation maximised as a goal, or measures chosen without reference to what limits throughput.
Accepted by operators
3 questions10How would you handle it if management did not accept your conclusions?
Listen forThe disagreement explored to find the missing constraint, with the analysis revisited where they had a point.
Conclusions defended regardless, or objections from operations dismissed as resistance to change.
11How comfortable are you presenting analysis outcomes to management?
Listen forResults presented as decisions and trade-offs, with the model's limitations stated rather than hidden.
Presentations built around methodology, or limitations left out to make the result look stronger.
12How do you work with other departments on operational problems?
Listen forFrontline staff involved early, with their objections treated as information about the real constraints.
Analysis conducted in isolation, or operational staff consulted only at presentation stage.
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%5Writes objective functions and constraints from a messy business problem, names solver settings, cuts and warm starts that cut runtime.
Systems and trade-offs
25%5Explains a specific tractability wall and the trade-off chosen, including runtime, solution gap, and why stakeholders accepted it.
Evidence and rigour
25%5Cites measured outcomes (miles cut, inventory turns, staffing hours saved) with baseline, validation method, and honest caveats.
Collaboration and communication
15%5Describes converting a skeptical operations team by exposing model logic clearly and training them to run scenarios themselves.
A schedule that is optimal on paper and impossible on the floor changes nothing. A one-way video screen asks what was implemented.
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 implemented, test their method selection, and check how they work with operational teams.
How much technical depth should I expect?
Enough to formulate a problem correctly and know when a heuristic beats an exact method. Software proficiency matters less than knowing which formulation actually represents the operation.
Evaluating answers
What is the strongest signal when screening this role?
Something that was implemented and still runs. Analysts who deliver name the change and the measured effect. Anyone whose work ended at a recommendation has not been through adoption.
How do I judge whether operations will accept their work?
Ask how they gather constraints. Real answers involve time spent watching the process. Anyone who builds from a specification will miss the constraint that makes the solution unusable.
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
