What do interviewers evaluate in Learn and Be Curious questions?

Interviewers listen for signals like: Was the learning self-driven, or just training your employer assigned you? Did curiosity lead to a concrete result, or was it learning for its own sake with no application? Did you step outside your comfort zone or established expertise to do it?

gitGood.dev

Amazon LPFoundational Premium

Learn and Be Curious (Amazon Leadership Principle)

Interviewers want self-driven learning that produced a concrete result - not a list of courses you took or technologies you've 'heard of.'

About this theme

Learn and Be Curious is one of Amazon's 16 Leadership Principles. It states that leaders are never done learning and always seek to improve themselves, that they are curious about new possibilities and act to explore them. The principle is about intellectual hunger applied with purpose: not collecting certificates, but noticing a gap or an interesting question and chasing it down until it produces something useful - a fix, a new capability, a better mental model that changes how you work. In interviews, this LP rewards stories where you taught yourself something outside your comfort zone because the problem demanded it, then applied it to real impact. Interviewers are wary of two weak patterns: the passive learner who lists trainings they sat through, and the curious-but-aimless engineer who learns for fun but never ships anything from it. They listen for a triggering question or gap, a deliberate effort to close it, and a concrete outcome. The best answers also show curiosity that spilled outward - you shared what you learned, or your digging uncovered a problem nobody had asked you to look at.

What interviewers are evaluating

→Was the learning self-driven, or just training your employer assigned you?
→Did curiosity lead to a concrete result, or was it learning for its own sake with no application?
→Did you step outside your comfort zone or established expertise to do it?
→Did a question or gap trigger the learning, showing you noticed something others missed?
→Did you share what you learned, multiplying its value beyond yourself?
→Do you keep learning continuously, or was this a one-off?

Common prompts

Variations on these are asked at every level. Have a story pre-loaded for at least three of them.

?Tell me about a time you taught yourself a new skill or technology to solve a problem.
?Describe something you learned recently outside of your core job responsibilities.
?Tell me about a time your curiosity led you to discover or fix something.
?How do you stay current in a fast-changing field?
?Give an example of when you went deep on a topic you knew little about.
?Tell me about a time you learned something that changed how you approached your work.
?Describe a time you explored a new idea that others were not paying attention to.

Sample STAR answers (preview)

The full library pairs strong and weak examples with notes on what makes each work (or fail). Here's how two of the strong stories open.

STRONG

Strong: Self-taught eBPF to crack an intermittent latency bug

Prompt: "Tell me about a time you taught yourself a new skill or technology to solve a problem."

Situation: We had an intermittent 200-millisecond latency spike on a core service that nobody could explain. Standard APM traces showed time disappearing 'somewhere in the kernel,' and the issue had been open as a low-priority ticket for four months because no one knew how to look deeper.
Result: I added a local DNS cache, which cut the p99 spike from 200 milliseconds to under 15 and closed the four-month-old ticket. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

STRONG

Strong: Dug into a billing line item and learned the pricing model

Prompt: "Tell me about a time your curiosity led you to discover or fix something."

Situation: I noticed our team's monthly cloud bill had a data-transfer line item that had quietly grown to about 8,000 dollars a month, roughly a third of our infra spend. Nobody owned cost, and the general assumption was that it was just the cost of doing business at our scale.
Result: Co-locating the service with its database in one AZ and switching the log shipper to a compressed, batched transport cut that line item by about 70 percent, saving roughly 5,600 dollars a month. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

What's in the full theme

3 full STAR answers (strong and weak, with interviewer notes) · 6 common pitfalls · 5 follow-up strategies

Subscribe to Continue

Get full access to gitGood.dev with a subscription.

Start Your 10-Day Trial

Try everything free for 10 days. Cancel anytime.

1000+ practice questions
AI mock interviews (3/day)
Coding challenges with real execution
Verified skill badges
105+ certification study guides

View Plans

10-day trial, then $5/mo - or $40/yr ($3.33/mo, save 33%). Cancel anytime.

