Why pre-screen smart factory consultants before the interview
A digitisation programme that ends with screens on the wall and unchanged output is the norm rather than the exception. What separates consultants is whether they start from a constraint the plant already knows about and can show a number that moved: downtime, changeover time, scrap. A short screen asks what the line actually did differently, and whether the operators were involved before the decision.
What actually matters when screening Smart Factory Consultant candidates
- 01
Technical depth
Check command of ISA-95 layers, MES/MOM platforms (SAP DMC, Ignition, Opcenter), OPC UA and MQTT connectivity, historians, and how they model OEE and downtime taxonomies.
- 02
Work that shipped
Probe plants they digitised end to end: line count, sensors retrofitted, digital twin or dashboard delivered, and the OEE, scrap, or changeover numbers before and after go-live.
- 03
Diagnosis under uncertainty
Test how they handled a stalled deployment: bad PLC tag data, operators bypassing the terminal, or a pilot that never scaled past one line. Ask what they changed.
- 04
Working across the org
Assess how they align plant managers, OT engineers, corporate IT, and machine operators, including cybersecurity segmentation debates and building business cases for capital approval.
Pre-screening questions to ask Smart Factory Consultant 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.
Production changed
3 questions01Can you describe your experience implementing smart factory solutions?
Listen forImplementations that reached production with the plant and process named, and their own scope stated.
Strategy and roadmap work only, or pilots that never scaled beyond one cell or line.
02Can you describe a project where you integrated a digital solution into a manufacturing process?
Listen forIntegration into an existing line with the disruption managed, and the production effect measured after.
Solutions installed alongside the process rather than into it, or benefits never measured.
03Can you provide a case where your work improved productivity or efficiency?
Listen forA specific measure that moved, such as downtime, scrap or changeover time, with a before and after figure.
Benefits described qualitatively, or improvements attributed with no baseline measurement.
Plant floor reality
3 questions04Are you skilled in process optimisation and lean techniques?
Listen forThe constraint identified before any technology is proposed, with waste addressed without new systems first.
Technology proposed before the constraint is understood, or lean treated as a separate exercise.
05Do you have experience with predictive maintenance and analytics?
Listen forFailure modes understood before instrumenting, with maintenance actually changed because of the predictions.
Sensors installed broadly with no failure mode analysis, or predictions nobody acts on.
06What is your exposure to manufacturing execution and operations systems?
Listen forReal implementation experience with the difficulty of accurate shop floor data entry acknowledged.
Systems described at vendor level, or data assumed accurate because a system records it.
Control systems
3 questions07Do you have experience working with industrial control systems?
Listen forControl system constraints respected, including why production equipment cannot be patched on a normal cycle.
Control networks treated like corporate networks, or changes proposed without change control.
08Have you worked on projects involving industrial automation?
Listen forAutomation delivered with safety systems respected and commissioning planned around production windows.
Safety functions treated as an obstacle, or commissioning planned without production agreement.
09Do you have experience with data security in a factory setting?
Listen forSegmentation between plant and corporate networks, with remote vendor access controlled and monitored.
Flat networks accepted, or vendor remote access left permanently open for support convenience.
Operators adopted it
3 questions10Do you understand change management and how to apply it in a factory?
Listen forSupervisors and operators engaged before the solution is chosen, with their objections shaping the design.
Change management described as communication, or operators involved only at training stage.
11Do you have experience designing training for factory workforces?
Listen forTraining built around the actual task with shift patterns accommodated, and competence checked afterwards.
Classroom training delivered once, or no check that operators can use the system unaided.
12Can you describe a project where you worked through implementation difficulties?
Listen forA real obstacle such as legacy equipment or a shutdown window, with how it was worked through.
Difficulties described as client resistance, or no project that ran into serious trouble.
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 MES and edge stacks deployed, explains ISA-95 level integration and tag architecture without retreating into Industry 4.0 buzzwords.
Work that shipped
30%5Cites named plants and lines with measured gains, rollout duration, and what stayed in production long after the consulting engagement closed.
Diagnosis under uncertainty
20%5Traces a failing rollout to a concrete root cause (data quality, shopfloor buy-in, legacy PLCs) and describes the corrective decision made.
Working across the org
15%5Describes running workshops with maintenance and IT together, translating shopfloor constraints into a costed roadmap that leadership actually funded.
Most of these programmes end with screens on the wall and unchanged output. A one-way video screen asks what the line did differently.
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 implementations that changed production, test their control system knowledge, and check adoption on the floor.
How much plant floor experience should I expect?
Real time on a shop floor, not just in a client's meeting room. A consultant who has never watched a changeover will propose systems that assume a process nobody actually follows.
Evaluating answers
What is the strongest signal when screening this role?
A production number that moved. Consultants who deliver name downtime, scrap or changeover time with a figure. Anyone describing dashboards delivered has added visibility rather than value.
How do I judge whether their work will be adopted?
Ask when operators were first involved. Sound answers put them before the solution was chosen. Anyone who involved them at training stage will leave systems that get worked around.
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
