Will AI Replace RF Engineers? The Post-MWC 2026 Debate, Without the Hype
Will AI replace RF engineers after MWC 2026? Nokia-NVIDIA, Ericsson, AI-RAN analysis from a field perspective. The real future of network diagnostics.
Tuesday, 7:30 AM. You are standing in an underground parking garage, RSRP reading -118 dBm on SSB beam 4. The NOC told you yesterday the sector was โgreenโ on the dashboard. Nokia AVAโs coverage algorithm indicates the area is adequately covered. Except you are there, physically, and the signal does not pass.
Every RF engineer knows this scenario. And it is precisely the one that MWC 2026 in Barcelona did not show on stage.
What MWC 2026 Actually Showed
MWC 2026 (March 2-5) established a central theme: AI is no longer limited to analyzing KPIs. It is making real-time decisions inside the RAN.
Nokia and NVIDIA: the $1 billion partnership. NVIDIA acquired a 3% stake in Nokia and invested $1 billion in the joint development of the ARC-Pro platform. The concept: embed GPUs directly into RAN infrastructure to execute real-time optimization models at the scheduler, beamforming, and power control levels. Nokia positions this as the next generation of โself-optimizingโ networks.
Ericsson: the opposite approach. Rather than adding GPU silicon at cell sites, Ericsson demonstrated a 10% spectral efficiency gain using a micro-LLM running directly on existing baseband hardware, with no additional equipment. Their argument: operators have neither the budget, the power infrastructure, nor the desire to deploy GPUs at every site.
The AI-RAN Alliance continues to expand. Far EasTone reports that 60% of its NOC operations are now assisted by AI agents. And 89% of telecom operators are increasing their AI budgets in 2026, according to NVIDIA.
The MWC message was clear: AI is entering the RAN. The question is no longer โifโ but โhow.โ
โก Nokia ARC-Pro (On-site GPU)
- ๐ Real-time scheduler
- ๐ก Adaptive beamforming
- ๐ AI power control
Investment: $1 billion with NVIDIA
๐ก Ericsson micro-LLM (No GPU)
- ๐ Spectral efficiency +10%
- โ Zero additional GPU
- ๐ฐ Zero extra infrastructure
Approach: LLM on existing baseband
Where AI Fails in the Field
The MWC narrative is compelling. But it rests on an implicit premise: AI optimizes what it can see. There is an entire category of problems that AI will never see, because the network itself does not report them.
Real indoor coverage. A new commercial building was erected 200 meters from a cell site. It blocks 18 dB of signal in a third-floor office corridor. The OSS generates no alarm: no UE has complained yet, handover counters remain within thresholds. The AI sees nothing. Only an indoor walk test with real-time RSRP/RSRQ/SINR measurement can document this degradation.
External interference. A malfunctioning security camera emits spurious noise at 3.5 GHz. SINR drops 8 dB on beam 2 of a 5G NR sector. Because the interference is external to the network, it appears in no OSS counter. AI correlates KPIs with each other, but without input data on this interference, it cannot identify it. An RF engineer with a field spectrum analysis tool detects it in 10 minutes.
Physical anomalies. Wind-tilted antenna, damaged coaxial cable, corroded connector after a harsh winter. These mechanical issues degrade VSWR and coverage, but AI has no physical sensor on the tower. It can observe that KPIs are degrading, but it cannot identify the root cause without human intervention.
Multi-vendor Open RAN. Multi-vendor Open RAN introduces interactions that AI models have never encountered during training. When an RU from vendor A, a DU from vendor B, and a CU from vendor C produce undocumented behavior, no AI model trained on single-vendor data can diagnose the issue. It takes an engineer capable of real-time Layer 3 decoding to isolate the cause.
Protocol edge cases. A misconfigured SIB parameter causes 2% of inter-frequency handovers to fail in a specific mobility scenario (high-speed train, highway). AI sees the handover rate drop but classifies it as โnormal variation.โ Only a targeted RRC/NAS analysis can trace back to the offending parameter.
The Real Split: the 80/20 Rule
RF engineers who fear being replaced are fighting the wrong battle. RF engineers who ignore AI are making the opposite mistake. The reality is a well-defined competency split.
๐ค AI Handles 80%
- ๐ Large-scale KPI analysis
- โ ๏ธ Predictive fault detection
- โก Real-time traffic optimization
- ๐ Alarm correlation
- ๐ Adaptive scheduling
- ๐ Capacity planning
๐ง Field Handles 20%
- ๐ก Indoor walk test
- ๐ป External interference
- ๐ฉ Physical anomalies
- ๐ Protocol debug L3
- ๐ Open RAN validation
- โ Site acceptance SSV/CV
AI excels at large-scale pattern recognition. Identifying anomalies across millions of KPI data points, predicting failures, optimizing traffic, correlating alarms. These are data-intensive, repetitive tasks perfectly suited to machine learning.
The field handles what AI cannot perceive: the physical reality of the radio environment, measurements that only an on-site UE can perform, protocol diagnostics that only a live decoding tool can provide.
This is not a competition. It is a feedback loop: AI flags, the field verifies. The field documents, AI integrates.
Operators Are Skeptical
MWC 2026 produced spectacular announcements. But in the hallways, the operator tone was considerably more measured.
Vodafone expressed notable skepticism about GPUs at cell sites. Vodafoneโs Open RAN lead pointed out that adding GPUs to every site raises questions about power consumption, cooling, and cost. Across a network of 30,000 sites, the investment is substantial and the business case is not yet proven.
BT and Verizon converge on a centralized approach: AI inference runs from core facilities, not from cell sites. Their argument: scheduling and power control models do not require sub-millisecond latency to be effective. A 5 to 10 ms round trip to a data center is more than sufficient for 95% of RAN optimization use cases.
This caution also reflects the broader network context. Only 10% of global MNOs have fully deployed 5G SA. The rest operate in NSA mode, with an underlying 4G LTE layer that remains the capacity backbone. Deploying advanced AI on a network that has not yet migrated to 5G SA means optimizing an architecture that is not yet tomorrowโs target state.
For field RF engineers, this means that 5G NR drive testing and 5G SA validation remain critical skills for at least the next 3 to 5 years.
The Real Future: AI AND Field, Not AI OR Field
The โAI replaces RF engineersโ debate is poorly framed. It pits two components against each other that, in operational reality, are complementary.
AI does not replace the RF engineer. It replaces the most repetitive tasks of the RF engineer. 24/7 KPI surveillance, routine parameter tuning, capacity planning based on historical data. An algorithm performs these tasks better, faster, and without fatigue.
But AI also creates new tasks for the RF engineer. Validating AI recommendations in the field. Providing the ground truth that AI cannot generate on its own. Diagnosing the cases that AI flags as anomalous but cannot explain. Auditing AI configurations before deployment across a cluster of sites.
The RF engineer of the future is not the one who ignores AI. It is the one who understands AIโs limitations and knows precisely when and where the field takes over.
Vendors sell AI. Operators buy network performance. And network performance is verified, measured, and validated in the field. With tools capable of delivering real-time RSRP, RSRQ, SINR measurements, Layer 3 protocol decoding, and actionable exports to feed optimization systems.
The network of the future will be steered by AI. But it will be verified by humans, in the field, with the right tools.
AI optimizes the network. The field proves the network works. One without the other is an aircraft with autopilot but no pilot in the cockpit.
Founder of HiCellTek. 15+ years in telecom, operator side, vendor side, field side. Building the field tool RF engineers deserve.
Request a personalized demo of HiCellTek โ 2G/3G/4G/5G network diagnostics on Android.