Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Had to Learn Something Quickly Question
Transcript
- Lucas: You're in an interview and the hiring manager asks: 'Tell me about a time you had to learn something new quickly.' Luna: That question feels almost inevitable now, especially if you're interviewing at a tech company or a consulting firm. Lucas: It's everywhere. And it's not just about whether you can learn fast — it's about how you handle uncertainty, how you prioritize, and how honest you are about the gaps in your knowledge. Luna: So what makes a good answer versus a bad one? Lucas: Let me give you a real example. I worked with a product manager candidate last month who was interviewing at a mid-stage SaaS company. They asked her this exact question. Luna: What did she say? Lucas: She talked about a time she had to learn SQL to pull her own data for a product launch. She had zero coding background. The launch was six weeks out, and the data team was swamped. Luna: Six weeks to go from zero to writing queries that actually matter — that's a real constraint. Lucas: Exactly. And she didn't just say 'I learned SQL.' She walked through her process. She started with a specific book recommended by a colleague. She spent two evenings going through the basics. Then she asked a data analyst to pair with her for one hour on a real query. Luna: That's smart — showing she used resources strategically. Lucas: Right. She also admitted that her first query had a bug. She had to debug it with the analyst, and that taught her about joins. By week four, she was pulling her own data confidently. The launch went smoothly. Luna: So the structure is: pick a specific skill, explain your learning process, show the outcome, and include a moment of struggle. Lucas: Perfectly said. The struggle part is key. If you say 'I just learned it, no problem,' it sounds like you either didn't really learn it or you're not being honest. Interviewers want to see that you can navigate the messy middle. Luna: I think a lot of candidates feel pressure to sound like they absorbed everything instantly, but that actually hurts them. Lucas: It does. Because the interviewer knows that in a real job, you'll constantly face new tools, new domains, new processes. They want to hire someone who can be honest about the learning curve and still deliver. Luna: What about industries outside tech? Does this question still come up? Lucas: All the time. I've seen it in marketing, finance, even healthcare administration. Any role where the landscape changes — new regulations, new software, new market dynamics. Luna: So the framework is universal, but the example should be specific to the job you're applying for. Lucas: Right. If you're interviewing at a bank, don't talk about learning a coding language unless it's relevant. Talk about learning a new regulatory framework or a new risk model. Luna: And keep the timeline realistic. Six weeks is great for SQL. Learning a new compliance system might take three months. Lucas: Exactly. Another mistake I see is people picking something too trivial. 'I learned the new coffee machine' — that's not going to cut it. Luna: Or too broad. 'I learned about machine learning' — that's not a specific skill you can demonstrate mastery of in a short time. Lucas: The sweet spot is a skill that's non-trivial but bounded. Something you could credibly go from zero to functional in a few weeks. Like a new analytics tool, a new programming language, a new compliance process. Luna: And you should mention the resources you used. People, books, online courses — it shows resourcefulness. Lucas: Let me give you another example. A friend of mine was interviewing for a marketing role at a fintech startup. They asked him this question. He talked about learning Google Analytics 4 in two weeks because the company was migrating from Universal Analytics. Luna: That's timely and specific. Lucas: He said he watched a series of videos from Google's own training, set up a test account, and ran a campaign tracking event data. He also made a mistake with parameter tagging — double counted some events — and had to redo it. Luna: That's the struggle part. Did he get the job? Lucas: He did. And he told me the interviewer specifically commented that his honesty about the double-counting mistake made the answer credible. Luna: It's a good reminder that the STAR method — situation, task, action, result — works best when you include a real obstacle. Lucas: And the result doesn't have to be a home run. It can be 'I completed the project on time' or 'I was able to contribute to the team's goal.' That's enough. Luna: One thing I'd add: if you're early in your career, you might not have a work example. You can use a class project or a volunteer experience. Lucas: Great point. I had a student who used a time she learned to build a website for a nonprofit using WordPress. She had no web experience. She watched tutorials, asked a friend, and launched the site in two weeks. Luna: That's a perfect example for someone just starting out. Lucas: The key is to show that you can take initiative and be resourceful, even if you're not an expert. Luna: You know, Lucas, this episode is exactly the kind of thing that listeners tell us they find most useful — practical, concrete advice they can use right away. Lucas: I'm glad. And a quick note — a handful of listeners actually chip in monthly through buy me a coffee dot com slash fexingo, and that's what keeps this podcast running without ads. We really appreciate that. Luna: Yeah, it's a small community but it makes a big difference. So if you've gotten value from episodes like this one, consider joining them. Lucas: Alright, back to the question. One more tip: practice your answer out loud. Record yourself. You'll hear if you're rambling or if the timeline is confusing. Luna: Great advice. And time yourself. A good answer to this question should be about 90 seconds to two minutes long. Lucas: That's enough to cover the situation, the learning process, the struggle, and the result without losing the interviewer's attention. Luna: So to recap: pick a specific skill, explain your process, include a moment of honest struggle, and show a tangible result. Lucas: And remember, the interviewer isn't testing whether you already know everything. They're testing whether you can figure things out. That's the real skill they're hiring for.