Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / The Career Pivot Audit Framework
Transcript
- Lucas: There is a specific kind of panic that sets in around week six of a new job, especially when you have switched fields entirely. You are no longer the expert you were in your old role, but you do not yet feel like the competent professional you are supposed to be in this one. It is a limbo state that most career switchers underestimate. Luna: Exactly. I call it the valley of quiet incompetence. You are surrounded by people who speak the jargon fluently, and you are just trying to keep up with the acronyms while pretending you understand the strategic implications. Lucas: And the worst part is that you cannot complain about it because you chose this path. If you had stayed in your old industry, you would be confident and comfortable. So any confusion you feel is framed as a personal failure rather than a structural reality of learning something new. That internal narrative is dangerous. Luna: It leads to overworking, doesn't it? Trying to prove yourself by logging extra hours instead of asking for clarity. Lucas: Precisely. And we see this play out constantly in our inbox. People describe situations where they are asked a simple technical question during a meeting and freeze. Not because they lack the intelligence, but because their brain has switched from execution mode to threat assessment mode. They are not thinking about the answer; they are thinking about how this moment defines their entire future here. Luna: That freeze response is so common. It makes you withdraw, which makes you look less engaged, which then feeds the cycle of self-doubt. Lucas: Let me give you a concrete example that illustrates this perfectly. A listener named Marcus wrote in recently. He was a high school history teacher for twelve years. He decided to pivot into product management because he loved the intersection of storytelling and data. He completed a rigorous three-month bootcamp and landed a junior product role at a mid-sized fintech company. Luna: That sounds like a solid foundation. Teaching requires a lot of communication and stakeholder management, which translates well. Lucas: It does. But Marcus hit a wall in his second month. His manager asked him to prioritize a feature request based on user retention metrics. Marcus knew the concept of retention, but he did not know how to pull the specific SQL query to isolate the cohort. In his old life, if he did not know an answer, he would say, let me research that and get back to you. Here, he felt like he was failing a test he had already taken. Luna: Because in education, you are the authority figure. In tech, even at a junior level, you are expected to be a solver, not just a learner. Lucas: Right. The power dynamic shifts. Marcus started staying late every night to relearn SQL basics, convinced that his colleagues were judging his technical speed. He stopped speaking up in sprint planning because he was afraid of asking a basic question. Within eight weeks, he was ready to quit. He thought he had made a mistake choosing this path. Luna: So the issue wasn't his capability. It was the pressure he put on himself to perform at a senior level immediately. Lucas: Exactly. We need to distinguish between a genuine skill gap and what I call an identity tax. The skill gap is real—you might need to learn SQL. The identity tax is the psychological weight you carry because you are comparing your current reality to someone else's highlight reel. Marcus was comparing his day-to-day struggles to a product director's polished presentations. Luna: And directors probably still struggle with things Marcus doesn't know, like complex financial modeling or legal compliance issues. Nobody knows everything. Lucas: That is the hard truth. Most people in leadership roles are just better at hiding their own knowledge gaps or delegating them effectively. Marcus needed a framework to separate the two. He needed to ask: can I solve this with help, or is this a fundamental blocker? If he could solve it with help, he should ask for help immediately. If it was a blocker, he needed dedicated time to learn it without the shame spiral. Luna: So the first step is admitting that you don't know, but framing it as a temporary state rather than a permanent trait. Lucas: Yes. And that requires changing your vocabulary. Instead of saying, I am bad at data, you say, I am currently building my proficiency in data extraction. One statement describes your character. The other describes your progress. Language shapes perception, including your own. Luna: I love that distinction. It moves the goalpost from innate ability to acquired skill. Lucas: Let's go deeper into the mechanics of this. When you switch careers, you lose your social proof. In teaching, your classroom management and student outcomes were visible evidence of competence. In product management, your early work might be invisible drafts or small bugs fixes. You are working on tasks that do not have immediate, tangible rewards. Luna: Which makes it harder to gauge whether you are doing a good job. You rely entirely on external feedback, which might be scarce or vague. Lucas: Correct. This is why the first ninety days are critical. You need to create your own evidence of competence. Marcus started keeping a weekly log of problems he solved, even small ones. Did he clarify a requirement? Did he mediate a disagreement between engineering and design? He documented these moments. By the end of the third month, he had a list of ten wins that proved he was adding value, regardless of his technical speed. Luna: That is essentially building a private resume. A record of contributions that exists independently of your boss's opinion. Lucas: Exactly. It gives you leverage in performance reviews and, more importantly, it gives you internal stability. When you feel that wave of imposter syndrome coming on, you can look at the log and say, I handled this last week. I can handle this one too. Luna: It turns abstract anxiety into concrete data points. That feels much more manageable. Lucas: There is also the element of mentorship. Switchers often avoid asking for help because they feel they are wasting everyone's time. But experienced professionals actually enjoy helping people who show initiative. The problem is that many switchers wait until they are completely stuck before reaching out. By then, the damage to their confidence is done. Luna: So proactive vulnerability is better than silent struggle? Lucas: It is infinitely better. There is a phrase used in some tech cultures called 'fail forward.' It means you try something, it doesn't work, you learn, and you move on. But you only fail forward if you acknowledge the failure publicly. If you hide it, you just fail silently. Marcus learned to say, I am trying approach A, but I think approach B might be faster. Can you take a look? That invites collaboration instead of judgment. Luna: It signals that you are thinking strategically about efficiency, not just blindly following instructions. Lucas: Yes. It shows you are engaging with the problem space, which is exactly what a product manager should do. The technical details can be filled in later. The mindset is what matters most in those early stages. Luna: So the advice for listeners is to focus on the mindset first, and let the technical skills catch up? Lucas: Prioritize the mindset. Technical skills are binary. You either know Python or you do not. Mindset is continuous. Your ability to tolerate ambiguity, to ask questions, and to persist through confusion is what will determine your long-term success. The technical stuff can be taught. The resilience is harder to install. Luna: And that resilience is built through small, repeated acts of showing up and being imperfect. Lucas: Exactly. You are not supposed to be perfect. You are supposed to be learning. The moment you accept that the first year of a career switch is a learning year, not a proving year, the pressure drops significantly. Luna: That reframing alone could save people from burning out in those crucial first few months. Lucas: If you want to support that choice, the link is buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. We deliberately do not run ads on these shows because we believe in providing clear, uncommercialized advice for your career development. Your support keeps that integrity intact. Luna: Yeah, it really helps us maintain this quality without compromising the content for sponsorships. Lucas: Returning to Marcus, he eventually realized that his background in history gave him a unique advantage in understanding user narratives. While other junior product managers were obsessed with features, he was focused on the story behind the user action. That perspective became his unique selling point within the team. Luna: So the thing that felt like a weakness—the non-tech background—became his strength once he stopped fighting it. Lucas: Precisely. Imposter syndrome often comes from trying to erase your past to fit into your future. But your past is your toolkit. You just need to find the right tools for the new job. Luna: A great reminder that we bring more to the table than just the technical skills we learn on the job. Lucas: Always. The question isn't whether you are enough. The question is how you integrate who you were with who you are becoming.