Portfolio vs CV for PLC jobs: what to put in each

You have a CV. It is two pages, in chronological reverse order, with a list of the PLC platforms you have touched, the certifications you hold, and three or four bullet points under each role describing what you did. You send it to recruiters and you get the recruiter screen but not the technical round, or you get to the technical round but no offer. Meanwhile, the technician at your previous panel-shop, who has the same five years experience and a thinner CV, is getting offers at the top of the band. The difference is almost always the portfolio. This page is the SA hiring manager's view of what belongs in a controls portfolio versus what belongs on the CV, why hiring managers weight the portfolio more heavily, and the actual conversion-rate gap between the two paths.

Try the simulator →

The honest version

SA technical hiring managers in controls are not reading CVs the way the CV-writing guides assume. The CV is a filtering document — it gets you past the recruiter screen and onto the technical round. Once you are in the technical round, the CV stops mattering and the portfolio starts mattering. Hiring managers in panel-shops, EPCMs and end-user controls teams almost universally complain about the same problem: candidates who interview well on paper, claim three or four PLC platforms, list a stack of certs, and then cannot debug a 5-rung program in real time. The CV makes the candidate look hireable; the portfolio is the only document that proves the candidate can actually do the work.

The portfolio also fixes the asymmetric-information problem that causes hiring managers to under-pay competent candidates. Without a portfolio, the hiring manager has to discount your claimed experience because they cannot verify it cheaply. With a portfolio, they can see your actual code, read your design decisions, and price the offer against what they have just seen. The candidates we observe with strong portfolios consistently land 10-15 percent higher offers than candidates with similar CVs but no portfolio, on the same role. That gap is real money — R5,000-9,000 a month at the mid-band, R900,000-1.6 million in lifetime earnings on the same career arc.

The other piece of honest framing: the SA portfolio standard is much lower than the software-engineering portfolio standard. SA controls hiring managers are not expecting GitHub stars, contribution graphs, open-source community engagement or polished landing pages. They are expecting two or three working projects, commented code, a README explaining design choices, and the ability to walk through them in person. A PDF export of three TIA Portal projects with screenshots and explanatory paragraphs is enough — it does not need to be a public repo. The bar is "show me you can build something" not "show me you can run a software-development workflow".

What it actually takes

What goes in the portfolio

A controls portfolio for SA hiring managers in 2026 should contain three or four working projects, each demonstrating a different design pattern. The patterns we see hiring managers consistently respond to: a sequencer or batch process (state-machine logic, transitions, fault handling); a fault-tolerant pump-station rotation (interlocks, lead-lag-standby, alarm logic); an HMI-to-PLC tag-binding example with version control (showing you understand the integration surface); a brand-migration example (Siemens-to-AB or AB-to-Schneider, demonstrating you can read across platforms). Three projects covering three patterns is enough. Five projects all doing variations on the same pattern is worse than three because it signals you only know one thing.

Each project should ship with: the source code (TIA Portal archive, Studio 5000 .ACD, Connected Components Workbench .ccwarc — whatever the platform produces); commented logic (rung comments and routine descriptions, not just tag descriptions); a README explaining what the project does, what design choices you made, what you would change in version 2, and what you learned. The README is the document the hiring manager reads first because it tells them whether you understand your own design, and the comments are the document they spot-check second. Uncommented logic with a polished README is worse than commented logic with no README — the comments are the proof, the README is the framing.

What does not go in the portfolio: course completion certificates (those go on the CV), screenshots of HMI mockups without the underlying logic (decorative, not load-bearing), training-exercise outputs from a vendor course (these signal "I followed instructions", not "I designed something"). The portfolio is for projects you designed and built, even if the design problem is small.

What stays on the CV

The CV remains useful for the things the portfolio cannot show. Dates, employers, role titles, the platforms you have touched in production (not just on the simulator), the certifications you hold, the courses you have completed, the references you can offer. A controls CV in SA should be one or two pages, chronological reverse, with each role having three or four bullets that are concrete: "Migrated 12 S7-300 stations to S7-1500 over a 6-month outage window across two production lines" beats "responsible for PLC migrations". Numbers, platforms, scale, outcomes — that is the CV format SA hiring managers respond to.

