Telecommunications engineer CVs carry three precision gaps that directly reduce shortlisting rates in a market where technical specification depth separates a first-round phone call from a first-round rejection. The first is 5G NR standards vagueness: "5G experience" in 2026 can mean anything from a network operations engineer who monitors KPIs on a live 5G NSA network to an RAN engineer who understands 5G NR Numerology (μ — the 3GPP subcarrier spacing configuration: μ=1 for 30kHz SCS on FR1 Sub-6GHz deployments, μ=3 for 120kHz SCS on FR2 mmWave), Massive MIMO beam management (SSB-based beam sweep, CSI-RS non-zero power ports, SRS-based uplink beamforming), and the difference between NSA Option 3x (LTE anchor with NR secondary carrier — 3GPP Release 15) and SA Mode 2 (standalone 5GC — NR only, 3GPP Release 15+). The 3GPP Release number and deployment mode are the specifics that ATS systems and senior RF engineers search for. The second gap is RF link budget not quantified: "RF planning experience" describes an activity that covers everything from adjusting antenna tilts on a live network to building a greenfield link budget from first principles (EIRP, path loss model, receiver sensitivity, interference margin, fade margin, SINR target → spectral efficiency → throughput). The quantified link budget is the fundamental design document for a radio network cell — and not quantifying it on the CV is the equivalent of a civil engineer saying "designed a bridge" without mentioning the span, load, and code. The third is transmission/backhaul protocol stack not specified: "MPLS backhaul experience" and "IP networking knowledge" describe tool categories rather than the configuration depth that distinguishes a telecom transport engineer who has built MPLS-TE tunnels with RSVP-TE, implemented BGP route policy for MPLS VPN CE-PE peering, and configured DSCP-based QoS for real-time traffic from one who has read the RFC.

What Telecommunications Engineer Job Descriptions Require in 2026

Telecom engineer JDs cluster around four technical domains:

5G NR Radio Access Network (RAN) engineering: Design, planning, optimisation, and commissioning of 5G NR radio access networks. JDs specify: 3GPP Release 15 (initial 5G NR specifications — NSA Option 3x/3 dual connectivity, SA Mode 2, NR-FR1 sub-6GHz, NR-FR2 mmWave), Release 16 (URLLC enhancements, NR-U for unlicensed spectrum, IAB — Integrated Access and Backhaul, MBS — Multicast and Broadcast Service for NR), Release 17 (NR-Light for RedCap IoT, NTN — Non-Terrestrial Network support for satellite, MIMO/FeMIMO enhancements), and Release 18 (5G Advanced — AI/ML-based RRM, XR optimisation for AR/VR); NR Numerologies (μ=0: 15kHz SCS, equivalent to LTE for coexistence; μ=1: 30kHz SCS — standard for FR1 TDD n77/n78 3.5GHz deployments; μ=2: 60kHz; μ=3: 120kHz SCS — used for mmWave FR2 deployments on n257/n258 at 26–28GHz); NR physical channels: DL — PDSCH (data), PDCCH (control), PBCH (broadcast), SS/PBCH Block (SSB — 4 OFDM symbols for primary synchronisation); UL — PUSCH, PUCCH, PRACH, SRS; Massive MIMO (up to 64TRX antenna arrays — codebook-based precoding with Type I CSI and non-codebook SRS-based uplink beamforming); NR-DC (NR Dual Connectivity) for CA aggregation of FR1 + FR2; 5GC (5G Core — service-based architecture: AMF, SMF, UPF, NRF, PCF, NSSF, AUSF over HTTP/2 + JSON N-interface); NSA vs SA deployment transitions. Radio planning tools: Atoll 3.3/3.4 (Forsk — industry-dominant commercial radio planning platform for 5G NR, LTE, and Wi-Fi 6; Monte Carlo simulation, geographic data layers, SINR analysis); Planet EV; WinProp (Altair). Drive testing: TEMS Investigation (Ascom), Actix Analyzer (Nokia), NEMO Outdoor (Anritsu).

