IEEE 802.11 Wi-Fi Generations Explained for Engineers (Wi-Fi 4 to Wi-Fi 8) Interview Prep

IEEE 802.11 wireless standards for engineers: 802.11n/ac/ax/be/bn, Wi-Fi 4 through Wi-Fi 8, OFDMA, MU-MIMO, MLO, EMLSR, NPCA, 6 GHz.

Quick answer

Wi-Fi generations are the marketing labels assigned by the Wi-Fi Alliance to the underlying IEEE 802.11 standards.

Wireless interviews use Wi-Fi standards as a fast filter for whether a candidate can connect specification features to product trade-offs.

Editorial review

Written by

CompoundLearn editorial team

Wireless / RF / hardware engineering

Reviewed by

CompoundLearn editorial team

Wireless / RF / hardware engineering

Last reviewed

Built from curated topic maps, editorial validation, and subject-matter review so the page stays aligned with the interview intent and the current content pipeline.

What it is

Wi-Fi generations are the marketing labels assigned by the Wi-Fi Alliance to the underlying IEEE 802.11 standards. Wi-Fi 4 maps to 802.11n, Wi-Fi 5 to 802.11ac, Wi-Fi 6 to 802.11ax (with Wi-Fi 6E covering the same standard in the 6 GHz band), Wi-Fi 7 to 802.11be (published as IEEE Std 802.11be-2024 in July 2025), and Wi-Fi 8 to the in-progress 802.11bn TGbn Ultra-High Reliability amendment. Each generation adds technology, not just bandwidth. Wi-Fi 5 introduced downlink MU-MIMO and the 256-QAM modulation. Wi-Fi 6 introduced OFDMA, uplink MU-MIMO, 1024-QAM, BSS coloring, and Target Wake Time. Wi-Fi 7 introduced 320 MHz channels (only possible in 6 GHz), 4096-QAM, Multi-Link Operation, preamble puncturing, and Restricted Target Wake Time for latency-sensitive traffic. Wi-Fi 8 shifts the target from peak throughput to worst-case latency and seamless mobility — coordinated spatial reuse and coordinated beamforming across access points are the central new mechanisms. Per-amendment focus, the way wireless engineers usually frame it in interviews: 802.11n (Wi-Fi 4) is the MIMO generation — spatial multiplexing, transmit diversity, and 40 MHz channels mainstream. 802.11ac (Wi-Fi 5) is the wider-channel generation — 80 and 160 MHz channels in 5 GHz with downlink MU-MIMO and the move to 256-QAM. 802.11ax (Wi-Fi 6) is the dense-network efficiency generation — OFDMA scheduling with 26-tone through 996-tone resource units, uplink MU-MIMO, BSS coloring for spatial reuse, Target Wake Time for battery clients. Wi-Fi 6E is the same 802.11ax mechanisms operating in the 6 GHz band. 802.11be (Wi-Fi 7, published as IEEE Std 802.11be-2024) is the peak-throughput generation — 320 MHz channels, 4096-QAM, MLO with STR / Non-STR / EMLSR modes, preamble puncturing for fragmented spectrum. 802.11bn (Wi-Fi 8) is the reliability-and-coordination generation — the headline is no longer peak rate but worst-case latency, with Non-Primary Channel Access (NPCA), Dynamic Sensitivity Control (DSC), Coordinated Beamforming (Co-BF), and refined MLO link selection as the mechanisms that move the floor up. The peak PHY data rates often quoted in marketing — 600 Mbps for Wi-Fi 4, 3.5 Gbps for Wi-Fi 5, 9.6 Gbps for Wi-Fi 6, 46 Gbps for Wi-Fi 7 — are corner-case maxima assuming top channel width, top spatial streams, top modulation, and ideal channel conditions. Real-world throughput is typically 30 to 60 percent of peak under good conditions and degrades quickly with interference, walls, and distance. Case study: an enterprise office may advertise a Wi-Fi 7 refresh, but the real question is whether the deployment actually benefits from 6 GHz access, wider channels, MLO, and low-latency scheduling. If the floor plan, client mix, and regulatory constraints do not support those mechanisms, the upgrade can cost more than it improves. The useful interview answer is not "Wi-Fi 7 is better" but "Wi-Fi 7 is better when the deployment constraints let its mechanisms matter."

Why interviewers ask

