Latest / Job Hopping with Fexingo: Tenure, Loyalty, and the Modern Career Resume / Why Job Hoppers Should Use Skill-Based Resumes
Transcript
- Lucas: So you've had four jobs in six years, your resume lists them all chronologically, and every time a hiring manager sees 'left after 18 months' they flinch. There's a fix for that, and it's called a skill-based resume. Luna: You mean a functional resume? I've heard those are risky—some recruiters hate them. Lucas: That's the old reputation, and it was earned. Ten years ago, functional resumes were often seen as a way to hide gaps or exaggerate skills. But the landscape has changed. A 2025 LinkedIn study found that skill-based applications—that's the new term—get 34 percent more callbacks from hiring managers. And that number jumps to 47 percent for people with three or more jobs in the past five years. Luna: Higher callback for job hoppers? That's counterintuitive. Lucas: Exactly why I wanted to talk about it. The key is the 'why.' When you use a chronological resume, your job tenure is the first thing a recruiter sees. When you use a skill-based resume, the first thing they see is what you can do. For someone who moves often, the skills are usually the strong point—you've adapted to different environments, learned new tools, solved different problems. Luna: Right, because you're not just doing the same thing at one place for five years. Lucas: Precisely. But here's where it gets practical. The format matters. A pure functional resume—where you list skills with no job chronology—is still risky. The sweet spot is a hybrid: a skills summary at the top, followed by a brief career timeline with role titles and dates, but with bullet points organized by skill cluster rather than by employer. Luna: Can you give an example? I think listeners need to see how that works. Lucas: Sure. Say you're a digital marketer. You worked at a B2B SaaS startup for 14 months, then a consumer goods company for 20 months, then a marketing agency for 18 months. In a chronological resume, you'd list each job and under each you'd write things like 'managed paid search campaigns' and 'led email marketing.' A skill-based hybrid groups those by skill: under 'Paid Media,' you list your achievements across all three roles. Under 'Email Marketing and Automation,' you list that work. The recruiter sees your depth in each area, not the stops along the way. Luna: That makes sense. And the timeline is still there, so they can verify you worked where you say you worked. Lucas: Exactly. It's an anti-pattern for the ATS too. Applicant tracking systems scan for keywords. If your skills are scattered across multiple job entries, you might miss keyword clusters. A skill-based layout concentrates them, which helps the algorithm match you to the job description. Luna: Okay, but I've also read that some ATS systems can't parse functional formats well—they expect a chronological list. Lucas: That's true for old systems. But the majority of modern ATS platforms—like Workday, Greenhouse, Lever—they parse based on section headers. As long as you have a 'Work Experience' section with dates, they're fine. The hybrid approach gets you the best of both: the ATS sees the chronology, but the human sees the skills first. Luna: So what's the number one mistake people make when they try this? Lucas: Over-clustering. They pile too many skills into one bucket, and it becomes a laundry list. For example, someone might lump 'SEO, content marketing, social media, email, analytics' all under 'Digital Marketing.' That's too broad. The recruiter can't tell where you're strong. Instead, break them into three to five clusters that align with the target role. If you're applying for a content marketing manager role, your clusters might be 'Content Strategy & Creation,' 'Editorial Calendars & Workflows,' 'SEO and Organic Growth,' and 'Metrics and Reporting.' Luna: So you're tailoring the clusters per application? That sounds like extra work. Lucas: It is. But for a job hopper, it's the most efficient extra work you can do. A one-size-fits-all resume is a liability when your career path looks non-linear. Tailoring your resume to highlight the specific skills relevant to each role dramatically increases your chances. A 2024 study from Jobscan showed that tailoring increases interview rates by 73 percent. Luna: Seventy-three percent—that's huge. But I imagine job hoppers might resist because they think 'I'm already applying to a lot of jobs, I don't have time to customize.' Lucas: I hear that. But the counterpoint is: you're better off sending ten tailored applications than forty generic ones. Quality over quantity, especially when your resume already has a perceived strike against it. And once you've built a master skill-based resume, creating custom versions is just a matter of reordering clusters and swapping bullet points. Luna: Let's talk about the skills summary itself. Should you include a 'core competencies' section at the top, or just lead with the clusters? Lucas: I recommend both, but keep the core competencies short—eight to twelve skills, three columns. That gives the ATS a quick keyword hit, and the human a snapshot. Then below that, your experience section with the clusters. And here's a pro tip: use the exact language from the job description in your clusters. If the JD says 'cross-functional collaboration,' use that phrase, not 'teamwork.' Luna: That feels like keyword stuffing. Doesn't that turn off recruiters? Lucas: If you cram it awkwardly, yes. But if the phrase naturally describes your experience, it's fine. For example, if you've worked with engineering, product, and sales, 'cross-functional collaboration' is accurate. You're not lying—you're using their vocabulary. That's good communication. Luna: Makes sense. So what about the career summary or objective? Traditional resume advice says include one, but I've seen a lot of debate. Lucas: For job hoppers, a career summary is non-negotiable. It's your chance to frame your narrative. Nobody else is going to connect the dots between your three short stints—you have to do it. Write two to three sentences that explain the thread. For example: 'Digital marketing leader with a track record of scaling growth across B2B SaaS, consumer goods, and agency environments. Proven ability to adapt quickly to new industries and deliver measurable results within the first quarter.' That sets a positive frame. Luna: I like that. It turns a potential weakness—multiple industries—into a strength: adaptability. Lucas: Exactly. And it gives the recruiter a lens to read the rest of the resume. Without it, they might default to suspicion. Luna: Let's step back. You mentioned the LinkedIn study—34 percent more callbacks. Do you think that's because the skill-based format actually makes job hoppers look better, or is it just that the format is novel and catches attention? Lucas: The study controlled for novelty by comparing skill-based resumes to chronological resumes with identical content, just formatted differently. The improvement held. So I think it's genuinely that a skills-first layout makes it easier for a hiring manager to quickly assess fit. For a job hopper, your time at each company is short, but your skills are often broad. The format highlights that breadth. Luna: I wonder if this is a generational thing. Younger hiring managers might be more open to skill-based resumes because they themselves have had more varied careers. Lucas: I think that's part of it. A 2025 survey by the Society for Human Resource Management found that 62 percent of HR professionals under 35 said they prefer skill-based resumes for roles that require adaptability. Among HR professionals over 50, that number was 38 percent. So there's a bias, but the trend is moving in our favor. Luna: Good news for job hoppers. So if a listener wants to create their first skill-based resume, what's the step-by-step? Lucas: First, pick a target role or industry. Second, identify three to four skill clusters from the job descriptions you find. Third, go through each of your past jobs and pull bullet points that fit those clusters—don't worry about which job they came from yet. Fourth, write a career summary that tells the story. Fifth, build the hybrid format: summary at top, core competencies, then experience section where each cluster is a header with bullets underneath, and finally a brief timeline with company names and dates. Sixth, tailor for each application by tweaking clusters and language. Luna: That's a lot of steps. But one thing I want to flag: a lot of job hoppers worry about the 'job-hopping penalty' when applying to more traditional companies. Does a skill-based resume help there too? Lucas: It helps, but it's not a magic wand. If you're applying to a bank or a law firm that still values long tenure, you might face more scrutiny. But even then, many of those organizations are modernizing. JPMorgan, for instance, has publicly stated they're shifting to skills-based hiring for many roles. So the stigma is eroding. Luna: Let's talk about the 'skill-based resume' versus 'functional resume' terminology. Should listeners use the term 'skills-based' or 'functional' on their resume file? Some recruiters might search for those formats. Lucas: I'd avoid putting either term on the resume itself. Just let the format speak. But when you're networking or talking to a recruiter, say 'skill-based' or 'skills-focused.' 'Functional' carries baggage. I had a recruiter client once tell me that whenever she sees 'functional resume' in a cover letter, she rolls her eyes. So stick with 'skill-based.' Luna: Good advice. So, to wrap up: if you've changed jobs frequently, a skill-based resume isn't just a workaround—it's actually a strategic advantage because it showcases what you've accumulated across roles. Lucas: Exactly. The key is to own your path. Don't try to hide it. Use the format to tell a coherent story about your growing expertise. And if you need a place to start, LinkedIn now offers a skills-based resume generator in their job seeker tools—I'd recommend trying that as a starting point. Luna: I'll check that out. And listeners, if you've found this episode helpful—if it's changed how you think about your resume—we hope you'll consider supporting the show. We keep it ad-free, and listener support is what makes that possible. You can find us at buy me a coffee dot com slash fexingo. Even a small contribution helps us keep going. And now, back to the topic—Lucas, what about the do's and don'ts of quantifying achievements in a skill-based format? Lucas: Great question. The number one rule is: every bullet point should include a result. Not just 'managed social media accounts' but 'grew LinkedIn followers by 200 percent in six months.' Even in a skill-based format, results matter. And if you don't have numbers because you're early in your career, use qualitative outcomes: 'Led a cross-functional team to launch a product on schedule.' The format is different, but the fundamentals are the same. Luna: So the skill-based resume is not an excuse to be vague. Lucas: Never. If anything, it demands more precision because you're grouping achievements from multiple roles. But done right, it's the most powerful tool a job hopper has.