How to answer: “Tell me about a time you had to learn a new technology fast.”

What they’re actually asking

Whatever stack they run, it will change while you work there. This question tests your ramp speed and, more subtly, your method: people who can describe HOW they learn can be pointed at anything.

How to structure your answer

Pick a story with a real clock on it. Describe your method, not just the grind: reading real code before docs, building a toy version first, finding the one person who already knew it. End with what shipped and how fast.

Example answer

“Our payments vendor got acquired and we had eight weeks to migrate to a new provider I'd never touched. I skipped the tutorials, read their example repos, and rebuilt our simplest flow in a sandbox in the first two days — that surfaced the webhook-ordering gotcha the docs never mention. Full migration shipped in six weeks with zero dropped transactions. The method scales: toy version first, real edge cases second.”

What sinks people

• A story with no deadline — "I eventually picked up React" tests nothing
• Listing courses you took instead of things you built
• Forgetting the result. Learning fast only matters if something shipped.