Wireless interviews use Wi-Fi standards as a fast filter for whether a candidate can connect specification features to product trade-offs. A strong answer goes past "Wi-Fi 7 is faster than Wi-Fi 6" and explains which mechanisms enable that speed (320 MHz channels, 4096-QAM, MLO), what constraints they impose (6 GHz hardware on both ends, multi-radio cost and power, regulatory caps on EIRP), and which workloads actually benefit (high-throughput downlinks for content delivery, low-latency for cloud gaming and AR/VR). Hiring teams care about three signals. First, can the candidate distinguish PHY features (OFDMA, MU-MIMO, modulation) from MAC features (Target Wake Time, BSS coloring, MLO link steering)? Second, can they explain what changes for the product — battery life on a wearable, antenna count and placement, certification cost in the United States versus Europe, coexistence with legacy clients on the same access point? Third, can they reason about Wi-Fi 8 before any product ships — what kinds of applications need worst-case latency guarantees, why coordinated spatial reuse needs cross-AP coordination, what infrastructure changes are implied? Product teams hiring wireless engineers want the same things: someone who can read a Wi-Fi 7 specification chapter and translate it into a feature-set decision, a hardware bill of materials change, or a test-plan addition.

Common mistakes

The most common mistake is treating peak data rate as a real-world performance number. The 9.6 Gbps Wi-Fi 6 number and 46 Gbps Wi-Fi 7 number assume conditions that do not occur in shipping products. A second common mistake is confusing OFDMA and MU-MIMO — OFDMA serves multiple stations in different frequency slots in one transmission, while MU-MIMO serves multiple stations on the same frequency at the same time using spatial streams. They solve different problems and modern access points combine both. Other frequent gaps: assuming Wi-Fi 6E and Wi-Fi 7 just need a firmware update (they require new radios and antennas), assuming MLO doubles or triples throughput in all conditions (it depends on which links are simultaneously available and free of interference), assuming 6 GHz is universally available (regulatory rules vary by region and the AFC system constrains outdoor standard-power use in the United States), and conflating Wi-Fi 8's goals with Wi-Fi 7's (Wi-Fi 8 is about reliability and latency, not peak rate). New graduates often miss that the 802.11 working group is active across many parallel amendments — UHR (Wi-Fi 8 / TGbn), Ambient Power Communications, Integrated mmWave, Post-Quantum Cryptography, and AI/ML study groups all run in parallel and feed into future generations.

IEEE 802.11 amendments and Wi-Fi generations — what each one introduced

IEEE amendmentWi-Fi namePrimary focusKey PHY additionsKey MAC additions
802.11nWi-Fi 4MIMO and 40 MHz channelsMIMO, 40 MHz channels, 64-QAMFrame aggregation (A-MPDU)
802.11acWi-Fi 5Wider channels in 5 GHz80 / 160 MHz, 256-QAM, DL MU-MIMOExplicit beamforming sounding (NDP)
802.11axWi-Fi 6 / 6EDense-network efficiencyOFDMA (26 to 996-tone RUs), UL MU-MIMO, 1024-QAMBSS coloring, Target Wake Time, OBSS/PD spatial reuse
802.11beWi-Fi 7Peak throughput and multi-link320 MHz channels, 4096-QAM, preamble puncturingMLO (STR / Non-STR / EMLSR), Restricted TWT, TXOP sharing
802.11bnWi-Fi 8Ultra-high reliability and AP coordinationDistributed Resource Unit (DRU), UHR-LTF, PHY HARQ-like retransmissionNPCA, Dynamic Sensitivity Control, Coordinated Beamforming, enhanced MLO

