INTERVIEWS

How to answer "Tell me about a time you had to learn something quickly"

This question asks for one time you had to get up to speed fast, and how you did it. Tell it in four parts: what you had to learn, how you learned it, how you used it and how it turned out. Keep what you had to learn to a sentence or two, and spend most of the answer on how you learned it.

Every new job starts with things you don't know yet, so the interviewer wants to hear how you learn. Who did you ask? What did you learn first, and what did you leave for later? How did you check that you had it right?

The common trap is skipping the part they asked about. "I picked it up in a week" says how fast you learned and leaves out how. Another trap is a story where someone walked you through every step and you followed along. Pick a time when you chose how to learn it.

The structure: what you had to learn, how you learned it, how you used it, how it turned out

Say what you had to learn and by when, in a sentence or two. Then say how you learned it, in order: who you asked, what you read or watched and what you practiced first. Then say when you first used it on real work. End on how it turned out, with a number if you have one.

Aim for about a minute, and no more than two minutes. It's a version of the STAR method with its own part for how you learned it, since that's what the question is about. Write each part as a few words, then answer out loud from those notes.

The short answer

If they want it quick, two sentences will do: "I had [how long] to learn [what] before [the deadline]. I [the two or three things you did], and [how it turned out]." Then stop and let them ask for more.

How to pick the story

Pick something you had to learn by a date, like a system before it went live, a product before a big meeting or a job before the person doing it left.
Pick one where you chose how to learn it: who you asked, what you practiced first and what you left for later.
Pick one where you used it on real work soon after.
Pick one with an ending you can name, like running it on your own by the second week or training the next new hire.
Pick one close to the job you want: software for an office job, a menu for a restaurant job, a new product for a sales job.
If you're a student or a new grad, a class, a research job, a campus job or a club role all count.

Six sample answers

The people and companies below are made up. Read each answer out loud with a timer. Each runs about a minute. Then swap in your own story and keep the shape.

Taking over a coworker's job

"I'm an office assistant at a moving company. Last April, the coworker who ran our dispatch software gave two weeks' notice, just before our busy season. My manager asked me to take it over, and I'd never used it. Most of our jobs were local moves, so I decided to learn those first and leave long-distance moves for later. I asked her for an hour to show me one local schedule from start to finish, and I wrote down each step. After that, I built the next day's local schedule myself every afternoon, and she checked it before it went out to the crews. For how long each job would take, I asked our crew leads. By her last day, she'd stopped finding mistakes. After she left, I ran the local schedule on my own. In June we had up to eight moves a day. My manager handled long-distance moves until I learned them that summer, and I've used my notes to train a backup."

A new technology

"I'm a developer at a company that makes software for gyms. Last year we bought a smaller company, and my team took over its Android app. It was written in Kotlin, a programming language none of us had used, and its next update was due in six weeks. The update was mostly bug fixes, so I started with the five bugs users reported most. For each one, I learned only the parts of Kotlin that each fix needed, from the official docs and the app's own code. The developer who built the app was staying on for two months. I asked her for an hour a week to answer my questions, and she reviewed my first few changes. My first fix took four days, and by the fifth fix I was down to one. Our team sent the update on time with 22 fixes, and I took over the app when she left."

A new product, before a big meeting

"I sell office furniture to companies. In January, we started selling a line of standing desks, and ten days later I had a meeting with a law firm that wanted 40 of them. I'd never sold one. I asked our product manager what buyers ask about most. She named three things: how high the desks go, how much weight they hold and what the warranty covers. I learned those first, from the spec sheets. Then I put one together in our warehouse, so I'd know how long setup takes. I practiced the demo on my manager twice, and she asked me the questions she'd heard from buyers. At the meeting, the firm's office manager asked how loud the motor is, which I hadn't prepared for. I said I'd find out, and I emailed her the number that afternoon. They ordered all 40 desks, and my manager had me walk the rest of the team through the demo."

In a restaurant job

"When I started as a server at a seafood restaurant, I had five training shifts to learn the menu before my first table. The menu had about 40 dishes, and the manager tested every new server on which ones had shellfish, nuts or gluten. I made a flash card for each dish, with what was in it on the back, and I went through them before every shift. At family meal, I asked the cooks to let me taste anything I hadn't tried, so I could describe it to guests. I also asked the kitchen manager to quiz me on five dishes at the end of each shift. I passed the menu test on my fourth shift, a day early. On my first night with tables, a guest with a shellfish allergy asked what she could order. I named four dishes right away, then checked them with the kitchen, as we did for every allergy. Two months later I was training new servers with my cards."

Without formal training

"After six years as a bank teller, I took a job in the claims department of a car insurance company. The department had no formal training, so new hires learned on the job. Most took about six weeks to handle simple claims on their own. Two people were out, so my manager needed me doing that by the end of my first month. I asked her which simple claims came in most. She said fender benders and cracked windshields. I read ten closed files of each from start to finish, so I could see how they usually went. I kept a list of every word or step I didn't know, and each afternoon I took it to our senior adjuster for ten minutes. By my fourth week, I was handling both kinds on my own. That list became a glossary, and our next new hire got it on her first day."

As a student

