Company Values, Amazon's Leadership Principles and Follow-Up Pressure

Your STAR answer was good. The interviewer nods, then asks: "What exactly did you say to your teammate?" You hesitate. "And what did the others think of your decision?" You start to reshape the story. "How did you know the change actually helped?" The story now sounds different from how it started, and the interviewer has learned two things: some of it may not be true, and you struggle under pressure.

Behavioral rounds are often decided in these follow-ups. This article prepares you for them, and for the company-specific lens many interviewers use.

• How to find a company's values and map your stories to them.
• How to prepare for Amazon's Leadership Principles as a fresher.
• Eight follow-up questions that test any story.
• A voice drill that rehearses follow-up pressure.

Many companies publish what they value in people: on their careers page, a "culture" or "values" page, in job descriptions ("we value ownership and bias for action"), in founders' posts and in engineering blog posts about how they work. Interview reports (article 26) often say which behavioral questions were asked.

Collect:

• the published values, word for word, with their short descriptions;
• phrases that recur in job descriptions;
• behavioral questions mentioned in recent candidate reports.

Do not rely on second-hand summaries of a company's culture, or an assistant's memory of it. Values pages change, and summaries often attach slogans to the wrong company.

Below are [company]'s published values (copied from their careers page) and shortsummaries of my 10 STAR stories.1. For each value, which of my stories fits best? Say whether the fit is strong   or a stretch, and what I should emphasise to make the connection clear.2. Which values have no good story? Suggest which experience from my inventory   could become one, or say none fits.3. Which two stories should I lead with for this company?Use only my stories; do not add details.Values: [paste]My stories: [paste summaries]

The output becomes part of your one-page brief (article 29): two stories to lead with and a value-to-story map.

Amazon is the best-known example of a company that publishes the principles its interviewers assess. It lists sixteen Leadership Principles:

1. Customer Obsession
2. Ownership
3. Invent and Simplify
4. Are Right, A Lot
5. Learn and Be Curious
6. Hire and Develop the Best
7. Insist on the Highest Standards
8. Think Big
9. Bias for Action
10. Frugality
11. Earn Trust
12. Dive Deep
13. Have Backbone; Disagree and Commit
14. Deliver Results
15. Strive to be Earth's Best Employer
16. Success and Scale Bring Broad Responsibility

Older preparation material often lists fourteen; the last two were added in 2021. Read the full descriptions on Amazon's own page, because the descriptions, not just the titles, are what questions are built from.

Some principles fit a fresher's experience naturally; others are about managing people or company-wide impact. Do not stretch a college project into an organisational story; it will not survive questioning. Credible fresher-scale examples:

For principles such as "Hire and Develop the Best", a story about mentoring juniors or teaching may fit. If none fits, say so honestly if asked, and offer the closest real example.

Amazon interviews are known for asking the same principle from several angles and for deep follow-ups. That makes the next section especially important for Amazon, but it applies everywhere.

Run every important story through these, aloud:

1. Your role. "What exactly did you do, versus what others did?"
2. The moment. "When did you realise something had to change? What triggered it?"
3. Alternatives. "What other options did you consider? Why didn't you choose them?"
4. Measurement. "How do you know it worked? What did you measure, and how?"
5. The hardest point. "What was the most difficult moment, and what did you do right then?"
6. Hindsight. "What would you do differently now?"
7. Others' views. "What did your teammates or your guide think of your approach at the time?"
8. Afterwards. "What happened later? Did the result last?"

If you cannot answer one of these specifically, either strengthen the story (find out, remember, measure) or choose a different story. A story that cannot survive question 1 or 4 is not ready.

Typing answers does not train you for spoken pressure. Use a voice mode (article 33):

You are an interviewer running a behavioral round for an entry-level role at[company]. I'll name the value or principle and tell my story aloud.After my story, ask the follow-up questions below one at a time, in any order.If my answer is vague, ask one more probing question before moving on.Be sceptical but professional.After all eight, tell me: which answers were specific and consistent, which werevague or contradicted my original story, and whether this story is ready.Follow-ups:1. What exactly did you do versus others?2. When did you realise something had to change?3. What alternatives did you consider?4. How did you know it worked?5. What was the hardest moment?6. What would you do differently?7. What did others think at the time?8. What happened afterwards?

Record yourself, and compare the first telling with your answers to the follow-ups. Any change of fact is something to fix before the real interview.

Interviewers sometimes ask about the same story twice, in different rounds or from different angles. A story that stays the same in its facts, whichever angle you emphasise, builds trust. A story whose numbers or roles change is a serious warning sign, even if both versions sound good. This is the strongest reason to build stories from real details (article 35) and to practise retelling them in different words.

Varun is preparing for an Amazon SDE interview. His story bank has ten stories. Mapping them to the principles:

• Strong fits: Ownership (taking over a teammate's module), Dive Deep (tracing a memory leak in his project to an unclosed connection), Learn and Be Curious (learning Go for a hackathon), Deliver Results (shipping the fest app on time with a cut feature), Earn Trust (admitting he had broken the shared database and restoring it).
• Stretches: Think Big (his ideas were small), Hire and Develop the Best (no mentoring story yet).
• Gap work: he remembers running two sessions teaching juniors Git, which fits Hire and Develop the Best at fresher scale.

The follow-up drill on his Dive Deep story exposes a weakness: asked "how did you know the fix worked?", he had no measurement. He re-runs his load test with and without the fix and records memory use over 30 minutes. The story now survives question 4.

• Generic stories not linked to any of the company's values.
• Relying on an outdated list of a company's values or principles.
• Inflating scale to match a principle written for senior leaders.
• Never practising follow-ups, only first answers.
• Changing details when retelling.
• Inventing a precise detail under pressure.

Story: taking over the notifications module.Changed facts: first telling "week 6", follow-up answer "around week 7".Said "we cut SMS" first, then "I decided to cut SMS".Weak answers: Q4 (how did you know it worked? only "the demo went fine").Fixes: confirmed week 6 from the chat history; decided it was my decision, agreedwith the team; added the result "all 23 test complaints triggered emails in the demo".Second drill: consistent; Q4 now specific.

• Next: Weakness, Failure, Conflict and the HR Round covers the questions that feel like traps, and the HR round itself.
• For mock interview formats, revisit Mock Interviews: AI Voice Practice, Peers and Recordings.
• For common HR questions, see Common HR Interview Questions and How to Answer Them (With Examples).