Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / The Quiet Value of Non-Tech Experience in Tech Hiring
Transcript
- Lucas: If you have spent any time in the job market lately, you have probably noticed a shift in what hiring managers are actually penalizing. It used to be that if you did not have a computer science degree or a bootcamp certificate, you were invisible. Now, with the market stabilizing into this fourth quarter of twenty twenty six, I am seeing a different kind of friction. Luna: Right, and it is not just about technical chops anymore. I am talking to recruiters who say they are actively filtering out candidates who try too hard to sound like fresh graduates. Lucas: Exactly. The trend I am tracking is what I call the 'maturity discount.' When a former teacher, a logistics coordinator, or a senior hospitality manager applies for a project management or operations role in tech, they often strip away their actual experience to make themselves look like juniors. They think they need to prove they can code before they can prove they can lead. Luna: But isn't that a mistake? If the role requires SQL and Python, shouldn't they highlight those first? Lucas: Only if the role is purely individual contributor engineering. For roles involving cross-functional work, stakeholder management, and process optimization, your decade of running a P&L or managing a crisis in a restaurant is infinitely more valuable than knowing how to write a basic loop in Java. The problem is that switchers do not know how to translate that authority into tech-speak. Luna: So they write a resume that looks like an apology letter instead of a case study. Lucas: Precisely. Let us look at a concrete example. Take Sarah, a former regional manager for a mid-sized logistics firm. She wants to move into product operations. On her old resume, she listed 'managed a team of forty people' and 'reduced shipping delays by fifteen percent.' In the eyes of a tech recruiter, that sounds like warehouse management. It does not scream 'product ops.' Luna: It needs to be reframed as managing complex systems and optimizing workflows. Lucas: Correct. But it goes deeper than just changing words. She needs to show the architecture of her decision-making. Did she use data to identify bottlenecks? Did she implement new software tools to track inventory? That is essentially product lifecycle management. The difference is that she is framing it as 'logistics' when it should be framed as 'operational scalability.' Luna: That makes sense because tech companies are obsessed with efficiency right now. Every department is being asked to do more with less. Lucas: Yes, and that is where the 'non-tech' background becomes a superpower. Most tech natives come from academic environments where projects are theoretical. They have never had to manage a budget that directly impacts payroll or deal with a vendor who refuses to honor a contract. Those are real-world constraints that tech companies desperately need in their ops teams. Luna: But how do you get past the initial screen if the keyword parser is looking for 'Agile' and 'Scrum'? Lucas: You have to bridge the gap in your summary and your bullet points without lying. You do not need to claim you ran Scrum ceremonies if you did not. But you can say 'facilitated weekly syncs to align cross-functional teams on deliverables,' which is exactly what a daily standup is. You are translating the behavior, not faking the credential. Luna: It feels like a lot of work to deconstruct ten years of experience into five lines of tech jargon. Lucas: It is work, but it is necessary work. And I want to pause here for a second because if we have helped you think through a career move or decision today, the way these stay ad-free is listener support. Buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, and honestly, that support helps us keep digging into these niche career strategies instead of just covering general finance news. Lucas: Let us get back to the interview loop. Because once you get past the resume filter, you face the behavioral interview. This is where most switchers fail. They try to answer every question as if they are applying for a developer role. Luna: Like they are trying to prove they belong in the room by speaking the language of engineers. Lucas: Spot on. A common trap is when a hiring manager asks, 'Tell me about a time you failed.' A switcher might talk about a coding project that broke. But if you are interviewing for a project management role, talking about a bug is irrelevant. You should talk about a supply chain disruption you navigated, or a client retention crisis you solved. Luna: Because that shows resilience and problem-solving under pressure, which is universal. Lucas: It shows leadership. And here is the thing: tech leaders are tired of hiring twenty-two-year-olds who have never managed a difficult stakeholder. If you can demonstrate that you can calm down an angry client or negotiate a deadline extension, you are instantly ahead of the fresh grads. Luna: So the strategy is to lean into the maturity, not hide it. Lucas: Leaning into it is key. But you have to be careful about the 'overqualified' label. Some hiring managers worry that a former manager will get bored doing execution-level tasks. You need to address that proactively in your cover letter or early in the interview. Luna: How do you reassure them that you are happy to roll up your sleeves? Lucas: By showing curiosity. Instead of saying 'I have done this before,' say 'I am excited to learn your specific workflow.' Frame your experience as a foundation for learning their system, not a replacement for it. You are bringing domain expertise in operations, not trying to replace their junior analysts. Luna: That shifts the dynamic from competition to collaboration. Lucas: Exactly. And this brings us to a specific metric that is trending in Q four of twenty twenty six. Companies are looking for 'hybrid profiles.' Someone who understands the business side and can speak the technical side. You do not need to be a coder, but you need to understand the basics of how the product is built. Luna: So taking a course on API fundamentals or cloud architecture is still worth it, even if you are not going to code. Lucas: Absolutely. It signals that you respect the craft and you are willing to invest in the language of the tribe. It removes the fear that you will be impossible to work with because you do not understand the constraints the engineers face. Luna: It’s about building empathy for the engineering team. Lucas: Yes. And I want to mention one more specific tactic. When you are networking, do not ask for a job. Ask for a 'process audit.' Tell someone in the role, 'I am coming from logistics and I want to understand how your team handles handoffs between design and engineering. Can I buy you a virtual coffee for thirty minutes?' Luna: That is such a smart angle because it positions you as a peer solving a problem, not a beggar asking for a favor. Lucas: It does. And most people love talking about their processes. They feel validated. And in that conversation, you will learn exactly what gaps they have in their current team. Maybe they need someone who is better at documentation. Maybe they need someone who is better at conflict resolution. That is your entry point. Luna: So you are reverse-engineering the job description based on real pain points. Lucas: Precisely. And then you tailor your pitch to solve that specific pain point. If they tell you their onboarding process is chaotic, you share how you standardized training for fifty new hires in your previous role. You are offering a solution, not just submitting a resume. Luna: That is a much higher-leverage approach than applying through a portal. Lucas: It is. And the final piece of this puzzle is salary negotiation. Switchers often undervalue themselves because they compare their title to a junior engineer's title. But if you are bringing operational maturity, you should be negotiating for the mid-level band, not the entry-level band. Luna: Because your impact on the bottom line is immediate, whereas a junior takes six months to ramp up. Lucas: Right. You reduce risk and increase speed from day one. That has a quantifiable value. Do not be afraid to anchor your expectations in the value you bring, not the title you held previously. Luna: It really changes the narrative from 'can they do the job?' to 'how quickly can they add value?' Lucas: Exactly. And that is the shift we need to see in twenty twenty six. Stop apologizing for your past. Start leveraging it as your unique competitive advantage in a market that is hungry for substance over pedigree. Luna: So the question for listeners is, what part of your old career are you hiding that could actually be your biggest asset? Lucas: Great question. Think about the skills you take for granted. The ones you have mastered so well they seem invisible. That is usually where the leverage lies.