Amazon's PM Written Assessment Scores You on Customer Obsession Before You Write a Word

Amazon's written assessment for PM candidates is not scored by a product manager. It's scored by a bar raiser, a trained evaluator whose explicit job is to measure candidates against Leadership Principles, not to evaluate product strategy. Most candidates sitting down with 24 hours and a blank document don't know that. They write the wrong thing, competently.

If you've just received the assessment link from your recruiter, the anxiety you're feeling about frameworks and prioritization logic is real but misdirected. The question in front of you isn't whether you can demonstrate product sense. It's whether your reasoning visibly starts from the customer before it moves anywhere else. Those are different documents, and you have a short window to write the right one.

For context on where this assessment sits within the full hiring process, our Amazon interview hub covers the broader loop structure. But if the assessment is in front of you right now, stay here.

What the Evaluator Is Actually Scoring

Amazon publicly states that all hiring decisions are evaluated against its 16 Leadership Principles. That applies to written assessments as much as it applies to behavioral interviews. The bar raiser reviewing your document has a rubric, and that rubric is organized around LP alignment, not product quality. This is documented: Amazon's Leadership Principles page on Amazon Jobs describes these principles as the criteria applied across every format of its hiring process.

Customer Obsession sits at the top of that list, and it's described specifically as leaders starting with the customer and working backwards. That phrase isn't decorative. It's a structural instruction. A candidate who opens a written response with market size, competitive context, or product vision has already signaled, in the first paragraph, that their reasoning begins somewhere other than the customer. The bar raiser sees that signal immediately, before reading another word of the analysis.

Amazon's bar raiser process is explicitly designed to evaluate LP alignment across all interview formats. The written assessment is not an exception to this. It is one of the clearest tests of it, because a document shows reasoning architecture in a way a verbal answer can obscure.

This is where the structural inversion happens. Most PM candidates are trained, through MBA programs and standard interview prep, to open with opportunity framing: the size of the market, the strategic gap, the product vision. That structure works at most companies. At Amazon, it reads as solution-first reasoning, which is the opposite of what Customer Obsession describes. Amazon has written publicly about its Working Backwards methodology, which begins with the customer's problem before any product solution is considered. The written assessment is, in part, a test of whether that methodology is genuinely internalized or just something a candidate can name.

To illustrate the structural difference: a candidate responding to a prompt about improving a grocery delivery product might open with "The grocery delivery market represents a significant opportunity with fragmented last-mile logistics." A second candidate might open with "A working parent ordering groceries online consistently cannot trust that substitutions will match their family's dietary constraints." Both candidates are addressing the same product space. The second opening maps directly to Customer Obsession as a scoreable criterion. The first doesn't, regardless of what follows it.

PM interviews vary significantly across companies in how much weight they place on LP alignment versus product instinct. Our product manager interview hub covers those differences across companies. At Amazon, the distinction is that LP alignment isn't a secondary signal layered on top of product evaluation. It's the primary filter through which the written response is read.

How to Use the 24 Hours You Actually Have

Given the time constraint, the sequencing of your effort matters more than the total effort. The instinct is to start drafting immediately, then edit for quality. That sequence produces a well-written document organized around the wrong criteria.

The more useful sequence starts before you write a word. Read the prompt and ask which Leadership Principles the prompt is designed to surface. A prompt about a struggling product with declining retention is almost certainly designed to test Customer Obsession and possibly Invent and Simplify. A prompt about a resource-constrained prioritization decision is more likely to surface Are Right A Lot, which describes strong judgment and the ability to seek diverse perspectives before deciding. Identifying the target LPs first means your structure can be built to surface them, rather than hoping they emerge from good product thinking.

After that, write your opening paragraph with a specific customer problem. Not a customer segment. Not a persona archetype. A specific, observable frustration that a real person experiences. This is the most important sentence in the document, because it's where LP alignment is either established or missed. Once that opening is set, the analytical content can follow. Prioritization logic, solution design, tradeoffs: all of that matters, but it's read after the evaluator has already formed a view of how your reasoning is organized.

Edit last, and edit specifically for your conclusion. Candidates often close with a summary of the recommended solution. A stronger close returns to the customer: what does this decision do for the person named in your opening paragraph? That loop, from customer problem to solution back to customer outcome, is what a document built around Customer Obsession actually looks like from the evaluator's side.

The full breakdown of how Amazon evaluates PM candidates across every stage of the loop is in our Amazon PM interview guide, including how behavioral rounds, the bar raiser interview, and the written assessment fit together as a system. What matters in the next 24 hours is narrower: your document needs to demonstrate that your default reasoning direction is toward the customer, not toward the product.

A strong no-hire response can contain genuinely good product strategy. It can demonstrate analytical depth, creative thinking, and sound prioritization. It can also score below the bar because the reasoning architecture is visibly organized around the solution rather than the customer who needs it. Amazon's hiring philosophy, as documented in its bar raiser program, places equal weight on cultural alignment and technical skill. In the written assessment, cultural alignment is visible in your structure. Technical skill is visible in your content. You control both, but only one of them shows up in your first paragraph.