50 PLC Interview Questions and Answers for Maintenance Technicians

PLC interviews for maintenance technicians are rarely focused on programming alone.

An employer may ask about ladder logic, but they are just as likely to describe a stopped conveyor, a missing sensor signal or an output LED that is on while the contactor does absolutely nothing.

What are they really testing?

Whether you can troubleshoot safely, follow a logical process and avoid changing the PLC program before checking the obvious electrical causes.

Below are 50 common PLC interview questions with practical answers suitable for maintenance technicians, industrial electricians and junior automation specialists.

PLC Fundamentals

1. What is a PLC?

A PLC, or programmable logic controller, is an industrial computer used to control machinery and processes. It reads inputs, executes a stored program and updates outputs repeatedly.

PLCs are designed to operate reliably in industrial environments containing vibration, electrical noise, heat and dust.

2. What are the main parts of a PLC system?

A typical PLC system contains:

• Power supply
• CPU or controller
• Input modules
• Output modules
• Communication interfaces
• Programming software
• Field devices such as sensors, contactors and valves

Remote I/O, HMIs and variable-frequency drives may also form part of the system.

3. What is the PLC scan cycle?

The PLC scan cycle normally consists of:

1. Reading the physical inputs
2. Executing the program
3. Updating the physical outputs
4. Performing communications and internal diagnostics

The process repeats continuously, often within a few milliseconds.

4. Why are PLCs used instead of relay logic?

PLCs require less wiring, are easier to modify and can handle timers, counters, calculations, diagnostics and communications.

Relay systems are still useful for simple circuits, but changing a complex relay panel may require significant rewiring. A PLC change can often be made through software.

5. What is the difference between a PLC and a DCS?

A PLC is commonly used for machine control, fast discrete logic and industrial automation.

A distributed control system is more commonly used for large continuous processes such as chemical plants, refineries and power generation. The distinction is less rigid than it once was because modern PLC platforms can also handle large process applications.

6. What is the difference between digital and analog signals?

A digital signal has two main states, such as on and off.

Examples include:

• Push buttons
• Limit switches
• Proximity sensors
• Contactor feedback

An analog signal represents a changing value. Common industrial examples include 4–20 mA and 0–10 V signals used for pressure, temperature, flow and level.

7. What is the difference between an input and an output?

An input sends information to the PLC.

An output receives a command from the PLC.

For example, a proximity sensor is normally an input, while a solenoid valve or contactor coil is controlled by an output.

8. What is the difference between normally open and normally closed?

A normally open contact is open in its normal, unactuated condition.

A normally closed contact is closed in its normal condition.

In PLC logic, the instruction appearance represents how the program evaluates a bit. It does not always show the physical construction of the field device, so the technician must understand both the wiring and the program.

9. What is retentive memory?

Retentive memory keeps its value after power loss or after the controlling rung becomes false, depending on the instruction and platform.

Examples may include production counters, recipe values or latched machine states.

Retentive data must be used carefully because an old value can affect what happens after the controller restarts.

10. What is a watchdog timer?

A watchdog monitors whether a PLC task or program finishes within an allowed time.

If execution takes too long because of an infinite loop, excessive logic or task-priority problem, the controller may generate a watchdog fault and stop execution.

Inputs, Outputs and Field Devices

11. The input-module LED is on, but the PLC input tag is off. What would you check?

I would check:

• Whether the correct module and channel are being monitored
• Module connection status
• Whether the module is inhibited
• Hardware configuration and electronic keying
• Communication with remote I/O
• Whether the program references a different input tag

The channel LED may show the local electrical state even when the controller does not have a healthy connection to the module.

12. The PLC output tag is on, but the device does not operate. What would you do?

I would follow the circuit from the output module to the device.

Checks would include:

• Output-channel LED
• Field power
• Voltage at the output terminal
• Fuse condition
• Terminal blocks and wiring
• Interposing relay
• Device coil resistance
• Neutral or 0 V return path

An active output bit does not prove that power reaches the load.

