Skill Profile

HTTP/2 & HTTP/3 QUIC

HTTP/2: multiplexing, server push; HTTP/3: QUIC, 0-RTT, connection migration

Networking & Telecom Network Protocols

Roles

3

where this skill appears

Levels

5

structured growth path

Mandatory requirements

6

the other 9 optional

Domain

Networking & Telecom

Group

Network Protocols

Last updated

3/17/2026

How to Use

Choose your current level and compare expectations. The items below show what to cover to advance to the next level.

What is Expected at Each Level

The table shows how skill depth grows from Junior to Principal. Click a row to see details.

Role Required Description
IoT Engineer Understands differences between HTTP/1.1, HTTP/2, HTTP/3 for IoT. Uses HTTP/2 for REST API interaction between IoT gateway and cloud services.
Network Engineer Knows basic HTTP/2 and HTTP/3 concepts for network engineering and can apply them in typical tasks. Uses standard tools and follows established team practices. Understands when and why this approach is used.
Telecom Developer Understands the fundamentals of HTTP/2 & HTTP/3 QUIC. Applies basic practices in daily work. Follows recommendations from the team and documentation.
Role Required Description
IoT Engineer Applies HTTP/2 server push and multiplexing for IoT gateways. Optimizes HTTP communication for constrained networks. Configures gRPC over HTTP/2 for device management.
Network Engineer Confidently applies HTTP/2 and HTTP/3 for network engineering in non-standard tasks. Independently selects the optimal approach and tools. Analyzes trade-offs and proposes improvements to existing solutions.
Telecom Developer Independently applies HTTP/2 & HTTP/3 QUIC in practice. Understands trade-offs of different approaches. Solves typical tasks independently.
Role Required Description
IoT Engineer Required Designs HTTP strategy for IoT platform: HTTP/2 for gateways, HTTP/3 QUIC for mobile networks. Evaluates protocol overhead vs reliability trade-offs.
Network Engineer Expertly applies HTTP/2 and HTTP/3 for network engineering to design complex systems. Optimizes existing solutions and prevents architectural mistakes. Conducts code reviews and trains colleagues on best practices.
Telecom Developer Required Has deep expertise in HTTP/2 & HTTP/3 QUIC. Designs solutions for production systems. Optimizes and scales. Mentors the team.
Role Required Description
IoT Engineer Required Defines HTTP standards for IoT platform. Establishes guidelines for choosing HTTP/2 vs gRPC vs MQTT for various IoT scenarios.
Network Engineer Establishes HTTP/2 and HTTP/3 usage standards for the network engineering team and makes architectural decisions. Defines the technical roadmap incorporating this skill. Mentors senior engineers and influences practices of adjacent teams.
Telecom Developer Required Defines HTTP/2 and HTTP/3 QUIC strategy at the team/product level. Establishes standards and best practices. Conducts reviews.
Role Required Description
IoT Engineer Required Defines enterprise HTTP strategy for IoT. Evaluates QUIC adoption for IoT in the context of enterprise networks and proxy infrastructure.
Network Engineer Shapes HTTP/2 and HTTP/3 strategy for network engineering at the organizational level. Defines best practices and influences technology choices beyond their own team. Is a recognized expert in this area.
Telecom Developer Required Defines HTTP/2 and HTTP/3 QUIC strategy at the organizational level. Establishes enterprise approaches. Mentors leads and architects.

Community

👁 Watch ✏️ Suggest Change Sign in to suggest changes
📋 Proposals
No proposals yet for HTTP/2 & HTTP/3 QUIC
Loading comments...