Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Technical Program Management
Transcript
- Lucas: One of the most underrated career paths for bootcamp grads is Technical Program Management or TPM. Most people think the next step after bootcamp is either engineering or product management, but TPM sits right in between — and it's a role that actually rewards the kind of cross-functional muscle you build during a bootcamp. Luna: I've seen that too. A lot of bootcampers end up doing project management tasks informally, especially in smaller teams, without realising that's a legitimate career track. Lucas: Exactly. Let's use a real example. I spoke with Maria, who graduated from a 12-week full-stack bootcamp in 2023. She got hired as a junior front-end developer at a mid-sized SaaS company. Within six months, she was the person everyone went to when a sprint was falling apart — she'd re-prioritise tickets, unblock dependencies, and keep the stand-ups on track. Luna: So she was doing TPM work but getting paid as a dev. Lucas: Right. And she didn't even know the title existed until a senior program manager mentored her. She started shadowing their meetings, then took over a cross-team initiative to migrate their CI/CD pipeline. That project became her portfolio piece. By month 18, she formally transitioned into a TPM role with a 15 percent raise. The key insight here is that bootcamp grads already have a lot of the raw materials for TPM — they just need to repackage them. Luna: What are those raw materials exactly? Because when I think bootcamp, I think coding, not program management. Lucas: Sure. First, bootcamp trains you to work in rapid cycles — scrum, stand-ups, retrospectives. That's the agile fluency that TPMs live in. Second, you learn to communicate across disciplines: you talk to designers, product managers, and stakeholders during a build. That cross-functional translation is the core of TPM. Third, bootcamps teach you to scope work realistically — breaking a feature into tickets, estimating effort. That's program execution. The gap is just vocabulary and framing. Luna: So how does someone actually make that leap? Let's say I'm a bootcamp grad in a dev role right now. What's the first step? Lucas: First, audit your current responsibilities. Look at your past three sprints and identify every task that wasn't pure coding — unblocking a teammate, running a retro, documenting a process. List those on your resume as accomplishments, not as part of your dev duties. Then, start looking for tpm adjacent gaps in your team. Is there a cross-team project that has no clear owner? Volunteer to coordinate it. That's your portfolio. Luna: And I imagine networking plays a big role too. TPM is often an informal promotion path. Lucas: Huge. Maria did two smart things: she found a mentor who was already a TPM, and she joined the Program Management office hours at her company. She also started a monthly lunch and learn on agile best practices. That built her reputation as someone who thinks about process, not just code. If your company doesn't have internal TPM roles, look for tpm adjacent titles like 'project coordinator' or 'delivery lead' at smaller companies where the role is more fluid. Luna: A quick honest thing — we only make this show because a handful of listeners chip in monthly through Buy Me a Coffee dot com slash Fexingo. It keeps us ad-free and lets us dive deep into niche career paths like this. If you've gotten value from an episode, that's literally what funds the next one. Lucas: Yeah, it's a small group but it makes a big difference. And it means we never have to sell you a mattress or a meal kit. Back to TPM — one thing that surprises people is the interview format. It's less about coding and more about case studies. You might get a scenario like: 'A feature launch is delayed by three weeks because the QA team is overloaded. What do you do?' Luna: I've seen those questions. They test your ability to trade off speed, quality, and stakeholder communication. Lucas: Exactly. A strong answer shows you can identify the bottleneck, propose a concrete mitigation — like pulling in a contractor or descoping a non-critical feature — and escalate clearly. They want to see you think in systems, not just tasks. Bootcamp grads often do well here because they've lived through those tight deadlines. Luna: What about the certification question? Should someone pursuing TPM get a Scrum Master cert or a PMP? Lucas: Scrum Master certification is cheap and fast — you can get it in a weekend for a few hundred dollars. It signals you know the agile framework. The PMP is more rigorous and expensive, but it's valued in traditional program management roles. For most bootcamp grads targeting tech companies, a Scrum Master cert plus demonstrable experience is enough. Maria didn't have a PMP when she transitioned. Luna: So the timeline — if someone starts actively pivoting today, how long does it realistically take? Lucas: I've seen it happen in as little as six months if you're in a company that promotes internally. But a more realistic path is 12 to 18 months. You spend the first three months building your network and taking on small coordination tasks, the next six months leading a meaningful cross-team project, and then the final three months interviewing externally or pitching an internal transition. The key is intentionality — don't just wait for the opportunity to come to you. Luna: And what about the risk of being seen as 'not technical enough'? TPM roles often require some technical credibility. Lucas: That's actually where bootcamp grads have an edge. You have real coding experience, even if it's only a year or two. You can read a pull request, understand an API contract, and troubleshoot a deployment issue. That's more technical than many TPMs who come from a pure business background. The trick is to frame it: say 'I've shipped production code in React and Node,' not 'I'm a full-stack developer.' Luna: So it's about reframing, not upskilling from scratch. Lucas: Exactly. One more thing — if you're looking at external TPM roles, pay attention to the job description. Some TPM roles are more technical, requiring you to manage engineering schedules and dependencies. Others are more strategic, focusing on executive reporting and roadmap alignment. Bootcamp grads tend to fit better in the technical TPM track early on, because you can lean on your hands-on engineering experience. Luna: Any final advice for someone listening who's thinking, 'I'm in a dev role and I'm bored, but I don't want to become a manager'? Lucas: TPM might be your sweet spot. It's not people management — you don't have direct reports — but you do lead projects and influence without authority. You get to solve complex coordination problems and see the big picture. Start by having a conversation with a TPM at your company. Ask them what their day looks like. Most likely, you'll recognise a lot of what you're already doing. Luna: And if you don't have a TPM at your company, reach out on LinkedIn. Program managers are surprisingly generous with their time. Lucas: Alright, that's the path. Next episode we'll look at how bootcamp grads can break into sales engineering — another hidden gem. Until then, keep building and keep asking questions.