Sample interview questions

  1. Why is Wi-Fi 7 not just "faster Wi-Fi 6" in practice?
    • A. Because Wi-Fi 7 adds 320 MHz channels, 4096-QAM, Multi-Link Operation, and puncturing, which change throughput, latency, and resilience trade-offs.
    • B. Because Wi-Fi 7 only changes the marketing name and not the technology.
    • C. Because Wi-Fi 7 only improves battery life, not throughput or latency.
    • D. Because Wi-Fi 7 removes the need for access points and client radios.

    Option A is correct. Wi-Fi 7 is not just a speed bump. It adds 320 MHz channels in 6 GHz, 4096-QAM, Multi-Link Operation, and preamble puncturing, which change how systems trade throughput, latency, coexistence, and hardware cost. Those changes are why Wi-Fi 7 matters even when the headline peak rate is not reached in practice. Option B is wrong because Wi-Fi 7 is an actual PHY/MAC evolution, not a branding-only change. Option C is wrong because Wi-Fi 7 affects throughput and latency together, not just power. Option D is wrong because access points and client radios are still required.

  2. What is the key deployment trade-off of moving more traffic into 6 GHz?
    • A. You get longer range and more wall penetration than 2.4 GHz.
    • B. You get cleaner spectrum and wider channels, but shorter range and stricter hardware / regulatory constraints.
    • C. You can use the same hardware without any changes.
    • D. You lose the ability to use OFDMA and MU-MIMO.

    Option B is correct. The 6 GHz band gives cleaner spectrum and much wider channels, which helps throughput and latency in dense deployments. The trade-off is shorter range because of higher path loss, plus stricter hardware and regulatory constraints such as AFC for some outdoor standard-power use cases in the United States. Option A is wrong because 6 GHz does not improve range relative to lower bands. Option C is wrong because 6 GHz support requires appropriate radios and antennas. Option D is wrong because 6 GHz still uses Wi-Fi 6 / Wi-Fi 7 mechanisms like OFDMA and MU-MIMO.

  3. When does Wi-Fi 8 become a better story than Wi-Fi 7 for a customer?
    • A. When the customer wants the highest possible peak throughput at any cost.
    • B. When the customer cares more about worst-case latency, reliability, roaming, and interference resilience than peak speed.
    • C. When the customer wants to avoid using any radios in the 6 GHz band.
    • D. When the customer wants to replace access points with software only.

    Option B is correct. Wi-Fi 8 shifts the public story from peak throughput to worst-case latency, reliability, roaming behavior, and interference resilience. That makes it a better story for industrial automation, mixed reality, and dense enterprise networks where tail latency matters more than headline speed. Option A is wrong because peak throughput is more of a Wi-Fi 7 story. Option C is wrong because Wi-Fi 8 still builds on the wireless spectrum story, including 6 GHz behavior. Option D is wrong because Wi-Fi still depends on physical radios and access infrastructure.

  4. In 802.11bn (Wi-Fi 8), what problem does Non-Primary Channel Access (NPCA) address that primary-channel-only EDCA does not?
    • A. NPCA lets an access point transmit on a non-primary 20 MHz subchannel when the primary channel is busy, addressing the "different view" problem where the AP and station see different channel-state conclusions due to obstacles or attenuation.
    • B. NPCA replaces OFDMA resource units with a higher-priority frequency-domain reservation that bypasses contention entirely.
    • C. NPCA forces all stations onto the primary channel to eliminate hidden-node collisions in dense deployments.
    • D. NPCA is a security mechanism that authenticates non-primary channel use under WPA3-Enterprise rules.

    Option A is correct. NPCA is an 802.11bn MAC-layer mechanism that extends channel access to non-primary 20 MHz subchannels when local conditions justify it. The "different view" problem — where the AP perceives the primary channel as busy from a distant interferer while a nearby station perceives it as idle (or vice versa) — is the deployment pain that NPCA addresses, using a secondary EDCA procedure on the non-primary channel with an RSSI gating threshold to prevent hidden-node collisions. Option B is wrong because NPCA is medium-access machinery, not a frequency-domain reservation that replaces OFDMA RUs. Option C is wrong because NPCA expands channel access options rather than constraining stations to the primary channel. Option D is wrong because NPCA is a channel-access feature, not a security or authentication mechanism.

  5. How does Enhanced Multi-Link Single Radio (EMLSR) in 802.11be/802.11bn differ from full Simultaneous Transmit and Receive (STR) MLO?
    • A. EMLSR uses one radio chain at a time and switches between links via a low-power frame detector that wakes the high-capability receiver; STR uses two independent radios that transmit and receive concurrently on different links.
    • B. EMLSR is identical to STR except that it operates only in the 2.4 GHz band.
    • C. EMLSR replaces MLO entirely for any device with battery constraints, and STR is only used on access points.
    • D. EMLSR doubles peak throughput because it runs both 5 GHz and 6 GHz radios at full power continuously.

    Option A is correct. EMLSR (Enhanced Multi-Link Single Radio) is a power-efficient MLO mode where the device uses one radio chain at a time, switches between links, and uses a low-power frame detector to wake the high-capability receiver when traffic arrives on an alternate link. STR (Simultaneous Transmit and Receive) requires two independent radios with sufficient frequency separation and antenna isolation to operate concurrently without self-interference. EMLSR trades concurrency for power and cost; STR trades cost and power for true parallel link operation. Option B is wrong because EMLSR is band-agnostic — the constraint is single-radio operation, not the band. Option C is wrong because EMLSR is one of several MLO modes; STR remains available for devices with sufficient RF isolation regardless of battery posture. Option D is wrong because EMLSR does not run both radios concurrently — that is exactly what STR does, and EMLSR explicitly does not.

