Bluetooth Versions: Classic vs BLE, 5.x & LE Audio Interview Prep

Bluetooth versions and BLE generations compared for interview prep: Classic BR/EDR vs Low Energy, what 4.0 / 4.2 / 5.0 / 5.1 / 5.2 / 5.4 / 6.0 each changed, PHYs, LE Audio, and Channel Sounding.

Quick answer

Bluetooth is a family of short-range wireless standards maintained by the Bluetooth SIG, and "Bluetooth versions" usually means the Core Specification releases engineers reference in interviews.

Interviewers ask about Bluetooth versions to check whether you understand the Classic-versus-LE split and can place features in the right release.

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.

Key points

  • Bluetooth splits into two distinct PHY and link-layer systems on the same 2.4 GHz band: Classic (BR/EDR), and Low Energy (BLE), which arrived in Bluetooth 4.0 (2010). They do not interoperate directly; a "dual-mode" device implements both inside one controller sharing a single RF front-end (distinct PHY and link-layer systems, not two physical radios).
  • BLE PHYs scale by generation: LE 1M (4.0), then LE 2M and LE Coded long-range (both 5.0). Classic tops out at 3 Mbps via EDR (2.0).
  • The security/robustness arc: Secure Simple Pairing (2.1), LE Secure Connections + Data Length Extension (4.2), Encrypted Advertising Data (5.4).
  • The feature arc on LE: Advertising Extensions (5.0), Direction Finding AoA/AoD (5.1), the enabling core features for LE Audio (LE Isochronous Channels, EATT) in 5.2 — with the LC3 codec and LE Audio profiles published separately (2020+), so 5.2 enables LE Audio rather than containing all of it — plus Auracast broadcast, Periodic Advertising with Responses for Electronic Shelf Labels (5.4), Channel Sounding for secure ranging (6.0).
  • Bluetooth Mesh (2017) is a separate spec layered on BLE — not a numbered Core Specification version.

What it is

Bluetooth is a family of short-range wireless standards maintained by the Bluetooth SIG, and "Bluetooth versions" usually means the Core Specification releases engineers reference in interviews. The version history has one decisive branch point: Bluetooth 4.0 (2010) added Bluetooth Low Energy (BLE), so from 4.0 onward the standard carries two separate PHY and link-layer systems — Classic BR/EDR and Low Energy — that share the 2.4 GHz ISM band but use different PHYs, channel plans, and connection models. A dual-mode device implements both inside one controller sharing a single RF front-end; they are distinct PHY and link-layer systems, not two physical radios. Bluetooth Classic (BR/EDR) is the older path: 79 channels of 1 MHz with adaptive frequency hopping, up to 3 Mbps with Enhanced Data Rate, built for sustained links like A2DP audio. Bluetooth Low Energy is the modern, battery-first path: 40 channels of 2 MHz, an advertising-and-connection model designed to sleep aggressively, and a GATT/ATT attribute data model used by sensors, wearables, beacons, and IoT endpoints. Each later version mostly extended BLE. 4.2 hardened security and let packets carry more data. 5.0 added the 2M and Coded PHYs and bigger advertising payloads. 5.1 added direction finding for positioning, using antenna arrays much like /topics/beamforming. 5.2 introduced LE Audio (ISO channels, the LC3 codec, Auracast broadcast audio). 5.4 added Periodic Advertising with Responses and encrypted advertising. 6.0 added Channel Sounding for secure, high-accuracy ranging. A strong answer does not just recite numbers — it explains which layer each version touched and why.

Why interviewers ask

Interviewers ask about Bluetooth versions to check whether you understand the Classic-versus-LE split and can place features in the right release. Candidates who say "Bluetooth 5 made audio better" or "BLE is just slower Bluetooth" reveal that they have not worked with the stack. The precise story — Low Energy in 4.0, the 2M and Coded PHYs in 5.0, LE Audio in 5.2, Channel Sounding in 6.0 — signals real exposure. The question also tests systems thinking that matters for wireless and connectivity roles. Why does BLE use 40 channels of 2 MHz instead of Classic's 79 of 1 MHz? Why does the Coded PHY trade data rate for range, and when would you pick it? Why did audio historically live on Classic A2DP, and what does moving it to LE Audio change for power and multi-stream use cases? How does Bluetooth coexist with Wi-Fi (802.11b/g/n/ax in 2.4 GHz) when both share the band? Those follow-ups separate someone who memorized a feature list from someone who can reason about link budget, power, and coexistence trade-offs in a real product.

Common mistakes

