Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / The Career Anchor Strategy For Uncertain Times
Transcript
- Lucas: If we've helped you think through a career move or decision lately, you know our stance is pretty clear. We deliberately don't run ads on these shows because we want to keep the focus entirely on your long-term trajectory, not a thirty-second pitch for some app. If that resonates with you, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, keeping the signal clean matters when you're trying to hear the actual advice. Thanks for supporting that choice. Lucas: Let's get into today's angle. We've talked a lot about stacking skills and finding scarcity, but there's a trap I'm seeing in my inbox that I think is worth unpacking right now. It's what I call career anchoring. The idea is simple but hard to execute: you need one non-negotiable core competency that defines who you are professionally, and then you build everything else around it. Without an anchor, you drift. Luna: Drift is a polite way to put it. Most people just end up being generalists who aren't good at anything specific enough to charge premium rates. Lucas: Exactly. And the pressure to be a generalist is intensifying. Look at the tech sector as of September tenth twenty twenty six. Companies aren't just looking for pure coders anymore. They want engineers who can talk to clients, understand business units, and navigate ambiguity. That sounds great on paper, but if you don't have a strong technical anchor, you become a translator with no source text. You lose your edge. Luna: So the danger isn't learning new skills, it's letting them overwrite your original expertise? Lucas: Precisely. I spoke with a former director at a mid-sized software firm last week. He told me they stopped hiring for pure backend development roles two years ago. Now, every engineer needs basic project management and stakeholder communication skills. The problem? Half their team forgot how to actually code because they spent so much time in meetings. Their anchor was gone, and they were paying for it in technical debt. Luna: That's a classic case of process eating product. If the engineers stop producing code, the whole pipeline breaks regardless of how well they communicated. Lucas: Right. And here's the thing most professionals miss. Anchoring isn't about refusing to adapt. It's about knowing what you will never compromise on. For a data scientist, that might be statistical rigor. For a marketer, it might be consumer psychology. If you start treating your core skill as optional, you're no longer an expert. You're a commodity. Luna: It reminds me of the difference between a Swiss Army knife and a scalpel. One does a little bit of everything okay, the other does one thing perfectly. Lucas: I love that analogy. But let's make it concrete. Let's look at a specific scenario. Say you're a financial analyst. Your anchor is your ability to model complex scenarios and spot risks others miss. Now, your company wants you to take on more sales responsibilities because they're short-staffed. You say yes, thinking you're being versatile. Six months later, you're spending eighty percent of your time on calls and twenty percent on models. Luna: And your modeling skills atrophy while your sales skills are still junior compared to actual account executives. You've sunk both ships. Lucas: You've sunk your primary value proposition. The market doesn't pay you for half-assed sales work. It pays you for elite analysis. When you dilute your anchor, you lower your ceiling. I see this constantly in consulting firms where consultants try to do strategy, implementation, and sales all at once. They burn out because they're never deep enough in any one area to command respect. Luna: But how do you tell the difference between healthy adaptation and dangerous drift? Sometimes you have to stretch to grow. Lucas: Good question. The rule of thumb is the ten percent rule. You can allocate up to ten percent of your energy to adjacent skills, but never let it exceed that threshold relative to your core. If your core is coding, you can spend ten percent of your time learning product management. But if you're spending fifty percent, you've crossed the line. You're no longer an engineer who understands product. You're a failed product manager who used to code. Luna: That distinction is brutal but accurate. Being a failed something is worse than being a successful something. Lucas: It is. And this brings us to the second part of anchoring: signaling. You need to communicate your anchor clearly to your employer and the market. This means your resume, your LinkedIn profile, and even your casual conversations should highlight your core competency first. Everything else is secondary context. If you lead with your side projects, people assume that's your main gig. Luna: So if I'm an engineer who also writes, my headline should be Software Engineer, not Aspiring Author. Lucas: Exactly. Unless writing is your anchor. Then obviously flip it. But most people bury the lead. They want to seem multidimensional, so they list every hobby and certification equally. That creates noise. Recruiters skim for keywords. If they don't see your anchor immediately, they categorize you incorrectly. Luna: It's like search engine optimization for your own brain. If you don't optimize for your core value, you get lost in the results. Lucas: Spot on. And this is especially relevant given the current job market environment in late twenty twenty six. With AI tools handling more routine tasks, the premium is shifting toward judgment and specialized insight. Those are anchored skills. An AI can write code, but it can't yet replicate the nuanced understanding of a senior architect who knows exactly which system design decisions will save the company millions in five years. Luna: So the AI threat actually reinforces the need for anchoring, because it strips away the generic stuff and leaves only the deep expertise. Lucas: That's the counterintuitive truth. People think they need to become more generalist to survive AI. I argue they need to become more specialist. Because if you're generalist, AI is better at doing generalist work than you are. If you're a world-class specialist in a narrow domain, AI is just a tool you use faster. Your anchor becomes your moat. Luna: A moat made of depth. That sounds expensive to build, though. It takes years to reach that level of expertise. Lucas: It does. Which is why starting early matters. But it's never too late to redefine your anchor. If you've been drifting for ten years, you can still choose a new center of gravity. You just have to be willing to sacrifice some breadth to regain depth. You might have to turn down promotions that require you to manage people if your anchor is individual contribution. That's a hard choice, but it's a strategic one. Luna: Turning down a promotion is scary, but staying in a role that erodes your core value is scarier in the long run. Lucas: Absolutely. Let's look at another example. Marketing. A lot of marketers today are pressured to become full-stack growth hackers. SEO, paid ads, content, email, analytics, community management. It's overwhelming. The ones who succeed are the ones who pick one channel, say, email retention marketing, and master it completely. They become the go-to person for that specific outcome. Luna: And then they leverage that reputation to bring in broader projects, but always return to the email expertise as their home base. Lucas: Yes. They use the anchor to pull in other opportunities, not the other way around. It's proactive diversification, not reactive scrambling. Reactive scrambling is what happens when you're fired and desperate to find any job. Proactive diversification is what happens when you have a strong foundation and you're building a skyscraper. Luna: So the mindset shift is from fear of missing out on opportunities to fear of losing your competitive advantage. Lucas: That's the key. Fear of missing out drives bad career decisions. Fear of losing your edge drives good ones. You protect your edge by saying no to things that don't serve your anchor. It feels restrictive, but it's actually liberating because you stop wasting energy on things you're mediocre at. Luna: Less noise, more signal. That's a much more sustainable way to work, especially with the burnout rates we're seeing. Lucas: Burnout often comes from context switching between roles you haven't fully committed to. When you're anchored, you know your lane. You drive fast in your lane. You might cross over to help someone else occasionally, but you always return to your lane. That predictability builds trust with employers, which leads to better compensation and stability. Luna: Trust is currency. If they know exactly what you bring to the table, they'll pay a premium for that certainty. Lucas: They will. So, here's your homework for this week. Identify your anchor. Is it writing, coding, sales, design, analysis? Write it down. Then audit your last three months of work. How much time did you spend on that anchor versus everything else? If it's less than ninety percent, you're drifting. Start reclaiming that time, even if it means pushing back on low-value requests. Luna: And if you find your anchor has shifted naturally, that's fine too. Just acknowledge the shift explicitly rather than letting it happen invisibly. Lucas: Exactly. Intentionality is the opposite of drifting. Whether you stay the course or pivot, make sure you're steering the ship, not just hoping the wind carries you somewhere interesting. Luna: I hope that helps listeners find their footing in such a volatile market. It's easy to forget that you get to choose your center of gravity. Lucas: It really is. And once you find it, protecting it becomes the most important job you have. What do you think is the hardest part of identifying your true anchor in a world that rewards constant change?