Frequently asked questions

How do Wi-Fi generations map to 802.11 standards and channel widths?
Wi-Fi 4 is 802.11n (2.4 and 5 GHz, up to 40 MHz channels, MIMO, 64-QAM, ~600 Mbps PHY). Wi-Fi 5 is 802.11ac (5 GHz only, up to 160 MHz, downlink MU-MIMO, 256-QAM, ~3.5 Gbps). Wi-Fi 6 is 802.11ax (2.4, 5, and 6 GHz once Wi-Fi 6E lands, OFDMA, uplink and downlink MU-MIMO, 1024-QAM, ~9.6 Gbps). Wi-Fi 7 is 802.11be (320 MHz channels in 6 GHz, 4096-QAM, Multi-Link Operation, preamble puncturing, ~46 Gbps peak). Wi-Fi 8 is the marketing label for the in-progress 802.11bn TGbn Ultra-High Reliability amendment, which prioritizes worst-case latency and reliability over peak throughput.
What changed technically between Wi-Fi 6, Wi-Fi 6E, and Wi-Fi 7?
Wi-Fi 6 introduced OFDMA, uplink MU-MIMO, 1024-QAM, BSS coloring, and Target Wake Time. Wi-Fi 6E is the same Wi-Fi 6 PHY/MAC operating in the newly opened 6 GHz band, so the technology did not change, only the spectrum. Wi-Fi 7 added 320 MHz channels (only possible in 6 GHz), 4096-QAM (4K-QAM), Multi-Link Operation, preamble puncturing to work around in-band interferers, and a Restricted Target Wake Time mode for low-latency traffic.
What is MLO (Multi-Link Operation) and why does Wi-Fi 7 introduce it?
MLO lets a single Wi-Fi 7 station and access point exchange data across two or three radio links simultaneously, typically 2.4 + 5 + 6 GHz or 5 + 6 GHz. It supports three modes: simultaneous transmit and receive across links for throughput aggregation, link selection for latency-sensitive frames, and redundant duplicate transmission for reliability. MLO is the headline reason Wi-Fi 7 reaches multi-gigabit real-world throughput and the precursor to the worst-case-latency work in Wi-Fi 8.
How does OFDMA differ from MU-MIMO in Wi-Fi 6 and Wi-Fi 7?
OFDMA splits a channel into resource units in the frequency domain so the access point can serve multiple stations on disjoint sub-bands in one transmission, which is best for many small packets and reduces latency. MU-MIMO uses spatial streams to serve multiple stations on the same frequency at the same time, which is best for large packets to capable client devices and depends on accurate channel state information. Modern access points combine both: MU-MIMO for high-throughput downlinks and OFDMA for low-latency uplinks and dense client mixes.
What is Wi-Fi 8 (802.11bn) and how is it different from Wi-Fi 7?
Wi-Fi 8 is the marketing name for the in-progress IEEE 802.11bn TGbn Ultra-High Reliability amendment. The headline target is worst-case latency, mobility under interference, and seamless roaming, not peak throughput. Expected mechanisms include coordinated spatial reuse across access points, coordinated beamforming, enhanced MLO, and tighter retransmission and acknowledgement timing. Wi-Fi 8 is being designed for industrial automation, mixed-reality, real-time voice, and dense enterprise deployments where the tail of the latency distribution matters more than the peak data rate.
What Wi-Fi standards questions should engineers expect in wireless interviews?
Strong wireless interviews go past peak data rate. Expect questions on the practical difference between OFDMA, MU-MIMO, and MLO, on channel-width trade-offs in 5 GHz versus 6 GHz, on coexistence rules in the 6 GHz Automated Frequency Coordination model, on what a Wi-Fi 7 preamble looks like with puncturing, on how MLO chooses which link carries which frame, and on how Target Wake Time interacts with battery-powered clients. Candidates who can map standards features to product trade-offs — battery, range, throughput, latency, certification cost — stand out.
What do new graduates typically miss about Wi-Fi standards beyond peak data rate?
The advertised peak rate is a corner-case number: max channel width, max spatial streams, max modulation, line-of-sight, perfect SNR. Real-world rates are 30 to 60 percent of peak in good conditions and much lower indoors with interference and walls. New graduates also miss that 6 GHz operation requires Wi-Fi 6E or Wi-Fi 7 hardware on both ends, that 802.11be in the United States caps EIRP and constrains outdoor use, and that MLO requires multiple radios per device which has cost, power, and antenna placement implications.
How does the 6 GHz band change Wi-Fi performance compared to 2.4 and 5 GHz?
The 6 GHz band gives Wi-Fi up to 1.2 GHz of contiguous, lightly-used spectrum versus around 70 MHz in 2.4 GHz and 500 MHz in 5 GHz. This enables 160 MHz and 320 MHz channels without having to share the channel with legacy 802.11n or 802.11ac devices, so throughput and latency improve in dense deployments. The trade-offs are shorter range due to higher free-space path loss, more regulatory complexity (AFC for standard-power outdoor operation in the United States), and the need for new client hardware. The 6 GHz band is now the engineering battleground where Wi-Fi 7 and Wi-Fi 8 do their best work.
What does the IEEE 802.11 amendment letter system mean, and how does it map to Wi-Fi marketing names?
IEEE 802.11 amendments use single or double lowercase letters assigned by the IEEE 802.11 working group in the order projects are authorized — not in alphabetical or chronological order of release. The mapping for the major Wi-Fi generations is: 802.11n is Wi-Fi 4, 802.11ac is Wi-Fi 5, 802.11ax is Wi-Fi 6 (and Wi-Fi 6E in 6 GHz), 802.11be is Wi-Fi 7, and 802.11bn is Wi-Fi 8. The IEEE name is the technical, search-stable reference; the Wi-Fi Alliance marketing name is what consumers see. In wireless engineering interviews, candidates who can switch between both naming systems and explain which amendment introduced a given feature stand out from candidates who only know the marketing labels.
Which Wi-Fi standards features are PHY versus MAC, and why does that distinction matter in interviews?
PHY (physical layer) features include OFDM, MIMO, channel widths, modulation order (256-QAM, 1024-QAM, 4096-QAM), OFDMA resource units, preamble puncturing, and the new UHR-LTF training fields in 802.11bn. MAC (medium access control) features include Target Wake Time, BSS coloring, EDCA traffic prioritization, TXOP rules, Multi-Link Operation, Enhanced Multi-Link Single Radio (EMLSR), Non-Primary Channel Access (NPCA), and Dynamic Sensitivity Control. The distinction matters because PHY changes typically require new radio silicon, while MAC changes can sometimes ship as firmware updates — and because interview questions about coexistence, scheduling, and roaming live entirely at the MAC layer regardless of what the PHY can do.

