PR/FAQ: Amazon's product definition document, explained

The PR/FAQ is Amazon’s forcing function for honest product thinking. You write a press release and a two-part FAQ as if the product has already launched, then use that document to decide whether to build it at all. Most guides treat it as a template. Amazon treats it as a truth-seeking instrument, and the distinction is the entire point.

The two-part structure

The document has a hard limit of six pages total. It is divided into a press release (one page) and a FAQ section with two distinct parts: External FAQ (customer questions) and Internal FAQ (leadership and business questions). Most candidates know the first two and skip the third. The Internal FAQ is where the document’s actual work happens.

The press release: eight required components

The press release answers one question per section: would this customer change behavior for this product?

1. Heading. Product name only. No tagline.
2. Subheading. Target customer plus the specific benefit they receive. One sentence. If you cannot name the customer precisely, the document is not ready.
3. Summary paragraph. Launch context: what is available, where, and at what price. Written as if the product ships today.
4. Problem paragraph. The customer’s pain, in their voice, at specific cost. “Engineers lose 90 minutes per day reconstructing context before decisions” is a problem paragraph. “Teams struggle with information overload” is not.
5. Solution paragraph(s). What the product does from the customer’s perspective, not the company’s. Differentiation belongs here, stated as what customers experience, not as feature names.
6. Spokesperson quote. An Amazon executive’s quote on strategic significance. In practice, this tests whether leadership would actually say this publicly.
7. Customer testimonial quote. A specific, named customer type expressing the result in their words. Vague quotes (“it changed everything”) fail; named pain and named relief pass.
8. Call to action. Where to start, one sentence.

The weak version of every section has the same tell: it describes what the company can build rather than what the customer needs. The Fire Phone is the canonical case. Its PR/FAQ was organized around Amazon’s hardware capabilities (Firefly feature recognition, 3D display) rather than any problem customers were trying to solve. The product launched to a market that did not exist and was discontinued in under a year. The document shape was correct; the truth-seeking was absent.

The External FAQ

Customer-facing questions: How does it work? What does it cost? What if something goes wrong? This section is shorter and, in senior review meetings, receives the least scrutiny. It matters for launch readiness, not for resource approval.

The Internal FAQ: the load-bearing section

Leadership questions stress-test the business case before a dollar is spent. This is what senior leaders interrogate, and what most interview candidates skip entirely. A complete Internal FAQ covers:

• Market size and TAM. Not aspirational. Named segments, sizing method, and realistic penetration timeline. If the TAM requires capturing 1% of “the global productivity market,” it fails.
• Competitive advantage and switching costs. Why will customers switch from what they use today? Better, cheaper, or faster, and by how much, specifically.
• Financial projections. Revenue model, cost-to-serve at scale, payback period. Numbers with named assumptions, not ranges.
• Technical risks and constraints. What could prevent this from being built at acceptable cost or quality? This is where PMs who draft the Internal FAQ last reveal they are hiding uncertainty rather than surfacing it.
• Team and build requirements. What would need to be true organizationally to ship this?
• Success conditions. What metrics define success at six months, and what would cause you to kill it?

Early drafts of a PR/FAQ are intentionally incomplete. Gaps and unanswered questions in the Internal FAQ are the signal: they direct research across multiple iterations. Amazon expects 10 or more drafts before resource approval; the Kindle PR/FAQ went through more than 50.

How review meetings actually work

The document is circulated in advance. The meeting opens with 15 to 20 minutes of silent reading, during which attendees write inline comments. No one presents. After the reading period, 40 minutes of open discussion follow. The presenter’s job is to answer questions, not to pitch.

Reviewers evaluate across seven dimensions: (1) customer clarity, whether the target customer and problem are specific enough to be falsifiable; (2) problem definition, whether the problem is real and has economic weight; (3) solution-problem alignment, whether the product actually solves the stated problem; (4) behavior change likelihood, whether customers would actually switch given their current alternatives; (5) competitive advantages, whether the product is better, cheaper, or faster in a way that holds; (6) TAM sufficiency and payback period, whether the market is large enough to cover cost of build and generate sustainable profit; and (7) constraint identification, whether the team has honestly named what could prevent success.

A document that reads like a pitch deck fails on dimension (7) alone. The review process is designed to surface constraint identification, not to approve confident presentations.

PR/FAQ vs. PRD vs. one-pager

The PR/FAQ is written before engineering begins. It captures customer value and strategic direction, and is iterated across many drafts before a resource decision is made. A PRD follows resource approval and governs execution: it contains requirements, acceptance criteria, and technical constraints. A one-pager is an early-stage briefing, not a decision artifact. They serve different moments and conflating them signals unfamiliarity with how Amazon actually operates.

For products with multiple customer types, segment-specific versions of the press release can be written separately. For early-stage explorations, just the press release (without the FAQ) can be sufficient to pressure-test the core idea.

The Amazon writing assessment

For PM and TPM roles at Level 6 and above, a writing sample must be submitted 48 hours before the on-site loop. The document is a maximum of four pages, with two pages as the target. Interviewers in the loop will have read it before meeting you and may reference it directly. The evaluation focuses on clarity of thinking and structure, not writing style. A document that buries the problem in paragraph four, or that has an empty Internal FAQ, signals Level 5 thinking regardless of how polished the prose reads.

The 2026 reframe

In 2026, the press release paragraphs are no longer the hard part. AI has collapsed the cost of generating a compelling customer narrative. The document’s load-bearing work has shifted entirely to the Internal FAQ: specifically, the TAM question (is this a problem worth solving at scale?), the behavior-change question (will customers actually switch given what they already use?), and the constraint question (what will prevent this from succeeding?).

A PR/FAQ that breezes through viability and lingers on features is exactly backwards now. Feasibility is nearly free; viability is the hard problem. The solution paragraphs also face a higher bar: they need to describe not just a functional fix but a product that meets customers where they work, anticipates friction proactively, and earns the behavior change it requires. Write the Internal FAQ first, not last. The holes you find there will tell you whether the press release is worth finishing.

The working backwards framework page covers how this fits Amazon’s broader interview rubric. The TAM/SAM/SOM framework covers how to size the market question in the Internal FAQ without relying on aspirational totals.