Society of Automation Software Engineers
Automation engineer
or software engineer?
Yes.
We reject the status quo that automation engineering and software engineering are two separate fields. Not only are they converging — software practices are completely revolutionizing automation. SASE is a community of engineers who already operate at that intersection.
Join us on Slack Free · No signup form · You're one click from the conversation
Ask the hive
Stuck on motion tuning, OPC UA quirks, or structuring a PLC project for Git? Someone in here has hit it before — and answered within the hour.
Show your work
Demos, war stories, and the occasional proud "I broke something!" — peer feedback from engineers who ship to factory floors.
Push the field
Digital twins, CI/CD for controls, source-controlled automation. We're building the ASE discipline in public, together.
Why SASE?
Automation engineers are a deeply multidisciplinary bunch. Success and survival in automation demands that all mechanical, electrical, motion, and programming aspects merge together seamlessly and perform in perfect harmony.
Software engineers are sorcerers of the digital realms, bringing to bear decades of experience building systems that enable entirely new ways of solving problems using computing and networks.
Both disciplines are rightly proud of their unique abilities. But because of their cultures and distinct histories, these worlds have persistently misunderstood each other.
Until now. Led by a new generation of engineers and platforms, automation engineering and software engineering are beginning to converge. These unified methods will revolutionize industry just as much as mechanics, electricity, and the first waves of programmability did in earlier eras.
It's not automation engineer OR software engineer anymore. We can be both. We can do both. We are Automation Software Engineers.
And if you're one, too: Welcome! We're glad you're here.
Join us on Slack