AWS product design: a managed service for extracting data from paper receipts

Quick Overview

A product design question for an AWS product manager role: propose a new service that converts paper receipts into structured digital records. It tests choosing the right business customer, defining capture, extraction and review capabilities, prioritizing a first release, and measuring accuracy and adoption.

AWS product design: a managed service for extracting data from paper receipts

Company: Amazon

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Amazon Web Services. Propose a new service in the AWS portfolio whose purpose is converting paper receipts into digital records that customers can store and put to use. Explain which customers you would target, which problems the service solves for them, what the service does and how customers would use it, and how you would measure its success. ```hint Who is the AWS customer here? AWS mostly sells to builders and businesses rather than to the person holding the receipt. Decide whose workflow the receipt data feeds and what happens to it after capture before you list features. ``` ### Clarifying Questions - Is the target customer a business that handles receipts at scale, such as an expense-management or accounting software provider or a company's finance team, or an individual consumer? - Should the service be a developer building block called through an API, a finished application that business users operate, or both? - How do receipts arrive: phone photos, scanned batches, emailed images, or a mix? - Which countries, languages and currencies must the first version support? ### What a Strong Answer Covers - A clear choice of target customer and the job the digitized receipt data does for them afterward. - Pain points of today's receipt handling, such as manual data entry, lost or faded paper, poor photos and record-keeping obligations. - What the service does end to end, the form it takes (API, console, SDK) and how it relates to existing AWS building blocks. - A prioritized first version and a roadmap beyond it. - Success metrics that include extraction accuracy and customer adoption, and risks such as financial data privacy, poor image quality and pricing. ### Follow-up Questions - Accuracy is high on clean printed receipts but poor on faded, crumpled or handwritten ones. What do you launch with, and how do you set customer expectations? - How would you price the service, and why would a customer choose it over building on a general text-extraction API? - A large expense-software company wants to adopt the service for millions of its users. What would it need that a small developer would not?

Overview: A product design question for an AWS product manager role: propose a new service that converts paper receipts into structured digital records. It tests choosing the right business customer, defining capture, extraction and review capabilities, prioritizing a first release, and measuring accuracy and adoption.

Amazon logo
Amazon
Oct 23, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Amazon Web Services. Propose a new service in the AWS portfolio whose purpose is converting paper receipts into digital records that customers can store and put to use. Explain which customers you would target, which problems the service solves for them, what the service does and how customers would use it, and how you would measure its success.

Clarifying Questions Guidance

  • Is the target customer a business that handles receipts at scale, such as an expense-management or accounting software provider or a company's finance team, or an individual consumer?
  • Should the service be a developer building block called through an API, a finished application that business users operate, or both?
  • How do receipts arrive: phone photos, scanned batches, emailed images, or a mix?
  • Which countries, languages and currencies must the first version support?

What a Strong Answer Covers Guidance

  • A clear choice of target customer and the job the digitized receipt data does for them afterward.
  • Pain points of today's receipt handling, such as manual data entry, lost or faded paper, poor photos and record-keeping obligations.
  • What the service does end to end, the form it takes (API, console, SDK) and how it relates to existing AWS building blocks.
  • A prioritized first version and a roadmap beyond it.
  • Success metrics that include extraction accuracy and customer adoption, and risks such as financial data privacy, poor image quality and pricing.

Follow-up Questions Guidance

  • Accuracy is high on clean printed receipts but poor on faded, crumpled or handwritten ones. What do you launch with, and how do you set customer expectations?
  • How would you price the service, and why would a customer choose it over building on a general text-extraction API?
  • A large expense-software company wants to adopt the service for millions of its users. What would it need that a small developer would not?