← All posts
general

Learn and Be Curious: Amazon Interview Questions and Answers

Learn and Be Curious is the fifth of Amazon's 16 leadership principles and the one candidates most often answer with a platitude. "I love learning" is not an answer. Interviewers want a recent, specific, slightly uncomfortable example of you closing a gap in your own knowledge, and evidence that it changed something you built or how you work.

This guide covers the official wording, what the principle means in practice, examples from engineering, product, data and non-technical roles, 14 interview questions, a sample STAR answer, and the follow-ups to expect.

The official wording from Amazon

Leaders are never done learning and always seek to improve themselves.

That is the first sentence on Amazon's leadership principles page. The second sentence adds curiosity about new possibilities and, importantly, acting to explore them. Read the principle as two tests. The first is deliberate self-improvement: you close your own gaps without waiting for a training budget or a manager's nudge. The second is curiosity that leads somewhere: you do not just wonder how something works, you go and find out, and what you learn changes what you do.

What Learn and Be Curious means in practice

  • You can name something hard you learned in the last six months, why you chose it, and what it let you do.
  • When you are the least knowledgeable person in a room, you ask the basic question out loud instead of nodding.
  • You investigate things outside your responsibilities, and sometimes that investigation turns into a project.
  • You treat critical feedback as information about a gap, and you can show what you did with it.
  • You dig into why you were wrong, not why you were almost right.

Learn and Be Curious examples at work

A frontend engineer is handed a performance bug she cannot explain. Rather than apply the fix a colleague suggests, she spends a weekend reading how the browser's rendering pipeline actually works, finds the real cause, and writes an internal guide that becomes the team's onboarding reading. The bug was the excuse; the guide was the result.

A product manager moves from a consumer app to a payments team and knows nothing about card networks. He gives himself four weeks: two industry primers, calls with three people in the risk team, and a spreadsheet of every fee in a transaction. By week five he catches a pricing error in a partner contract that the previous PM had signed off on.

A data analyst is curious why a weekly metric spikes every fourth Tuesday. Nobody asked her to look. It turns out to be a billing batch job that double-counts a segment, and fixing it changes a revenue figure the board had been shown.

A recruiter notices that engineers keep declining offers after the system design round. He asks three of them why, sits in on the round, and learns enough about the interview to rewrite the candidate prep email. The decline rate at that stage drops over the next quarter.

Learn and Be Curious interview questions

Direct questions

  • Tell me about the last thing you taught yourself. Why that, and how?
  • Describe a time you had to learn a new skill or domain quickly to deliver.
  • Tell me about a time your curiosity led you somewhere unexpected.
  • What do you do when you realize you are the least knowledgeable person in the room?
  • How do you keep your skills current? Give me a concrete recent example.
  • Describe a time you explored an idea outside your responsibilities. What came of it?
  • Tell me about a time you were wrong about something you were confident in. What did you learn?

Questions that test it indirectly

  • Tell me about a piece of critical feedback that changed how you work.
  • Describe a time you took on a project in a domain you knew nothing about.
  • What is something you believed about your field two years ago that you no longer believe?
  • Tell me about a time you asked a question nobody else wanted to ask.
  • How did you get up to speed in your current role? What would you do differently?
  • Tell me about a technology or method you resisted at first and later adopted.
  • What have you learned from a failure that you still apply?

A sample STAR answer

Question: "Describe a time you had to learn a new skill or domain quickly to deliver."

Situation: I was a backend engineer on a logistics product when our only machine learning engineer left two weeks before we were due to ship a delivery-time prediction feature. The model existed; nobody left on the team understood how to retrain, evaluate or deploy it.

Task: The launch was committed to a large customer. My manager asked whether we should pull the feature. I asked for one week to find out whether I could own the model well enough to ship it responsibly.

Action: I wrote down what I did not know: how the model was evaluated, what "good" looked like, and how retraining worked. I read the departed engineer's notebooks end to end, took a short online course on evaluation metrics in the evenings, and booked three thirty-minute calls with ML engineers on other teams, each with a specific question. By day four I could retrain the model and reproduce its validation numbers. On day five I found that the evaluation set included data from after the prediction time, which inflated accuracy. I fixed it, re-ran the numbers, and reported the honest (lower) accuracy to the customer before launch.

Result: We shipped on time with a model I could explain and maintain. The customer accepted the corrected accuracy because we told them first. I became the team's model owner for the next year, and the evaluation leak I found became a standard check in our pipeline.

Why this answer works

  • The learning is recent, specific, and uncomfortable: a domain switch under deadline pressure.
  • Curiosity found a real problem (the evaluation leak) that a pass-through learner would have missed.
  • The result shows what the learning let the candidate do, not just that it happened.

What the interviewer probes next

  • "What exactly did you learn, and from where?" Name the sources. Vague "research" sounds like nothing happened.
  • "How do you know you learned it well?" Point to an output: a shipped change, a found bug, a document others use.
  • "What did you get wrong along the way?" Learning stories without a stumble sound rehearsed.
  • "What are you learning right now?" Have a live answer.
  • "How do you decide what to learn?" Interviewers want to hear a connection to a problem, not a hobby.

Common mistakes

  • Answering with a disposition ("I am naturally curious") instead of an event.
  • Picking something you learned years ago. Recency is part of the signal.
  • Describing a course you took with no outcome attached.
  • Choosing a learning story that was entirely comfortable. The principle is about seeking improvement, which usually stings.
  • Forgetting the second half: curiosity that never turns into action is a personality trait, not a leadership principle.

Related leadership principles

  • Dive Deep: the weekend spent on the rendering pipeline is both principles at once. Interviewers often score them together.
  • Are Right, A Lot: working to disconfirm your beliefs is a learning habit, and the "I was wrong" story serves both principles.
  • Insist on the Highest Standards: finding the evaluation leak in the sample answer and reporting the lower number is where learning meets standards.

All 16 principles, with questions for each, are in the Amazon leadership principles guide.

Add two recent learning stories to your story bank, give them a STAR shape, then get matched with a coach who will test whether the learning actually changed what you do.