The most common mistake is treating BLE as "a slower Bluetooth Classic." They are different radio systems with distinct PHY and link layers, channel plans, and use cases, typically implemented in one dual-mode controller that shares a single RF front-end — not necessarily two physical radios; one is not a degraded version of the other. A second mistake is assuming a higher version number automatically means faster or longer-range for every device — most version features are optional, and a 5.0 device that does not implement the Coded PHY gets no range benefit. A third mistake is mixing up what each release added. Saying direction finding came with LE Audio, or that Channel Sounding is the same as 5.1 direction finding, loses credibility. Direction finding (5.1) uses Angle of Arrival / Angle of Departure from an antenna array; Channel Sounding (6.0) uses phase-based ranging and round-trip timing for distance — related goals, different mechanisms. A fourth mistake is calling Bluetooth Mesh a Core version. Mesh is a separate specification layered on the BLE advertising primitives. Finally, candidates often forget that audio is mid-migration: Classic A2DP still dominates, while LE Audio (5.2+) with LC3 and Auracast is the forward path — so "Bluetooth audio" is no longer a single answer.

Bluetooth versions compared: radio added, PHY/data rate, headline feature, and design priority

Version (year)Radio focusTop PHY / data rateHeadline featureWhy it mattered
1.1 / 1.2 (2002–03)Classic BR1 Mbps (BR)Adaptive frequency hopping (1.2)First robust, mainstream Bluetooth
2.0 + EDR (2004)Classic BR/EDR3 Mbps (EDR)Enhanced Data RateHigher throughput for audio/data
2.1 + EDR (2007)Classic BR/EDR3 MbpsSecure Simple PairingEasier, stronger pairing
3.0 + HS (2009)Classic + 802.11 AMP~24 Mbps via 802.11High Speed (alternate MAC/PHY)Bulk transfer offload (rarely used)
4.0 (2010)Adds Low Energy (BLE)LE 1M (1 Mbps)Bluetooth Low Energy / GATTThe branch point — battery-first IoT
4.2 (2014)BLELE 1MLE Secure Connections + Data Length ExtensionStronger security, bigger packets
5.0 (2016)BLELE 2M; LE Coded (long range)2M + Coded PHYs, advertising extensions2x speed / 4x range / 8x advertising
5.1 (2019)BLELE 2MDirection Finding (AoA / AoD)Indoor positioning, item finding
5.2 (2020)BLELE 2MEnabling core for LE Audio: LE Isochronous Channels, EATTAdded the enabling core features (LE Isochronous Channels, EATT); the LC3 codec and LE Audio profiles were published separately (2020+), so 5.2 enables LE Audio rather than containing all of it; audio can move to LE (A2DP still dominates shipping products); Auracast broadcast
5.3 (2021)BLELE 2MConnection subrating, periodic adv. enhancementsLower latency / power tuning
5.4 (2023)BLELE 2MPeriodic Adv. with Responses (PAwR), Encrypted Adv. DataElectronic Shelf Labels at scale
6.0 (2024)BLELE 2MChannel Sounding (secure ranging)More accurate, harder-to-spoof distance than RSSI

Frequently asked questions

