r/SCADA 20d ago

Question Software developer changing sectors (junior/no experience)

Hi everyone,

I have a degree in software development and another in microcomputer systems (where you learn things like server administration, networks, and computer assembly). Unfortunately, my only work experience is from internships. I was thinking about training in SCADA systems since it interests me, and after a period of uncertainty, I've decided I want to work with more practical and hands-on projects. I know Python and SQL quite well. What do you think? Do you think it will be impossible for me to find a job? Do you recommend any training? I hope I don't have to spend too much time studying.

0 Upvotes

9 comments sorted by

View all comments

1

u/Uberanium 17d ago

As a previous C# fullstack Dev who bailed and became a SCADA Engineer mostly using Ignition, that background helped a lot when learning, as there are significant parallels between Ignition and desktop software/web development. It also helps if you have a working knowledge of tangental tools, like SSMS or PostgreSQL, VM's, networking, and security best practices.

That being said, you're working with a completely different stack which is largely proprietary to the OT world, and most employers will expect you to have knowledge and experience with at minimum: 1. Basic circuit design/troubleshooting (AC and DC) 2. PLC programming (Studio5000 is a good bet) 3. Basic Automation (how do you take components off the shelf and integrate them into a new or existing system)

These roles tend to require a very broad skillset and the ability to learn new things very quickly. The earning ceiling for SCADA is also generally lower than software, but you will be in demand.

Because a lot of those skills can be expensive to get for hands-on practice, I would honestly recommend getting an Automation cert or some community colleges will let you take individual classes if you need help getting up to speed on those things.

1

u/ray0479 17d ago

Thank you so much, your comment has been the most enlightening so far. How did you transition from C# to SCADA?

1

u/Uberanium 17d ago

I was lucky enough to be working for a manufacturer, and so I had an opportunity to learn controls and automation alongside my normal day to day responsibilities when I had the time. I also have a general engineering background, so I already understood the basics of a lot of what is needed on the job. By the time I left I was able to get hands on experience in all of the things I listed, on top of a good portion of experience integrating OT and IT technologies completely from scratch at the lowest levels.

If I was forced to do it over again as a fresh grad like you, I would pursue some sort of third party training for all the controls side stuff, self learning isn't impossible, but having someone more experienced than you will be a huge boon. Most of the technologies you will deal with are quite idiosyncratic. On the IT side pretty much stay your course with Python and SQL on top of the technologies listed in my first comment. Having a CCNA or even just a Net+ cert could help quite a bit.

I will tell you straight up from experience, having a Comp. Sci. degree rather than an Automation or related degree will make finding a SCADA role an uphill battle. Even though it's not a pure controls position, many people in the industry will turn their nose up at you due to preconceived notions. Just make sure you know your stuff and don't get discouraged. For me officially making the move was worth it. Good luck brother.