13. How would you troubleshoot a sensor that is not detected by the PLC?

First, I would inspect the sensor LED and confirm that the sensor is being actuated.

Then I would check:

• Sensor supply voltage
• Correct PNP or NPN wiring
• Signal voltage at the sensor
• Signal voltage at the PLC terminal
• Input-module LED
• PLC input tag
• Program logic using that input

This separates a sensor fault from a wiring, module or program problem.

14. What is the difference between PNP and NPN sensors?

A PNP sensor switches positive voltage to the input.

An NPN sensor switches the input toward 0 V.

The PLC input module must be compatible with the sensor type and wired with the correct common. Mixing sourcing and sinking devices incorrectly is a common reason an input never turns on.

15. How would you test a 24 V DC PLC input?

I would measure the voltage between the input terminal and the correct input common.

Then I would check whether the voltage changes when the field device operates. I would also compare the electrical reading with the module LED and online input tag.

16. What does a 4–20 mA signal represent?

A 4–20 mA signal represents a scaled process value.

Typically:

• 4 mA represents the minimum value
• 20 mA represents the maximum value

The 4 mA live zero helps distinguish a valid minimum measurement from a broken or unpowered loop.

17. What could cause a 4–20 mA input to read 0 mA?

Possible causes include:

• Missing loop power
• Open circuit
• Incorrect polarity
• Broken wire
• Failed transmitter
• Incorrect meter connection
• Blown loop fuse
• Incorrect analog-input wiring

I would verify the complete current path rather than replacing the transmitter immediately.

18. What could cause an analog signal to fluctuate?

Common causes include:

• Poor shielding
• Incorrect grounding
• Signal cable routed beside motor or VFD cables
• Loose terminals
• Unstable transmitter power
• Ground loops
• Incorrect analog filtering
• Process instability

I would determine whether the electrical signal itself is unstable or whether only the PLC-scaled value is changing.

19. What does a flashing red I/O module LED usually mean?

It often indicates a recoverable fault, connection timeout or field-side problem.

However, the exact meaning depends on the module family and LED label. I would record the catalog number, LED name and flash pattern, then check the controller diagnostics and manufacturer documentation.

20. What are PLC forces?

Forces override the normal relationship between field I/O and the controller program.

They can be useful during commissioning or controlled troubleshooting, but they are dangerous if left installed or enabled without documentation. Enabling forces may activate several previously installed force values at once.

Ladder Logic and Programming

21. What is a seal-in circuit?

A seal-in circuit keeps an output command active after the momentary Start button is released.

A contact associated with the output or internal run bit is placed in parallel with the Start command. The Stop or fault condition breaks the holding path.

22. What is the difference between a latch and a normal output instruction?

A normal output follows the current condition of its rung.

A latch remains set after the rung becomes false and must be cleared by a separate unlatch instruction.

Latches are useful in some applications, but they can make troubleshooting harder if their reset conditions are unclear.

23. What is an on-delay timer?

An on-delay timer begins timing when its rung becomes true.

After the preset time expires, its done bit becomes active. When the rung becomes false, a non-retentive on-delay timer normally resets.

24. What is a retentive timer?

A retentive timer keeps its accumulated value when the enabling condition becomes false.

It requires a separate reset instruction to clear the accumulated time.

25. What is a one-shot instruction?

A one-shot makes an event true for one program scan when a condition changes from false to true.

It is useful for operations that should occur once, such as increasing a counter or storing a value when a button is pressed.

26. What is an interlock?

An interlock prevents an action when another condition makes that action unsafe or undesirable.

For example, forward and reverse contactors should be interlocked so they cannot energise simultaneously.

27. What is a permissive?

A permissive is a condition that must be satisfied before an action is allowed.

A pump may require:

• Correct operating mode
• Sufficient tank level
• No overload fault
• Valve in the correct position
• Safety circuit healthy

All required permissives must be true before the start command is accepted.

28. What is a state-machine sequence?

A state machine divides a machine cycle into defined steps or states.