Related topics

Essential AI-Native Skills for IEEE 802.11 Wi-Fi Generations Explained for Engineers (Wi-Fi 4 to Wi-Fi 8)

Modern engineering work increasingly uses AI tools for design and code review, debugging, documentation, test and testbench generation, and workflow automation. The goal is not to let AI replace engineering judgment — it is to move faster while keeping verification discipline.

  • Use AI to explain unfamiliar code, logs, waveforms, datasheets, or test failures.
  • Break large problems into small, reviewable steps you can verify independently.
  • Ask AI for hypotheses, then validate them against tests, measurements, simulations, or lab data.
  • Version-control your analysis scripts, testbenches, and configs — keep changes small and reviewable.
  • Document your assumptions, design tradeoffs, and debugging decisions.
  • Verify AI output before trusting it: run the checks that fit the domain — unit tests, linters, simulations, or bench/lab measurements.
  • Review AI output for correctness, edge cases, and real-world consequences.

Next up: Wi-Fi standards practice

The adaptive practice engine is live now for core wireless and RF topics. Wi-Fi-standards-specific questions — 802.11ax / be / bn, OFDMA, MU-MIMO, MLO, 6 GHz, and real-world deployment trade-offs — are rolling out next. Join the early-access list to get them first.

One email when this topic launches. Nothing else. Unsubscribe in one click.