Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / Why Your Soft Skills Need a Hard Skills Friend
Transcript
- Lucas: So there's this idea that keeps floating around — that the future belongs to either the technical genius who can code anything, or the charismatic leader who can rally any team. And I think that's a trap. Luna: A false binary, basically. You're saying you need both? Lucas: Exactly. And I've got a stat to anchor this. LinkedIn released a workforce report in early 2025 — they looked at millions of job postings globally. And the share of ads that explicitly ask for both a hard skill and a soft skill in the same listing rose 28 percent year-over-year. That's not nothing. Luna: Twenty-eight percent — that's significant. So employers aren't just saying 'we want a coder' or 'we want a people person.' They want someone who can do both. Lucas: Right. And the specific pairing that showed up most often was analytical thinking paired with communication. Not surprising when you think about it — you can run the best regression in the world, but if you can't explain what it means to a product manager, it's basically useless. Luna: I've seen that firsthand. I worked with a data scientist once — brilliant modeler, but his presentations were just walls of numbers. No one could follow. He got passed over for a lead role because the VP said, quote, 'he can't tell the story.' Lucas: That's the classic case. And I think the trap is that people assume they have to pick a lane — I'm either the technical person or the people person. But the data says the market is rewarding people who refuse that trade-off. Luna: So how do you actually build that combination? It's not like you can just wake up one day and decide to be both. Lucas: No, and I think the smartest approach is to pick one primary strength and then add a complementary skill that sits in the other category. So if you're a project manager — strong on coordination, stakeholder management, those are soft skills — you add a technical layer like SQL or basic data visualization. Suddenly you can query your own timelines, spot bottlenecks yourself. You're not just the person who asks for updates; you're the person who already knows. Luna: I love that example. I actually interviewed a project manager at a fintech company who did exactly that. She learned SQL in three months through a part-time course. Within six months, she was building her own dashboards. Her team's delivery speed improved by, I think she said, about 40 percent. Lucas: Forty percent — that's huge. And it's not because SQL is some magic productivity wand. It's because she removed the translation step. She didn't have to wait for a data analyst to get to her request. She could answer her own questions. Luna: Right. And that made her more valuable not just as a PM, but as a strategic thinker. She started spotting patterns in project delays that no one else saw. Lucas: That's the multiplier effect. The hard skill doesn't replace the soft skill — it amplifies it. The same works in reverse. If you're a developer, adding a soft skill like mentoring or technical writing makes you exponentially more effective. Luna: I think about the developer who can lead a code review without making people feel stupid. That's a rare combo. And companies pay a premium for it. Lucas: They do. And I want to bring in another example from a different angle. Salesforce and JPMorgan have both launched internal programs in the last couple of years specifically designed to train for this blend. Salesforce calls theirs 'Trailhead for Soft Skills' — it's a mix of technical modules and communication workshops. JPMorgan has a program where junior bankers rotate through both quantitative analysis roles and client-facing roles in the same year. Luna: So the big firms are already investing in this. They see the data too. Lucas: Exactly. And what's interesting is they're not just saying 'go take a class.' They're designing the work itself to force the combination. Because the best way to develop a skill is to use it in a real context. Luna: That's a good point. So if someone listening wants to start building this kind of blend, where do they begin? Lucas: I'd say two steps. First, audit your current role. What's the one thing you do that feels most valuable? That's your primary skill. Then ask: what's a skill from the other category that would make that primary skill more visible or more impactful? For a marketer, maybe it's basic data analysis. For an accountant, maybe it's presentation skills. Luna: So don't try to become an expert in everything. Pick one complementary skill. Lucas: Exactly. The second step is to find a low-stakes project where you can practice the combo. Don't sign up for a six-month certification right away. Instead, volunteer to present the team's quarterly results next month. Or offer to build a simple dashboard for your own workflow. That way you're learning in context, not in a vacuum. Luna: And the feedback is immediate. You either made the data clearer or you didn't. You either saved time or you didn't. Lucas: Right. And that feedback loop is what actually builds the skill. Not the course, but the application. And honestly, this is the kind of thing that we talk about a lot on this show — practical, actionable ways to think about your career. Luna: Speaking of which — and I promise this connects — we only have this show because listeners like you support it. It's ad-free, no sponsors, no interruption. And the way it stays that way is a small group of listeners who chip in monthly. Lucas: Yeah, it's not a big ask. If you've ever gotten something useful out of an episode — maybe a framework you actually used, or a stat you brought up in a meeting — that's the kind of thing that keeps us going. And it's all through buy me a coffee dot com slash fexingo. Luna: We don't do pledge drives or guilt trips. Just a quiet thank you to everyone who already does, and an open door if anyone else wants to join. Now back to the blend — you mentioned that the best way is to start small. What about people who feel like they're too far behind? Lucas: I hear that a lot. 'I'm 40, I've never written a line of code, is it too late?' And the answer is no, because you're not trying to become a software engineer. You're trying to add one tool to your existing toolkit. And that's very doable. Luna: There's a great example from a listener actually — well, someone I met at a conference. She was a senior HR director, and she felt like she was being left out of strategic conversations because she didn't understand the data side. So she took a three-week online course on people analytics — just basics, turnover metrics, headcount forecasting. Lucas: And what happened? Luna: Within two months, the CEO asked her to present at the quarterly board meeting. Because she could finally speak the language of the business. She didn't become an analyst. She became an HR leader who could also analyze. Lucas: That's exactly the point. You're not changing your identity. You're expanding your range. And that's what the market is rewarding right now. Luna: So the real skill isn't hard or soft. It's the ability to combine them. Lucas: I'd say that's the meta-skill of this decade. And the good news is it's learnable. It just takes intentionality. Luna: And a willingness to look a little foolish at first, while you're learning. Lucas: That's the part nobody talks about. You will be bad at SQL for a while. Your first presentation after adding data might be clunky. But that's how learning works. And the people who get comfortable with that discomfort are the ones who end up with the most career leverage. Luna: Alright, so to wrap up — pick one primary skill, add one complementary skill from the other bucket, practice on a real project, and embrace the awkward phase. Lucas: That's the blueprint. And if you do that even once a year, you'll be a dramatically different professional in five years. Luna: I think that's a good note to end on. Thanks for listening, and we'll see you next time. Lucas: Take care.