Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Product Management
Transcript
- Lucas: So, we've talked a lot about breaking into specific technical roles, but today I want to tackle something different. I want to look at how bootcamp grads can pivot into product management. And I think this is a really timely question, because a lot of the folks I talk to who've spent a couple of years in engineering start to feel that pull toward the 'why' and the 'what' rather than just the 'how.' Luna: Oh, that's interesting. And it's not like you're leaving coding behind, right? It's more like you're expanding your toolkit. Lucas: Exactly. And that's a key point. One of the biggest misconceptions about moving into product is that you're abandoning your technical skills. But actually, your coding background becomes your superpower. You can speak the language of engineers, you can estimate feasibility, and you can spot technical debt a mile away. I remember a case study from a few years back where a bootcamp grad with a background in Python became a product manager at a mid-size SaaS company, and she told me that her ability to prototype quickly and read code was what set her apart in the interview process. Luna: So it's not about forgetting the code, it's about leveraging it differently. So what's the actual first step for someone who's thinking about making this switch? Lucas: The first step is to understand what product management really is. It's not a role where you're the boss of the engineers. It's a role where you're the bridge between the business, the users, and the development team. You're responsible for setting the vision, prioritizing features, and making sure the team is building the right thing. And that sounds simple, but it involves a lot of customer interviews, data analysis, and stakeholder management. Luna: And that's a big shift from the very defined world of writing code. How do you even start building those skills if you're not in that role yet? Lucas: Well, one of the most practical things you can do is to start acting like a product manager in your current job, even if you're not one. Volunteer to lead a feature, talk to users, write a PRD, or even just document the problems you're seeing. That's exactly what the person I mentioned did. She started by asking her engineering manager if she could sit in on customer support calls, and then she started writing up a one-page analysis of the most common pain points. That got her noticed. Luna: That's a great example. And it's not about having the title, it's about showing you can do the work. But I'm curious, what about the formal side? Do you need an MBA or a product management certificate? Lucas: That's a big question, and the short answer is no. I know that some of the big tech companies have historically hired a lot of MBA grads for PM roles, but that's changing. In fact, there's a growing recognition that technical skills and a track record of shipping things are just as valuable, if not more. A friend of mine who's a hiring manager at a fintech startup told me that they now explicitly look for candidates who can write a SQL query and talk to customers, rather than those with a fancy degree. Luna: So it's more about skills and evidence than credentials. That's encouraging for bootcamp grads. But what about the interview process? I imagine it's very different from a coding interview. Lucas: Oh, it's night and day. Coding interviews are usually about solving an algorithm problem. Product interviews are about how you think through a problem. They'll give you a scenario like 'Our mobile app has a fifty percent drop-off at the signup screen, what do you do?' And they're looking for a structured approach: start with understanding the user, form hypotheses, think about metrics, and then propose a solution. They also want to see that you can communicate clearly and collaborate. Luna: So it's less about the right answer and more about the way you think. Do you have a specific framework you recommend for answering those kinds of questions? Lucas: Yeah, the one I always come back to is the 'CIRCLES' method, which is a popular mnemonic. It stands for Comprehend the situation, Identify the customer, Report the customer's needs, Cut through prioritization, List solutions, Evaluate trade-offs, and Summarize your recommendation. You don't have to follow it rigidly, but it gives you a structure to make sure you cover the bases. Luna: I like that. It's a way to stay calm and organized under pressure. And you mentioned metrics earlier, which brings up a good point. How important is it for a product manager to be data-savvy? Lucas: I'd say it's essential. You don't need to be a data scientist, but you need to be comfortable with numbers. You should be able to define the key metrics for your product, understand how to analyze them, and be able to explain them to others. The good news for bootcamp grads is that they often have some background in SQL or Python, which is a huge plus. In fact, a survey by a product management community found that over sixty percent of PM job descriptions now mention SQL as a preferred skill. Luna: That's a really concrete statistic. So if you're a bootcamp grad who already has some SQL under your belt, you're already ahead of the pack. But what about the business side? How do you get that customer empathy if you've been living in a codebase for a while? Lucas: That's where you have to make a deliberate effort to get out of your comfort zone. Start by talking to users, even if it's just five calls a week. Listen to support calls, read app store reviews, and try to understand the problems people are facing. You can also do what we call 'customer discovery' in your own time. Pick a product you use, and try to figure out why they made certain decisions. It's like a muscle that you have to train. Luna: Speaking of training muscles, this is a career change podcast, and we're all about helping you make moves. And we've been doing that for years, and it's been ad-free because of the support from listeners like you. If you've found a piece of advice that's helped you, or if you just like what we're putting out, you can support us at buy me a coffee dot com slash fexingo. It takes a minute, and it keeps the show going. Lucas: Yeah, we really appreciate that. It's a small thing that makes a big difference. And, actually, that's a perfect segue. One of the best ways to build that customer empathy muscle is to work on a side project. And not just a tech side project, but one where you have to talk to people and make product decisions. Luna: Oh, that's true. Like building a small app for a specific niche, and then actually trying to get people to use it. That would force you to do all the PM stuff: defining the value prop, prioritizing features, and measuring success. Lucas: Right, and it doesn't have to be a big thing. It could be a simple tool for a local community group, or a side feature for an open-source project. The key is to document your process. Write a case study about how you identified the problem, what you built, and what the impact was. That becomes your portfolio piece for PM interviews. Luna: And that's a lot more compelling than just saying 'I want to be a PM.' It shows you've done it. So what's the best way to find that first PM role? Is it any different from finding a dev job? Lucas: It's both similar and different. Networking is still huge, but you might need to tap into different circles. Instead of just going to tech meetups, you might want to go to product-focused events or even business meetups. Also, consider looking for PM roles at companies that are smaller or less sexy, because they're often more willing to take a chance on someone with a non-traditional background. You can also look for 'associate product manager' roles, which are specifically designed for people making this transition. Luna: And if you're coming from a bootcamp, you might not have the network of an MBA grad, but you do have a network of fellow bootcamp alums. Have you seen people use that to their advantage? Lucas: Absolutely. Bootcamp alumni networks are incredibly strong. I've seen people form study groups to practice PM case interviews, share job leads, and even refer each other. There's a real community feel. And that's something that a lot of hiring managers find attractive: you're not just a lone wolf, you're someone who knows how to collaborate. Luna: That's a great point. And I think it also speaks to a broader shift in the industry. We've been talking about skills-based hiring for a while now, and it seems like product management is catching up with that trend. Do you think that's fair to say? Lucas: Definitely. In fact, I read a report earlier this year that said the number of job posts for product managers that require a degree has dropped by about twenty percent over the past three years. More and more, it's about what you can do, not where you went to school. And bootcamp grads are well positioned to show that through their portfolio and their ability to ship. Luna: That's a really encouraging trend. So for someone listening who's been coding for a couple of years and is thinking 'this is great, but I want to have more influence on strategy,' what's the single most important thing they should do this week? Lucas: I'd say start by shadowing a PM at your company, if you have one. Just ask if you can sit in on their backlog grooming or sprint planning. You'll learn a ton just by observing how they think and what questions they ask. And if you don't have a PM, then start reading some product blogs or books, like 'Inspired' by Marty Cagan. But the key is to start doing, not just reading. Luna: I think that's the perfect takeaway. It's about moving from the code to the conversation. And I'm curious, for those who make the switch, what's the kind of salary expectation? Is it comparable to a senior dev role? Lucas: That's a tricky one, because it varies a lot by location and company. But in general, product management salaries are competitive with engineering, especially at more senior levels. A mid-level PM at a tech company in a major city might earn anywhere from one hundred twenty to one hundred sixty thousand dollars, plus equity. So it's not a financial step down. And the career trajectory can be very rewarding, because you're not just executing, you're shaping the product. Luna: That's a solid incentive. But also, I think for many people, the appeal is more about the work itself. There's a certain satisfaction in taking ownership of a product's success. Lucas: For sure. And that's really what product management is about: ownership and impact. You get to see the direct result of your decisions in how users engage with the product. And I think for many bootcamp grads who are looking for that next challenge, it's a natural evolution. You've mastered the craft of building, and now you want to master the craft of deciding what to build. Luna: That's a really nice way to frame it. So if you're listening and you're a bootcamp grad who's been thinking about this move, I hope this episode gave you some practical steps and a bit of confidence. And remember, your technical background is not a liability, it's an asset. Lucas: Exactly. So go out there, start talking to users, and start thinking like a product manager. And if you have questions, you can always reach out to us on social media. We'd love to hear how it goes.