RF engineering and microwave backhaul: RF propagation analysis, link budget design, and microwave point-to-point backhaul link engineering. JDs specify: path loss models (3GPP UMa/UMi close-in + far-out model for 5G NR; COST-231 Hata for LTE macro; Ericsson 9999 model; indoor ITU-R M.2412; ray-tracing in Atoll 3D propagation); link budget analysis (downlink: BS EIRP = Ptx + Gantenna − feeder loss; path loss at cell edge; UE Rx sensitivity = −174 dBm/Hz + NF + 10·log10(BW) + SINRrequired; interference margin Imargin; fade margin F_margin; SINR → spectral efficiency via Shannon bound); microwave P-to-P backhaul (ETSI EN 302 217 classes 1–4 for availability targets; ITU-R P.530 rain attenuation model — specific attenuation γR = k(f) · R^α, fade margin calculation for 99.999% annual availability; Vigants-Barnett multi-path fading; XPIC — Cross-Polarisation Interference Cancellation for co-channel dual-polar 1+1 HSB links; synchronisation: IEEE 1588v2 PTP G.8275.1 telecom profile for phase synchronisation; SyncE ITU-T G.8261 for frequency); antenna systems (Active Antenna Unit — AAU for 5G Massive MIMO; passive antenna with Remote Radio Head — RRH for LTE; beamtilt, electrical downtilt vs mechanical tilt; MIMO/cross-polar isolation requirement > 30dB).

Transport and IP/MPLS networks: Design and operation of backhaul, fronthaul, and midhaul transport networks for mobile and fixed telecoms. JDs specify: IP/MPLS (OSPF for IGP; IS-IS as alternative IGP in large carrier networks; BGP iBGP/eBGP with route policy, community tagging, MED, local preference — in Cisco IOS-XR and Juniper Junos; MPLS-TE with RSVP-TE for traffic-engineered LSP paths — FRR Fast Reroute for 50ms protection; LDP for hop-by-hop label distribution; Segment Routing SR-MPLS as LDP/RSVP-TE replacement for simplified MPLS forwarding — now dominant in new designs); MPLS VPN (L3VPN — RFC 4364 BGP/MPLS IP VPN, VRF tables, CE-PE BGP peering; L2VPN — VPWS, VPLS — for backhaul point-to-point and multipoint Ethernet services); QoS (DSCP classification — EF (46) for voice/signalling, AF41 for video, AF31 for interactive data, BE (0) for best-effort; traffic policing and shaping; WRED for congestion management); OTN (Optical Transport Network — ITU-T G.709 — ODU0 to ODU4 container mapping; DWDM with 100GHz or 50GHz ITU-T G.694.1 channel spacing; coherent 400G/800G optics with DP-16QAM or DP-64QAM; EDFA amplification on long-haul spans).

Fixed broadband and FTTx/FTTP: Design and deployment of passive optical networks for residential and business broadband. JDs specify: GPON (ITU-T G.984 — 2.5Gbps DL / 1.25Gbps UL, AES-128 encryption, split ratio 1:64); XGS-PON (ITU-T G.9807.1 — 10Gbps symmetric — the current Openreach UK FTTP standard since 2020, being deployed under the BEAD and BDUK broadband programmes); NG-PON2 (ITU-T G.989 — 40Gbps aggregate, TWDM wavelength stacking for legacy-compatible wavelength assignment); Active Ethernet P2P fibre; OLT (Optical Line Terminal — Nokia ISAM FX, Huawei MA5800, Calix E-Series) and ONT/ONU (Optical Network Termination) configuration; optical power budget (OLT Tx power, splitter loss, cable attenuation at 1490nm/1310nm/1550nm, ONT receive sensitivity — class B+ or C+ per G.987); Openreach FTTP (OR TM 2533 engineering rules), UKPN duct access (NDUP — Duct and Pole Access), CLLT/VULA Ofcom wholesale access products.

Telecommunications engineer salaries in 2026: £32K–£56K UK for graduate and junior RAN and transport; £54K–£85K for senior 5G NR RAN, RF, and MPLS engineers; £80K–£125K for lead/principal 5G SA core, RAN architecture, and optical transport design engineers at MNOs and infrastructure vendors.

ATS Keywords for a Telecommunications Engineer Resume

Telecom engineer ATS filtering is extremely specification-dependent. Generic terms carry minimal signal — the search is for 3GPP release numbers, NR Numerologies, specific routing protocols, and ITU-T standards.

