Design an Interplanetary Network Linking Mars to Earth Under Light-Speed Delay

Quick Overview

A technical product interview prompt about designing a communication system between Earth and Mars. It tests whether a candidate can turn physical limits such as light delay, signal loss and solar blackouts into requirements, an end-to-end architecture, a delay-aware user experience and a phased plan with metrics.

Design an Interplanetary Network Linking Mars to Earth Under Light-Speed Delay

Company: Atlassian

Role: Product Manager

Category: System Design

Difficulty: medium

Interview Round: Other

You are asked to design a communication system that connects Earth and Mars, so that messages, data and commands can travel between the two planets in both directions. Explain whom the system serves and what it must carry, the architecture you would propose, how people would actually use it, and how you would judge whether it works. ```hint Let physics set the requirements Before choosing any hardware, estimate what the distance between the planets does to delay and to signal strength, and check whether a clear line between them is always available. Then sort those limits into ones engineering can improve and ones the product has to be designed around. ``` ### Clarifying Questions - Whom does the system serve first: robotic rovers and orbiters, a small crewed mission, or a future settlement whose residents expect everyday internet services? - Which traffic matters most when capacity runs short: commands and spacecraft health data, large science datasets, or personal voice, video and messages? - Should the design build on the deep-space antennas and Mars orbiters already in service, or start from a clean sheet? - Can Mars ever be out of contact for an extended period, or must it be reachable all year? ### What a Strong Answer Covers - Requirements derived from the users and traffic types, with an explicit priority order among commands, health data, science data and personal communication. - The physical limits quantified roughly: one-way light delay across the range of Earth–Mars distances, signal loss with distance, planetary rotation, and periods when the Sun blocks the path. - An end-to-end architecture spanning the Mars surface, Mars orbit, the interplanetary link and the Earth ground segment, with a networking approach that tolerates long delays and broken paths. - A user experience designed for delay rather than against it, plus metrics for delivered volume, availability and delivery time. - Trade-offs and phasing: radio versus laser links, relay count versus cost, command security, and a path from today's assets to a larger network. ### Follow-up Questions - An astronaut on Mars wants to video call family on Earth. What experience would you build, and how would you set expectations? - When Mars passes behind the Sun as seen from Earth, the direct link fails. Would you accept the outage or pay for a relay that routes around the Sun, and how would you decide? - If the budget allows one major upgrade in the next phase, would you fund laser links, more Mars relay orbiters or more antennas on Earth? What evidence would settle it?

Overview: A technical product interview prompt about designing a communication system between Earth and Mars. It tests whether a candidate can turn physical limits such as light delay, signal loss and solar blackouts into requirements, an end-to-end architecture, a delay-aware user experience and a phased plan with metrics.

Atlassian logo
Atlassian
Sep 5, 2024
mediumProduct ManagerOtherSystem Design
0
0

You are asked to design a communication system that connects Earth and Mars, so that messages, data and commands can travel between the two planets in both directions.

Explain whom the system serves and what it must carry, the architecture you would propose, how people would actually use it, and how you would judge whether it works.

Clarifying Questions Guidance

  • Whom does the system serve first: robotic rovers and orbiters, a small crewed mission, or a future settlement whose residents expect everyday internet services?
  • Which traffic matters most when capacity runs short: commands and spacecraft health data, large science datasets, or personal voice, video and messages?
  • Should the design build on the deep-space antennas and Mars orbiters already in service, or start from a clean sheet?
  • Can Mars ever be out of contact for an extended period, or must it be reachable all year?

What a Strong Answer Covers Guidance

  • Requirements derived from the users and traffic types, with an explicit priority order among commands, health data, science data and personal communication.
  • The physical limits quantified roughly: one-way light delay across the range of Earth–Mars distances, signal loss with distance, planetary rotation, and periods when the Sun blocks the path.
  • An end-to-end architecture spanning the Mars surface, Mars orbit, the interplanetary link and the Earth ground segment, with a networking approach that tolerates long delays and broken paths.
  • A user experience designed for delay rather than against it, plus metrics for delivered volume, availability and delivery time.
  • Trade-offs and phasing: radio versus laser links, relay count versus cost, command security, and a path from today's assets to a larger network.

Follow-up Questions Guidance

  • An astronaut on Mars wants to video call family on Earth. What experience would you build, and how would you set expectations?
  • When Mars passes behind the Sun as seen from Earth, the direct link fails. Would you accept the outage or pay for a relay that routes around the Sun, and how would you decide?
  • If the budget allows one major upgrade in the next phase, would you fund laser links, more Mars relay orbiters or more antennas on Earth? What evidence would settle it?