Software teams assume the hardware is a black box with an API. AV teams assume the software is a black box with a button. Both are wrong in ways that only show up at commissioning time, usually at 2 AM.
The software engineer's blind spot is physics. A DSP does not care that your retry logic is elegant; the room has a 12 ms acoustic path and the lip-sync budget is what it is. Network audio (Dante, AES67) is deterministic in ways that web developers never have to think about — a PTP clock drifting is not a "transient error", it is a wrong system.
The AV engineer's blind spot is state. Control systems are often written as if the room is the only thing in the universe. The moment a facility has forty rooms, a scheduling system, and an asset database, the "it works in the room" mindset produces forty slightly different programs that nobody can maintain. That is a software problem, and it needs version control, configuration as data, and a test plan.
The useful engineer is the one who has been embarrassed by both. Having pulled the cable and written the ORM, I have come to believe the two disciplines need each other more than either admits — and that the hiring market has almost nobody who speaks both languages fluently.