If you’ve spent any time in or around the AV integration world lately, you’ve probably heard some version of this question whispered: “Will Crestron programming still be around in a few years?” The question is being debated at trade shows and on industry podcasts, or typed into a search bar at 11 p.m. by an aspiring programmer wondering if they will ever get a job in the industry. It’s a fair question.
AI is changing entire industries, and Crestron itself keeps creating products with “AI” in the name. In addition, large language models can already generate simple control logic, and it’s reasonable to expect that capability to keep improving.
So, is Crestron programming heading for the same fate as, say, elevator operators?
The short answer is no—the work of Crestron programming experts will not become obsolete anytime soon. Here’s why Crestron programming still needs actual humans:
What Actually Makes Crestron Programming Hard
The reason Crestron programming has resisted full automation isn’t a lack of good tools. It’s the nature of the work itself. A Crestron programmer isn’t just writing code; they’re translating a client’s vague, often contradictory wishes into a system that behaves predictably across dozens of integrated devices, including displays, lighting, shades, security systems, HVAC, and video conferencing platforms.
That work involves:
- Determining client needs — sitting down with a client and figuring out what they actually need, which is rarely exactly what they initially describe.
- Physical-world judgment — accounting for room acoustics, sightlines, and how real people actually use a space.
- Accountability — someone has to be responsible when a conference call system fails five minutes before a board meeting. AI doesn’t carry that liability; a company and a person do.
AI tools are genuinely useful for the more mechanical parts of Crestron programming, but the judgment-heavy, client-facing work has proven resistant to automation thus far.
Rather than disappearing, the role of Crestron programming is moving in the same direction as many technical trades when better tools arrive: fewer people doing repetitive work and more people working at a higher level.
A Useful Comparison
This isn’t the first time a skilled trade has faced this exact worry. Electricians didn’t disappear when smart panels and prefabricated wiring harnesses were introduced. When the tools got better, the routine parts of the job became faster, and people to focus on the parts of the job that required judgment, adaptability, and accountability.
Crestron programming looks like it’s on a similar track. The company’s own public messaging supports this. Crestron continues to invest heavily in training programs aimed at growing the next generation of programmers, which is a strange thing to invest in if leadership believed the profession was winding down.
An Honest Caveat
It’s worth being upfront about the uncertainty here because nobody—including people inside Crestron—can predict AI’s trajectory with confidence.
If AI systems eventually become capable of genuinely reliable system-level troubleshooting and negotiating with human clients, things could change dramatically. That’s a much higher bar than code generation, but it’s not impossible on a long enough timeline.
Conclusion
Crestron programming isn’t becoming obsolete. It’s becoming less about writing every line of code from scratch and more about system design, making judgment calls, and managing increasingly automated tools. The programmers most at risk aren’t necessarily the ones facing “replacement by AI”—they’re the ones who refuse to incorporate AI into their workflow while their peers do. The ones who adapt are likely to find themselves doing more interesting, higher-value work, not less.
If there’s a single takeaway, it’s this: hone the skill of integrating complex systems for real, unpredictable humans, because that’s the part of the job that’s proven hardest to automate in every trade that has faced this question before Crestron did.
