A PLC programmer does not have one typical day, because the work splits into design days at a desk, commissioning days on site and support days responding to faults. This post describes each as a general pattern, not one person's diary. Context on pay: according to ITJobsWatch, permanent UK PLC Engineer adverts quoted a median salary of £60,000 in the six months to 21 October 2026, though entry-level roles sit lower.
The official description of the job points the same way. The Skills England standard for an automation and controls engineering technician describes duties such as installing, commissioning, fault-finding and supporting hardware and software for automation systems, including PLCs, HMIs, robots and industrial networks. For how titles differ, see PLC programmer vs PLC engineer vs controls engineer, and for the route in, how to become a PLC engineer in the UK.
What is a typical day for a PLC programmer?
The honest answer is that it depends on three variables: the employer type, the project phase and the seniority. This table compares the three most common patterns.
| Design day | Commissioning day | Support day | |
|---|---|---|---|
| Where | Office or home | On a customer site | Plant, or remote |
| Main tools | TIA Portal or Studio 5000, drawings, simulator | Laptop, multimeter, drawings, test sheets | Laptop, remote access, alarm and diagnostic logs |
| Main output | Tested program, documentation | Systems running and signed off | A fault understood and fixed |
| Pressure | Deadlines and reviews | Production schedule | Downtime cost |
| People | Project team | Electricians, mechanics, operators | Operators, maintenance, vendor support |
What does a design day usually involve?
A design day usually starts by checking what the specification requires and what has changed since yesterday. The programmer then spends most of the day writing and testing code against an I/O list: structuring blocks, naming tags, adding alarms and interlocks, and linking the screens. Much of the testing happens in a simulator, so the logic is proven before anyone is on site. Typical tasks:
- reading a functional design specification and clarifying anything vague;
- writing or modifying program blocks, then testing them in simulation;
- configuring HMI screens and alarm lists to match the program;
- updating drawings, I/O lists and version records; and
- reviewing a colleague's changes before release.
Free tools let you try this workload: the PLC simulator and free Siemens TIA Portal course reproduce the cycle of write, simulate and fix on your own PC.

What happens on a commissioning day?
A commissioning day usually begins with a safety briefing, a permit and a walk-round before any power-up. After that the day follows a loop: check wiring and I/O point by point, download the program, run the sequence step by step with the mechanical team, fix what breaks, and record results. Production pressure is high, because every hour a line is stopped costs money, so good commissioning engineers are methodical rather than fast.
Common experiences on site:
- Wiring and signals first. Many "software bugs" turn out to be a swapped cable, a wrong sensor type or a missing 24 V supply. A multimeter and the drawings are as important as the laptop.
- Live changes need care. Edits on running plant are controlled, tested and recorded.
- Handover matters. Test sheets, backups and a clear note of what changed let the next person trust the system.
Commissioning is a good place to learn quickly, but it can mean travel and long days. Our post on PLC troubleshooting covers the fault-finding method.
What does a support or maintenance day look like?
A support day is driven by what breaks. An operator reports a fault or an alarm; the programmer connects remotely or goes to the machine, reads diagnostics, checks the program state and the field device, and either corrects the logic or points maintenance to a hardware issue. Between faults there are smaller improvement tasks: alarm tuning, adding a counter, updating a recipe.
The skill that matters most is a calm, structured approach: what changed, what does the PLC think is happening, what does the field say? Documentation and backups make the difference between a ten-minute fix and a two-hour hunt. The free PLC electrical troubleshooting and maintenance course is a useful companion.
What are the best and hardest parts of the job?
Many people in the field enjoy seeing a machine they programmed run for the first time, and solving problems that mix electrical, mechanical and software causes. The harder parts are also common:
- deadlines that compress testing time;
- site work in noisy, cold or awkward spaces;
- being on call for production support; and
- documenting work that nobody asks about until something fails.
A second short video shows another view of daily automation work.
What skills make the day easier?
Four groups of skill turn up in every pattern: electrical basics (reading drawings and using a multimeter), programming (ladder, function block and structured text), communication (with operators, mechanics and clients), and tidy documentation. Soft skills are often underestimated; our post on soft skills for automation engineers explains why. Entry roles are plentiful in the listings: Reed's trainee PLC page showed about 135 jobs on 21 October 2026, with example salaries from £25,000 for a graduate control systems role to £50,000 for a junior automation engineer role using Siemens TIA Portal. Those are example adverts, not averages.
How do you prepare for your first week?
Preparation for a first week is mostly about habits. Ask for the I/O list, the latest drawings and a read-only backup before you touch anything. Learn the plant's naming convention and the version-control routine. On site, ask who owns each system and who can authorise a change.
A few habits that experienced engineers share:
- keep a notebook or digital log of every change, with the time and reason;
- take a backup before and after any download;
- test in simulation first whenever possible;
- never assume a signal is wired as drawn: check it; and
- hand over clearly, in writing.
These habits matter more than clever code, because they make your work trustworthy. The ladder logic tutorial and PLC programme structure and modular design posts show how to write programs that other people can maintain. If you are weighing up the role itself, the PLC programmer, PLC engineer and controls engineer comparison explains how the days above shift as you become more senior.
How can you try a PLC programmer's work before committing?
You can try each type of day at home. For a design day, build a small sequence in the ladder logic simulator, write a short test list, and run it. For a commissioning day, use the electrical wiring simulator and multimeter simulator to practise checking signals before blaming the code. For a support day, create a deliberate fault and diagnose it from the evidence only.
Keep notes as you go: what you expected, what you saw and what fixed it. Those notes are exactly what a real handover contains, and they make a sound talking point in an interview for a junior controls role.
How EDWartens can help
If you want to try the work before committing, start with the free browser labs and free courses. EDWartens' Professional Module then gives structure: a five-day live, instructor-led online class on Siemens TIA Portal (PLC, HMI and WinCC SCADA), self-paced Basic Engineering modules, and career support that includes 3 one-to-one profile sessions (resume, LinkedIn and job profile) and 5 interview-preparation sessions. It costs £2,140 + VAT (£2,568), a £100 deposit reserves a seat, and cohorts start each Monday with at most ten learners. The certificate is a CPD certificate recording 80 hours of learning, not a regulated qualification; the course is online and simulation-based, and there is no job guarantee. See the Professional Module or sign up.





