Design a PacketAssembler API that accepts streaming fragments and emits a completed payload once enough bytes have been received. Example interaction: packetit(0x04, 'a', 'b', 'c') -> no output (header 4 indicates total size; only 3 bytes arrived); packetit('d') -> 'abcd' (completes the prior packet). Specify the class/method signatures, state management (buffering and expected size), behavior for multiple consecutive packets, handling of invalid headers or oversized input, when/if state resets after emission, and thread-safety considerations. Provide tests and analyze time and space complexity.

This question evaluates API design, stream-oriented buffer management, stateful packet assembly, input validation, concurrency control, testing strategy, and time/space complexity reasoning.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Technical Screen rounds at Bloomberg.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Bloomberg during technical interviews.

Design a packet reassembler API | Bloomberg Interview Question

Design a PacketAssembler API for Streaming Fragments

Context and Assumptions

You are building a small component that assembles packets from a byte stream.
Each packet begins with a 1-byte header that encodes the payload length N (0–255). The header byte is not part of the payload.
The stream may arrive fragmented arbitrarily; a single call may contain parts of a packet or multiple full packets back-to-back.

Example interaction:

packetit(0x04, 'a', 'b', 'c') -> no output (header 4 indicates a 4-byte payload; only 3 bytes arrived)
packetit('d') -> 'abcd' (completes the prior packet)

Requirements

Specify the class and method signatures of a PacketAssembler API.
Describe state management: buffering, expected size, and how fragments are handled.
Behavior when receiving multiple consecutive packets within one or many calls.
Handling of invalid headers and oversized input (e.g., header value exceeds a configured maximum).
Define when/how state resets after emission and on errors.
Thread-safety considerations and options.
Provide tests (unit-style examples) that exercise common and edge cases.
Analyze time and space complexity.

Context and Assumptions

You are building a small component that assembles packets from a byte stream.

Each packet begins with a 1-byte header that encodes the payload length N (0–255). The header byte is not part of the payload.

The stream may arrive fragmented arbitrarily; a single call may contain parts of a packet or multiple full packets back-to-back.

Example interaction:

packetit(0x04, 'a', 'b', 'c') -> no output (header 4 indicates a 4-byte payload; only 3 bytes arrived)

packetit('d') -> 'abcd' (completes the prior packet)

Requirements

Specify the class and method signatures of a PacketAssembler API.

Describe state management: buffering, expected size, and how fragments are handled.

Behavior when receiving multiple consecutive packets within one or many calls.

Handling of invalid headers and oversized input (e.g., header value exceeds a configured maximum).

Define when/how state resets after emission and on errors.

Thread-safety considerations and options.

Provide tests (unit-style examples) that exercise common and edge cases.

Analyze time and space complexity.

Design a packet reassembler API

Quick Overview

Design a packet reassembler API

Design a PacketAssembler API for Streaming Fragments

Context and Assumptions

Requirements

Submit Your Answer to Earn 20XP

Design a packet reassembler API

Quick Overview

Design a packet reassembler API

Design a PacketAssembler API for Streaming Fragments

Context and Assumptions

Requirements

Submit Your Answer to Earn 20XP