Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Pivot Into Product Management
Transcript
- Lucas: So you finished a coding bootcamp, you can build stuff, you've shipped a couple of side projects — but now you're wondering if you want to actually build things for the rest of your career, or if there's a way to help decide what gets built. Luna: You're talking about product management. Lucas: Exactly. And I think bootcamp grads are sleeping on this path. There's this assumption that PM is a role for people with MBAs from Stanford or ten years of engineering experience. But the reality — especially at early-stage startups and for associate product manager roles — is that PM is about communication, curiosity, and a willingness to be wrong in public. And bootcamp grads already have a huge head start on the technical literacy part. Luna: Technical literacy is key. You don't need to be the best coder on the team, but you need to understand what's hard and what's easy, what takes two days versus two months. Lucas: Right. And that's exactly what bootcamp teaches you — not just syntax, but the rhythm of building. You've felt the pain of scope creep. You know why a 'simple' feature can spiral into a three-week refactor. That empathy is gold in a PM. Luna: So what's the concrete path? Let's say I'm a bootcamp grad working as a junior dev, or maybe I'm still looking for my first tech role. How do I pivot toward PM? Lucas: I think the smartest first step is to start doing PM work in your current role, even if your title says 'developer.' Volunteer to write the product requirements doc for the next feature. Lead the user research sessions. Run the stand-up when the PM is out. That's how you build a narrative — 'I've already been doing the job.' Luna: And if you're not in a tech role yet? If you're still job hunting? Lucas: Then you build a PM portfolio the same way you built a dev portfolio. Pick a product — could be a real app you use, could be a hypothetical — and write a full mock product requirements document for a new feature. Include user stories, acceptance criteria, wireframes — even if they're rough — and a prioritization framework like RICE. Then share it publicly on LinkedIn or Medium. It shows you understand the PM process. Luna: RICE stands for Reach, Impact, Confidence, and Effort, right? That's a common prioritization framework. Lucas: Yeah, and there are others — MoSCoW, Kano model — but RICE is widely used and easy to explain in interviews. The point is you can demonstrate product thinking without having a formal product title. Luna: I want to talk about a specific case. A friend of mine — let's call her Maya — was a high school teacher for five years, then did a web development bootcamp in 2023. She worked as a junior dev for about a year at a small SaaS company, but she kept gravitating toward the product side. She'd ask 'why are we building this?' in meetings, she'd talk to customers on support calls. Eventually she applied for an associate product manager role at a Series B fintech startup and got it. Lucas: What did she emphasize in the interview? Luna: She told me she leaned hard on her teaching experience. Classroom management is stakeholder management. Lesson planning is roadmapping. Explaining calculus to teenagers is communicating complex ideas to non-technical audiences. The hiring manager told her they'd rather teach product frameworks to someone who already knows how to listen and synthesize than the other way around. Lucas: That's such a powerful framing. It's not about hiding your non-tech background — it's about reframing it as a strength. Every PM job ultimately requires you to understand users, influence without authority, and make decisions with incomplete information. Teachers do that every single day. Luna: Exactly. And I think that's the message for bootcamp grads — you already have transferable skills. The technical foundation from bootcamp gives you credibility with engineers, but your past career gives you the soft skills that actually differentiate great PMs. Lucas: So let's talk about the job titles to target. The most common entry point is Associate Product Manager, or APM. A lot of big tech companies have formal APM programs — Google, Meta, Microsoft — but those are hyper-competitive. I think bootcamp grads have a better shot at smaller companies, Series A through C, where the PM role is less defined and they value versatility over pedigree. Luna: Right. And those smaller companies often don't have the budget for a Stanford MBA, so they're more open to hiring someone with a bootcamp background and a few years of professional experience in any field. Lucas: The other title to look for is 'Product Owner' — it's more common in agencies and consultancies, and it's more execution-focused, but it's a stepping stone. And 'Technical Product Manager' is also an option, though that usually requires more engineering experience. Luna: What about the skills you need to learn? Beyond what you already know from bootcamp. Lucas: You need to get comfortable with data analysis — not just writing SQL queries, but knowing which metrics matter for your product. You need to understand A/B testing, cohort analysis, retention curves. You don't need to be a data scientist, but you should be able to ask 'is this experiment statistically significant?' and know what that means. Luna: And you need to learn how to write a good product requirements doc. That's a specific genre of writing — clear, concise, with well-defined acceptance criteria. Lucas: Yeah. And the other big skill is user research. How to conduct a customer interview without leading the witness. How to synthesize feedback into themes. How to decide when to trust user input and when to ignore it. That's a craft in itself. Luna: I think bootcamp grads actually have an advantage here because they're used to learning by doing. They've built projects, they've iterated based on feedback. That mindset is perfect for product work. Lucas: Exactly. And one more thing — don't underestimate the value of building a product community. Join product management Slack groups, attend product meetups, follow product thinkers on LinkedIn. The product world is surprisingly open and generous with advice. And when you do land that PM role, you'll have a network to lean on. Luna: Speaking of community, if you've gotten value from this show — maybe it helped you think through a career move or gave you a new idea to try — we keep this podcast ad-free because of listeners who support us directly. Lucas: Yeah. If you'd like to help us keep the episodes coming, you can buy us a coffee at buy me a coffee dot com slash fexingo. No pressure at all — just a way to say thanks if the show has been useful to you. Luna: And we really appreciate it. Every bit helps us keep doing what we love. Lucas: Alright, back to product management. One more concrete step I want to mention: consider taking a product management course — but not the expensive ones. There are free or low-cost resources from Reforge, Product School, even YouTube. The goal isn't the certificate, it's the vocabulary. If you can talk about 'user stories' and 'MVP' and 'north star metric' fluently, you'll sound like a PM in interviews. Luna: And practice the product sense interview questions. There are tons of examples online — 'design a vending machine for office workers' or 'how would you improve the Twitter onboarding experience?' The key is to show your thinking process, not to get the 'right' answer. Lucas: Exactly. Walk through the steps: clarify the goal, identify the user, brainstorm solutions, prioritize, and explain your reasoning. That structure alone will set you apart from most candidates. Luna: I think the biggest takeaway from this episode is that bootcamp grads shouldn't see PM as a distant, unreachable role. The skills are learnable, the entry points exist, and your background — whatever it is — is an asset, not a liability. Lucas: Yeah. And if you're already in a dev role, you're even closer than you think. Start doing PM tasks. Build the portfolio. Network with product people. And when you're ready, apply. The market needs more PMs who actually understand how software gets built. Luna: And that's a wrap for Episode 44. Next time, we'll talk about how bootcamp grads can break into data engineering. Lucas: See you then.