Role Definition
| Field | Value |
|---|---|
| Job Title | Drive Test Engineer — Mobile Network |
| Seniority Level | Mid-Level |
| Primary Function | Drives predetermined routes collecting RF measurements (RSRP, SINR, throughput, call quality) using specialist equipment such as TEMS Investigation and Nemo Outdoor. Post-processes collected data, generates KPI reports, and identifies coverage gaps, interference, and handover failures for RF planning and optimisation teams. |
| What This Role Is NOT | NOT an RF Planning/Optimisation Engineer (office-based network design and parameter tuning). NOT a Cell Tower Technician (climbing towers to install antennas). NOT a Telecommunications Engineer (end-to-end network architecture). |
| Typical Experience | 2-5 years. Knowledge of LTE/5G NR radio parameters, drive test tools (TEMS, Nemo, XCAL), post-processing software (TEMS Discovery, Nemo Analyze, Actix). |
Seniority note: Junior drive testers who only operate equipment and follow routes would score deeper Red. Senior RF Optimisation Engineers who interpret data, tune parameters, and design network solutions would score Yellow (Urgent) — see RF Planning Engineer assessment (39.3).
Protective Principles + AI Growth Correlation
| Principle | Score (0-3) | Rationale |
|---|---|---|
| Embodied Physicality | 2 | Must physically drive routes in a vehicle with mounted test equipment. Not desk-based. However, this is structured physical work — driving on public roads in a vehicle, not unstructured craft work in unpredictable environments. |
| Deep Interpersonal Connection | 0 | Minimal human interaction. Equipment-focused data collection role with occasional coordination handoffs. |
| Goal-Setting & Moral Judgment | 0 | Follows predetermined routes and standardised test procedures. No strategic decision-making or ethical judgment. |
| Protective Total | 2/9 | |
| AI Growth Correlation | -1 | 3GPP MDT (Minimization of Drive Tests) is specifically designed to reduce manual drive testing. SON and crowdsourced UE data further erode demand. More network automation = fewer manual drive tests. |
Quick screen result: Protective 2 + Correlation -1 = Almost certainly Red Zone.
Task Decomposition (Agentic AI Scoring)
| Task | Time % | Score (1-5) | Weighted | Aug/Disp | Rationale |
|---|---|---|---|---|---|
| Driving routes & operating test equipment | 35% | 2 | 0.70 | AUG | Physical driving with mounted TEMS/Nemo equipment cannot be done remotely. AI assists with route optimisation (Infovista Precision Drive Testing), but someone must physically drive. MDT reduces the VOLUME of tests needed, not the execution method. |
| Collecting RF measurements | 20% | 4 | 0.80 | DISP | MDT enables UE-based measurements directly from subscriber handsets — 24/7 coverage data across entire networks without dispatching engineers. Crowdsourced solutions (Tutela, Opensignal) provide continuous measurement. Manual collection increasingly reserved for acceptance testing only. |
| Post-processing & analysing drive test data | 20% | 4 | 0.80 | DISP | AI/ML analytics platforms auto-process drive test logs, correlate with network KPIs, and identify anomalies. Infovista, Actix Analyzer, and TEMS Discovery automate what was manual data crunching. Output IS the deliverable. |
| Generating reports & KPI summaries | 10% | 5 | 0.50 | DISP | Template-driven reporting from structured measurement data. Fully automatable — tools generate coverage maps, KPI dashboards, and anomaly reports without human intervention. |
| Equipment setup, calibration & maintenance | 10% | 1 | 0.10 | NOT | Physical handling of test equipment — mounting antennas, connecting GPS, calibrating scanners, maintaining hardware. Human hands required. |
| Coordinating with RF planning/optimisation teams | 5% | 2 | 0.10 | AUG | Handoff of findings to optimisation engineers. Some interpretation required but mostly structured data transfer. AI prepares handoff materials; human adds context. |
| Total | 100% | 3.00 |
Task Resistance Score: 6.00 - 3.00 = 3.00/5.0
Displacement/Augmentation split: 50% displacement, 40% augmentation, 10% not involved.
Reinstatement check (Acemoglu): Limited. Some new tasks emerge — validating MDT data quality, configuring automated test platforms, operating drone-based RF measurement systems — but these require fewer people and different skills. The reinstatement effect is weak compared to the displacement volume.
Evidence Score
| Dimension | Score (-2 to 2) | Evidence |
|---|---|---|
| Job Posting Trends | -1 | Glassdoor shows 840 open RF drive test engineer positions (Feb 2026), but this is a niche role within telecom. Postings are declining as operators shift budget from manual drive testing to MDT/SON-based monitoring. 5G rollout creates some demand, but net trend is negative. |
| Company Actions | -1 | Deutsche Telekom targets 40% cost savings via SON (including MDT). Operators across Europe and Asia actively deploying MDT as the primary network monitoring method. Accenture acquired AI technology specifically to accelerate autonomous network operations (Jan 2026). Infovista markets "anyone can do" precision drive testing — explicitly de-skilling the role. |
| Wage Trends | 0 | ZipRecruiter average $117,680; Glassdoor $103,524. Stable but not growing above inflation. Contractor/day-rate model common, compressing effective compensation. No premium signals emerging. |
| AI Tool Maturity | -2 | MDT is a 3GPP standard (Release 10+) — not experimental, not beta, but a ratified international standard specifically designed to replace manual drive testing. Production-deployed across major operators globally. Infovista Precision Drive Testing uses AI/ML for autonomous test execution. Crowdsourced measurement platforms (Tutela, Opensignal, Ookla) provide continuous network quality data at scale no drive test team can match. Anthropic observed exposure: SOC 49-2022 at 3.33% — low, but reflects the broader installer category, not the data-analysis-heavy drive test sub-role. |
| Expert Consensus | -1 | Industry consensus is clear: MDT/SON/crowdsourced data will progressively replace manual drive testing. 3GPP has been standardising this replacement since 2010. MWC 2026 showcased AI-native networks moving from demos to deployment. The debate is pace, not direction. Remaining use cases: regulatory compliance testing, new site acceptance, and benchmark campaigns — a shrinking fraction of current workload. |
| Total | -5 |
Barrier Assessment
Reframed question: What prevents AI execution even when programmatically possible?
| Barrier | Score (0-2) | Rationale |
|---|---|---|
| Regulatory/Licensing | 1 | Some regulatory testing (FCC compliance, Ofcom requirements, new site acceptance) still mandates formal drive test methodology. No strict personal licensing, but BICSI/vendor certifications exist. Regulatory barrier is moderate and narrowing. |
| Physical Presence | 1 | Must be physically in the vehicle driving routes. Cannot be done remotely. However, this is structured (driving on roads), not unstructured craft work — and the entire point of MDT is to eliminate this physical requirement by collecting measurements from subscriber devices. |
| Union/Collective Bargaining | 0 | Predominantly contractor/subcontractor workforce. No meaningful union protection. |
| Liability/Accountability | 0 | Low stakes if measurements are inaccurate. No personal liability, no licensing to revoke, no prison risk. Equipment and methodology errors are correctable. |
| Cultural/Ethical | 0 | No cultural resistance to automated network testing. Operators actively prefer automated solutions — they are cheaper, faster, and provide continuous monitoring versus periodic snapshots. |
| Total | 2/10 |
AI Growth Correlation Check
Confirmed at -1 (Weak Negative). 3GPP MDT was explicitly designed to minimize drive testing — the name says it. SON (Self-Organizing Networks) further automates network optimisation that previously required drive test data as input. AI-native networks showcased at MWC 2026 move network monitoring from human-driven to machine-driven. The more autonomous and AI-capable networks become, the less manual RF measurement is needed. This is not collateral damage from general AI progress — it is targeted displacement by purpose-built standards.
JobZone Composite Score (AIJRI)
| Input | Value |
|---|---|
| Task Resistance Score | 3.00/5.0 |
| Evidence Modifier | 1.0 + (-5 x 0.04) = 0.80 |
| Barrier Modifier | 1.0 + (2 x 0.02) = 1.04 |
| Growth Modifier | 1.0 + (-1 x 0.05) = 0.95 |
Raw: 3.00 x 0.80 x 1.04 x 0.95 = 2.3712
JobZone Score: (2.3712 - 0.54) / 7.93 x 100 = 23.1/100
Zone: RED (Green >=48, Yellow 25-47, Red <25)
Sub-Label Determination
| Metric | Value |
|---|---|
| % of task time scoring 3+ | 50% |
| Task Resistance | 3.00 (>= 1.8) |
| Evidence | -5 (> -6) |
| Sub-label | Red — AIJRI <25 but Task Resistance >= 1.8, so not Imminent |
Assessor override: None — formula score accepted. The 23.1 is borderline Red/Yellow (1.9 points below boundary), but the evidence is honest: MDT is a ratified 3GPP standard designed to eliminate this role, not a speculative AI threat. No override warranted.
Assessor Commentary
Score vs Reality Check
The 23.1 score places this role just below the Yellow boundary, and the label is honest. Task Resistance at 3.00 is higher than typical Red Zone roles because physical driving genuinely protects 35% of task time — you cannot remotely drive a vehicle through a coverage area. But the evidence modifier (0.80) and growth modifier (0.95) compound to cut that base by 24%. This is a rare case where the displacement technology is not speculative AI but a ratified international standard (3GPP MDT, Release 10, 2010) that operators have been progressively deploying for over a decade. The role is not being disrupted by a startup — it is being deprecated by the standards body that governs the entire industry.
What the Numbers Don't Capture
- Function-spending vs people-spending. Operators are spending MORE on network quality monitoring than ever — but that spending goes to MDT platforms, crowdsourced analytics (Tutela, Opensignal), and SON systems. The function grows while the headcount shrinks.
- Delayed trajectory. MDT adoption has been slower than 3GPP envisioned due to UE implementation gaps and operator conservatism. This has given drive test engineers a longer runway than the technology warranted. But MWC 2026 signals the tipping point — AI-native networks are moving from demos to deployment, and MDT maturity has caught up.
- Title rotation. Some drive test work is being absorbed into broader "RF Optimisation Engineer" or "Network Performance Engineer" roles where drive testing is 10-15% of the job rather than 100%. The work partially survives under a different title with a different skill mix.
Who Should Worry (and Who Shouldn't)
If your entire job is driving routes and collecting data — you are the most exposed worker in telecom. MDT does exactly what you do, 24/7, across the entire network, using subscriber devices. No drive test team can compete with that coverage density. Your runway is 1-3 years at operators actively deploying MDT.
If you also post-process, analyse, and interpret the data — you have slightly more time, but AI analytics platforms are rapidly automating this layer too. Infovista explicitly markets its precision drive testing as something "anyone can do." The interpretation skills buy you time, not safety.
If you are transitioning into RF optimisation, network planning, or SON configuration — you are moving toward Yellow Zone territory. The RF knowledge from drive testing transfers directly to roles where human judgment about network design persists. This is the exit path.
The single biggest separator: whether you are purely a data collector or an RF engineer who happens to do drive testing as part of a broader skill set. The pure drive tester is being replaced by a standard. The RF engineer who drive tests as one tool among many is transforming.
What This Means
The role in 2028: Manual drive testing will persist for regulatory compliance, new site acceptance, and benchmark campaigns — but as a shrinking fraction of current volumes. Most routine coverage monitoring will be handled by MDT, crowdsourced platforms, and drone-based RF measurement. The "drive test engineer" as a full-time role will be rare; the work that remains will be absorbed into broader RF optimisation positions.
Survival strategy:
- Upskill into RF optimisation and network planning. Your field measurement experience gives you an advantage understanding propagation in real environments — translate that into parameter tuning, interference management, and network design skills.
- Learn SON/MDT platforms and AI-driven network analytics. Become the person who configures, validates, and interprets the automated systems replacing manual drive testing. The tools need human oversight during the transition.
- Move toward physical telecom infrastructure roles. Cell tower installation, fibre optic splicing, and small cell deployment require the same RF awareness but add irreducible physical work that AI cannot perform.
Where to look next. If you are considering a career shift, these Green Zone roles share transferable skills with drive test engineering:
- Cell Tower Technician (AIJRI 70.6) — RF knowledge transfers directly; tower climbing and antenna installation add irreducible physical protection that drive testing lacks
- Fibre Optic Splicer (AIJRI 79.3) — Telecom infrastructure skills transfer; precision physical work in field environments with acute global workforce shortage from FTTP/BEAD rollout
- Telecom Equipment Installer (AIJRI 58.4) — Equipment handling and RF awareness transfer; physical installation work in customer premises and exchange buildings
Browse all scored roles at jobzonerisk.com to find the right fit for your skills and interests.
Timeline: 1-3 years for significant role compression at operators actively deploying MDT/SON. 3-5 years for the broader market as smaller operators and emerging markets catch up. Regulatory compliance testing is the last bastion — likely persists 5+ years but supports a fraction of current headcount.