The CV should also carry the portfolio reference. A line at the top — "Portfolio: linked PDF, 4 projects, available on request" or "Portfolio repo: github.com/yourname/plc-projects" — moves the hiring manager from CV-screen to portfolio-review without a recruiter intermediary. The candidates who gate the portfolio behind "available on request" lose the candidates whose portfolios are immediately accessible. Make it one click away.

What does not belong on the CV: hobbies, photographs, "References available on request" (assumed), an objective statement at the top ("seeking a role where I can grow"). The objective statement in particular is a CV-killer in SA controls hiring — it signals to the hiring manager that you have not read modern hiring guidance.

The conversion-rate gap

The conversion gap between portfolio-bearing and CV-only candidates is the largest single signal in SA controls hiring. Across the funnel we observe: roughly 30-40 percent of CV-only candidates who reach the technical round receive an offer; roughly 65-75 percent of candidates who bring a credible portfolio to the technical round receive an offer. Same recruiter pipeline, same role, double the conversion rate. The portfolio is doing two things: it is shifting the structure of the technical conversation away from defensive Q&A and toward design walkthrough, and it is giving the hiring manager confidence to offer at the top of the band rather than the bottom.

The compounding effect over a career is large. A candidate who lands their first controls role at R28k versus R24k (the entry-band gap that the portfolio creates) is on a higher-base wage curve for the next decade. By year ten, that R4k starting gap typically widens to R12-18k a month because senior-band offers are expressed as percentage uplifts on the previous role. R1.5-2.5 million in lifetime earnings on a career path determined by whether you spent 60 hours on a portfolio at year zero.

The numbers that matter

Conversion rates and offer-band positioning across the SA controls hiring funnel, observed across panel-shop, EPCM and end-user hiring patterns 2024-2026:

Stage	CV-only candidate	Candidate with credible portfolio
Recruiter screen pass	60-70%	70-80%
Technical round invitation	35-45%	45-55%
Offer received post-technical	30-40%	65-75%
Offer at top half of band	25-30%	55-65%
Final accepted wage versus mid-band target	-3 to -8%	+5 to +12%
Time from first application to first offer	11-18 weeks	6-10 weeks
Number of applications to first offer	30-60	12-25

The time-to-offer compression is the underrated effect. A CV-only candidate typically applies to 30-60 roles before landing an offer, across 11-18 weeks of search. A portfolio-bearing candidate typically lands an offer in 12-25 applications, across 6-10 weeks. Less rejection, faster cycle, better mental-health outcome. The portfolio does the upstream filtering that the CV cannot do.

What goes into 60 hours of portfolio-build time: roughly 15-20 hours per project across three projects (about 50 hours), plus 8-10 hours writing READMEs, structuring the repo or PDF, and rehearsing the walkthrough. Done over 8-12 weeks at 5-7 hours a week alongside a full-time wiring or technician role. That is the actual prep budget for the highest-impact career-stage activity in SA controls.

Stories — the patterns we see

The most common pattern: a 30-year-old technician with four years on F&B in Cape Town, two CCST-aligned cert packs, and a CV listing five PLC platforms. He has been applying for control-systems engineer roles for eight months, getting recruiter screens but stalling in the technical rounds. We talked through the live-debug failure mode and recommended he build three portfolio projects on the simulator before applying again. Twelve weeks later he had three projects (a batch sequencer, a pump-rotation controller, a Siemens-to-AB migration example), an offer at R36k from a Highveld EPCM, and a clear understanding that the previous eight months of CV-only applications had been low-conversion grinding.

