← All posts
general

Amazon Writing Assessment: Prompts, Format and Examples

A few days before the loop, the recruiter's email has an attachment you were not expecting: two questions, pick one, answer in writing, send it back before the interviews. That is the Amazon writing assessment. Candidates who have spent three weeks on stories and system design tend to give it a rushed evening, because it looks like a formality next to five interviews.

It is the only part of the loop your interviewers can read twice. They open it before they meet you, some of them quote it back to you, and it is on the table when they decide. It is also the one part you control completely: no clock in the room, no follow-up you did not see coming. Two focused hours are enough to make it work for you, provided you know what the readers are looking for.

Why Amazon asks for writing at all

Amazon runs on documents. Its 2017 shareholder letter says so directly: "We don't do PowerPoint (or any other slide-oriented) presentations at Amazon. Instead, we write narratively structured six-page memos", which are read in silence at the start of each meeting. A manager, product manager or senior engineer there spends real time writing and reviewing those memos, so a hiring process that never looked at a candidate's writing would miss part of the job.

The assessment is a small version of that. It checks whether you can lay out a situation, a decision and its result in plain prose that a busy reader can follow without you in the room.

Which roles and levels get one

Amazon confirms the exercise for some roles and says little else. As of November 2026 its candidate prep pages for software development manager and for product manager both say that after a successful phone screen the recruiter sends a writing assessment, and both place it two days before the interview loop. Both pages also list a "writing exercise" among the things the loop assesses.

Beyond that, the picture comes from prep sites and candidates:

  • The exercise is usually tied to level. Guides say it is standard from L6 upward and appears at L5 for writing-heavy roles such as product management. Technical program manager candidates report it routinely.
  • For individual engineers it is less clear. Amazon's SDE II and SDE III prep pages do not list one.
  • Some job families get a role-specific prompt instead of the general one. One guide gives legal roles as an example, with a prompt about explaining legal concepts to non-lawyers.

If the recruiter has not mentioned a writing exercise by the time your loop is scheduled, ask. It is an ordinary question and the answer is immediate.

The two prompt families

Candidates usually get two prompts and choose one. The wording varies by year and role, but the accounts fall into two families.

Something you invented or changed. Reported versions ask for the most innovative or inventive thing you have done, or a time you innovated or dealt with a challenging situation. The reader is looking for a problem that was real, an idea that was yours, and a result somebody could measure.

A judgment call. Reported versions ask you to elaborate on a judgment call you made, to write about a time you had limited data but had to make an important decision, or about a time you had to convince a stakeholder of your view. The reader is looking for the options you had, why you chose one, what you gave up, and whether you were right.

Both are behavioral questions on paper. They map onto the leadership principles in the obvious way: the first onto Invent and Simplify and Think Big, the second onto Are Right, A Lot, Bias for Action and Have Backbone. Pick the prompt for which you have the better story, not the one that sounds more impressive.

One practical point: have a story for the prompt you did not choose as well. One coaching site advises preparing both because interviewers may ask about either.

Length, format and time limits

Sources disagree on the numbers, which probably means the instructions differ between recruiters and years. Read your own email and follow it over anything written here.

  • Length. Most accounts say about two pages. One guide says four pages is the ceiling and two is what to aim for; another says to stay under a page and a half. The safe reading is two pages or fewer.
  • Time. Amazon's pages put the assessment two days before the loop. One coaching site says candidates typically have 48 hours from receiving the prompt; another says several days. It is done at home, untimed within that window.
  • Form. Narrative prose: full sentences in paragraphs. Short headings are acceptable if they help. Avoid bullet lists as the main structure, and leave out charts, images and tables. One guide says it is submitted as a Word document; use whatever format your recruiter names.
  • Your own work. You are expected to write it yourself. One guide that tracks the process says explicitly that help from colleagues, friends or AI tools is not allowed. Apart from the rule, there is a practical reason: interviewers ask about the document, and a text you did not write is hard to defend sentence by sentence.

How the document is read and who reads it

Amazon does not publish how the assessment is scored. The consistent description is this. The hiring manager reads it, the Bar Raiser reads it, and the other interviewers in the loop usually have access to it beforehand. One guide describes the evaluation as pass or fail with no numeric score; an older one for program managers says reviewers grade two things, clarity of expression and structure of thought. A prep guide for managers says the writing counts as a competency of its own next to the interview rounds.

Three uses follow.

  1. As an interview prompt. Someone will ask about it: why you chose that option, how the number was measured, what you would do now. The follow-ups work exactly as they do for a spoken story.
  2. As a consistency check. If the same project comes up in an interview, the numbers and your role have to match what you wrote. Written claims are easy to compare.
  3. As evidence in the decision. In the debrief, interviewers argue from written evidence. Your document is the one piece of it that you wrote. A clear two pages will not rescue a weak loop. But if it is judged pass or fail, as one guide says, a careless one is a risk you have no reason to take.

A structure that works

