Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Product Management
Transcript
- Lucas: Let’s talk about one of the most common questions I get from bootcamp grads: 'Can I move into product management without a computer science degree?' And the short answer is yes — but the path looks very different from the one you’d take for a pure engineering role. Luna: I’ve seen a few people make that leap. A friend of mine finished a web dev bootcamp in 2023, worked as a junior developer for about a year, and then shifted into a PM role at a mid-size SaaS company. It took him about eight months from the moment he decided to pivot. Lucas: That timeline is pretty realistic. The key is that bootcamp grads already have something most career changers lack: they can speak the language of engineers. They understand agile ceremonies, they know what a pull request is, they’ve written user stories in a technical context. That’s a huge advantage over someone coming from marketing or sales. Luna: Right, but I think a lot of bootcamp grads underestimate how different the PM skill set is from coding. It’s less about building the thing and more about deciding what to build and why. Lucas: Exactly. The biggest gap I see is in what’s called 'product sense' — the ability to identify a real user problem, evaluate trade-offs, and prioritize features based on business impact. That’s not something bootcamps typically teach. But it is something you can practice. Luna: How would you recommend someone start practicing? Like, what’s the first step? Lucas: I’d start with reverse-engineering products you use every day. Pick a feature in an app you love — say, the 'swipe to archive' in Gmail. Ask yourself: what problem does this solve? Who asked for it? What metrics would tell you it’s working? Then write a one-page product brief. Luna: That’s essentially a mock case study. I’ve seen hiring managers be impressed when a candidate brings a portfolio of those briefs — especially if they also include user research, even if it’s just talking to five friends. Lucas: Yeah, and that ties into another thing bootcamp grads can leverage: their capstone project. If you built a full-stack app in your bootcamp, you already have a product. The question is, can you talk about it like a PM? Why did you choose those features? How did you validate the idea? What would you do next if you had a team of three engineers? Luna: That reframing is huge. Instead of saying 'I built an e-commerce site with React and Node,' you say 'I identified that small sellers needed a simple inventory tool, so I built an MVP, tested it with five shop owners, and iterated based on feedback.' Lucas: That’s exactly the kind of story that gets you past the resume screen. But the interview itself is a different beast. Most PM interviews have a 'product sense' round where they ask something like 'design a new feature for Instagram.' And they don’t want a perfect answer — they want to see your thinking process. Luna: So what’s the framework for that? Because I think a lot of people freeze when they hear 'design a feature.' Lucas: The simplest structure is: clarify the goal, identify the user, list their pain points, propose a solution, and then talk about how you’d measure success. For example, if they say 'design a feature for Instagram,' you might ask 'for which user? A creator, a casual user, or a brand?' Then you pick one and go deep. Luna: That also shows you can handle ambiguity — which is a big part of the job. I think bootcamp grads are actually pretty good at that because they’ve already navigated a career transition. Lucas: True. And there’s one more advantage: bootcamp grads tend to be very comfortable with fast iteration. They’ve shipped projects in weeks, not months. That aligns well with how modern product teams work — especially in startups and scale-ups. Luna: That said, do you think bootcamp grads need a certification to be taken seriously? Like a CSPO or something? Lucas: Honestly, no. A certification like Certified Scrum Product Owner can help you get past HR filters, but it’s not a substitute for real product thinking. I’d rather see a candidate who has written a product brief for a fake feature than one who has a cert but can’t explain trade-offs. Luna: Yeah, I’ve heard hiring managers say that. They want to see that you can talk to customers, prioritize a backlog, and say no to stakeholders. Lucas: That last point — saying no — is actually one of the hardest skills. And bootcamp grads sometimes struggle with it because they’re used to being told what to build. In product, you’re constantly pushing back on requests that don’t align with the roadmap. Luna: How do you practice that? It’s not exactly something you can mock. Lucas: You can practice by doing stakeholder interviews with friends who play the role. Or even better, if you’re in a current job, volunteer to shadow a PM or product owner. Most teams welcome an extra hand with user research or documentation. Luna: That’s a good point. Internal mobility is often the easiest path. I’ve seen developers move into PM within the same company just by expressing interest and asking to sit in on product reviews. Lucas: That’s how my friend did it. He was a dev on a team, and he started writing user stories for bugs and small features. After a few months, the PM noticed and offered him a junior PM role when a spot opened up. Luna: That’s a great example. And it shows you don’t need a fancy title — you just need to start doing the work. Lucas: Honestly, if this episode helped you think through a career move or gave you one practical idea, that’s exactly why we make it. If it’s worth a coffee to you, the link is buy me a coffee dot com slash fexingo. No pressure — but listener support is what keeps this show ad-free. Luna: Yeah, it really does. And it means we can keep digging into these specific transition paths without worrying about sponsors. Lucas: So back to the practical side: once you have that portfolio of product briefs and you’ve practiced the interview framework, the next step is networking. And for bootcamp grads, I think the best place to start is your bootcamp’s alumni network. Luna: Those groups are gold. Most bootcamps have a Slack or Discord with thousands of alumni, and many of them are working in product. A simple message like 'Hey, I’m exploring PM — could I buy you coffee and ask about your path?' works way more often than people think. Lucas: And when you do those informational interviews, ask specific questions. Not 'how do I become a PM?' but 'what was the biggest gap you had to close when you moved into product?' That gets you actionable advice. Luna: What about the resume? Should bootcamp grads list their bootcamp under education, or lead with their project experience? Lucas: Lead with the project. List the bootcamp, but frame it as a product experience. Under your bootcamp project, write something like: 'Defined product requirements, conducted user interviews with 10 small business owners, and built an MVP that reduced inventory errors by 30 percent in testing.' That reads as PM experience. Luna: That’s smart. And if they have any data from their current job — even if it’s not a product role — they should include that too. Like 'Improved customer onboarding time by 20 percent by suggesting a process change.' Lucas: Exactly. Product managers are storytellers. You need to weave a narrative that shows you can identify problems, drive decisions, and collaborate across teams. Bootcamp grads have the technical foundation — now they just need to reframe their experience. Luna: I think the biggest takeaway is that it’s not about having a PM title on your resume. It’s about demonstrating product thinking, even if it’s through side projects or volunteering. Lucas: One last thing: the job market for junior PMs is competitive, but it’s not impossible. Companies like Asana, HubSpot, and even some banks hire associate product managers without requiring years of experience. The key is to tailor your application to each company’s product and user base. Luna: And don’t be afraid to apply to roles that aren’t explicitly labeled 'product manager.' Titles like 'product analyst' or 'technical product owner' can be a foot in the door. Lucas: Right. Once you’re in, you can grow. The first PM role is the hardest to get — after that, the experience speaks for itself. Luna: So for anyone listening who’s thinking about making the switch, start with one product brief this week. That’s a concrete step. Lucas: Do that, and you’ll already be ahead of most candidates. Good luck out there.