Amazon Learn and Be Curious Interview Questions and Answers (2026)
Everyone says they love learning. Amazon interviewers want proof: what you taught yourself, why you went looking for it, and what changed because you did. Here are the questions, three sample STAR answers and the follow-ups that separate real curiosity from a line on a resume.
What Learn and Be Curious Actually Means
Learn and Be Curious is one of Amazon's 16 Leadership Principles, and it asks whether you keep improving yourself and actively explore new possibilities, rather than waiting to be trained. Amazon's published wording is two sentences: leaders are never done learning and always seek to improve themselves. They are curious about new possibilities and act to explore them.
That second sentence is the part most candidates miss. Curiosity on its own is a personality trait. The principle asks for curiosity that turns into action: you noticed something you didn't understand, you went and learned it, and you used what you learned to do something differently. An interviewer can't score "I'm naturally curious," but they can score a story where you taught yourself SQL because the weekly report kept arriving late and then automated it.
| Phrase in the principle | What it means in practice | What interviewers listen for |
|---|---|---|
| Never done learning | You keep building skills after you are already competent in your role | Recent learning, not only what you studied in college |
| Always seek to improve themselves | You look for feedback and gaps in your own ability, and close them deliberately | A specific weakness you identified and a plan you followed |
| Curious about new possibilities | You ask "why do we do it this way?" and "what else could work?" | The question or observation that started the story |
| Act to explore them | You test the idea: a prototype, a pilot, a conversation with an expert, an experiment | What you actually did and what the result was |
If your story ends with "and I found it really interesting," it is incomplete. Every strong Learn and Be Curious answer ends with an outcome: a skill applied, a process changed, a decision informed, a project unblocked. Learning that changed nothing is hard for an interviewer to write up as evidence.
Learn and Be Curious overlaps with several other principles, which makes it useful for your story bank. Exploring an unfamiliar technology to solve a problem overlaps with Invent and Simplify. Learning the details of a process to find a defect overlaps with Dive Deep. Seeking out feedback and acting on it overlaps with Earn Trust. In the interview, though, you need to keep the emphasis on the learning itself: what you didn't know, how you found out, and how quickly you got useful.
It is also one of the principles most often probed for early-career candidates, interns and people changing careers, because they have less track record to point to. If you are in that group, expect at least one curiosity or fast-learning question. For an overview of all 16 principles and the interview loop, see our Amazon interview questions hub.
How Amazon Tests Learn and Be Curious
Amazon's interviews are built around behavioral questions tied to the Leadership Principles. In a typical loop, each interviewer is assigned a small number of principles to cover and asks for specific past examples. Amazon's own interview guidance encourages candidates to use the STAR format (Situation, Task, Action, Result), and interviewers take detailed notes that are discussed in a debrief after the loop.
Learn and Be Curious can show up at several stages. Here is where you are most likely to meet it.
| Stage | How the principle shows up | How to prepare |
|---|---|---|
| Online assessment | For many roles, a Work Style survey includes statements about seeking feedback, trying new approaches and learning new skills | Answer consistently and honestly; read our Work Style assessment guide |
| Phone or video screen | A recruiter or hiring manager may ask one broad question such as "What have you learned recently?" | Have a recent, job-relevant example ready that takes under two minutes |
| Interview loop | One interviewer may own the principle and ask for one or two detailed stories with follow-ups | Prepare two or three stories with different types of learning |
| Bar Raiser interview | Bar Raisers often probe growth and self-awareness, including what you would do differently | Know the limits of what you learned and what you're still working on |
Interviewers don't always name the principle. "Tell me about a time you had to get up to speed on something quickly" and "What's a skill you've developed in the past year?" are both Learn and Be Curious questions. If the question involves new knowledge, an unfamiliar area or self-improvement, assume this principle is being scored.
What the interviewer writes down matters more than how the conversation feels. They are looking for data points they can quote in the debrief: what you didn't know at the start, the resources or people you used, how long it took, and the measurable result. A story full of enthusiasm but light on those facts is hard for them to defend when the panel discusses you.
The principle is weighted differently by role. Software engineers are often asked how they learned a new language, framework or system. Operations and fulfillment leaders get questions about learning an unfamiliar process or site. Business and program roles tend to hear about picking up a new market, customer segment or analytical skill. The underlying behavior is the same: you identified a gap, closed it on your own initiative and put the knowledge to work.
A course your employer required, or a certification you needed for the job, shows compliance rather than curiosity. If a certification is your best example, focus on why you chose it, what you did beyond the syllabus, and how you applied it.
15 Common Learn and Be Curious Questions
These questions are drawn from the wording candidates commonly report and from how the principle is defined. They fall into four groups. Prepare at least one story for each group and you will be able to adapt to almost any version of the question.
| # | Question | What it is really testing |
|---|---|---|
| 1 | Tell me about a time you had to learn something new very quickly. | Speed and method of learning |
| 2 | Describe a time you taught yourself a skill to solve a problem at work. | Self-directed learning tied to an outcome |
| 3 | Tell me about something you learned recently. How did you apply it? | Learning is ongoing, not historic |
| 4 | Give an example of a time you explored an area outside your core role. | Breadth of curiosity |
| 5 | Tell me about a time curiosity led you to a new idea or improvement. | "Act to explore" in practice |
| 6 | Describe a time you questioned why something was done a certain way. | Willingness to challenge the default |
| 7 | Tell me about a time you sought out feedback to improve. | Self-improvement, humility |
| 8 | What is a weakness you have worked to improve, and how? | Self-awareness plus a plan |
| 9 | Tell me about a time you learned from a mistake. | Reflection and changed behavior |
| 10 | Describe a time you used a new technology or tool for the first time. | Comfort with the unfamiliar |
| 11 | Tell me about a time you learned something from a customer or colleague that changed your approach. | Learning from others, open-mindedness |
| 12 | How do you keep up to date in your field? | Habits and sources (back it with an example) |
| 13 | Tell me about a time you were outside your comfort zone and had to learn. | Resilience while learning |
| 14 | Describe a time you shared something you learned with your team. | Multiplying learning across others |
| 15 | Tell me about a time you explored an idea that didn't work out. What did you learn? | Experimentation and honest reflection |
The four groups
- Fast learning (Q1, Q10, Q13): you were dropped into something unfamiliar and became useful quickly. Have a clear timeline, such as "within two weeks."
- Self-directed skill building (Q2, Q3, Q12): nobody asked you to learn it. You saw a reason and went after it.
- Curiosity that led to change (Q4, Q5, Q6, Q14): a question you asked turned into an improvement for the team or the customer.
- Self-improvement and reflection (Q7, Q8, Q9, Q11, Q15): you found a gap or a failure in yourself and did something about it.
Listing newsletters and podcasts is a weak answer on its own. Name one source, then give a specific example of something you picked up from it and used at work in the past few months. That turns a generic habit into evidence.
For a deeper treatment of the fast-learning version, see our guide to "Tell me about a time you learned something quickly", which includes extra sample answers for non-Amazon interviews.
Three Sample STAR Answers
Each sample below is about 2 to 3 minutes when spoken. They are written for different experience levels so you can see how the same principle works for an intern, an operations lead and a software engineer. Use them to see the structure, not as scripts: your interviewer will ask follow-ups that only your own story can answer.
Sample 1: Teaching yourself a skill to solve a problem (early career)
Question: Tell me about a time you taught yourself a skill to solve a problem.
Situation: "In my marketing internship, I was responsible for a weekly campaign report. It was built by copying data from three exports into a spreadsheet by hand, and it took me about six hours every Monday. The numbers often didn't match because of copy errors, and my manager was spending time on corrections."
Task: "Nobody had asked me to change the process, but I wanted to cut the time and remove the errors. I didn't know SQL or any automation tools at the time."
Action: "I asked one of the analysts which tool the data team used and she pointed me to the read-only database. I took a free online SQL course in the evenings over two weeks, then wrote queries for each of the three sources, starting with the simplest one so I could check my output against the manual report line by line. When two numbers didn't match, I found out the export used a different date cutoff than the database, so I documented the definition and agreed with my manager which one to use. Once all three queries matched for three weeks in a row, I connected them to the spreadsheet so it refreshed automatically."
Result: "The Monday report went from six hours to about twenty minutes of review, and we had no corrections for the rest of my internship. I wrote a one-page guide so the next intern could maintain it, and the team asked me to build a similar query for a second report. The bigger lesson for me was to ask where the source data lives before accepting a manual process."
It shows the full principle: a gap noticed without being asked, a clear learning method, validation against the old process, a measurable result and learning shared with others. The date-cutoff detail also gives the interviewer something concrete to probe.
Sample 2: Curiosity that led to an improvement (operations)
Question: Tell me about a time curiosity led you to improve something.
Situation: "I was a shift lead at a distribution center. Our pick rates were consistently lower on one aisle range, and the accepted explanation was that those items were heavier."
Task: "The weight explanation didn't fully make sense to me, because some of the slowest locations held light items. I wanted to understand what was really going on before we accepted it as permanent."
Action: "I spent parts of three shifts walking those aisles with pickers and timing the steps. I asked them what slowed them down, and two people independently mentioned that labels on the lower shelves were hard to scan because of the angle. I read up on our scanner settings with the IT lead and learned there was a configurable scan distance. We tested a change on one scanner and moved the worst labels slightly higher on a single aisle as a pilot."
Result: "On the pilot aisle, the average time per pick dropped by about 15 percent over two weeks. We rolled the label change to the rest of the range, and the gap with the rest of the building mostly closed. I now spend an hour on the floor with a new team each month specifically to ask what slows them down."
Sample 3: Learning an unfamiliar technology fast (software engineer)
Question: Tell me about a time you had to learn a new technology quickly.
Situation: "Our team inherited a service written in a language none of us had used, after the original team was reassigned. A customer-facing bug was open and the on-call rotation was about to include us."
Task: "I volunteered to get productive in the codebase within two weeks so the team wasn't blocked during on-call."
Action: "I started with the language's official tutorial for two evenings, then switched to reading the service's tests, because they showed how the code was actually meant to behave. I scheduled two 30-minute calls with an engineer from the original team and came with a written list of questions. I fixed the open bug in a pair session with him, then wrote a short onboarding doc with the build steps and the five things that confused me most."
Result: "The bug fix shipped in the first week. When the rotation started, I handled the first two pages without escalation, and three teammates used my onboarding doc to get set up in a day instead of the several days it had taken me. If I did it again, I would set up the debugger on day one; I lost most of a day reading logs instead."
Sample 3 closes with a small self-critique. For a learning principle, that kind of reflection is a strength, not a weakness. It shows that you are still learning from the experience itself.
The Follow-Up Probes to Expect
Amazon interviewers are known for drilling into stories with follow-up questions. For Learn and Be Curious, the probes are designed to find out whether the learning was really yours, really self-directed and really applied. Expect several of these after your initial answer.
| Follow-up | What they want to know | How to answer well |
|---|---|---|
| "What made you want to learn that?" | Whether the motivation was yours | Name the trigger: a problem, a question, a customer complaint |
| "How exactly did you learn it?" | Your learning method | Specific resources, people and how you practiced |
| "How long did it take?" | Speed and realism | A believable timeline with milestones |
| "How did you know you'd learned it well enough?" | Judgment and quality checks | How you tested or validated your new skill |
| "What was hardest to learn?" | Honesty and self-awareness | One genuine difficulty and how you got past it |
| "What would you do differently?" | Reflection | A specific change, not "nothing" |
| "What are you learning right now?" | Whether learning continues | A current example with a reason it matters to your work |
Many candidates prepare past stories and freeze on this one. Have a current answer ready: a course, a book, a side project or a skill you are building at work. Ideally it connects to the role you are interviewing for, but honesty matters more than relevance.
The follow-ups tend to move from the story toward you. Early probes check the facts. Later ones check habits: whether this was a one-off or how you usually operate. That is why having a consistent learning approach helps. If you can describe the way you typically get up to speed (for example, finding an expert, reading the tests or documentation, building something small, then teaching it back), your answers to the later probes will sound natural rather than invented.
Keep your numbers honest. If the interviewer asks how you measured a 15 percent improvement and you can't explain it, the whole story loses weight. Use approximate figures if that's all you have, and say they are approximate. Interviewers generally respect "roughly" far more than a precise number you can't support.
Ask a friend to respond to every answer with "Why?" and "How do you know?" three times in a row. If your story still holds after the third round, it's ready for an Amazon loop. Our STAR interview technique guide has a practice framework you can use.
Building Your Curiosity Story Bank
Amazon loops usually cover many principles across several interviewers, and you can't reuse the same story with every person. Build a bank of 8 to 12 stories in total and map each one to two or three principles. For Learn and Be Curious, aim for at least two or three stories that cover different types of learning.
| Story type | Example prompt to jog your memory | Also works for |
|---|---|---|
| Self-taught technical skill | A tool, language or method you learned outside work hours to solve a work problem | Invent and Simplify, Bias for Action |
| New domain or area | A time you moved teams, took on a new market or covered for someone in an unfamiliar role | Ownership, Deliver Results |
| "Why do we do it this way?" | A process you questioned and then improved | Dive Deep, Insist on the Highest Standards |
| Feedback you acted on | Critical feedback that changed how you work | Earn Trust |
| An experiment that failed | An idea you tried that didn't work and what you took from it | Are Right, A Lot; Think Big |
| Learning you multiplied | A guide, session or mentoring you gave after learning something | Hire and Develop the Best |
A simple worksheet for each story
- The gap: what did you not know or not understand at the start?
- The trigger: what made you go looking? (A problem, a question, a customer, a mistake.)
- The method: who did you ask, what did you read, how did you practice?
- The timeline: how long until you were useful?
- The application: what did you do with it?
- The result: what changed, with a number if possible?
- The reflection: what would you do differently, and what are you still learning?
A modest example from the last 12 months usually works better than a dramatic one from five years ago. The principle says leaders are never done learning, so a recent story shows the habit is still active.
Avoid putting too much weight on a single story. If an interviewer has already heard your SQL story from a colleague in the debrief notes, a second interviewer asking about learning will want something different. Spreading your examples across work, side projects and volunteering also helps, as long as each one has a clear result.
Don't forget the assessment stage. Many Amazon roles start with an online assessment before you reach the loop, and for corporate roles that can include work simulations and a Work Style survey based on the same principles. Our Amazon online assessment guide explains the formats by role.
Mistakes That Sink These Answers
Learn and Be Curious looks easy, which is why candidates often under-prepare for it. These are the problems that most commonly weaken otherwise good answers.
| Mistake | Why it hurts | Fix |
|---|---|---|
| Describing a trait ("I'm very curious") | There is no evidence to write down | Open with a situation, not a self-description |
| Learning with no outcome | Misses "act to explore them" | End with what changed because you learned it |
| Required training as the example | Shows compliance, not initiative | Choose learning you chose to do |
| Hobby stories with no work link | Hard to connect to the role | Use them only if you show how they changed how you work |
| Overstating how fast you learned | Follow-ups expose it | Give a realistic timeline with milestones |
| No current learning | Suggests the habit has stopped | Prepare an answer to "What are you learning now?" |
A story where you explored something interesting while your main deliverable slipped can backfire, because it conflicts with Deliver Results. If your exploration took time, explain how you protected your core work or why the trade-off was the right call.
Another common problem is a story that is all about a course. "I completed a data analytics certificate" is a fact, not a story. What makes it interesting is the reason you chose it, the hardest part, and the first time you used it on a real problem. Interviewers will usually ask those questions anyway, so build them into your answer.
Lastly, watch for the "we" trap. Learning is personal by definition. If your answer says "we researched" and "we figured out," the interviewer can't tell what you learned. Use "I" for your own actions and credit others by name where they helped.
If you are also facing reasoning tests earlier in the process, use timed practice tests to build speed on numerical and verbal questions before you get to the interview stage.
Frequently Asked Questions
Get Through Amazon's Assessment Stage First
Many Amazon roles start with an online assessment before you reach the interview loop. Build speed and accuracy with timed SHL-style numerical, verbal and inductive reasoning practice, then review our full guide to Amazon's tests.
Keep reading
- Article · Strategy & ScoringAmazon Customer Obsession Interview Questions and Answers (2026)
- Article · Strategy & ScoringAmazon Dive Deep Interview Questions and Answers (2026)
- Guide · Company GuidesAmazon Aptitude Test & Work Style Assessment
- Guide · Company GuidesAmazon Interview Questions & Leadership Principles Guide
- Guide · Company GuidesAmazon SDE Online Assessment 2026: Questions, Format & Prep
- Guide · Company GuidesAmazon Bias for Action Interview Questions & Sample Answers