0 day streak

BEHAVIORAL · CURIOSITY AND GROWTH

Tell me about something you had to learn quickly for a project: sample answer

Whether you can learn something unfamiliar quickly and on purpose: a plan for what to learn first, using people and code as well as documents, and applying it to real work. Curiosity should lead to a result, not just a course you finished.

Also asked as

  • Tell me about the hardest feedback you have given or received.
  • Tell me about a project that failed. What did you learn?
  • Tell me about something you had to learn quickly for a project.
  • What is something you explored on your own that made you better at your job?
  • How have you used AI tools in your work, and how did you check their output?

The short version: Show something you learned on your own and how you used it at work.

Sample STAR answer

An invented example from typical software engineering work, about 270 words, around two minutes spoken. Use the structure, not the story: yours should be real.

Situation The engineer who owned our team's pricing service moved to another team with two weeks' notice. The service was written in a language nobody else on the team knew, and it was due for a change to support a new discount type in five weeks.

Task I volunteered to take it over. I had never written that language, so I needed to become safe on call for the service within two weeks and ship the discount change on time.

Action I made a plan around the service rather than the language. In the first three days I read the code path for a single price request from start to finish and drew it, writing down every language feature I did not understand. I learned only those features first, from the official tutorial and by writing small throwaway programs. I booked three one-hour sessions with the departing owner and used them only for questions I could not answer from the code, such as why certain decisions were made. To learn by doing, I fixed two small open bugs in my first week and asked an engineer from another team who used the language daily to review them. I kept a notes page of patterns and pitfalls, which became the service's onboarding guide.

Result I took over on-call for the service after two weeks and shipped the new discount type a week early, with no incidents. A second teammate onboarded in four days using my notes. I still use the same approach for unfamiliar systems: trace one real request, learn what it needs, and ship something small in week one.

Weak answer vs strong answer

Weak

"I love learning new things. Recently I took an online course on a new programming language in my free time, and I found it very interesting."

Why it scores low: It shows interest but no application. There is no work problem, no deadline, no method for learning fast and no result anyone else benefited from.

Strong

A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show something you learned on your own and how you used it at work.

How the story changes with level

SDE 1

At SDE 1, learning a new framework, tool or part of the codebase quickly to finish your task is the right scope. Show your method and the result.

Senior and staff

At senior or staff level, show that you learned a new area well enough to make design decisions in it, and that you made it easier for others to learn after you.

SDE 1 interviews · Senior interviews · Staff interviews

Follow-up questions interviewers ask

  1. How did you decide what to learn first?Learn what the real code needs, not the whole language.
  2. How did you know you were ready for on-call?Name a test: fixing real bugs and walking through past incidents.
  3. What is something you are learning right now?Have a current, specific answer and how you are using it.
  4. How do you use AI tools when learning, and how do you check them?Use them to explain or draft, then verify against code, tests and docs.

Amazon Leadership Principles that test this

Learn and Be Curious · Tell me about something you learned on your own that improved your work.

Never stop learning, keep improving yourself, and be curious about new possibilities and how things work.

Situation A monthly finance report our team owned took six hours to run and sometimes timed out. The usual fix had been to give the database more memory.

Task I was curious why one query could be that slow, and I realised I did not really understand how the database chose to run queries.

Action Over two weeks I spent a few evenings learning how the query planner works: reading the documentation, then running the report's queries with the planner's explanation turned on. I found the planner was using a poor plan because our table statistics were badly out of date after a large data import, and one join was doing a full scan of 200 million rows. I refreshed the statistics, added one composite index and rewrote a subquery as a join. I wrote a one-page explainer with three examples from our own queries and ran a 30-minute session for the team.

Result The report went from six hours to twelve minutes and stopped timing out. Two teammates used the same method the next month to fix slow queries in their own services.

Tip: Show curiosity that led to a result at work, and ideally to others learning too.

All 16 Amazon Leadership Principles with sample answers

Companies that test this

Prepare your own

Write your story in the story bank and tag it "Curiosity and growth"; it will show up against every company value that tests this theme.

Related: Disagreement and candor · Failure and learning · High standards

All behavioral themes · How the behavioral round is scored