Latest / Job Hopping with Fexingo: Tenure, Loyalty, and the Modern Career Resume / Why Job Hoppers Should Screen for Skills, Not Titles
Transcript
- Lucas: So there was a LinkedIn study earlier this year that found 45 percent of hiring managers now say they screen for skills before they even look at your job history. And I think for job hoppers, that is the single most important shift in hiring we've seen in a decade. Luna: Forty-five percent? That's huge. But how does that actually play out in practice? I mean, do recruiters really look at skills first, or is it still the resume scanning bots that reject you for having a two-year tenure? Lucas: That's the thing — it's a mix. Some companies have genuinely redesigned their screening to be skill-based, with structured interviews and work samples. But a lot of others just claim it. They put 'skills-based hiring' in their job description and then the ATS still parses for keywords and tenure. Luna: So how do we tell the difference? How do we know if a company is actually walking the talk? Lucas: Well, a really practical tell is the application process itself. If they ask you to complete a skills assessment or a work sample early on, that's a strong signal they're serious about skills. But if the first screen is just a phone call with a recruiter who asks, 'Why did you leave your last job after fourteen months?' — then you know it's still tenure-focused. Luna: That makes sense. And I think for job hoppers, this is actually a huge opportunity. Because if you've moved around, you probably have a broader skill set than someone who stayed in one role for ten years. Lucas: Exactly. And that's the angle I want to dig into today. Because so much of the job hopping conversation is about how to frame tenure, what to say in interviews, how to handle the 'why do you leave so often' question. But the real game-changer is flipping the conversation entirely: stop trying to justify the tenure and start leading with the skills you've built across those roles. Luna: So it's not about storytelling or spinning the resume, it's about actually redefining the resume around skills. Like, what would that look like in practice? Lucas: Right. So a traditional resume lists your jobs in reverse chronological order, each with your title and dates. A skills-first resume flips that: you lead with a core skills section, then back it up with a 'selected achievements' section that groups your accomplishments by skill, not by job. That way, the focus is on what you can do, not how long you stayed anywhere. Luna: I love that. And I actually have a friend who did something similar. She had a really patchy work history — like, she was a barista, then a freelance designer, then a marketing temp — and she felt like her resume was a mess. But she built a portfolio that grouped her work by skill: 'visual design,' 'social media strategy,' 'project management.' And she got a senior role at a startup because they were hiring for those exact skills, not for a specific tenure. Lucas: That's a perfect example. And it's not just for creative fields. I've seen engineers, finance folks, operations managers do this. The key is doing a real skills audit first. You have to list out every skill you've actually used, not just the ones in the job titles you've held. Luna: So how do you do a skills audit? Like, where do you start? Lucas: Start by going through each job you've had, even the ones you hated, and write down every tool, every process, every type of interaction. Then categorize them: technical skills, like specific software or coding languages; soft skills, like negotiation or cross-functional collaboration; and domain skills, like knowledge of a particular industry. You'll be surprised at how much you've accumulated. Luna: And then you prioritize them based on what you want to do next, right? Like, if you're pivoting into product management, you highlight your user research and prototyping skills, not your barista latte art. Lucas: Exactly. And that's the thing — job hoppers have an advantage here because they've been exposed to more variety. A person who's been five years in one company might have deep expertise in one thing, but a job hopper has a breadth that's really valuable in a fast-changing economy. Luna: But isn't there a risk of 'skill-washing'? Like, listing a skill you only used once in a side project and presenting it as a core competency? Lucas: Oh, absolutely. And that's the flip side. Companies are getting wise to that. If you claim a skill, you'd better be able to demonstrate it in an interview or a work sample. That's why I always advise people to only list skills they can talk about in depth for at least fifteen minutes. Luna: Fifteen minutes is a good rule. And it's also why those skills-based assessments might actually be a good thing for job hoppers. Because if you're confident in your skills, you can shine in a work sample, even if your resume doesn't look traditional. Lucas: Right. And that's the deeper point here. The move toward skill-based screening is a response to a labor market where skills change fast and tenure no longer predicts performance. So job hoppers are actually ahead of the curve if they position themselves correctly. Luna: So what should someone do tomorrow if they're a job hopper and they want to start using this angle in their job search? Lucas: First, do the skills audit. Write down every skill you have, categorize them, and pick the top seven to ten that are most relevant to your target role. Then, rewrite your resume to lead with those skills. And third, start asking every recruiter you talk to how they screen for skills — do they use assessments, do they review portfolios, what does their process look like? Luna: That's a really concrete action plan. And I think it's a much more empowering way to approach job hunting than just trying to explain away short tenures. Lucas: Yeah, it's a shift in mindset. Instead of defending your past, you're pitching your future value. And that's a much stronger position to negotiate from, too. Luna: I like that. And before we keep going, I just want to say — if this conversation is helping you think about your own career, the reason we can do this without any ads is because of listener support. If you've gotten value from the show, you can buy us a coffee at buy me a coffee dot com slash fexingo. It's a simple way to keep these episodes coming. Lucas: Yeah, genuinely, that support is what keeps this pod ad-free and independent. We don't have sponsors to please, so we can talk about whatever we think is actually useful. Anyway, back to skills — one more angle I want to hit: how to spot the companies that are actually serious about skills-based hiring. Luna: Yes, because I don't want to waste my time applying to places that still secretly want a five-year tenure. Lucas: So look at their job descriptions. If they list specific skills and say 'we will train for the rest,' that's a good sign. If they ask for 'a bachelor's degree in computer science' even though the role is about project management, that's a red flag. Also, check if they have public statements about skills-based hiring — some companies have committed to dropping degree requirements. That's a real signal. Luna: That's helpful. And what about the interview process? How can you tell if they're actually assessing skills? Lucas: Ask them directly. In the first interview, you can say, 'I see you're committed to skills-based hiring — what does your assessment process look like?' If they give you a vague answer like 'we look at your whole profile,' they're probably not doing it. But if they say 'we'll have you do a case study' or 'we'll ask you to write a sample memo,' that's a green flag. Luna: And that kind of process actually benefits job hoppers, because you can show your skills in action, not just talk about your job history. Lucas: Exactly. And I think this is where the future is going. The whole tenure debate is starting to feel outdated. As more companies move to skills-based screening, the question 'how long did you stay at each job' will become less and less relevant. What matters is what you can do. Luna: So for someone who's been job hopping and feeling insecure about their resume, the takeaway today is: stop worrying about tenure, start building your skill narrative. Lucas: That's the takeaway. And I'd add one more thing: your skills are portable, your tenure isn't. So as you plan your next move, think about what skills you want to accumulate next, not just what title you want. That's how you build a career that's resilient, even if you change jobs often. Luna: That's a really powerful way to think about it. I know I'm going to do a skills audit this weekend. Lucas: Good. And when you do, think about this: if you had to describe yourself in three skills, not three job titles, what would they be? And does that description feel more true to who you are and where you want to go? Luna: That's a great question to leave our listeners with. Thanks for joining us on Job Hopping with Fexingo. Lucas: Yeah, until next time, keep building those skills.