Latest / The Resume Room with Fexingo: Resume Writing, Cover Letters, and Application Strategy / How to Explain a Job You Took for the Experience
Transcript
- Lucas: So Luna, you know that classic resume dilemma where someone took a job primarily for the experience, not for the title or the pay? We get this question a lot, and it's a real puzzle. Luna: Yeah, I've seen that. It's like, how do you spin 'I took this because it was the only way to learn a skill' without sounding desperate or like you're underselling yourself? Lucas: Exactly. And it's more common than you'd think, especially in fields like marketing or tech where the entry-level path can be a maze. Today I want to dig into a specific case: a marketing coordinator who took a junior analyst role at a fintech startup to get data skills. Luna: That's a great example. What was the situation? Lucas: So she had two years in marketing at a mid-size agency, but every time she applied for a data-driven marketing role, she got passed over for lack of analytics experience. So she took a junior analyst job at a startup, a title step down, likely a pay cut, but she knew it was the fastest way to build that skill set. Luna: Right, and now she's applying for her next role and needs to explain that move without it looking like a random detour. Lucas: Exactly. The first thing I tell her — and anyone in a similar spot — is to reframe the narrative. On the resume, that junior analyst role isn't 'junior' anything. It's the place where you acquired a specific, high-demand competency. So instead of listing 'Junior Analyst' as the title, she could write 'Data Analyst' and then use the bullets to prove that's what she actually did. Luna: But isn't that a bit risky? Changing the title? Lucas: You have to be honest, but you can be strategic. The job title on the resume doesn't have to match the official one to the letter, as long as it accurately reflects your responsibilities. So 'Data Analyst' is fine if that's what she did, even if her official title was 'Junior Analyst'. The key is the bullets underneath. Luna: And what kind of bullets are we talking about? Because 'learned SQL' is not going to cut it. Lucas: No, it won't. You need to show impact. For example, instead of 'Built dashboards in Tableau', write 'Developed a customer churn dashboard that identified three key risk segments, leading to a 12 percent reduction in monthly churn over two quarters.' Luna: That's concrete. But what if she didn't have a metric like that? What if the experience was more about learning the ropes? Lucas: Then you focus on process and scope. Maybe she automated a manual report that saved the team five hours a week. Or she was the one who set up the A/B testing framework for the marketing emails. Those are achievements, even if they're not tied to revenue. Luna: So the language shifts from 'learned' to 'implemented' or 'streamlined'. Lucas: Exactly. And that's the core: the resume should show that you didn't just absorb experience — you produced something with it. That's what makes a 'learning' role look like a strategic career move. Luna: I also think it helps to address the salary question head-on. Because a recruiter might see that pay cut and wonder if you're going to jump ship the moment someone offers you more money. Lucas: That's a fair point. In the interview, you can say something like, 'I took that role because the learning opportunity was more valuable to me at this stage than a higher salary. I knew the skills I'd gain would pay off in the long run.' That reframes it as a deliberate investment, not a compromise. Luna: And now, when you're negotiating for the next role, you have a stronger story. You're not just asking for a raise, you're asking to be compensated for skills you now have. Lucas: Right. And that's a powerful position. But there's another angle: the cover letter. That's where you can really tell the narrative arc — from marketing coordinator to data analyst to, say, a marketing analytics manager. The resume is the evidence, the cover letter is the story. Luna: Do you have an example of how to phrase that in a cover letter? Lucas: Sure. Something like: 'When I realized my marketing roles would plateau without a strong data foundation, I sought out an analyst position at a fintech startup. There, I built the skills that now let me combine creative strategy with rigorous measurement.' It acknowledges the detour but frames it as a calculated step toward a clear goal. Luna: That's smooth. And it doesn't apologize for the lower title or salary. Lucas: No, it doesn't. And that's important. Confidence matters. If you're ashamed of the experience, it'll show. But if you own it as a smart career decision, recruiters will see it that way too. Luna: And what about the concern that it looks like a step backward? Some people might worry about the title regression on paper. Lucas: That's why the functional format can work well here. Instead of a strict chronological list, you can group your experience by skill area — say, 'Data Analysis' and 'Marketing Strategy' — and then list the roles under each. That way, the junior analyst position isn't a step down, it's a component of your data analysis skill set. Luna: But doesn't that raise red flags with some recruiters who prefer chronological? Lucas: It can, but it's a trade-off. You have to choose the format that tells the best story. And if you do use a hybrid format, the dates are still there, so you're not hiding anything. The emphasis is just on the skills, not the progression. Luna: I think it's also worth mentioning that this 'experience for experience' move is more common in tech and startups, where the landscape is always shifting. Like, people often take roles at a startup to learn a specific stack or a new methodology. Lucas: Absolutely. In fast-moving fields, the ability to say 'I've worked in a high-growth environment and learned how to do X' can outweigh a traditional title. Recruiters are often more interested in the skills and the adaptability than the exact career ladder. Luna: And that's a good thing for our listener who might be in that exact situation right now. Lucas: Exactly. So to recap: reframe the title to reflect the actual work, use strong achievement bullets to prove you produced value, tell the story in the cover letter, and consider a functional format to emphasize skills over chronology. Luna: And in the interview, be ready to explain the salary difference with confidence. Lucas: Right. And if you're listening and you've taken a role for the experience, you're not alone. Many successful careers are built on those stepping stones. The key is to present it as a deliberate choice, not a fallback. Luna: And we should mention, if you're enjoying these deep dives into resume strategy, and they've helped you think through a career move, consider supporting the show. It's what keeps us ad-free and independent. Lucas: Yeah, a coffee goes a long way. You can do that at buy me a coffee dot com slash fexingo. Every little bit helps us keep doing this. Luna: It really does. And it helps us plan more episodes like this one. Lucas: So, back to the example we were looking at. One more thing I'd add: don't forget to include any side projects or freelance work that came out of that experience. If she built a small dashboard for a local nonprofit while learning SQL, that's another proof point. Luna: Good point. That shows initiative and that you can apply the skills outside your day job. Lucas: Exactly. And that's the kind of thing that can tip the scale in your favor. So, whether you're five years in or just starting, remember: every job is a chapter, and you control how it's written. Luna: Well said. And if you have a tricky resume situation you'd like us to tackle, reach out. Lucas: We read everything. Until next time, keep building that story.