Latest / The Resume Room with Fexingo: Resume Writing, Cover Letters, and Application Strategy / How to Explain a Job With Drifting Responsibilities on Your Resume
Transcript
- Lucas: We've talked a lot on this show about explaining gaps and exits, but one of the trickiest resume problems I hear about is role drift — when the job you were hired for isn't the job you actually did. Luna: I got a question from a listener named Sarah exactly on that. She was hired as a marketing coordinator at a mid-size software company, but within a month, she was spending sixty percent of her time on Salesforce data entry because the CRM specialist quit and they never backfilled. Lucas: Classic case. The job description said campaign analysis and content creation. The reality was database hygiene. And Sarah's worry, I think, is that if she lists those data entry duties, she looks like an admin, not a marketer. But if she leaves them off, there's a gap in her story. Luna: So what's the first move? Do you adjust the job title? Lucas: I'd be cautious about changing the title unless the company officially changed it. If Sarah calls herself 'Marketing Coordinator & CRM Specialist' when her official title was just 'Marketing Coordinator', that's a red flag if a background check turns up the real title. Instead, I'd focus on how you frame the responsibilities. Luna: Okay, so how does she list the Salesforce work without it sounding like a data entry role? Lucas: The key is to emphasize the outcome, not the activity. So instead of 'Entered leads into Salesforce', she can write 'Managed CRM database to support lead scoring and campaign segmentation, improving follow-up response rate by fifteen percent.' Now it sounds analytical, not clerical. She was really doing data management with a marketing purpose. Luna: That makes sense. What if the role drift was even more extreme — like a project manager who ended up doing customer support? Lucas: That's a bigger shift. In that case, I'd consider a combination resume format. You have a strong summary at the top that tells the reader, 'I was hired as a PM, but I also built the support playbook.' Then under the job, you can separate your bullet points into two clusters: 'Project Management Duties' and 'Customer Operations Contributions.' That way you're not hiding either side, but you're structuring the narrative. Luna: So the clustering approach — that's different from the purely chronological format we usually recommend. Lucas: Right. For most people, chronological is best. But when your job looked nothing like the title, you need to guide the recruiter's eye. A combination format — skills summary followed by a streamlined chronological list — works because you can highlight the most relevant competencies first. Luna: What about the cover letter? Should Sarah mention the role drift there? Lucas: Yes, but briefly and proactively. She can say something like, 'During my tenure, I also took over CRM management, which deepened my understanding of data-driven campaign optimization.' That turns a potential negative — 'I didn't get to do the job I wanted' — into a story of adaptability. Luna: We hear so many stories like Sarah's. If today's episode helped you rethink how to frame a tricky job, consider supporting the show at buy me a coffee dot com slash fexingo. Listener contributions like that are what keep this podcast ad-free and focused on real career questions. Lucas: Absolutely, we appreciate every bit of support. And speaking of Sarah's situation — she also asked about the interview. How does she explain the role drift when a recruiter asks, 'Why did you leave?' Luna: That's a tough one. It can sound like complaining. Lucas: Exactly. I'd advise her to frame it positively: 'I enjoyed the challenge of learning Salesforce, but my passion is campaign strategy, and I want to return to that focus.' That's honest without trashing the old company. Luna: And if the interviewer asks, 'So you didn't get to do what you were hired for?' — that's a direct hit. Lucas: Then you pivot to the skill you gained. 'I learned to be resourceful and solve problems outside my scope. That experience made me a more well-rounded marketer.' Never acknowledge it as a failure. It's a detour that built capability. Luna: What about references? If Sarah lists her manager from that job, and the manager describes her as the 'data entry person' — that could contradict her resume. Lucas: That's a real risk. Ideally, she'd provide a reference who oversaw her broader contributions — maybe the director of marketing rather than the direct supervisor. Or she can prepare her reference by reminding them of the full scope of her work. Most managers are happy to emphasize the positive if you ask. Luna: Let's shift to another listener scenario: a software engineer who was hired to build features but ended up doing QA testing full-time for a year. Lucas: That's a structural role drift. In tech, that's common. I'd handle it similarly: reframe QA as 'quality assurance engineering' and emphasize the tools and processes they built. If they wrote test scripts, that's coding. If they managed bug tracking, that's project management. The title is 'Software Engineer' — the bullets should reflect engineering thinking, not just clicking. Luna: So the principle is: focus on the skills you used, not the task label. Lucas: Exactly. And never lie about the title. If the title genuinely doesn't match, you can use a parenthetical like 'Software Engineer ' — but only if you're prepared to explain it. Luna: One more from the mailbag: a finance analyst who was hired to do modeling but spent nine months on PPT slides for the VP. Lucas: That's a classic. The slides probably contained analysis, so she can lead with 'Developed executive presentations synthesizing financial data to support capital allocation decisions.' That's modeling in disguise. The output was a slide deck, but the input was analysis. Recruiters know that's how the corporate world works. Luna: Right, they're not naive. They know roles morph. Lucas: Exactly. The worst thing you can do is omit the whole job or make it sound like it was something it wasn't. The truth, reframed, is almost always more compelling than a fiction. Luna: Let's wrap with the one piece of advice you'd give to anyone facing role drift on their resume. Lucas: I'd say: control the narrative. You can't control what the job became, but you can control how you present it. Lead with the highest-value outcome. If a recruiter sees 'improved sales follow-up by fifteen percent' and 'managed CRM optimization initiative,' they'll see a problem-solver, not a data entry clerk. Luna: And if the drift was so extreme that you can't salvage it — like you were a graphic designer but you ended up in accounts payable? Lucas: Then consider whether to list the job at all. If it's a short tenure under a year and completely off-brand, you might leave it off and focus on the roles that align with your target. But if it's a longer tenure, you have to address it. Even then, you can angle it toward transferable skills — maybe you designed invoices and reports, which required attention to detail and software proficiency. Luna: Good point. There's always a thread to pull. Lucas: If you've got a role drift story you'd like us to workshop, send it in. We're at fexingo dot com slash resume room — that's one word. And we'll try to tackle it in a future episode.