Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition into Product Management
Transcript
- Lucas: Alright, here's something I've been hearing a lot lately from bootcamp grads who've been in their first dev or QA role for about a year. They start looking around and thinking: 'I like the problem-solving part, but I want to be the person who decides what gets built, not just the person who builds it.' That's the product management itch. Luna: Yeah, I've seen that too. And a lot of them assume they need a CS degree or an MBA to even be considered for a PM role. But that's not really true. Lucas: Not at all. In fact, bootcamp grads have a couple of unfair advantages for product management. First, they're technically literate—they understand how software is actually built. And second, most bootcamps are structured around agile, user-centered projects. That's basically the PM playbook. Luna: So the question is: how do you reframe that bootcamp experience as PM experience on your resume? Lucas: Right. Let's walk through it. The typical bootcamp project: you build an app, you do user research, you prioritize features, you ship in two weeks. That's exactly what a PM does. You just need to change the language. Instead of 'built a React front-end for a task manager app,' say 'led product definition and user testing for a task manager app, resulting in 40 percent user retention over two weeks.' Luna: I love that. It's not lying—it's translating. And when you present it in an interview, you can talk about the trade-offs you had to make. Why did you choose that feature over another? How did you handle scope creep? Lucas: Exactly. And that's what PM hiring managers want to hear. They don't care that you can write a for-loop; they care that you can decide which for-loop to write and why. There's a survey from Product School—published in early 2025—that showed 23 percent of new PM hires came from non-traditional backgrounds. Bootcamps, self-taught, career changers. That's almost one in four. Luna: That's a big number. But let's be real—there's also a misconception that PM is an easy way out of coding. Some people think it's just meetings and sticky notes. Lucas: Yeah, and that's dangerous. PM is not a step down from engineering; it's a lateral move into a different kind of hard work. You're still problem-solving, but now the problems are about people, priorities, and politics. You're the person who has to say no to stakeholders. You're the person who has to defend the roadmap. It's not for everyone. Luna: And you lose the deep technical craft. If you love refactoring code and optimizing queries, PM will probably frustrate you. But if you love strategy and user impact, it's a great fit. Lucas: Let's talk about a concrete example. I spoke with a bootcamp grad named Maria—she did a full-stack bootcamp in 2023, got a front-end role at a mid-size SaaS company called Flowtrac. After about 14 months, she started taking on more product-adjacent tasks. She volunteered to write user stories for her sprint team. She sat in on customer calls. She started a product discovery doc that the senior PM noticed. Luna: That's the move. You don't apply for a PM job cold; you grow into it inside your current company. It's way easier to transition internally because they already know you and trust your judgment. Lucas: Exactly. Maria's manager created a sort of 'PM intern' role for her—she spent 50 percent of her time on PM tasks, 50 percent still coding. Six months later, a PM position opened up, and she got it. Total time from bootcamp to PM: about 18 months. Luna: That's impressive. And she didn't get a PM certification, right? Lucas: She didn't. She considered the Certified Scrum Product Owner, but her manager told her it wasn't necessary for an internal move. Now, if you're applying externally, some hiring managers do look for that CSPO or a product management certification from Reforge or Product School. But it's not a hard requirement. Luna: Honestly, if today's episode helped you think about a possible pivot into product management, that's exactly the kind of thing that makes this show worth doing. And if it was worth a coffee to you, you can find us at buy me a coffee dot com slash fexingo. Seriously, even a single coffee's worth helps us keep this ad-free. Lucas: Yeah, no pressure at all. We're just grateful you're here. But listener support does let us spend time researching episodes like this one. Luna: Alright, back to it. So for bootcamp grads who want to go the external application route, what's the first step? Lucas: First, you need to understand the PM interview process. It's very different from coding interviews. There's no whiteboarding algorithms. Instead, you'll get product sense questions: 'Design a feature for Instagram that improves user engagement.' Or analytical questions: 'How would you measure the success of a new checkout flow?' And behavioral questions: 'Tell me about a time you disagreed with a stakeholder.' Luna: So bootcamp grads need to practice a whole new muscle. And the best way to practice is to do mock interviews with other aspiring PMs. There are communities like Product Buds or the Product School Slack. Lucas: Right. And you can also do PM work on the side. Offer to help a local nonprofit define their product requirements. Or write product specs for an open-source project you use. That gives you real artifacts to show. Luna: What about networking? Does the typical PM networking path look different from engineering? Lucas: It's actually more formal. PM roles are often filled through referrals, but you can't just cold message a senior PM on LinkedIn and say 'hire me.' You need to build relationships. One approach: find PMs at companies you admire, read their blog posts or conference talks, and then reach out with a thoughtful question about something they wrote. Over time, that turns into a conversation. Luna: I'd also add: go to product management meetups. They're less crowded than engineering meetups, so you'll actually get to talk to people. And PMs love talking about their work. Lucas: True. And there's a specific angle for bootcamp grads: you can position yourself as someone who understands engineering constraints. That's a huge selling point. Many PMs come from consulting or marketing backgrounds and struggle to earn engineers' trust. You already have that trust because you've been in their shoes. Luna: So your narrative could be: 'I spent a year as a developer, which taught me what's technically feasible and how to communicate with engineers. Now I want to apply that to the product side.' That's compelling. Lucas: Very. Now, one more thing: salary expectations. A PM role—especially at a startup—can pay similarly to a senior developer role, but the range is wide. At a Series B startup, a PM might make $110,000 to $140,000 base. At a big tech company, it can go over $200,000 with equity. But your first PM role might be a lateral move pay-wise. Maria took a slight pay cut initially, but within two years she was making more than she did as a developer. Luna: So the long-term upside is there. The question is: are you willing to start over at the bottom of a new ladder? Lucas: That's the key. If you're three years into an engineering career and you switch to PM, you're basically an associate PM again. That can be a hard pill to swallow. But if you're only one year in—like Maria—it's easier. Luna: Let's talk about certifications again. You mentioned CSPO and Product School. Are there any that actually move the needle? Lucas: In my opinion, the ones that matter most are the ones that teach you frameworks and give you a portfolio project. Reforge's Product Management program is well regarded. The Product School certification is decent for networking. But the CSPO is really just a two-day class—it doesn't teach you product strategy. So I'd prioritize learning over the piece of paper. Luna: And books? What should someone read? Lucas: "Inspired" by Marty Cagan is the classic. "The Lean Startup" by Eric Ries. "Escaping the Build Trap" by Melissa Perri. And if you want something practical, "The Product Manager Interview" by Lewis C. Lin has sample questions and frameworks. Luna: Solid list. I'd also add "Hooked" by Nir Eyal for the habit-forming product angle. But here's the thing: you can read all the books, but until you actually try to define a product roadmap and defend it to a stakeholder, you don't really know if you'll like it. Lucas: Exactly. So my advice is: try before you buy. Shadow a PM for a day. Volunteer for product-related tasks at your current job. Run a side project as a PM. You'll know pretty quickly if the ambiguity and constant communication energize you or drain you. Luna: And if it drains you, that's fine. You can stay in engineering and be a better engineer for understanding the product side. It's not a loss either way. Lucas: I think that's a great note to end on. For bootcamp grads, product management is a real path, but it requires deliberate effort to reframe your experience and build new skills. The good news: you already have a head start. Luna: Yeah. And the market is open to it. That 23 percent from the survey—it's growing. Companies are starting to value diverse backgrounds more. Lucas: Alright, that's all for this episode. We'll be back next week with another angle on career change. Until then, keep building—and keep thinking about what to build.