Behavioral: Learn and Be Curious

## Behavioral: Learn and Be Curious Tell me about a project where you had to **learn a large amount of new material from scratch** in order to get the work done. Walk me through what the project was, *how* you actually went about learning what you didn't know, and what the outcome was. ```hint Make the learning method concrete The interviewer's real probe is the *mechanics* of how you learn. Be ready to name specific tactics — reading source code, writing small throwaway tests/spikes to verify understanding, asking the right person the right question, and digging through design docs/RFCs — not just "I studied hard." ``` ```hint Structure with STAR Frame it as Situation → Task → Action → Result, but spend most of your airtime on the **Action**: the specific, repeatable learning techniques you used and *why* you chose each. ``` ### Constraints & Assumptions - This maps to Amazon's **Learn and Be Curious** Leadership Principle. - Pick a single, real, recent example you owned — depth beats breadth. - The interviewer **will** push past the narrative to ask how you concretely "learned it": expect a direct follow-up demanding the method (read the code? write small tests? ask people? read design docs?). ### Clarifying Questions to Ask - (To yourself, while picking the story) Was the new material a **technology/domain** I'd never touched, or a **system** so large no one fully understood it? Either works; be clear which. - Should I emphasize the *speed* of ramp-up (tight deadline) or the *depth* of mastery I reached? Read which the interviewer cares about and lean in. - Is a story where I learned something and it **partially failed** (then I corrected course) acceptable? Often yes — it shows curiosity and adaptation — as long as the learning method is the star. ### What a Strong Answer Covers ```premium-lock What a Strong Answer Covers ``` ### Follow-up Questions - Concretely, *how* did you learn it — did you read the code, write small tests to probe behavior, ask people, read design docs? Walk me through one specific thing you didn't understand and exactly how you resolved it. - How did you know when you'd learned *enough* to act, versus needing to keep going? How did you avoid both under- and over-investing in learning? - What did you do with the knowledge afterward — did you write it down or share it so the next person didn't have to start from zero? - Tell me about a time your initial understanding turned out to be wrong. How did you discover it, and what changed in how you learn because of it?