For example:

State 0: Idle
State 10: Filling
State 20: Mixing
State 30: Draining
State 40: Complete

Each state has defined actions and transition conditions. This is generally easier to troubleshoot than a sequence made from many overlapping timers.

29. Why are duplicate output instructions dangerous?

If several rungs write to the same output, the final executed instruction can determine the output state.

This makes the program difficult to understand and may cause unexpected behaviour. I would normally use one output instruction and combine the required logic before it.

30. What can cause an array-index fault?

An array-index fault occurs when the program tries to access an element outside the array’s valid range.

For example, an array containing elements 0 through 9 cannot safely be addressed using index 10. The index should be checked and limited before the instruction executes.

Going Online and PLC Communications

31. What is the difference between Upload and Download?

Upload transfers the project from the controller to the computer.

Controller → Computer

Download transfers the open project from the computer to the controller.

Computer → Controller

Downloading the wrong file can overwrite the working controller program, so I would never download simply to test communications.

32. What does Go Online mean?

Going online connects the programming software to the controller so the technician can monitor its current program and data.

The offline project normally needs to match or correlate with the project in the controller.

33. What would you do if your project does not match the controller?

I would not download immediately.

I would confirm:

• Correct controller
• Correct project file
• Controller name and IP address
• Firmware revision
• Project date
• Whether online changes were made

When the controller contains the most trustworthy version, I would upload into a new file and preserve the original offline file as a backup.

34. Why can a PLC respond to ping but still not communicate with the programming software?

Ping only confirms basic IP communication.

PLC communication may still fail because of:

• Wrong communication driver
• Incorrect routing path
• Closed industrial-protocol ports
• Wrong controller slot
• Unsupported firmware or software version
• Missing device name
• Controller security
• Communication service problems

A successful ping is useful, but it does not prove that an online PLC connection can be established.

35. What is a subnet mask?

A subnet mask determines which part of an IP address identifies the local network.

Devices on the same local network must have compatible IP addresses and subnet masks. An incorrect subnet can prevent communication even when cables and link lights appear normal.

36. What happens when two devices have the same IP address?

A duplicate IP address can create intermittent or complete communication failure.

One device may disappear, network connections may drop and the problem may seem random. I would disconnect one suspected device and use network diagnostics or switch information to identify the conflict.

37. What is EtherNet/IP?

EtherNet/IP is an industrial communication protocol that uses standard Ethernet infrastructure and the Common Industrial Protocol.

It is widely used with Rockwell Automation controllers, drives, remote I/O and other industrial devices.

38. What is PROFINET?

PROFINET is an industrial Ethernet system commonly used with Siemens and many other automation products.

It supports cyclic I/O communication, diagnostics and device identification. PROFINET devices are often identified by both an IP address and an assigned device name.

39. The HMI cannot communicate with the PLC. What would you check?

I would check:

• PLC and HMI power
• Ethernet links
• IP addresses and subnet masks
• PLC reachability
• HMI communication shortcut or device path
• Correct controller slot
• Runtime communication configuration
• Whether all tags or only one tag are affected
• Communication-service diagnostics

When all tags fail, the problem is likely in the network or communication path. When only one tag fails, I would inspect that tag reference.

40. How do you make online edits safely?

My basic process would be:

1. Put the machine in a safe condition.
2. Confirm the correct controller and project.
3. Create a backup.
4. Check controller mode, faults and forces.
5. Monitor the existing logic first.
6. Make the smallest necessary edit.
7. Accept and test it under controlled conditions.
8. Assemble only after successful testing.
9. Save and document the updated project.

I would never begin by changing logic simply because one input is false.

Practical Troubleshooting Questions

41. A machine will not start. How would you troubleshoot it?

I would begin with the machine symptom and check:

• Emergency-stop and safety circuit
• Operating mode
• Power supplies
• Active faults
• Start command
• Required permissives
• PLC inputs
• Logic controlling the output
• Physical output and load

The aim is to find the first missing condition, not to change the program until the cause is understood.

