How a Photo Message Travels in WhatsApp or Messenger: Upload, Encryption, Delivery

Quick Overview

A Meta product manager technical question asking candidates to trace a photo sent in WhatsApp or Messenger from the sender's phone, through the servers, to the recipient. It tests understanding of compression, upload, encryption, delivery status, offline handling and the user-facing trade-offs behind each step.

How a Photo Message Travels in WhatsApp or Messenger: Upload, Encryption, Delivery

Company: Meta

Role: Product Manager

Category: System Design

Difficulty: medium

Interview Round: Other

In a product manager interview at Meta, the interviewer tests your technical fluency with a familiar scenario: someone shares a picture in a chat app such as WhatsApp or Messenger. Explain what happens from the moment they tap send until the photo appears on the other person's phone. Cover what the sender's device does, what the servers in between do, and what the recipient's device does, and point out where the design choices in that flow shape what users experience. ```hint Size changes the path A photo is far larger than a text message. Think about how that difference affects the route the image takes, and what the recipient's phone could show before the full picture has arrived. ``` ### Clarifying Questions - Should I assume the chat is end-to-end encrypted, as WhatsApp chats are by default, and explain what that prevents the servers from doing with the image? - Is the recipient online right now, or should I also cover a phone that is offline or a recipient with several linked devices? - Is this a one-to-one chat or a group chat? - How deep should I go: the steps users can see, or also the network and server components behind them? ### What a Strong Answer Covers - A correct end-to-end sequence across the sender's device, the servers and the recipient's device, including the offline recipient - How the image is prepared on the phone (compression, preview) and the quality-versus-speed-and-data trade-off behind it - Where encryption applies and what it rules out on the server side - The status signals the sender sees (pending, sent, delivered, read) and the system event behind each - Handling of poor networks and retries, and the metrics a PM would watch for photo sending ### Follow-up Questions - How does the flow change when the photo goes to a large group instead of one person? - Users on slow, expensive mobile data complain that photos take too long and eat their data allowance. What would you change? - If the servers cannot see the image because of end-to-end encryption, how can the app still respond to abusive images?

Overview: A Meta product manager technical question asking candidates to trace a photo sent in WhatsApp or Messenger from the sender's phone, through the servers, to the recipient. It tests understanding of compression, upload, encryption, delivery status, offline handling and the user-facing trade-offs behind each step.

Meta logo
Meta
Aug 23, 2026
mediumProduct ManagerOtherSystem Design
0
0

In a product manager interview at Meta, the interviewer tests your technical fluency with a familiar scenario: someone shares a picture in a chat app such as WhatsApp or Messenger. Explain what happens from the moment they tap send until the photo appears on the other person's phone.

Cover what the sender's device does, what the servers in between do, and what the recipient's device does, and point out where the design choices in that flow shape what users experience.

Clarifying Questions Guidance

  • Should I assume the chat is end-to-end encrypted, as WhatsApp chats are by default, and explain what that prevents the servers from doing with the image?
  • Is the recipient online right now, or should I also cover a phone that is offline or a recipient with several linked devices?
  • Is this a one-to-one chat or a group chat?
  • How deep should I go: the steps users can see, or also the network and server components behind them?

What a Strong Answer Covers Guidance

  • A correct end-to-end sequence across the sender's device, the servers and the recipient's device, including the offline recipient
  • How the image is prepared on the phone (compression, preview) and the quality-versus-speed-and-data trade-off behind it
  • Where encryption applies and what it rules out on the server side
  • The status signals the sender sees (pending, sent, delivered, read) and the system event behind each
  • Handling of poor networks and retries, and the metrics a PM would watch for photo sending

Follow-up Questions Guidance

  • How does the flow change when the photo goes to a large group instead of one person?
  • Users on slow, expensive mobile data complain that photos take too long and eat their data allowance. What would you change?
  • If the servers cannot see the image because of end-to-end encryption, how can the app still respond to abusive images?