Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / Why Career Switchers Fail The First 90 Days
Transcript
- Lucas: We spend so much time talking about how to get hired. The resume hacks, the portfolio projects, the interview loops. But there is a much quieter, more dangerous phase that happens once you actually sit at the desk. It is the first ninety days. And if you look at the data on mid-career pivots, that is where the attrition spikes, not at the offer stage. Luna: Right. You get the job because you proved you could learn the syntax or the framework, but then you walk into an office where the politics are ancient and the tools are terrible. That is a totally different skill set. Lucas: Exactly. I call it the competence cliff. When you are a bootcamp grad or a career switcher, you are riding a wave of fresh curiosity. You are eager to prove yourself. But around day forty-five, that novelty wears off, and you hit the wall of institutional complexity. Suddenly, writing good code or crafting a great campaign isn't enough. You need to understand who actually holds power in the room and why things move slowly. Luna: I see this all the time with people moving from fast-moving tech startups into legacy financial institutions. They try to optimize everything in week two, and they just terrify their managers. Lucas: That is the first trap: the optimization impulse. In your old role, maybe speed was the metric. If you were in marketing, you launched, measured, iterated. Now you are in risk management or compliance at a bank like JPMorgan, and speed is literally a liability. If you bring that same velocity, you aren't seen as proactive; you are seen as reckless. You have to decouple your identity from being the person who fixes things quickly. Luna: So instead of fixing, what should they be doing? Just watching? Lucas: Not just watching, but mapping. You need to map the decision-making hierarchy. Who signs off on what? What are the unwritten rules for communication? Do people prefer Slack or email? Do they want bullet points or narratives? Most switchers ignore this because it feels like fluff. But if you send a detailed narrative to a manager who only reads three-line summaries, you will fail, even if your work is brilliant. Luna: It is basically learning the operating system of the company before you try to run any new applications. That makes sense. Lucas: Precisely. And this leads to the second major failure point: toolchain resistance. Bootcamps teach you the modern stack. React, Python, AWS, Tableau. But many established companies are running on Excel macros from 2014 and legacy databases that nobody understands. When you arrive and immediately complain that the tools are archaic, you alienate the very people who keep the lights on. Those older systems exist for a reason, usually because changing them carries massive risk. Luna: So you have to pretend to like the bad tools? Or just use them quietly? Lucas: You use them, and you document the pain. There is a difference between complaining and providing evidence. If you spend your first month using the broken process and collecting data on how long it takes versus how long it should take, you build a case for change later. If you start by saying the process is stupid, you are just another outsider disrupting the status quo. You need to become a stakeholder in the current system before you can propose a new one. Luna: That is such a subtle shift in mindset. From critic to architect. But I wonder if some people find that impossible if the culture is really toxic. Lucas: That is a fair point. If the toxicity is structural, no amount of mapping will help. But most cases are not that extreme. They are just boring, bureaucratic, and slow. The issue is that career switchers are often used to high-agency environments where they have control. In a large corporation, you might have zero control over your immediate environment. Accepting that lack of agency is emotionally difficult but professionally necessary for survival. Luna: Yeah, giving up that control feels like losing your professional identity. How do you reconcile that with your confidence? Lucas: You separate your competence from your autonomy. You are competent because you understand the problem space deeply, not because you are driving the car. Think of it like being a consultant embedded in a firm. You observe, you analyze, you suggest. You don't assume the wheel until you have earned the trust to drive. It requires a lot of humility, which is hard for people who got their new job because they were confident enough to pivot. Luna: Humility doesn't mean silence though. You still need to show value early on. Otherwise, your manager thinks you aren't pulling your weight. Lucas: True. So here is the third trap, which is the low-hanging fruit error. New hires love to pick small, visible problems to solve. They fix the formatting on the weekly report. They clean up the CRM data. These are good deeds, but they are often invisible to leadership. Meanwhile, the big strategic initiative that everyone cares about is stalled because of a bottleneck you didn't notice. You end up looking busy but irrelevant. Luna: So you should avoid the easy wins? That feels counterintuitive. Lucas: Not avoid, but align. Before you fix anything, ask your manager what keeps them up at night. Is it customer churn? Is it regulatory reporting? Is it product launch delays? Solve that specific problem, even if it is messy and hard. If you fix the weekly report format, you might save ten minutes a week for the team. If you solve the regulatory reporting bottleneck, you might save the department from a fine. Focus on impact, not activity. Luna: Impact over activity. That is a mantra worth remembering. But what about the social side? I know I felt isolated in my first few months at a new job, especially when everyone else had inside jokes and history. Lucas: Social isolation is a huge factor in early turnover. You feel like a tourist. The advice here is to schedule informational interviews, not mentorship meetings. Don't ask people to teach you. Ask them to tell you about a mistake they made in their first year. It lowers the stakes and builds connection. People love sharing war stories. It makes you part of the tribe faster than any team-building exercise ever could. Luna: Asking about mistakes is smart because it humanizes them and shows you aren't afraid of imperfection. It breaks down the perfectionist barrier a lot of switchers have. Lucas: Exactly. Perfectionism is the enemy of integration. You need to show you can handle being wrong, asking for help, and navigating ambiguity. That is what seniority looks like in a new context. It is not about knowing all the answers; it is about knowing how to find them without breaking things. Luna: So if someone is listening to this right now, maybe three weeks into their new role, feeling overwhelmed and like they don't fit in, what is the single biggest takeaway? Lucas: Slow down. Stop trying to prove you belong by moving fast. Start trying to understand why things are the way they are. Map the politics, respect the legacy tools, and solve the right problems. Trust that if you do that consistently for ninety days, the belonging will come naturally. You earn it by being a good colleague, not a hero. Luna: Being a good colleague rather than a hero. I think a lot of us need to hear that. It changes the whole game from performance to partnership. Lucas: And that partnership is what actually secures your long-term position. Once you pass that ninety-day mark and you have shown you can navigate the complexity, your previous experience starts to shine again. You become the bridge between the old ways and the new ideas. But you have to cross that bridge carefully. Luna: Thanks for that perspective, Lucas. It really reframes what success looks like in those early weeks. Lucas: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, if this helped clarify your own transition path, checking out that link helps keep the research going for future episodes. Lucas: Absolutely. It lets us dig deeper into these specific case studies without relying on sponsors who want us to say nice things about products. Your support keeps the integrity intact. Luna: It is really appreciated. And it means we can keep covering topics like this one with the depth they deserve. Lucas: Before we let you go, I want to leave you with one final question to ponder. When you look back at your own career switches, was there a moment where you realized you had to stop performing and start listening? What did that shift cost you, and what did it give you in return? Luna: That is a powerful place to end. It reminds us that the hardest part of a new job isn't the work itself, but the quiet work of becoming part of a new world. Lucas: Exactly. Listen first, act second. And remember, you are not behind. You are just finding your footing. Thanks for tuning in to Fexingo Business.