Essential ATS terms for a telecommunications engineer resume:

  • Title variants: Telecommunications Engineer, Telecoms Engineer, RF Engineer, Radio Planning Engineer, RAN Engineer, 5G Engineer, Network Planning Engineer, Transport Engineer, MPLS Engineer, Optical Network Engineer, FTTx Engineer, FTTP Engineer, Microwave Engineer, IP Network Engineer, Core Network Engineer, Network Optimisation Engineer
  • 5G NR and RAN: 5G NR, 3GPP, Release 15, Release 16, Release 17, NSA, SA, FR1, FR2, Sub-6GHz, mmWave, Numerology, μ=1, μ=3, SCS, subcarrier spacing, Massive MIMO, 64TRX, SSB, CSI-RS, SRS, PDSCH, PUSCH, PUCCH, NR-DC, 5GC, AMF, SMF, UPF, beamforming, Atoll, TEMS, Actix, drive test
  • LTE and legacy: LTE, LTE-A, LTE-A Pro, EPC, eNodeB, eNB, gNodeB, gNB, S1, X2, Xn, CA, carrier aggregation, VoLTE, VoNR, eMBB, URLLC, mMTC
  • RF and link budget: EIRP, link budget, path loss, SINR, RSRP, RSRQ, receiver sensitivity, interference margin, fade margin, Shannon capacity, spectral efficiency, COST-231, UMa, UMi, 3GPP UMa, Ericsson 9999, Atoll, Planet EV, WinProp, drive test, propagation, cell edge, antenna tilt, downtilt, beamtilt
  • Microwave and backhaul: microwave, P2P, ETSI EN 302 217, ITU-R P.530, rain attenuation, fade margin, XPIC, Vigants-Barnett, IEEE 1588, PTP, SyncE, G.8275.1, G.8261, Harris, Ericsson MINI-LINK, Nokia, Huawei, E-band, V-band
  • IP/MPLS and routing: IP, MPLS, OSPF, IS-IS, BGP, iBGP, eBGP, RSVP-TE, LDP, Segment Routing, SR-MPLS, L3VPN, L2VPN, VPLS, VPWS, VRF, QoS, DSCP, traffic shaping, IOS-XR, Junos, Cisco, Juniper, Nokia SR OS, Huawei VRP
  • Optical and FTTx: GPON, XGS-PON, NG-PON2, OTN, DWDM, G.709, G.9807, G.984, OLT, ONT, ONU, splitter, power budget, EDFA, coherent, 400G, ITU-T G.694, Openreach, FTTP, BDUK, BEAD
  • Long-tail phrases: telecommunications engineer resume, telecoms engineer cv, how to write a telecommunications engineer resume, telecoms engineer resume 2026, 5G engineer resume, RF engineer resume, RAN engineer resume, MPLS network engineer resume, FTTP engineer resume

Placement: "3GPP Release 16" or "Release 17" in the headline or first Skills line for RAN roles. Numerology μ value and SCS in any 5G NR physical layer bullet. Named routing protocols (OSPF, BGP, Segment Routing) in Skills for transport roles, not just "IP/MPLS." EIRP, receiver sensitivity, and SINR values in any RF link budget bullet. XGS-PON or GPON standard number (G.9807.1, G.984) in any FTTx design bullet.

Section order:

  1. Headline — "5G NR RAN Engineer | 3GPP Release 16 · Massive MIMO · Atoll · TEMS · FR1/FR2" or "Transport Network Engineer | MPLS-TE · BGP · Segment Routing · Nokia SR OS · OTN"
  2. Skills — RAN & Radio Planning / RF Engineering / Transmission & Backhaul / IP/MPLS & Core / Optical & FTTx / Tools & Protocols
  3. Experience — 4–5 bullets per role; 3GPP Release, NR Numerology μ, and SCS in 5G bullets; EIRP, SINR, and throughput in RF bullets; routing protocol stack in transport bullets
  4. Education — BEng/MEng Electronic Engineering, Telecommunications, Computer Networks; IET membership; at bottom

