Our Blog

If you’ve tried to hire a controls engineer or a SCADA specialist in the last couple of years, you already know: the resumes are thin, the good candidates have three offers, and the job posting sits open a lot longer than it should. This isn’t a fluke of the market. It’s structural, and understanding why can change how you approach the search.

Why this talent pool is so tight

Controls and SCADA engineering sits at an odd intersection. It’s not quite IT, and it’s not quite traditional electrical or mechanical engineering. A strong candidate typically needs to understand PLCs, HMIs, and industrial protocols (think Modbus, Ethernet/IP, OPC UA) while also being comfortable with the physical process they’re controlling, whether that’s a water treatment plant, a manufacturing line, or an oil and gas facility.

That combination is rare on its own. Add in the fact that most controls engineers learn a lot of what they know on the job, tied to specific platforms like Rockwell, Siemens, or Wonderware, and you end up with a candidate pool that’s small, specialized, and often already employed.

What good candidates actually look like

A few things separate a strong controls/SCADA hire from a resume that just uses the right keywords:

• Platform depth over platform breadth. Someone who has spent real years deep in one or two PLC platforms usually outperforms someone who has dabbled in five. Ask about specific projects, not just tool lists.
• Troubleshooting stories, not just design stories. Anyone can talk about a system they built. The candidates worth hiring can also describe a system that broke at 2am and how they figured out why.
• Comfort with the IT/OT boundary. As plants connect more of their control systems to the broader network, the engineers who understand both sides, control logic and basic network/security hygiene, are increasingly the ones who move projects forward without creating new risk.

The IT/OT convergence factor

This is probably the biggest shift in the space right now. SCADA systems that used to run in isolation are increasingly networked, remotely monitored, and integrated with plant-wide data systems. That’s good for visibility and efficiency, but it also means controls engineers can no longer treat security as someone else’s problem.

In practice, this shows up as hiring managers wanting controls candidates who can at least speak the language of network segmentation, remote access policies, and basic OT security practices, even if a dedicated cybersecurity team owns the deeper work. Candidates who can bridge that gap are becoming more valuable, not less, as automation and connected systems expand.

A few practical takeaways for hiring managers

• Widen the geography before you widen the job description. A controls engineer willing to relocate or travel is often easier to find than one who checks every box locally.
• Separate must-have platform experience from nice-to-have. If your systems run on Rockwell, don’t screen out someone with deep Siemens experience who can ramp up. The underlying logic skills transfer more than people expect.
• Move fast once you find the right person. In this market, a slow interview process is the single most common reason a strong candidate takes another offer.

Where this is heading

As manufacturing, water/wastewater, and energy facilities keep investing in automation and remote monitoring, demand for controls and SCADA talent isn’t slowing down. The employers who do well here tend to be the ones who understand the market realistically, know what tradeoffs are worth making on platform experience, and treat speed and candidate experience as part of the hiring strategy, not an afterthought.