Industrial Control Systems Specialist interview scorecard
Evaluate Industrial Control Systems Specialist candidates across 4 weighted areas: technical depth, work that shipped, diagnosis under uncertainty, and working across the org. Technical depth leads at 35%, so check depth on PLC and DCS platforms they name: Rockwell ControlLogix, Siemens TIA Portal, DeltaV. Ask about IEC 61131-3 languages, HMI tag. Use the rubric to compare role-specific evidence consistently.
For technical depth, look for evidence the candidate names specific controllers and firmware revisions, explains ladder versus structured text choices, and describes tag naming and alarm rationalisation conventions they enforced. For work that shipped, look for evidence the candidate walks through a named plant cutover end to end with FAT punch list, hot cutover sequencing, and quantified downtime or OEE improvement.
Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework
What to assess and how to score it
Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.
01
Evaluation factor
Technical depth
35% weight
Check depth on PLC and DCS platforms they name: Rockwell ControlLogix, Siemens TIA Portal, DeltaV. Ask about IEC 61131-3 languages, HMI tag architecture, Modbus TCP and Profinet addressing.
Evidence to listen for
Explains the physics or mechanism behind their work, not just the tooling
Names the standards, tolerances, and constraints they designed against
Can defend a design decision under follow-up questions
Distinguishes what they personally engineered from what the team delivered
Five-point scoring guide
1
Poor
Cannot explain the fundamentals of their own stated specialism.
2
Needs Improvement
Knows the vocabulary but not the underlying mechanism; struggles under follow-ups.
3
Satisfactory
Solid working knowledge for the role; depth thins out on edge cases.
4
Very Good
Strong command of the domain; explains trade-offs and defends decisions well.
5
Excellent
Names specific controllers and firmware revisions, explains ladder versus structured text choices, and describes tag naming and alarm rationalisation conventions they enforced.
02
Evaluation factor
Work that shipped
30% weight
Probe commissioned systems: loop checks, FAT and SAT sign-off, batch or motor control migrations, downtime windows they worked inside, and measured throughput or uptime gains after cutover.
Evidence to listen for
Names specific programmes, parts, or systems that reached production or field use
States their own scope inside the project
Can give measured outcomes: yield, cycle time, cost, failure rate
Explains what went wrong and what they changed
Five-point scoring guide
1
Poor
No delivered work; experience is coursework, lab-only, or purely observational.
2
Needs Improvement
Contributed to projects but cannot say what shipped or what their part was.
3
Satisfactory
Has delivered real work; outcomes described without numbers.
4
Very Good
Names shipped work and their scope, with some measured results.
5
Excellent
Walks through a named plant cutover end to end with FAT punch list, hot cutover sequencing, and quantified downtime or OEE improvement.
03
Evaluation factor
Diagnosis under uncertainty
20% weight
Test how they chased intermittent faults: nuisance trips, comms dropouts on a redundant ring, drifting analogue inputs. Ask what they trapped with historian trends or Wireshark captures.
Evidence to listen for
Describes a real failure they chased to root cause
Shows a method: isolate variables, reproduce, measure, eliminate
Distinguishes correlation from cause
Says what they ruled out and why, not only what the answer turned out to be
Five-point scoring guide
1
Poor
No diagnostic method; guesses or escalates immediately.
2
Needs Improvement
Trial and error with no structure; cannot explain how they narrowed the cause.
3
Satisfactory
Reasonable method on familiar problems; less structured on novel ones.
4
Very Good
Clear systematic approach with a real root-cause story.
5
Excellent
Describes narrowing an intermittent fault using trend data, packet captures, and controlled tests rather than swapping cards until symptoms disappear.
04
Evaluation factor
Working across the org
15% weight
Assess work with operations, maintenance, and OT security: change control under MOC, handover documentation, operator training, and negotiating patching or network segmentation with IT.
Evidence to listen for
Explains technical constraints to non-technical stakeholders without condescension
Has negotiated scope, cost, or timeline with manufacturing, product, or suppliers
Documents decisions so others can act on them
Takes review feedback without defensiveness
Five-point scoring guide
1
Poor
Cannot communicate outside their specialism; dismissive of other functions.
2
Needs Improvement
Communication gaps cause rework; avoids stakeholder contact.
3
Satisfactory
Works adequately with other teams; documentation is thin.
4
Very Good
Communicates clearly across functions; reliable collaborator.
5
Excellent
Gives examples of persuading operators to trust a new control strategy and agreeing segmentation or patch windows with IT without stalling production.
Evidence-led prompts
Interview questions for a Industrial Control Systems Specialist
Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.
01
What types of industrial control systems are you most familiar with?
02
Can you describe your experience with supervisory control and data acquisition platforms?
03
Do you have experience with programmable logic controllers?
04
What is your understanding of the cybersecurity risks specific to control systems?
05
How have you helped implement and maintain security measures in control environments?