"In my junior year, I got a job as a research assistant in a psychology lab. Two weeks in, the professor asked me to run the statistics for a study she was presenting at a conference in a month. The lab used R, a programming language for statistics, and I'd only used Excel. I asked the graduate student who'd done it before for her code from the last study. I worked through the first lessons of a free online course in R. Then I ran her code on the last study's data one line at a time, until I could get her numbers myself. I wrote a note next to each line saying what it did. After that, I ran the new study's data and asked her to check my results. She found one mistake, and I fixed it. The professor had her tables a week before the conference, and I ran the statistics for the lab's next two studies."

What to leave out

"I'm a fast learner." Give one time instead.
A story where someone walked you through each step and you followed along. Pick one where you chose how to learn it.
A list of every tool you've learned. Tell one story.
Complaints about having no training. Say it in a sentence, as in the claims answer, then say what you did.
A shortcut that broke a rule, like skipping a required training or a safety step.
Private details, like a customer's name, your company's code or numbers it keeps private.

How to tell it

How you sound matters too. If you rush through how you learned it, the interviewer can miss the part they asked about.

Give the time frame early, like "I had ten days." The deadline is what makes it quick.
Say your steps in order. Words like "first", "then" and "the second week" help the listener keep track.
Say what you did as a plain fact, like "I read ten closed files." "I kind of looked through some files" sounds unsure. If you hedge a lot, see how to sound confident.
Slow down for how it turned out, and give the number. If your answers tend to run long, see how to stop rambling.

If they ask "How did you approach it?"

That follow-up asks for your steps, so give them in order: "First I asked [who] what mattered most. Then I [what you practiced]. Then I [how you checked your work]." If your answer already covered them, give the one step that helped most and say why.

If they ask "How do you learn new things?"

That version asks what you usually do. Give your steps, then one short example: "I find out what I need first and learn that part. I ask someone who knows it, and I try it on real work early, with someone checking." Then add, "For example, when I..." and give a two-sentence version of one of your stories.

The same question in other words

"Describe a time you had to learn something new quickly" and "Tell me about a time you had to learn a new skill quickly" ask the same thing. Answer them the same way. "Tell me about a time you learned something new" is broader, since it doesn't ask how fast. Use the same four parts, and if there was a deadline, say it.

"Describe a time where you had to learn something quickly to achieve success. What was the outcome?" wants the result, so end on it with a number. "Tell me about a time you learned something new without formal training" wants a time you learned on the job, with no class, like the claims answer. "Tell me about a time you had to learn a new technology quickly" works like the developer answer. If the new thing came with a change you didn't choose, see how to answer "Tell me about a time you had to adapt to change".

Practice it out loud

A chatbot can tidy up the story. You still have to say your steps in order without rushing, and you can't tell how that sounds until you hear yourself. So practice the way you'll give it: out loud and on a timer.

Write the four parts: what you had to learn, how you learned it, how you used it and how it turned out. A few words each.
Answer from your notes into your phone's voice recorder, and time it.
Play it back and count your steps. If a listener couldn't tell what came first, add "first" and "then" and say it again.
Check that you said the deadline and how it turned out, with a number if you have one.
The next day, answer without the notes. Then have a friend ask the usual follow-ups: "How did you approach it?" and "What would you do differently?"

For the rest of the interview, there's a 15-minute routine in how to practice for an interview by yourself. The other common questions are in how to answer interview questions.

Practice it with an AI coach in Charisma Lab

Charisma Lab is a speaking coach on your iPhone. In Speak, tap INTERVIEW under PRACTICING FOR. Then tap the center, say what the job is and tell the coach you're practicing "Tell me about a time you had to learn something quickly." Tell your story one part at a time, since a pause of about two seconds ends a take. You hear each take played back. When something is off, the coach says what to fix, then the mic opens again.

To mark the steps of how you learned it, try Train's Structure Your Points. It's open from the start in the Clarity track. It shows you a flat line, like "The plan is to align, build, and launch." You say it again with structure words. A take passes when its transcript has at least two of the twelve words and phrases the app checks for, such as "first", "then" and "finally". Setup is free. If you tap MAYBE LATER when it shows the price, then SKIP FOR NOW when it asks you to sign in, setup goes on to a short live session with the coach. After setup, the app needs Pro, which is $14.99 a month in the US. See pricing.

Get the app

FAQ

How long should my answer be?

About a minute, and no more than two minutes. Keep what you had to learn to a sentence or two, and spend most of the rest on how you learned it.

What if I can't think of a time?

Your first weeks in any job count. So does a new system, a task you took over from someone or a class you joined late.

What if I didn't learn it as fast as I needed to?

You can still use it. Say how far you'd gotten by the deadline and when you caught up. Then say what you did to cover the gap, like asking someone to check your work.

Can I use something I learned outside work?

Yes, if you don't have a work or school story that fits. Pick one with a date and steps you can name, like building a website for a relative's shop before it opened. When you have a work story, use it, since it shows how you'd learn this job.

What if they ask what I'd do differently?

Have one thing ready, like asking for help a day sooner or taking notes from the first day. Say it in a sentence, then stop.

How is this different from "Tell me about a time you had to adapt to change"?

They're close. A change story is about adjusting to a new way of doing things that you didn't choose. A learning story is about how you got up to speed, step by step, before a date. For this question, spend most of the answer on how you learned. There are six change answers in how to answer "Tell me about a time you had to adapt to change".

More practice guides

Updated November 4, 2026.