Any clear structure is acceptable. This one fits both prompt families and uses the page well.

  • Situation, in one short paragraph. Company, team, your role, the problem, why it mattered and to whom. Give one number that sets the scale. The reader has never heard of your product; write for them.
  • The decision or the idea. What the options were, including the one of doing nothing. Which you chose and the reasoning, in the order you actually reasoned. Say what you did not know at the time.
  • What you did. Your actions in the first person, in sequence. Two or three concrete steps beat a list of ten. Mention the people you had to persuade and how.
  • The data. The result with a baseline, a time period and a method: what the number was, what it became, how you measured it. If the result was mixed, say so.
  • What you would change. A real second thought, not a compliment to yourself. This paragraph is where judgment shows.

Proportions for two pages: about a fifth on the situation, two fifths on the decision and the actions, a fifth on the data, the rest on the reflection. If the situation takes a whole page, the story needed too much setup; pick another or cut harder.

One worked outline

This sketch is invented for illustration. It is not a real candidate's document and the numbers are made up; it shows the level of detail to aim for on the judgment-call prompt.

  • Opening sentence. "In March I decided to delay a payments migration by six weeks, against my director's stated preference, because our rollback test had failed twice."
  • Situation. Team of seven owning checkout for a mid-size marketplace. Migration to a new payment provider, contractual deadline at the end of the quarter, a penalty clause for missing it.
  • Options. Ship on the date with a manual rollback plan; ship to one country first; delay until the automated rollback passed. What each would cost, in money and in risk, as known at the time.
  • Decision and reasoning. Chose the delay with a one-country pilot inside it. The deciding fact: a failed rollback during peak hours would stop all orders for an estimated forty minutes, which cost more than the penalty.
  • Actions. Wrote the two-page case for the director, negotiated the penalty down with the provider, reassigned two engineers to the rollback tooling, ran the pilot.
  • Data. Pilot surfaced a currency rounding defect affecting about one order in three hundred. Full launch five weeks late, no order loss, penalty paid at half the contract rate.
  • What I would change. The rollback test should have been in the plan from the first week, not discovered in the eighth. Now part of the team's launch checklist.

Notice what the outline has: a first sentence that states the decision, options with costs, a number for the deciding fact, a result that includes the bad part, and a lesson that changed a practice. Notice what it lacks: adjectives.

A two-hour writing plan

Split the two hours across two sittings if your deadline allows. The gap is where most of the improvement happens.

  • 0:00 to 0:15, choose. Write one sentence for each prompt stating the story you would tell. Pick the one with the clearer decision and the better numbers. Check that you have not planned to use it as your main story in the loop; if you have, prepare a second one for the interviews.
  • 0:15 to 0:35, outline. Five headings from the structure above, three or four fragments under each. Look up the real numbers now. If you cannot find a number, write how you know the result instead of inventing one.
  • 0:35 to 1:20, draft. Write straight through in full sentences without editing. Aim for about a quarter more than the limit.
  • Break. An hour at least, overnight if you can.
  • 1:20 to 1:50, cut. Remove the first paragraph if the second works as an opening. Delete every sentence that describes the company and not the decision. Replace "we" with "I" wherever it was you. Replace adjectives with numbers. Expand acronyms and internal names. Bring it under the limit without shrinking the margins.
  • 1:50 to 2:00, read aloud and check. Read it out loud once; rewrite any sentence you stumble on. Check spelling, the file name, the format the recruiter asked for. Send it before the deadline, not at it.

Keep the final text open when you prepare for the loop, and write down the five follow-up questions it invites. If you can get one person to read the draft and tell you where they got lost, do it for the reading, not for the writing: someone who has reviewed Amazon documents, such as one of the coaches with Amazon on their history, will point at the sentences a debrief would stop on.

Mistakes

  • An interview answer typed up. A spoken STAR answer runs in a straight line and leans on tone. On paper it reads thin. The page gives you room for options, reasoning and data, so use it.
  • Jargon from your current employer. Internal project names, team names and acronyms mean nothing to the reader.
  • Passive voice hiding the actor. "It was decided" tells the reader you did not decide.
  • Claims without evidence. "Significantly improved" with no number, or a number with no baseline.
  • A success with no cost. Every real decision gave something up. Leaving it out reads as either poor judgment or poor candour.
  • Going over the limit. It signals that you could not prioritize, which is the skill being tested.
  • Typos and formatting slips. In a spoken answer nobody notices; in a document they are the first thing a careful reader sees.
  • A text you cannot defend. If someone else, human or machine, wrote the sentences, the first follow-up question will show it.
  • Sending it and forgetting it. Re-read it the night before the loop. Your interviewers just did.

Where coaching fits

Writing is hard to judge from the inside, and the people around you may not read the way an Amazon debrief reads. A session with a coach who has worked there can go through your stories for the two prompts, tell you which one carries more evidence, and practise the follow-up questions the document will draw in the loop; the writing itself stays yours. Nine of the 40 coaches on techinterview.coach have Amazon on their history as of November 2026, and you can see them on the Amazon coaches page. To rehearse the questions your document invites, the free practice interview runs a behavioral round with an AI interviewer and a written recap. It is free; sign in to start.

Related guides