Is being a Telecommunications Engineer
at risk from AI?

Not in the foreseeable future, but AI will reshape the role significantly. Routine tasks like configuration, monitoring, and capacity planning are already being automated by tools from vendors like Juniper's Mist AI and Nokia's AVA. However, physical infrastructure work—tower construction, fiber deployment, site surveys—cannot be automated. Regulatory compliance, multi-vendor integration, and strategic network design require human judgment, relationships, and context that AI lacks. The engineers at risk are those doing purely desk-based configuration and monitoring. Those working on physical deployment, vendor negotiations, and architecture will remain in demand.

Automation is already here for routine tasks. Over the next 2-3 years, expect AI-driven network orchestration to handle 70-80% of standard configuration and first-tier diagnostics. By 2028-2030, capacity planning and optimization will be largely automated for greenfield networks. However, the physical layer—deploying 5G small cells, running fiber, managing spectrum—will remain human-intensive for at least a decade. If your work is primarily remote configuration and monitoring, start pivoting now. If you're hands-on with infrastructure or regulatory work, you have more runway but should still build strategic skills.

Focus on areas AI cannot touch: physical infrastructure (RF propagation, civil engineering for tower sites, fiber optics), regulatory expertise (spectrum licensing, FCC compliance, local permitting), and multi-vendor integration (making Ericsson, Nokia, and Cisco equipment interoperate). Also develop business skills—ROI modeling, vendor negotiation, and translating technical decisions into financial impact. On the technical side, learn cloud-native networking (SD-WAN, network slicing, edge computing) and security architecture. Avoid becoming solely a configuration specialist; that work is being automated rapidly.

Salaries will likely polarize. Engineers doing routine configuration and monitoring will face downward pressure as AI handles more of that work, potentially seeing 10-20% real wage stagnation over 5 years. However, specialists in physical deployment, regulatory affairs, and strategic architecture will see stable or growing compensation due to infrastructure buildout (5G, rural broadband, satellite) and scarcity of these skills. Senior engineers who can lead large deployments, navigate vendor politics, and manage regulatory risk will command premium pay. The key is to move up the value chain before automation commoditizes your current skill set.

Junior engineers face a tougher path. Entry-level roles traditionally involved configuration, monitoring, and documentation—exactly what AI automates first. Fewer junior positions will exist, and new engineers will need to demonstrate physical infrastructure skills or regulatory knowledge earlier in their careers. Senior engineers have an advantage: their experience with legacy systems, vendor relationships, and complex troubleshooting is hard to replicate. However, seniors who refuse to learn AI-assisted tools or cloud-native architectures will become obsolete. The safest position is mid-to-senior level with a mix of hands-on infrastructure experience and willingness to adopt new tooling.

Yes, significantly. Engineers in regions with active infrastructure buildout—rural broadband expansion in the US, 5G rollout in developing markets, fiber-to-the-home projects—will have strong demand because physical deployment cannot be offshored or automated. Urban markets with mature networks and heavy reliance on remote monitoring face more automation risk. Countries with strict telecom regulations (EU, US) offer more job security due to compliance complexity. Conversely, markets where vendors provide turnkey managed services (some parts of Asia, Africa) may see faster displacement of local engineering roles.

Assuming their technical depth alone will protect them. Many engineers believe that because telecom is complex, they're safe. But AI doesn't need to understand everything—it just needs to automate the repetitive 70% of the job. The mistake is staying in a comfort zone of configuration and monitoring instead of moving toward physical infrastructure, regulatory work, or strategic architecture. Another error is dismissing AI tools as 'not ready'—they're improving monthly, and engineers who don't learn to work alongside AI-driven orchestration and diagnostics will be outpaced by those who do. Adaptation beats expertise in a changing market.