Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Pivot Into Technical Program Management
Transcript
- Lucas: So let's talk about a role that kind of flies under the radar for bootcamp grads: Technical Program Management, or TPM. Luna: I feel like most people hear 'program manager' and think it's all Gantt charts and status emails. But TPM is way more technical than that. Lucas: Exactly. And the reason I want to spend time on it is that I've seen bootcamp grads actually have a weirdly natural advantage here. A buddy of mine, Dana, went from a coding bootcamp to a junior dev role at a midsize SaaS company called SyncFlow. Stayed there about a year and a half, then made the jump to a TPM role at a fintech firm. And she didn't have a CS degree or any prior management experience. Luna: Okay, that's interesting. What did she point to in the interview that made them say yes? Lucas: Three things. First, system thinking — bootcamps teach you to understand how the front end, back end, and database talk to each other. A TPM needs to map dependencies across teams, and that ability to hold the whole system in your head is exactly the same muscle. Second, stakeholder management — bootcamp group projects are chaotic. You've got designers, developers, and a product owner who changes their mind every week. Having survived that, you know how to push back and align people. Luna: Right, it's basically a mini cross-functional team. And the third? Lucas: Agile familiarity. Dana had used Jira and Scrum in her dev role. Most TPM roles expect you to run stand-ups and retrospectives. She could say 'I've been doing this for a year and a half' rather than 'I read a book about it.' That was huge. Luna: I think the biggest hurdle for bootcamp grads though is the perception that TPM requires a computer science degree. How did she handle that? Lucas: She didn't hide it. When they asked about her background, she said 'I don't have a CS degree, but I built production code for 18 months. I've debugged race conditions in production. I know what it feels like when a deployment goes wrong.' She turned the lack of a degree into a story about practical grit. Luna: That's smart. And honestly, a lot of TPMs I've worked with who came from CS backgrounds sometimes over-engineer the process. They want perfect dependency graphs. Someone who's actually shipped code knows that things break and you adapt. Lucas: Exactly. So if you're a bootcamp grad and you're thinking about this path, the first step is to look for a project at your current job that is cross-functional. Maybe it's a feature that touches the mobile app, the API, and the data pipeline. Volunteer to coordinate the rollout. That gives you a concrete talking point for your resume. Luna: And you can frame it as 'led cross-functional initiative' rather than 'coordinated schedule.' Language matters a lot in TPM interviews. Lucas: Totally. Another thing Dana did was she started writing lightweight status updates in a shared doc after each stand-up. She didn't wait for someone to ask. She just sent a note saying 'Here's what we did today, here's what's blocked.' That's program management behavior. That's what hiring managers look for. Luna: It's interesting — TPM is often confused with product management. Can you draw that line clearly? Lucas: Sure. Product management is about the 'what' and the 'why.' You're deciding which features to build based on user research and business goals. TPM is about the 'how' and the 'when.' You take that product vision and figure out the execution — the timeline, the dependencies, the risks, the communication across teams. If you like building things and making plans work, TPM might be a better fit than product. Luna: I think that's a really important distinction. A lot of bootcamp grads get told 'go into product management' because it's a hot role, but they actually enjoy the execution side more. TPM is a natural alternative. Lucas: And the pay is comparable. At the fintech where Dana landed, the base salary was around $140,000, plus equity. That's on par with a senior individual contributor role, but you're not grinding through code all day. You're solving coordination problems. Luna: What about the interview process? Is it similar to a dev interview? Lucas: Not really. There's usually no leetcode. Instead, you get a scenario like 'We're launching a new feature in three months. The design team is behind, the engineering team is overcommitted, and the marketing team needs assets. Walk me through how you'd handle it.' It's all about prioritization, communication, and risk mitigation. Dana said she practiced by thinking through past projects and asking herself 'What went wrong? How did I fix it?' Luna: That's a great prep strategy. Also, I'd add — learn the vocabulary of program management. Things like RACI charts, critical path, escalation paths. You don't need to be an expert, but being able to use those terms naturally signals that you've done your homework. Lucas: Right. And one more thing: certifications. There's no universally required cert for TPM, but something like the Certified ScrumMaster or a Project Management Professional can help if you're competing against candidates with more experience. Dana didn't have either, but she had a strong story. So it's not a must. Luna: I think the key takeaway is that bootcamp grads should not count themselves out for TPM. The skills they have — technical literacy, agile experience, stakeholder management from group work — are directly applicable. It's about reframing them. Lucas: Yeah, and the timing is good. Many companies are realizing they need more people who can bridge the gap between engineering and business. TPM is that bridge. If you're a bootcamp grad looking for a role where your coding background is an asset but you don't want to be coding all day, it's worth a serious look. Luna: Hey, before we wrap up — I want to mention something. If this episode helped you think through a career move or decision, honestly, that's the whole reason we do this. And if it was worth a coffee to you, there's a link — buy me a coffee dot com slash fexingo. That kind of listener support is what keeps this show ad-free and focused on practical advice. Lucas: Absolutely. We don't do sponsors, we don't do ads. It's just us and the listener. So if you find value in what we're doing, that's the place to show it. No pressure, ever. Luna: Yeah. And now back to TPM — one last piece of advice: if you're going to make this pivot, start building your program management muscle today. Even if it's just organizing a team lunch. It's the same skill set. Lucas: Ha, that's actually true. Organizing a team lunch with dietary restrictions is basically a small program. If you can do that without anyone getting hangry, you're on your way. Luna: Exactly. So for anyone listening, try to take on a coordination task at work or even in a volunteer setting. That experience will give you concrete stories for interviews. Lucas: Alright, that's it for today. Next time we'll talk about transitioning into developer relations — another path a lot of bootcamp grads don't know about. See you then.