42. A PLC input flickers intermittently. What could cause it?

Possible causes include:

• Loose terminal
• Damaged sensor cable
• Misaligned sensor
• Electrical noise
• Weak 24 V power supply
• Vibration
• Failing sensor
• Poor common connection
• Input filter set too short

I would monitor the electrical signal and PLC tag at the same time to determine whether the problem is physical or program-related.

43. A motor overload trips after ten minutes. Is it a PLC fault?

Usually not.

I would check:

• Motor current on all phases
• Mechanical load
• Phase loss or imbalance
• Overload setting
• Cooling and ventilation
• Loose power connections
• Motor condition
• Start frequency and operating cycle

The PLC may only report the overload contact opening.

44. A VFD shows an overcurrent fault. What would you inspect?

I would check when the fault occurs.

Possible causes include:

• Jammed load
• Acceleration time too short
• Incorrect motor data
• Damaged motor cable
• Motor winding fault
• Sudden load change
• Incorrect drive tuning
• Short circuit at the output

The fault code is a starting point, not proof that the drive itself has failed.

45. A remote I/O rack goes offline. What would you check?

I would inspect:

• Adapter power
• Field power
• Ethernet or network link LEDs
• Network switch port
• IP address or device name
• Duplicate address
• Cable and connector condition
• Adapter status LEDs
• Controller I/O configuration
• Chassis size or expected module arrangement

If several devices after the same switch or adapter fail together, I would look for a common upstream cause.

46. What would cause a PLC watchdog fault?

Possible causes include:

• Infinite loop
• Excessive FOR-loop execution
• Too much logic in one task
• Repeated task interruption
• Poor task priorities
• Large copy instructions
• Abnormal communication or motion processing
• Recent program changes

I would investigate task scan times before increasing the watchdog limit.

47. What is fail-safe design?

Fail-safe design means the system moves toward a safer condition when power, communication or a component is lost.

For example, a normally energised safety relay may drop out when a wire breaks. The design should consider how sensors, outputs, valves and motors behave during failures—not only during normal operation.

48. Why are PLC backups important?

A backup allows the machine to be restored after controller replacement, corrupted memory or an incorrect modification.

A useful backup should include:

• PLC project
• HMI project
• Drive parameters
• Network settings
• Safety signatures where applicable
• Date and machine identification
• Description of recent changes

A folder called “final_final_new2” is not an effective backup system.

49. What information should be documented after a PLC change?

I would record:

• Date and time
• Controller and machine
• Routine and rung changed
• Original problem
• Change made
• Reason for the change
• Test results
• Person who approved it
• Backup-file location
• Any temporary forces or bypasses

Good documentation protects both the machine and the next technician.

50. Tell me about a difficult PLC fault you solved.

A strong answer should follow a simple structure:

Situation: Briefly describe the machine and symptom.
Task: Explain your responsibility.
Action: Describe the checks you performed in order.
Result: State what you found, how you fixed it and what was done to prevent recurrence.

Example:

A conveyor stopped randomly several times per shift, but no permanent fault remained. I monitored the PLC input controlling the downstream permissive and found that it dropped for one scan. Electrical testing showed a loose 0 V terminal in a remote junction box. After repairing the connection and checking the remaining terminals, the conveyor operated normally. I also documented the fault and added the terminal inspection to the maintenance checklist.

That answer demonstrates safe troubleshooting, not merely familiarity with software menus.

What Interviewers Want to Hear

For a maintenance technician, the best answers usually show that you:

• Start with safety
• Understand the physical machine
• Check power and wiring before editing software
• Use PLC diagnostics logically
• Know the difference between Upload and Download
• Avoid guessing
• Document changes
• Ask for help when the risk or problem exceeds your authority

You do not need to know every instruction on every PLC platform.

Saying, “I would record the exact fault code, check the manufacturer documentation and verify the circuit before resetting it,” is much stronger than confidently inventing an answer.

Industrial automation rewards careful thinking.

Confident guessing? Not so much.