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
Transcript
- Lucas: So you're in an interview, and the hiring manager says, 'Tell me about a time you had to learn something new quickly.' This question shows up constantly, and I think a lot of candidates fumble it because they go too vague. Luna: Right, they say something like 'I'm a quick learner' without a story to back it up. Lucas: Exactly. Today we're going to build a concrete answer using a real example. Let's say you're a marketing coordinator applying for a data analyst role. You need to show you can pick up SQL in two weeks to pull campaign performance data. Luna: That's a specific scenario. Why do you think hiring managers love this question? Lucas: Because every job involves learning something new. They want to see your process — how you identify what you need to know, how you prioritize, and how you actually acquire the skill without hand-holding. Luna: So it's less about the skill itself and more about your learning strategy. Lucas: Exactly. The framework I recommend is PAR — Problem, Action, Result. But let's be specific. The problem: you're a marketing coordinator, and your team's database analyst just left. You're asked to pull weekly campaign performance reports, but you've never written a line of SQL. Luna: That's a high-pressure situation. How do you even start? Lucas: The action part is where most people go wrong. They say 'I took an online course.' That's too generic. Instead, name the resource. Say 'I found a free tutorial called SQL for Marketers on Mode Analytics, and I spent two evenings working through it. Then I asked a colleague in engineering to review my first query.' Luna: So you're showing initiative but also that you know when to ask for help. Lucas: Right. And the result: within two weeks, you were running the weekly report in thirty minutes instead of the four hours it took to do it manually in Excel. That's a concrete number. And you can add that the reports helped the team reallocate budget to the top-performing campaigns. Luna: I like that you mentioned a colleague. Some candidates think they have to say they did it entirely on their own, but collaboration is a plus. Lucas: It shows you're resourceful. Now, let's talk about what not to do. Don't say 'I learned it overnight' — that sounds like you're exaggerating. And don't pick something too easy, like learning a new software that everyone picks up in a day. Luna: What about if the skill you learned was something like public speaking? Is that too soft? Lucas: It can work if you frame it as learning a methodology — like Toastmasters or a specific presentation framework. But I'd lean toward a technical or analytical skill because it's easier to quantify. Even learning a new industry regulation can work. Luna: Let me push back a little. What if the candidate genuinely hasn't had to learn a technical skill quickly? Maybe they learned a new language or a new process at a retail job. Lucas: That's fine. The key is the structure. A retail example: learning a new inventory management system in a weekend. The problem could be that the store was switching systems and you were the only one scheduled to train others. Action: you stayed late, read the manual, created a quick reference sheet. Result: you trained three coworkers and the store had zero inventory errors during the transition. Luna: That's solid. And it shows leadership too. Lucas: Exactly. Now, I want to share a personal story. When I first started as a business journalist, I had to cover a data-heavy beat. I knew how to write, but I didn't know Python. I had a project that required pulling data from an API — I had two weeks. Luna: That's similar to our marketing coordinator example. Lucas: I bought a book called 'Automate the Boring Stuff with Python' — I know, cliché — and I worked through the chapters on web scraping and APIs. I also set up a daily check-in with a data scientist friend who answered my dumb questions for fifteen minutes each morning. Luna: How did it turn out? Lucas: I built a script that pulled the data and formatted it into a spreadsheet. The project was published on time, and my editor started sending me more data-driven stories. That story became an answer I've used in interviews. Luna: So you're saying it's okay to tell a story from a previous job, even if it's not exactly the same as the role you're applying for. Lucas: Absolutely. The skill is transferable. Now, here's a tip that not many people talk about: in your answer, mention what you decided NOT to learn. Because part of learning quickly is prioritizing. Luna: Oh, that's interesting. Can you give an example? Lucas: Sure. In my Python story, I could have tried to learn object-oriented programming, data visualization, and machine learning all at once. But I intentionally ignored all of that and focused only on the specific task: pulling data from an API and writing it to a CSV. That focus is what let me get it done in two weeks. Luna: That shows strategic thinking. I think a lot of candidates try to show how much they learned, but more isn't always better. Lucas: Right. The hiring manager wants to see that you can learn efficiently, not exhaustively. Luna: One more thing — how long should the answer be? I've heard the STAR method can drag on. Lucas: Keep it under two minutes. Problem: 20 seconds. Action: 60 seconds. Result: 30 seconds. And leave a little room for the interviewer to ask a follow-up. Luna: That's helpful. So practice your story out loud and time it. Lucas: Exactly. And if you're the interviewer, listen for those specific resources and outcomes. A vague story is a red flag. Luna: Alright, so let's recap. Pick a real situation, use a specific resource, quantify the result, and mention what you chose not to learn. Lucas: And if you've been following this show, you know we've covered a lot of behavioral questions. But this one — the learning question — is unique because it tests your meta-cognition. How do you think about learning itself? Luna: It's also a question that can come up in almost any interview, from entry-level to executive. Lucas: Speaking of the show — we want to keep these episodes free and ad-free. No ads, no sponsors. If you've ever found our advice useful, especially if it helped you think through a career move or nail an interview, you can support the show at buy me a coffee dot com slash fexingo. Luna: That's right. It's a simple way to keep us going without any interruption to your listening. Lucas: And we appreciate it. Now, back to the learning question — let's talk about how to avoid a common pitfall: choosing a story that's too old. Luna: How old is too old? Lucas: I'd say more than five years, unless it's a foundational skill. You want to show that you're currently capable of learning, not that you were capable five years ago. Luna: Good point. So if you're a career changer, pick something from the last year or two. Lucas: Exactly. And one last tip: if you're asked this question in a panel interview, look at each person briefly as you tell the story. It keeps everyone engaged. Luna: I think we've given listeners a solid template. Any final thoughts? Lucas: Just this: the best answers to this question don't just show that you can learn fast — they show that you know what to learn and what to skip. That's a skill every hiring manager wants.