What is the difference between Bluetooth Classic and Bluetooth Low Energy?
Bluetooth Classic (BR/EDR — Basic Rate / Enhanced Data Rate) and Bluetooth Low Energy (BLE, introduced in Bluetooth 4.0) are two distinct PHY and link-layer systems that share the 2.4 GHz band and the Bluetooth brand but are not interchangeable. A dual-mode device implements both inside one controller sharing a single RF front-end — they are distinct PHY and link-layer systems, not two physical radios. Classic uses 79 channels of 1 MHz and is built for sustained, higher-throughput links such as A2DP audio streaming and serial-style connections. BLE uses 40 channels of 2 MHz, a connection model optimized for short bursts and long sleep, and a GATT/ATT data model — it is what you use for sensors, wearables, beacons, and anything battery-constrained. A device can support one, the other, or both (a "dual-mode" device); the radios do not talk to each other directly.
Which Bluetooth version introduced Low Energy (BLE)?
Bluetooth 4.0 (2010) introduced Bluetooth Low Energy, originally marketed as Bluetooth Smart. This is the most important branch point in the version history: before 4.0 there was only Classic BR/EDR; from 4.0 onward the spec carries two separate PHY and link-layer systems (a dual-mode device implements both inside one controller sharing a single RF front-end, not two physical radios). For interviews, knowing that BLE arrived in 4.0 — and that 4.2 added LE Secure Connections and Data Length Extension — is usually enough to anchor deeper questions.
What did Bluetooth 5.0 actually change?
Bluetooth 5.0 (2016) was a BLE-focused release. It added the LE 2M PHY (double the symbol rate for higher throughput), the LE Coded PHY (forward-error-coded long-range mode, S=2 and S=8), and Advertising Extensions (much larger advertising payloads carried on data channels). The marketing shorthand "2x speed, 4x range, 8x advertising capacity" maps directly to those three features. None of it changed Bluetooth Classic.
What is LE Audio and which version introduced it?
LE Audio is the audio architecture built on Bluetooth Low Energy. Bluetooth 5.2 (2020) added the enabling core features (LE Isochronous Channels, EATT); the LC3 codec and the LE Audio profiles were published separately (2020+), so 5.2 enables LE Audio rather than containing all of it. The building blocks are LE Isochronous Channels (ISO) for time-synchronized streams, the LC3 codec (better quality at lower bitrate than SBC), and Enhanced ATT (EATT). LE Audio also enables Auracast broadcast audio — many receivers within radio coverage (broadcast, not paired one-to-one). As a spec capability it is the path for Bluetooth audio to move off Classic A2DP onto the LE link, but Classic A2DP still dominates in shipping products today and real LE Audio adoption depends on source, sink, OS, and codec support.
What is Bluetooth Channel Sounding and which version added it?
Bluetooth Channel Sounding was introduced in Bluetooth 6.0 (2024). It measures distance between two devices using phase-based ranging (PBR) and round-trip timing (RTT), which is more accurate and harder to spoof than RSSI-based estimates, though the accuracy achieved depends on implementation, calibration, and antenna design. It targets use cases such as secure keyless entry, device finding, and proximity unlocking — improving on earlier RSSI-based distance estimates that were easy to spoof and imprecise.
How do Bluetooth version numbers map to features I should know for interviews?
The jumps worth memorizing: 2.1 added Secure Simple Pairing; 4.0 added Low Energy; 4.2 added LE Secure Connections and Data Length Extension; 5.0 added the 2M and Coded PHYs plus advertising extensions; 5.1 added direction finding (Angle of Arrival / Angle of Departure); 5.2 added the enabling core features for LE Audio (LE Isochronous Channels, EATT), with the LC3 codec and the LE Audio profiles published separately (2020+) so 5.2 enables LE Audio rather than containing all of it; 5.4 added Periodic Advertising with Responses (used by Electronic Shelf Labels) and Encrypted Advertising Data; 6.0 added Channel Sounding. As with Wi-Fi generations (Wi-Fi 6 / 802.11ax, Wi-Fi 7 / 802.11be), the point is not the number — it is what each version changed in the PHY, the link layer, or the host.
Is Bluetooth Mesh a Bluetooth version?
No. Bluetooth Mesh (2017) is a separate specification that runs on top of the Bluetooth Low Energy radio (4.0 and later) using the advertising and scanning primitives — it is not a numbered Core Specification version. It adds a many-to-many, managed-flooding network for building automation and lighting. Confusing Mesh with a Core version is a common interview slip.
What does a strong versus weak answer about Bluetooth Classic vs BLE sound like?
A weak answer flattens the two into one thing — "BLE is just slower Bluetooth" or "Bluetooth 5 made audio better" — which signals the candidate never worked with the stack. A strong answer names Classic and BLE as distinct PHY and link-layer systems that share one 2.4 GHz dual-mode controller, then picks the right one per use case: BLE for low-power sensors and beacons, Classic A2DP for legacy audio streaming, and LE Audio for new multi-stream or broadcast designs. It also reasons about the trade-offs — power budget, the channel plans (40 channels of 2 MHz for BLE versus 79 channels of 1 MHz for Classic), and the way the Coded PHY buys range at the cost of data rate.
How should I prepare for a Bluetooth or BLE connectivity interview?
Drill the concrete flows rather than memorizing a feature list. Sketch the GATT, advertising, and connection state flow end to end. Compare the LE 1M, 2M, and Coded PHYs and explain when to pick each. Walk through a pairing and bonding sequence with LE Secure Connections. Reason about a Wi-Fi (802.11) coexistence or desense problem in the shared 2.4 GHz band. Finally, map three or four version-to-feature jumps cleanly: LE in 4.0, the new PHYs in 5.0, LE Audio in 5.2, and Channel Sounding in 6.0.

Related topics

Essential AI-Native Skills for Bluetooth Versions: Classic vs BLE, 5.x & LE Audio

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.

Bluetooth Versions: Classic vs BLE, 5.x & LE Audio — coming to the question bank

The adaptive practice engine is already live for core wireless, RF, and ML systems. Bluetooth Versions: Classic vs BLE, 5.x & LE Audio isn't covered in the question bank yet — get notified when it's added.

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