A PLC portfolio should show three to five small projects, each documented well enough that an engineer can see what you were asked to build, how you built it and how you proved it works. You do not need a machine: browser simulators, Siemens PLCSIM and Factory I/O are enough to create credible evidence.
Why does a portfolio help you get hired?
It replaces claims with evidence, which is what trainee and junior hiring is short of. On 21 October 2026, Reed's "trainee PLC" listings (around 130 jobs) included Graduate Control Systems Engineer training on PLC programming at £25,000 to £27,000, Junior Controls/PLC Engineer at £30,000 to £40,000 and Junior Automation Engineer (PLC/Siemens TIA Portal) at £40,000 to £50,000. Adverts at that level rarely expect years of site experience, but they do expect you to show you can specify, program, test and document. Counts and pay change daily, so use them as a snapshot.
What should each portfolio project contain?
Use the same structure every time so a reviewer can scan it in two minutes.
- Brief: what the process does and what it must achieve, in four or five lines.
- Specification: the functional requirements, including normal sequence, alarms and safe states.
- I/O list: tag name, address, type and description.
- Design: a state diagram or flowchart, and notes on program structure.
- Program: screenshots of the key blocks, plus the exported project in an archive.
- Test evidence: a table of test cases, expected results, actual results and fixes.
- Lessons: what went wrong, what you changed and what you would improve.
Keep each project to one or two pages. A reviewer is looking for method: clear naming, structure, safe states and honest testing.
Which five projects are worth building?
Choose projects that map to what employers ask for and that you can run on free tools. Our free lab simulators open in the browser with no install and save your work as you go.
| Project | Free tool | What it proves |
|---|---|---|
| Motor start-stop with overload, interlock and emergency stop | Ladder logic simulator | Boolean logic, fail-safe thinking, seal-in |
| DOL, star-delta and reversing starters | Motor starter simulator | Motor control, timers, interlocks |
| Tank level and temperature control with alarms and PID | Process lab | Analogue scaling, loop tuning, alarms |
| Sequenced batch or filling cell in Structured Text or SFC | IEC 61131-3 simulator | Sequences, states, readable code |
| Sorting or pick-and-place line with an HMI | TIA Portal, PLCSIM and Factory I/O | PLC-to-process integration, HMI, commissioning |
Two more good additions are a pick-and-place job with the PLC handshake in the robot simulator and a panel fault-finding exercise in the panel lab, where you isolate, wire, test and fault-find and then verify with a factory acceptance test.
How do you build a Siemens project without a PLC?
Use TIA Portal with PLCSIM, then connect to Factory I/O to give your program a process to control. The free course on virtual commissioning with TIA Portal and Factory I/O covers the workflow, and the three-hour TIA Portal course is a quick start. This video shows how to interface Factory I/O with TIA Portal.
A worked example is a sorting station. Write the specification (boxes arrive, a sensor identifies type, diverters sort them, an emergency stop halts everything), create the tags, build one FB for each device, add an HMI screen with start, stop, alarm and counters, then test normal, fault and recovery cases. Record a short screen capture of it running.
How should you present the portfolio?
Make it a single PDF plus a link to the project files. A PDF is easy to attach to an application. For code, a GitHub repository or a shared folder with the archived projects works, and a short README explaining how to open each project. Put the link in your CV and in the Featured section of your LinkedIn profile; see our CV guide and LinkedIn guide.
In an interview, prepare a ten-minute walk-through of your best two projects covering the problem, your design choices, what failed in testing and what you would change. Our interview tips cover how to talk through a practical task.
What should you keep out of a portfolio?
Keep out anything confidential. Do not publish an employer's or client's programs, drawings or process details without permission. Rebuild the idea as a simulator project instead. Equally, do not overstate your role in team projects; say which part you wrote. Training projects are legitimate entries when you state where they were done, and a CPD certificate shows structured learning without being a regulated qualification.
What makes a portfolio look weak?
Common weaknesses are projects with no specification or tests, screenshots with unreadable tag names, copied tutorial code presented as original, and a long list of tiny examples. Three well-tested projects beat ten untested ones. If you reuse a tutorial, say so and show what you changed.
What does a finished project page look like?
Here is a skeleton for the sorting station, which you can adapt. The brief says boxes of two types arrive on a conveyor and must be sent to separate exits. The specification lists the start and stop behaviour, emergency stop, jam alarm, product counters and a manual mode. The I/O list shows the sensors, diverter outputs and HMI tags. The test table below shows how to record evidence.
| Test | Expected result | Actual result | Fix |
|---|---|---|---|
| Start with empty line | Conveyor runs, no alarms | As expected | None |
| Type A box arrives | Diverter 1 operates, counter A +1 | Diverter fired late | Moved sensor delay into a TON and retested |
| Jam sensor blocked for 10 s | Jam alarm, conveyor stops | As expected | None |
| Emergency stop pressed | All outputs off, alarm latched | Conveyor restarted on release | Added reset requirement |
| Power cycle in auto | Machine starts in a safe state | Sequence resumed mid-step | Reset steps in start-up logic |
A table like this shows you test, find problems and fix them, which is more convincing than a perfect-looking result. Add a short screen recording so the reviewer can see the line running.
How much time should you spend?
Plan roughly a weekend or a couple of evenings for each of the first three projects, and longer for the Factory I/O one, depending on your background. Do the projects in order of difficulty, and write up each as you finish it rather than at the end. Update the portfolio as you learn: replace weaker early projects with better ones, and keep the last version of the source for each.
How do you keep improving the portfolio?
Return to older projects after a few months and improve them with what you have learned. Add structured naming, a reusable function block, better alarm handling or a cleaner HMI, and note the change in the lessons section. Showing progress between versions is a strong signal of a learner who reflects, and it gives interviewers an easy conversation: what you would do differently now. Remove projects that no longer represent your standard.
Can an employer verify what you built?
Make the evidence easy to check. Include the archived project so a reviewer can open it, a screen recording of the machine running and a plain list of what you wrote yourself. In an interview, be ready to open the project, find the block you are proudest of and explain every line of it. If you cannot explain a section, remove it or rewrite it until you can.
How EDWartens can help
Beyond the free simulators and courses, the Professional Module (£2,140 + VAT = £2,568) is a five-day live online class in Siemens TIA Portal covering PLC, HMI and WinCC SCADA, with self-paced Basic Engineering and TIA Portal, PLCSIM and Factory I/O set-up guides. Learners also get 7 role-specific CV templates and career support: 3 one-to-one profile sessions (resume, LinkedIn and job profile) and 5 interview-preparation sessions, with further sessions at £49 each. It is Siemens-focused and online, with simulation instead of a physical rig, and there is no job guarantee. See /courses/professional or /signup.




