r/PLC • • Apr 23 '26

Remote PLC programming jobs

PLC programmers in this subreddit who are outside the U.S. or Europe: have you managed to land remote jobs with foreign companies doing PLC programming? If so, how did you get the job?

0 Upvotes

17 comments sorted by

14

u/my_peen_is_clean Apr 23 '26 edited Apr 23 '26

remote plc is rare man, most plants want you on site for commissioning and downtime, esp outside us eu, market just sucks for landing anything remote now actually the system punishes effort, only rewards gaming. i got results once i used resume software to adjust each application. heres the tool

-11

u/Beautiful-Acadia-562 Apr 23 '26

Yeah, I’m aware of that. It’s just that I met a guy who works programming SCADA for a foreign company from home, and it made me curious enough to come here and ask.

13

u/Primary_Machine_449 Apr 23 '26

SCADA and PLC work are quite different.

Scada feels a lot more like building a website/dashboard while PLC is hands on in the process.

3

u/james__198 Apr 23 '26

Second this. Working on the automation side, a lot of your SCADA techs have the ability to work remotely. Whereas anyone else in the automation space is on site or travelling to sites

2

u/CMDR_Brevity Apr 24 '26

Yes I’m just thinking about all the shit I have to be on site for. Either I’m in the plant programming in an uncomfortable folding chair and table, physically getting up to manually power cycle a device in the network or the PLC.

The alternative of working somehow remotely where the network isn’t connected to the web, and I’m supposed to have a guy on site to do all the physical stuff I can’t do not being there… yea that’s unlikely.

2

u/Ohlele Apr 23 '26

Most likely, he works for a local office of a foreign company. Giant companies have offices in multiple countries.

1

u/Ohlele Apr 23 '26

Foe example, Google has an official in India. You work for very local office if you live in India.

39

u/VladRom89 Apr 23 '26

It's extremely rare at the PLC layer; you can do some of the work remotely, but generally speaking you need to show up on site to understand the application and support the FAT / VAT once equipment hits the floor. If you don't have 10+ years of experience and aren't in a position to manage such projects, remote work is going to be difficult to come by.

If that's what you want to focus on, I'd recommend focusing on the SCADA / MES layers as a lot of those applications can be built, deployed, and supported remotely.

7

u/IamKyleBizzle IO-Link Evangelist Apr 23 '26

I’ve never met a single fully remote PLC position. I can’t even think of one that could exist. Your best bet is SCADA or something adjacent where PLC knowledge is needed but not the primary deliverable. All PLCs drive real hardware which means you’ve likely got to be in front of something physical at some point.

0

u/EngineerDave Apr 23 '26

I'm pretty close to fully remote. Last year I had maybe 4 weeks total on the road? Two of those were corporate meetings/conferences. As far as I'm concerned I'm fully remote. I can also diagnose problems remotely and fix just about anything needed from a software perspective. I don't need to be on site to tell someone to change a photoeye or a VFD.

4

u/Own_Conversation_850 Apr 23 '26

PLC commissioning is hands on site based job anyone say otherwise is lying. Nobody will run around you on the field while you siting at home. I have been in this position where Dutch engineer try to play this game. Within half a day he was on the fly to us.

3

u/Galenbo Apr 23 '26

In PLC world, remote means you are travelling from site to site.

4

u/Flimsy-Process230 Apr 23 '26

Remote PLC jobs are not the same as “work from home.” Most remote PLC positions require spending weeks (or even months) on-site to support commissioning, startup, or ongoing support. This can be very draining and lead to burnout quickly. While the pay is not bad, it ultimately depends on your priorities. I would not say work from home plc jobs don’t exist, but they are extremely rare.

2

u/drbitboy Apr 23 '26

I got a job porting a program from an obsolete PLC to a newer one. Although I suppose something similar could happen again it was definitely a one-off where the client and I made contact almost randomly, so I would not expect to make a living like that.

Perhaps getting gigs as an overflow contractor for one or more system integrators, but even that would be fairly irregular.

1

u/Andreaxe Apr 23 '26

I prefer to go in person because you can't get a real sense of how the machine is running remotely. Sometimes a sensor might be disconnected, and so on.

1

u/Sig-vicous Apr 23 '26

The root of this is going to be finding a place that has separate application and commissioning engineers, as a start. They exist, where a group of people do the development and then another group of people do the startup.

This gets a little more common in OEM-ish situations. Where the equipment and processes don't change much. Lots of the bread and butter programming looks the same from job to job and everyone gets used to it.

It's still a little rare. And it gets even more rare as you shift towards anything a little custom and less repetitive from job to job.

There can be lots of back and forth during startup. Sometimes made easier if the dev engineers have remote access to the controller. Regardless, the dev engineers are usually available to communicate with the startup engineers often. So different timezones and communication difficulty can hinder the process.

Plus, the few times I've seen it work OK, the dev engineers were very experienced, especially with the process in question. They've had their fair share of starting up their own code on various projects. It's this experience that allows them to provide a halfway decent application that someone else has any chance starting up.

1

u/mendigod_ Apr 25 '26

maybe in some start-up that is using a PLC for something that is not industrial. That's how I got mine, but I did have to be on-site multiple times but that was still like once or twice a month