Latest / The Resume Room with Fexingo: Resume Writing, Cover Letters, and Application Strategy / How to Explain a Job You Were Underqualified For
Transcript
- Lucas: So we get a lot of questions about gaps and terminations and side hustles, but there's one resume problem we haven't really dug into yet, and it's the one I think a lot of people quietly struggle with. Luna: Which one is that? Lucas: The job you got even though you were clearly underqualified. Not the one you faked your way into, but the one where the posting asked for three years of experience and you had maybe six months of adjacent exposure. You applied anyway, you impressed someone, and you got the offer. Luna: And then you had to learn everything on the fly. Lucas: Exactly. So how do you put that on a resume without either overselling or underselling yourself? I've got a concrete example we can work through, and it's a story I've seen play out a few times. Luna: Let's hear it. Lucas: There's a woman I knew in Chicago, let's call her Maria. She was a banqueting manager at a big hotel, so she handled event logistics, staffing, budgets, client communications, all that. She got laid off in early 2025, and after a few months of searching, she landed a junior data analyst role at a regional logistics firm. No formal analytics degree, no SQL bootcamp, nothing. Luna: How did she sell that in the interview? Lucas: That's the thing. She didn't sell it as 'I'm a data analyst.' She sold it as 'I know how to run a complex operation, and I've already taught myself the tools.' The resume she used framed her hotel work through the lens of data she was already managing — banquet counts, labor costs, vendor pricing, even satisfaction survey scores. Luna: So she reframed her old job as a data-adjacent role. Lucas: Right. But here's the key move — she also added a short 'continuous learning' line at the bottom of her resume: 'Completed online coursework in SQL and Excel, and built a personal project analyzing public transit data.' That line did a lot of heavy lifting. Luna: Because it showed she wasn't just hoping to learn — she'd already started. Lucas: Exactly. And that's what I want to drill into today. The underqualified resume needs a 'learning narrative.' You're not hiding the gap; you're telling a story of rapid, self-directed acquisition. That's an asset, not a flaw. Luna: But isn't there a risk that highlighting the learning makes you look less experienced? Lucas: You have to balance it. The learning line is one line — maybe two. The rest of the resume has to show that you already brought something valuable. In Maria's case, the bullets focused on revenue responsibility and operational efficiency, not on 'I attended a tutorial.' Luna: So the learning is the garnish, not the main course. Lucas: That's a good way to put it. And before we go further, I want to take a quick beat here. This episode is brought to you by our listeners — literally. The Resume Room is ad-free, and that's because people who find value in these conversations chip in to keep it that way. If you've ever gotten a job or avoided a resume mistake because of something we said, and you want to support the show, you can do that at buy me a coffee dot com slash fexingo. No pressure, no perks, just knowing you're keeping this independent. We appreciate anyone who's done that already. Luna: Yeah, it genuinely helps us keep making these episodes without a sponsor breathing down our necks. Lucas: So, back to Maria. Once she got the job, the next problem was how to describe it on her resume when she updates it later. Because now she's actually doing the work, but she's still aware she came in underqualified. Luna: That's a common trap — you either downplay your role or you inflate it. Lucas: The fix is to write bullets that reflect what you actually did, not what the job description said you'd do. So instead of 'managed data pipelines,' she wrote 'built automated reports in SQL and Excel that cut weekly reporting time by 40 percent.' That's a true statement, and it's impressive without claiming years of experience. Luna: And it gives the interviewer something concrete to ask about. Lucas: Exactly. And here's a subtle point: when you're underqualified, you often learn faster because you're in survival mode. That's a story you can tell in an interview — 'I was thrown into the deep end and I taught myself to swim.' But on the resume, you have to show the swimming, not the drowning. Luna: So what if you didn't actually learn much? What if you coasted through the role? Lucas: Then you have a different problem, and honestly, the resume isn't the fix. But if you're in that situation, look for any small project you took on, any tool you picked up. If there's genuinely nothing, then you might have to consider whether that job is worth featuring at all. Luna: You mean leaving it off entirely? Lucas: Sometimes yes. If the role was a dead end and you didn't grow, it might be better to keep the gap and explain it as a period of exploration rather than highlight a job that shows no development. But that's a last resort. Most people have at least one or two wins they're not giving themselves credit for. Luna: That's a good point. I remember a friend who took a customer service job at a software company just to get a foot in the door. She was way underqualified, but she volunteered to write help articles and ended up in a technical writing role. Lucas: That's a perfect example of turning a low bar into a launchpad. On her resume, she could emphasize the writing she did, not the call center metrics. The underqualified entry is the backstory, but the transferable skills are the headline. Luna: So what's your formula for writing a bullet point in this situation? Lucas: Three parts. First, start with an action verb that's honest. 'Assisted,' 'supported,' 'contributed' are fine if that's what you did. Second, include a specific result or task that shows impact. Third, if you used a tool or skill you learned on the job, name it. So instead of 'helped with reports,' write 'assisted senior analyst in building weekly sales dashboards using Power BI, learning the tool on the job.' Luna: And you don't have to mention 'on the job' in the resume, right? Lucas: You don't need to, but sometimes it's smart. Saying 'learned on the job' signals that you're a fast learner, which is a real asset. But you have to be careful not to overdo it. One or two bullets like that, max. The rest should show what you already knew. Luna: I think the trick is to make the gap feel like a deliberate stepping stone, not a hole you fell into. Lucas: Exactly. And that's what I want listeners to take away today. If you've been in an underqualified role, you don't have to apologize for it. You just have to frame it as a learning sprint — and show that you finished the sprint with new skills. Luna: And if you're applying for a new job now, how do you handle the interview question about your background? Lucas: Own it. Say something like, 'I entered that role without the typical background, but I closed the gap quickly because I'm comfortable being uncomfortable.' That's a line that lands well, because it's honest and confident without being arrogant. Luna: I like that. It turns a potential negative into a character reference. Lucas: The thing is, hiring managers love a self-starter story. They'd rather have someone who's hungry and proven they can learn than someone with a perfect pedigree who might coast. So don't hide the underqualified chapter — use it. Luna: And if you're job hunting right now and feel like you're not qualified enough, what's the one thing you should do today? Lucas: Pick one skill that's adjacent to your target role and start learning it. It doesn't have to be a degree — a free online course, a small project, a blog post. Then add that to your resume as a 'continuous learning' line. That's the first step to building your learning narrative. Luna: That's actionable. And it's a good way to end today's episode. Thanks for listening, everyone. Lucas: Yeah, if you have a resume question you want us to tackle, shoot us an email or leave a comment. We read everything. Until next time.