Two pages for 5+ years. 3GPP Release number in every 5G NR bullet. NR Numerology (μ value and SCS) in every NR physical layer bullet. EIRP and SINR target in every link budget bullet. Named routing protocols (OSPF, BGP-4, SR-MPLS) in every transport design bullet. ITU-T standard number in every optical or PON design bullet.

Three elements make a telecommunications engineering bullet convincing: the 3GPP or ITU-T specification and version (3GPP Release 16 5G NR SA; ITU-T G.9807.1 XGS-PON; ETSI EN 302 217 Class 4; G.8275.1 PTP profile), the technical implementation specifics (NR n78 100MHz carrier, μ=1 30kHz SCS, 64T64R AAUU, Atoll 3GPP UMa NLoS model), and the quantified outcome (98% population coverage at −100dBm RS; downlink throughput 4.1Gbps peak per cell; 99.999% link availability; optical link margin 5.2dB above B+ budget). Three examples:

  • Designed 5G NR SA radio access network for 12 macro sites in dense urban deployment — n78 band (3.5GHz, 100MHz carrier, μ=1 30kHz SCS TDD, 64T64R Massive MIMO AAU — Ericsson AIR 6449, SRS-based uplink beamforming per 3GPP Release 16); Atoll 3.4 propagation model (3GPP UMa NLoS clutter correction using OS MasterMap 3D heights); DL link budget: BS EIRP = 69 dBm per beam (33 dBm Tx + 24 dBi array gain − 3 dB implementation loss − beam scanning loss), UE receiver sensitivity −96 dBm (QPSK r1/8, 100MHz BW, NF = 9dB), interference margin 5dB, SINR target 28dB for 256-QAM r4/5 → 4.1Gbps theoretical peak throughput; 98.2% population coverage at −100dBm RSRP reference sensitivity; RF coordination: SINR floor > 15dB (64-QAM eligible) across 96% of coverage area; accepted as Lot 2 baseline by MNO RF Director

  • Link budget and availability analysis for 38GHz E-band microwave P2P backhaul link (12.4km path over mixed urban/semi-rural terrain) — ITU-R P.530 rain attenuation model at 38GHz (specific attenuation γR = 0.21 mm/hr⁻¹·km⁻¹ for R0.01 = 32 mm/hr at UK site — Kh = 0.207, αh = 1.005 from Table 1): rain fade margin 28.4dB for 99.999% annual availability; Vigants-Barnett multi-path fading (shallow angle path, high humidity): multi-path fade margin 34dB; system gain check (Tx +23dBm, antenna 1.2m dish 42dBi G, FSL 143dB at 38GHz): RSL −58dBm vs threshold −90dBm (3×10⁻³ BER at QPSK) — fade margin 32dB; XPIC implemented (co-channel dual-polar V+H) — XPD > 38dB confirmed in link acceptance; link met ETSI EN 302 217-2 Class 4 availability (99.9995%) on commissioning acceptance test; IEEE 1588v2 G.8275.1 PTP telecom profile configured on both end terminals for 5G phase synchronisation (time error < 1.1μs)

  • Deployed XGS-PON FTTP network for 2,400-home build programme under BDUK contract — ITU-T G.9807.1 XGS-PON, Nokia ISAM FX OLT (16-port chassis, 1:32 primary and 1:2 secondary splitter cascade, 10Gbit/s symmetric per 64-subscriber PON port), ODN (Optical Distribution Network) designed using Openreach TM 2533 guidelines; optical power budget: OLT Tx +5dBm, primary splitter loss 16.0dB, 3km fibre cable attenuation 0.75dB (0.25dB/km at 1490nm), secondary splitter loss 4.0dB, connector losses 1.5dB total — received power at ONT −13.25dBm vs XGS-PON class C+ threshold −29dBm; margin 15.75dB above minimum receive sensitivity; rollout of 2,400 premises at 97.3% premises passed vs original design forecast; first-time pass rate on OTDR acceptance testing 94.1% (average FTP = 96% for similar builds); NDUP duct access completed with BT Openreach Fibre Works team in 18 months

Telecommunications engineer interviews include design questions (sketch a link budget for a 5G NR n78 macro cell at the 1% AEP coverage edge), standards questions (what is the difference between NSA Option 3 and SA Mode 2, and which 3GPP Release introduced standalone NR?), and network questions (explain Segment Routing and how it simplifies traditional MPLS-TE). Your CV's 3GPP Release specificity, link budget quantification, and routing protocol stack evidence determine whether the interview tests your RAN and transport engineering depth or your general telecoms awareness.

