Amazon Working Backwards and the PR-FAQ

Working Backwards is Amazon’s discipline of writing the customer outcome before writing the code. You draft a one-page press release and a two-part FAQ as if the product already launched, then use that artifact to decide whether to build at all. In an interview, most candidates treat it as a template exercise. Interviewers treat it as a forcing function for honest business thinking.

What the PR-FAQ actually contains

The document has two distinct halves, and most candidates conflate them.

The press release (one page, hard limit). Written as if the product launched today, answering five questions: Who is the customer? What problem? What solution from their perspective? Would they actually change behavior? Is the TAM sufficient? It also functions as an urgency test. A weak press release reads like a vitamin ad: “SmartNotes helps teams stay organized and makes collaboration easier.” A strong one names specific pain and cost: “Engineers at fast-growing startups lose 90 minutes per day reconstructing context from scattered Slack threads before they can make a decision.” If yours sounds like the first version, that is the signal before any engineering time is spent that the idea is weak. Amazon calls this the “vitamin tell.”

The External FAQ. Customer-facing questions: How does it work? What does it cost? What happens if something goes wrong? The shorter half, and the less important one in a review meeting.

The Internal FAQ. This is what senior leaders interrogate, and where most interview candidates have nothing to say. Questions that belong here: What is the realistic TAM and how did you size it? What is cost-to-serve per unit at scale? What is the competitive moat and how long does it hold? What regulatory risk exists? What could kill this? What would have to be true for customers to change behavior? If you cannot answer these with numbers and named assumptions, the document fails regardless of how crisp the press release reads.

Amazon expects 10 or more drafts and five or more senior leader review meetings before a PR-FAQ gets resource approval. The Kindle PR-FAQ went through 50 or more drafts; AWS S3 and EC2 took over a year of iteration (per Colin Bryar and Bill Carr’s “Working Backwards”). The bar is meaningfully better, cheaper, or faster. Bryar describes the review as “truth-seeking, not selling.”

What interviewers actually grade

The rubric is not whether you know the format. It is whether you can run an honest Internal FAQ. Interviewers check for four Leadership Principles through this exercise: Customer Obsession (does the press release solve a real problem?), Think Big (is the TAM framing ambitious?), Invent and Simplify (does the solution earn its complexity?), and Dive Deep (does the Internal FAQ show real rigor on cost, risk, and behavior change?).

The failure mode is treating the framework as structure rather than substance. Listing the paragraph template and name-dropping Customer Obsession answers the surface question and misses the actual one.

Using it in an interview

You do not need to literally write a press release. Demonstrate the same logic: name the customer precisely, state the problem with specificity, describe the solution from their perspective, then run through the internal questions that would determine whether to proceed. A strong framing: “Here’s the press release I’d want to write for this, and here are the three Internal FAQ questions that would decide whether we actually build it.”

At non-Amazon companies (Stripe, Google, Meta), interviewers may not know the format. Do not lead with the name. Run the logic: customer, problem, viability, cost-to-serve, risk. The Amazon company page covers how it fits their full loop. This pairs directly with strategy questions like entering a new market and the customer-first thinking the product sense six-step applies to design problems.

The 2026 reframe

When feasibility is nearly free, the press release half becomes almost trivially easy to write. AI can generate a compelling customer narrative in seconds. The signal interviewers look for has shifted almost entirely to the Internal FAQ.

At AI-native companies, the Internal FAQ must address questions the original format did not anticipate: What is cost-per-query at scale? What is the eval strategy? What happens when the model is wrong? What is the hallucination exposure? These are viability questions, not feasibility questions. The “vitamin tell” is sharper now: a press release for an AI feature that reads as nice-to-have (“helps you draft faster”) fails the urgency test just as a non-AI one would.

The PR-FAQ glossary entry covers terminology; this page covers the interview application and the grading criteria that most resources omit.