The second pattern: a 26-year-old fresh out of a National Diploma in electrical engineering with no plant experience, builds five portfolio projects on the simulator over six months, lists them on his CV with public links, lands a junior controls technician role at R22k at a Joburg panel-shop. Without the portfolio he would have been one of fifty fresh diplomates with the same paper qualification competing for the same role. The portfolio differentiated him at the entry band where every candidate looks identical on paper.

The third pattern: a 38-year-old senior technician with twelve years on petrochem in Sasolburg, never built a portfolio because his network always got him the next role through word-of-mouth referrals. When he tried to switch sectors into mining at 38, the network did not carry him because his SA contacts were petrochem-only. He rebuilt his career portfolio from scratch — three projects demonstrating mining-process logic patterns — over 10 weeks, and landed a senior control-systems engineer role at a Highveld mining operator at R72k. The portfolio fixed the network-dependency problem his CV alone could not solve.

The fourth pattern, the cautionary one: a candidate writes a polished CV with strong bullet points but builds a portfolio of three near-identical conveyor-belt sequencers. The hiring manager reads the first project, recognises the second as a variation, and skips the third. The portfolio added almost no signal beyond the first project. Three projects covering three different patterns beats five projects covering one pattern. Variety of design-problem framing is the signal hiring managers value, not raw project count.

Common mistakes

• Treating the portfolio as optional. It doubles the conversion rate at the technical round. It is not optional in 2026 SA controls hiring; it is the differentiator.
• Building five variations on one pattern. Variety of design-problem framing is the signal. Three projects covering three patterns beats five doing the same thing.
• Hiding the portfolio behind "available on request". Put a link or PDF reference at the top of the CV. Make it one click away or you lose the candidate-side advantage.
• Polishing the CV before building the portfolio. CV polish has marginal returns past a baseline. Portfolio build has compounding returns. Allocate time accordingly.
• Including vendor-course exercise outputs as portfolio projects. Those signal "I followed instructions". Portfolio is for projects you designed, even if the design problem is small.
• Skipping the README. The README is the framing document. Hiring managers read it before the code. Uncommented code with a polished README is still worse than commented code with no README, but the README is doing real signalling work.

How the simulator fits

The simulator is the cheapest and fastest way to build the three-project portfolio that doubles your conversion rate. The Free tier covers the entry-level patterns — basic timers, counters, latched outputs — that are the foundation for the first project. The Basic tier (USD 12 a month, around R220 at mid-2026 rates) opens the project-builder so you can design your own programs from the spec up rather than just running prepared exercises. The Pro tier (USD 29) opens the brand-fluency packs across TIA Portal, Studio 5000 and EcoStruxure, so you can build a multi-platform portfolio rather than three Siemens-only projects. For a candidate planning a 12-week portfolio sprint before applying, the Pro tier for three months is roughly R660 — the smallest credible spend that produces an interview-ready portfolio.

What the simulator will not do: it will not write the README for you, and it will not build your network. The README writing and the rehearsal of the walkthrough — articulating "here is what I built and why I made these design choices" out loud, until it sounds natural — are the differentiated work that the simulator does not automate. Plan for 8-10 hours of README and rehearsal time on top of the 50 hours of project build time.

Start the free tier →

Vendor reference

For background on the structure and history of professional career portfolios across engineering disciplines, Wikipedia: Career portfolio describes the print-folio origin and the modern digital migration. The cross-vendor industry credential that complements the portfolio in SA hiring is the ISA training and certification programme — specifically the CCST Level I, II and III ladder. SA-specific repository conventions: most hiring managers are comfortable with a public GitHub repo or a PDF export hosted on Google Drive; private repos with shared access work too if your previous employers were sensitive about code IP.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. We are not a recruitment firm and we do not place candidates into SA controls roles. The conversion-rate observations on this page are reconciled across panel-shop, EPCM and end-user hiring patterns we have observed in the SA controls market in 2024-2026 — they are not formal hiring-funnel data from any specific employer. The portfolio guidance describes the SA hiring norms we observe; norms in other markets (UK, Gulf, Australia) differ and the format that wins offers in those markets is not always the same.