Three Telecommunications Engineer CV Mistakes That Lose the Technical Signal

"5G experience" without 3GPP Release number, deployment mode, or NR Numerology. "Experience with 5G networks" and "knowledge of 5G technology" are entries on telecommunications engineer CVs that carry almost no ATS or recruiter signal in 2026, when 5G has been commercially deployed by UK MNOs for six years and "5G experience" is as broad as "internet experience." The meaningful 5G NR technical signal is found in the 3GPP Release version (Release 15 introduced the first standardised 5G NR specifications with SA Mode 2 and NSA Option 3x; Release 16 added URLLC enhancements, NR-U, IAB, and V2X; Release 17 introduced NR-Light for RedCap, NTN for satellite integration, and enhanced MIMO — naming the release signals which features the candidate has worked with), the deployment mode (NSA Option 3x — NR secondary carrier anchored to LTE primary with EPC core; SA Mode 2 — NR-only with 5GC standalone core — these are architecturally different and require different skills), and the Numerology (μ value and subcarrier spacing) for physical layer work. A candidate who writes "3GPP Release 16 5G NR SA deployment — FR1 n78 100MHz, μ=1 30kHz SCS, Massive MIMO 64T64R TDD, Atoll 3.4 propagation" has communicated a complete technical profile in one line.

RF link budget not quantified — EIRP, SINR, and throughput not stated. "RF planning and link budget analysis" is a job task, not an engineering record. The RF link budget is the fundamental document for a radio network cell design: it specifies the transmit EIRP (the effective isotropically radiated power in dBm — transmit power + antenna gain − feeder and connector loss); the path loss at the design range; the receiver sensitivity (noise floor + noise figure + required SINR — different for each MCS and bandwidth); the interference margin (from adjacent cells, in Monte Carlo simulation from the radio planning tool); the fade margin (for slow fading and multi-path); and the resulting cell edge SINR and hence spectral efficiency and throughput (via the Shannon-Hartley theorem or 3GPP link-level simulation tables). A complete link budget in the experience bullet — "DL EIRP 69dBm, UE sensitivity −96dBm, interference margin 5dB, SINR target 28dB for 256-QAM r4/5 → 4.1Gbps" — communicates that the candidate has designed a cell, not just reviewed one.

Transmission protocol stack listed generically — "MPLS experience" without named routing protocols. MPLS is not a single protocol — it is a label-switching forwarding paradigm that can be operated in several significantly different modes depending on how the label distribution and path signalling are handled. LDP (Label Distribution Protocol) is the legacy label distribution method where LSPs are established hop-by-hop following the IGP path — simple to configure but not traffic-engineering capable. RSVP-TE (Resource Reservation Protocol — Traffic Engineering) enables explicit path LSPs with bandwidth reservation — the traditional MPLS-TE approach, complex to operate at scale. Segment Routing (SR-MPLS) replaces LDP and RSVP-TE with source routing using SRGB label blocks in the IGP — simpler, more scalable, and now the preferred new deployment in most major carrier networks (Nokia, Juniper, and Cisco all support SR-MPLS natively). MPLS VPN (RFC 4364 — L3VPN with VRF tables and MP-BGP for route distribution between PE routers; L2VPN with VPWS or VPLS for Ethernet service delivery) requires both MPLS forwarding and BGP control plane competence. State the specific protocols used — "SR-MPLS with IS-IS TI-LFA for FRR, L3VPN CE-PE eBGP with community-based export policy, QoS DSCP EF PHB for real-time services" — rather than "MPLS backhaul experience."

If you are applying to telecommunications engineer, 5G NR RAN, transport engineer, or FTTx engineer roles and want your CV rebuilt around the specific 3GPP releases, NR Numerologies, routing protocols, and optical standards in a target job description, Resumegpt generates your telecommunications engineer CV from your work history in under 60 seconds — 3GPP Release and NR Numerology stated, RF link budget quantified, routing protocol stack named, ATS-optimised, and exported as a PDF ready to submit.