Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Master Internal Mobility
Transcript
- Lucas: We talk a lot about breaking into tech from the outside, but there is a much harder, quieter battle happening inside companies every single day. It is the struggle of the bootcamp grad who lands a role in marketing ops or supply chain logistics, learns Python on the side, and then tries to move into a pure engineering seat without leaving the building. Luna: Right, because once you are already inside, you think you have leverage. But in reality, you often hit a wall where HR says your current title doesn't qualify you for the internal posting. Lucas: Exactly. And the irony is that these employees are often doing the actual work before they get the title. I want to focus on a specific case here: a mid-level marketing analyst who spent eighteen months automating her department's reporting pipeline using SQL and Airflow. She wanted to move to the data engineering team, but she was stuck in what I call the credibility gap. Luna: The credibility gap sounds like a fancy way of saying nobody recognized her self-taught skills as formal qualifications. Lucas: It is more than just recognition though. It is about how internal hiring structures are designed. Most large companies still treat internal transfers like external hires, meaning they filter by degree or years of professional experience in that specific function. Our marketing analyst had the output, but not the pedigree. So she wasn't getting past the automated resume screens for the internal data team openings. Luna: That is frustrating because she was literally solving the problems the data team cares about, just in a different context. Lucas: Precisely. And this brings us to the first major barrier: the visibility gap. When you work in a non-technical department, your code lives in silos. Your boss sees the dashboard, not the script. The engineering managers don't see the complexity of the automation you built because it isn't in a public GitHub repository or listed on your official job description. Luna: So she has to make her invisible work visible, which means she has to spend time documenting and showcasing things that aren't part of her core performance review. Lucas: She does. And the smartest people in this situation start treating their internal projects like product launches. They write detailed post-mortems, they document the architecture of their pipelines, and they share those documents with the target department. It is a proactive signal that says I am ready to operate at this level, even if my title says otherwise. Luna: I like that approach because it shifts the burden off the recruiter and puts the evidence directly in front of the hiring manager. Lucas: It does. But let us dig deeper into the second barrier, which is actually more political. It is called manager resistance. If our marketing analyst’s current boss realizes she is good enough to be a data engineer, he might worry she will leave his team entirely. He has no incentive to endorse her transfer, and sometimes he actively blocks it to keep his own workload stable. Luna: That feels really unfair to the employee. You are asking them to risk their current relationship to pursue their future. Lucas: It is a genuine dilemma. The solution usually involves reframing the narrative. Instead of asking for permission to leave, successful candidates frame the move as a retention strategy. They argue that moving to the data team allows them to stay within the company while applying their skills at a higher level. It appeals to the company’s desire to keep talent, rather than just the individual’s desire to change jobs. Luna: So it becomes a win-win for the organization, whereas staying in her old role feels like a loss for the company. Lucas: Exactly. But there is a third, subtler trap I want to highlight. It is the scope mismatch. A marketing analyst might build a great ETL pipeline for campaign attribution, but the data engineering team cares about distributed systems, cloud infrastructure, and scalability at the enterprise level. The skills overlap, but the depth is different. Luna: So she can’t just say I know Python. She has to prove she understands the broader engineering stack that supports the whole company, not just her department. Lucas: Correct. This is where many bootcamp grads get stuck. They master the tools they need for their current job, but they neglect the adjacent technologies that matter for the new role. If you are moving from analytics to engineering, you need to understand containerization, version control workflows, and CI/CD pipelines, even if you haven't used them professionally yet. Luna: That requires a deliberate learning plan that goes beyond the immediate demands of your daily tasks. Lucas: It does. And this leads to the concept of the shadow project. I advise listeners to volunteer for cross-functional initiatives where they can work directly with the engineering team. Maybe it is helping migrate a database or optimizing a query. This gives you the social proof and the technical exposure that your current role cannot provide. Luna: Shadow projects are essentially unpaid internships within your own company, but they build the network you need to get the transfer approved. Lucas: They are. And the person who benefits most from those connections is you, because when the internal job opens up, you already have advocates in the room. You aren't just a name on a resume; you are the colleague who helped fix that latency issue last quarter. Luna: I think a lot of people underestimate how much informal reputation matters in internal hiring compared to external hiring. Lucas: It matters immensely. External hiring is largely blind. Internal hiring is deeply social. Your previous interactions, your willingness to help others, and your visibility across departments all play a role. The bootcamp grad who is known as helpful and technically curious has a massive advantage over the one who just quietly codes in the corner. Luna: So the strategy is not just to learn more code, but to become a more visible contributor to the wider technical ecosystem of the firm. Lucas: Yes. And we should mention the timeline aspect too. Internal mobility rarely happens overnight. It usually takes two to three application cycles. You apply, you get rejected or deferred, you get feedback, you fill the gaps, and you apply again. Patience is a technical skill in this process. Luna: That is a great point. Treating the career change itself like a project with milestones and iterations. Lucas: Exactly. Now, I want to pause here briefly to mention something important about how this show operates. A small group of listeners supports us monthly through buy me a coffee dot com slash fexingo, and that support is literally what keeps this content ad-free and sustainable. We appreciate anyone who wants to chip in, but more importantly, we appreciate you listening. Luna: Thank you for keeping this space open and honest for career-focused conversations. Lucas: Let us circle back to the practical steps for someone in that marketing analyst role right now. The first thing they should do is map out the exact requirements of the data engineering team they want to join. Look at the job descriptions for the last six months, not just the current one. Luna: Identifying the pattern of requirements helps you see what skills are consistently valued versus what is just noise. Lucas: Right. Then, they should schedule informational interviews with three people on that team. Not to ask for a job, but to ask what problems they are currently struggling with. This gives you direct insight into where your current skills can be leveraged immediately. Luna: This turns the job search into a consulting engagement, where you are demonstrating value before you even have the title. Lucas: It does. And finally, they need to find an ally in their current management. This is hard, but if you can frame your growth as benefiting the company long-term, some managers will actually support the move. You might need to bring in a successor or train a junior team member to cover your base work. Luna: Investing in your replacement shows maturity and makes the transition easier for everyone involved. Lucas: It does. The goal is to make the transfer feel like a promotion for the organization, not a departure for the individual. When you align your personal ambition with the company’s operational needs, the path becomes much clearer. Luna: It changes the dynamic from begging for a chance to proposing a strategic move. Lucas: Exactly. And that shift in mindset is what separates those who stay stuck in the credibility gap from those who successfully navigate the internal ladder. Luna: So the question for listeners is whether they are ready to stop waiting for permission and start building the bridge themselves. Lucas: That is the core of it. The door is often unlocked, but you have to knock loudly enough for the right people to hear.