Related behavioral themes

Dive Deep

Amazon LP

Leaders operate at all levels. The interviewer is testing whether you actually understand your own systems - or whether you summarize what your team built.

Invent and Simplify

Amazon LP

Interviewers want proof you removed complexity, not just added a clever feature. The 'Simplify' half is what most candidates miss.

Companies that test this theme

Practice these stories live

Reading STAR answers is the floor. The interview signal is in delivering them out loud, with follow-ups, under pressure. The AI mock interview probes your stories the way real interviewers do.

Start an AI mock interview →

Amazon LPFoundational Premium

Learn and Be Curious (Amazon Leadership Principle)

Interviewers want self-driven learning that produced a concrete result - not a list of courses you took or technologies you've 'heard of.'

About this theme

What interviewers are evaluating

→Was the learning self-driven, or just training your employer assigned you?
→Did curiosity lead to a concrete result, or was it learning for its own sake with no application?
→Did you step outside your comfort zone or established expertise to do it?
→Did a question or gap trigger the learning, showing you noticed something others missed?
→Did you share what you learned, multiplying its value beyond yourself?
→Do you keep learning continuously, or was this a one-off?

Common prompts

Variations on these are asked at every level. Have a story pre-loaded for at least three of them.

?Tell me about a time you taught yourself a new skill or technology to solve a problem.
?Describe something you learned recently outside of your core job responsibilities.
?Tell me about a time your curiosity led you to discover or fix something.
?How do you stay current in a fast-changing field?
?Give an example of when you went deep on a topic you knew little about.
?Tell me about a time you learned something that changed how you approached your work.
?Describe a time you explored a new idea that others were not paying attention to.

Sample STAR answers (preview)

The full library pairs strong and weak examples with notes on what makes each work (or fail). Here's how two of the strong stories open.

STRONG

Strong: Self-taught eBPF to crack an intermittent latency bug

Prompt: "Tell me about a time you taught yourself a new skill or technology to solve a problem."

Situation: We had an intermittent 200-millisecond latency spike on a core service that nobody could explain. Standard APM traces showed time disappearing 'somewhere in the kernel,' and the issue had been open as a low-priority ticket for four months because no one knew how to look deeper.
Result: I added a local DNS cache, which cut the p99 spike from 200 milliseconds to under 15 and closed the four-month-old ticket. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

STRONG

Strong: Dug into a billing line item and learned the pricing model

Prompt: "Tell me about a time your curiosity led you to discover or fix something."

Situation: I noticed our team's monthly cloud bill had a data-transfer line item that had quietly grown to about 8,000 dollars a month, roughly a third of our infra spend. Nobody owned cost, and the general assumption was that it was just the cost of doing business at our scale.
Result: Co-locating the service with its database in one AZ and switching the log shipper to a compressed, batched transport cut that line item by about 70 percent, saving roughly 5,600 dollars a month. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

What's in the full theme

3 full STAR answers (strong and weak, with interviewer notes) · 6 common pitfalls · 5 follow-up strategies

Subscribe to Continue

Get full access to gitGood.dev with a subscription.

Start Your 10-Day Trial

Try everything free for 10 days. Cancel anytime.

1000+ practice questions
AI mock interviews (3/day)
Coding challenges with real execution
Verified skill badges
105+ certification study guides

View Plans

10-day trial, then $5/mo - or $40/yr ($3.33/mo, save 33%). Cancel anytime.

Related behavioral themes

Dive Deep

Amazon LP

Leaders operate at all levels. The interviewer is testing whether you actually understand your own systems - or whether you summarize what your team built.

Invent and Simplify

Amazon LP

Interviewers want proof you removed complexity, not just added a clever feature. The 'Simplify' half is what most candidates miss.

Companies that test this theme

Practice these stories live

Reading STAR answers is the floor. The interview signal is in delivering them out loud, with follow-ups, under pressure. The AI mock interview probes your stories the way real interviewers do.

Start an AI mock interview →