Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Product Management
Transcript
- Lucas: So you finished a coding bootcamp, you've been working as a junior developer for maybe a year or two, and you're starting to realize that what you actually enjoy most isn't writing the code itself—it's figuring out what to build, and why. Luna: Yeah, you're the person who's always asking 'why are we building this feature?' in sprint planning. And everyone else is just heads-down on tickets. Lucas: Exactly. That instinct—the strategic curiosity—is the exact signal that product management might be a better fit. And for bootcamp grads especially, the move from engineer to product manager is actually one of the most natural pivots in tech. But it's one that people don't talk about enough. Luna: Right, because there's this assumption that you need an MBA or a business background. But that's not really true, especially for technical product roles. Lucas: If we've helped you think through a career move like this one, and you want to see more episodes that dig into the specifics, listener support is what keeps this show ad-free. You can help at buy me a coffee dot com slash fexingo. It's a small thing that makes a big difference for us. Luna: Totally. And we really appreciate it. Now, let's get into how you actually make that pivot. Lucas: Let's start with a real example. I was talking to a bootcamp grad named Priya last month. She graduated from a full-stack program in 2024, spent about 14 months as a junior dev at a mid-size SaaS company—think a company with about 200 employees, B2B product. And she made the move to associate product manager internally. Luna: Fourteen months is pretty fast. What was the trigger? Lucas: She said she kept volunteering for cross-functional stuff. When the product manager needed someone to do user research interviews, she raised her hand. When the design team needed feedback on prototypes, she sat in on those sessions. She basically made herself the bridge between engineering and product before she had the title. Luna: So she was doing the job without the title. That's a classic move. Lucas: Classic, and it works. But it only works if you also frame it correctly on your resume and in interviews. And that's where a lot of bootcamp grads trip up—they list 'wrote React components' and 'fixed bugs' when they should be listing 'collaborated with product to define user stories' and 'identified three usability issues through customer interviews that reduced churn.' Luna: So reframing your experience from a product lens. What are the specific skills that transfer? Lucas: There are three big ones. First, technical feasibility. Good PMs know what's hard to build and what's easy. Bootcamp grads have hands-on experience with APIs, databases, and front-end frameworks, so they can push back on unrealistic timelines or scope creep with actual engineering credibility. Second, data literacy—most bootcamps teach some SQL, some basic analytics. That's huge for a PM role where you're constantly looking at usage metrics and A/B test results. And third, user empathy. Bootcamp projects often involve building for real users. That's closer to product thinking than most CS degrees. Luna: I'd add one more: stakeholder management. As a developer, you're already negotiating with product, design, and maybe even sales. That muscle is directly transferable. Lucas: Absolutely. So if you're a bootcamp grad considering this move, the first step is to start behaving like a PM before you apply. Volunteer for the user research. Ask to sit in on product reviews. Offer to write user stories or acceptance criteria for a small feature. And then when you do apply, your resume should lead with impact statements, not code. Luna: What about the interview process? Product management interviews are pretty different from engineering interviews. Lucas: Completely different. You won't get a whiteboarding algorithm question. Instead, you'll get product case interviews: 'How would you improve our onboarding flow?' or 'Design a feature to increase retention among free users.' The framework matters more than the answer. You want to show you can structure thinking: define the goal, understand the user, generate ideas, prioritize, and propose a way to measure success. Luna: So it's less about the perfect answer and more about the thought process. That's actually good news for bootcamp grads who are used to problem-solving under time pressure. Lucas: Exactly. And there are great resources to practice—sites like Product School and Exponent have sample cases with walkthroughs. But the key is to practice out loud. Record yourself. You want to sound structured but conversational. And if you don't have a formal product background, lean into your technical experience. Say 'I'm a builder who wants to solve user problems.' Luna: One thing I've seen work well is building a side project that showcases product thinking. Like launching a small app or feature and documenting the decisions you made—why you built what you built, what you learned from users, what you'd do next. Lucas: That's gold. That becomes a portfolio piece. And it's way more convincing than a credential. I've talked to hiring managers at companies like Atlassian and Intercom who actively look for candidates who can show product instinct, not just a degree. Luna: So if someone is listening and thinking 'this sounds like me,' what's the first action they should take this week? Lucas: Schedule a coffee chat with a product manager at your company or in your network. Ask them what a typical week looks like. What decisions they own. What they wish they'd known when they started. Then ask yourself if that reality excites you. If it does, start volunteering on a product adjacent task by the end of the month. Luna: And if you don't have a product manager to talk to, there are tons of PM Slack communities and LinkedIn groups where people are open to mentoring. The bootcamp community is actually pretty tight-knit that way. Lucas: One more thing I want to address: the myth that you need an MBA to be a PM. It's just not true. According to data from the product management association, about 30 percent of product managers have an MBA. That means 70 percent don't. And that number's been trending down as companies prioritize skills over credentials. Luna: So the door is open. It just requires intentionality. Lucas: Exactly. Priya, the bootcamp grad I mentioned, she didn't have an MBA. She had 14 months of dev experience, a willingness to learn, and a portfolio of product work she'd done on the side. She got the role because she proved she could think like a PM before she had the title. Luna: That's the model. And it's replicable. Lucas: Next week, we're going to talk about another pivot that's gaining traction: bootcamp grads moving into technical writing. Not documentation, but developer experience and API docs. It's a niche with great pay and remote flexibility. Luna: Looking forward to that. For now, if you're thinking about product management, start acting like a PM today. Lucas: Thanks for listening, we'll see you next time.