Introduction
I'm part of a few mentorship programs and I usually get matched with people who are directly or indirectly interested in product management. After people decide that they want to explore product management as a career, the first question they ask is how to practically get into it. This article is usually my answer to that.
For an overview of what product management is, what are the types of product managers, and what skills you will need to know, check out my other articles. This one will focus mostly on what career path and specific resume points will get you past a CV screening for a product management job. Once you get there, what decides whether you're going to get the job or not is how you’re going to perform in the interviews. Following one of the paths outlined here will give you some experiences to talk through behavioral style interviews. The interview steps themselves vary widely company from company. I will write an article on how I personally like to structure product management interviews, however, not many companies follow that process. The internet is usually your best friend in figuring out what specific companies ask for during the interview process.
Out of each path, I will also cover my experience in evaluating the success that I have observed in people that have followed each of those paths.
External transfer versus internal transfer
There are three major ways that you can become a product manager, assuming you don't already hold a product management title:
- University: Straight out of university
- Internal: By transferring into a product management job in the company you're already working at
- External: By getting hired (or acquired) into a product management job in another company
The majority of people into product management have followed path number two. Overall in my career, through interfacing with people hiring for product managers, I've noticed that they either highly prefer to hire someone who has a product management title outside of the company, or that they want to convert someone they already know inside the company who is not a product manager into a product manager.
This follows a similar dynamic to people management, where people either promote internally individual contributors to become people managers, or hire from outside people that already have people management roles.
Hence, if you are looking to become a product manager and don’t have a product management title, I strongly suggest to focus on either the university or the internal transfer options.
Let’s briefly dive into each.
University - become a Product Manager straight out of university
The way to directly become a product manager out of university with no or little previous work experience is usually through associate product manager (APM) roles. These are rotational programs organized by big tech companies (Google, Meta…) that place you for six month rotations in different teams inside the company for two years and then place you in a full-time product manager role after (if you have been performing well).
Another one is through Product Manager internships. If you do well in those, then there’s a high chance that you will receive a return offer. Else you can use the internship as a way to show experience and get into a full time product manager role.
I'll dive into more detail about APM and internship roles and how well they are a predictor of success later on. What’s important to say at this stage is that students often focus on the APM or internship path, since it is the one that looks most direct out of university, however there are few APM and PM internship roles and they are usually very competitive to get into. Hence, students that over index on this path usually end up disappointed that they do not get the job and do not have any idea what to do as a result of it. Hopefully this article helps you in identifying other paths that you can follow to become a Product Manager.
The one exception to this is MBA graduates. I have seen people getting hired into product management roles after an MBA, especially if they have followed one of the paths listed below before their MBA. It is still not super common, but definitely more realistic compared to new college grads with no experience. Most of these tend to be people that have followed the consulting path outlined below. So I'll refer you to that section for more details.
Internal - transitioning into Product Management inside your company
This is by far the most common way people get hired into product management roles. I suggest you check out some of the paths below and get into those with the aim to then transition into product management. Given there are not a lot of hard skills that product managers need to know, the easiest way to usually be considered for a product management role internally is to get to know the hiring manager and other product managers in their team. If they can speak highly of you, then it's usually fairly easy to transition when a product management role is open.
Whenever any of my managers ever had an open product management position, they would firstly ask each of the product managers reporting to them if they had any people in mind inside the company, regardless of whether those people were product managers or not. I’ve seen a few of those transfers at Lyft, mostly from data scientist and data analyst roles, and they were all successful.
Hence it pays to start getting to know product managers inside your company early and letting them know that you are interested in moving into a product management role. You want them to think about you whenever a new product management position is open.
Needless to say, if you are a high performer in your current role that makes it easier to be considered for a product management (or really any) role. If you end up in a career for which you're not a great fit and are not performing great, it's usually pretty difficult for a hiring manager to seriously consider you even if your skillset is better positioned for product management. So becoming a strong performer is usually a good first step in any role change.
External - getting hired into Product Management inside another company
I have rarely seen this with one exception. I suggest transferring into a product management role inside your company before looking for external opportunities. If your company does not have a product management role and you have been following one of the paths below, then usually considering an MBA or graduate studies is also an alternative (and aiming for entry level product management roles after that).
The one exception to external hires is acquisitions. Usually when a bigger company acquires a smaller startup, it is hard for the bigger company to find appropriate titled roles for the founder or CX level executives. Often, given the CEOs of startups are often also the “product person”, they are assigned product roles (either people management or individual contributor roles). So if all else fails, creating your own startup and aiming to be acquired can be a path also towards product management, albeit a long and very uncertain one.
Paths to Product Management in detail
Software Engineer
Predictor of success as a product manager: high (if a good software engineer)
Better suited for: Technical product manager, platform product manager
Type of transition: internal (usual), external (possible at startups)
In my experience this is how this path works:
- a software engineer works on tickets and specs provided by a product manager which they are usually not happy with
- The software engineer proposes changes or deviations to the product spec to the product manager, which the product manager doesn't understand or consider. Alternatively, the software engineer thinks that they are not being provided all the information and the context correctly by the product manager and so they want to be in the broader meetings that product managers usually attend
- The software engineer grows dissatisfied with their product manager and thinks that they could do a better job
- The software engineer starts reading material about product management and preparing for product management interviews, thinking that they rather prefer to be on that side
Given software engineers actually understand how the system works (because they build it), they can be very good technical product managers because they can very clearly articulate what they want the experience and the end result to be in such a way that it's easy for engineers to make it happen. Additionally, if they transition to the role inside the company, they tend to have better relationships with the technical team, resulting in better outcomes.
Software engineers turned product managers tend to have a very fast ramp up cycle because they are inherently knowledgeable of what they are dealing with, hence, when I'm hiring, I tend to look for this kind of profile (because I happen to usually hire for technical product management roles).
Strong characteristics:
- In detail understanding of the system they are working with leads to realistic product proposals and reasonable milestones. Better for predictability and team morale. Tech teams don’t like when PMs set forth proposals which don’t make too much sense and have unreasonable deadlines (happens more often than you think)
- Familiarity with the needs of the developer customer (helpful if the product is SaaS or B2B)
- This is a particularly important skill since sometimes product managers who join B2B companies tend to treat a developer like a non technical consumer user. This is not necessarily wrong but leads to ignoring the importance of documentation and the need for certain developer products to be tuneable and customizable. Usually B2C product managers try to simplify the experience to reduce “friction” which isn’t always the best ROI for B2B / B2D(eveloper) products
Weak characteristics:
- Compared to other paths (consulting etc), software engineers usually are used to working less hours. If they think this is portable to product management, it can sometimes lead to slow delivery. Similarly, they may want to not pressure their former software engineer team mates, thus not setting tight enough deadlines
- I'll cover this elsewhere, but usually product managers need to work longer hours than other roles
- May tend to over-index optimizing for the developer experience and not realizing that sometimes the buyer and payer of the products are other roles inside the company, even though the actual user will be the developer. In those cases, it is usually more important to start tailoring the product to the buyer rather than the end user. See the early example of Microsoft building products for IT admins rather than the actual user. It worked to scale but ultimately led to Apple taking over due to better end user experience
- Usually think that technology rules everything, leading to them deprioritizing / downplaying the importance of design, marketing, and the interaction with other teams
In order to start transitioning to product management, software engineers should start to get more involved in cross-functional meetings and offering to represent the team and the product manager in places where neither the product manager nor the engineering manager have bandwidth to plug in. This can be a great way to increase visibility of the software engineer and ultimately gain buy in for a transition to product management. In all tech teams there are usually projects which the product manager doesn't have bandwidth or interest in overseeing and those are great opportunities to step up and be the de facto product manager for those projects. Doing well on those will be a great preparation for when a product manager role actually opens up.
Keep in mind that I've only seen good developers become good product managers. Good developers usually already need to be fairly cross-functional and debate with product and other roles on the best path forward, providing feedback at the product spec phase. Some engineers realize that they don't like coding or hardware and want to transition to product management for the more “people facing” aspect of the role. That is not a good reason or predictor of success, since it effectively neglects the positive points above, whereas retaining the negative points.
Data Scientist
Predictor of success as a product manager: medium
Better suited for: Data product manager, growth product manager
Type of transition: internal
This is how this path works:
- The data scientist spends a lot of time on the analysis of the success of the product and starts seeing trends and correlation around it
- The data scientist shares this information but the rest of the company doesn't spend too much time on it., leading the rest of the company to lose some of the insights that the data scientist has extracted
- The data scientist grows in their understanding of the product and starts making some proposals which get ignored or not prioritized appropriately
- The data scientist has built such a big knowledge of the product that they think they would do a product manager role better than the product manager
Given the amount of time that the data scientist spends with data, it is usual for them to actually have a better understanding of how the product is going, including the best strengths and the biggest weaknesses of it, compared to the product manager. Product managers have a lot more meetings and cross-functional commitments compared to data scientists, so they tend to spend less time with data, even though being familiar with the data of a product is a key predictor of success for a product manager.
Strong characteristics:
- Strong knowledge of all the data points of the product, leading to great narrative and reasons for prioritization of specific projects. Usually perform well from the point of view of executives and in executive reviews
- Being experiment and data driven ensures that products and features are always measured and decisions are taken based on data (and are so less opinable and contestable by others). Heavy use of experimentation results in frequent small iterations and improvements
- Familiar with data and data pipelines can clearly articulate requirements on data collection and transformation
Weak characteristics:
- Usually not as good at managing their team when it comes to roadmaps, tickets definitions and documentation. Tends to have a hands off approach, requiring to be paired with strong engineering managers
- Not as good at approaching 0 to 1 projects due to lack of data. Can end up in decision paralysis mode when there’s no direct data and indirect data proxies are not reliable (or just not available)
These characteristics are a good summary to point out that data scientists turned PM usually fare better in bigger companies where there is more convincing needed towards executives and less focus on execution. They tend to be better at managing “up” (expectations and narrative towards leaders and executives) rather than managing “down” (their engineering, design or operations teams to ensure that it is clear to them what they have to do).
In my career I've seen data scientists turned PM be very successful at Lyft (where there is a lot of planning and prioritization between an infinite list of small improvements) but not successful at all at Mythical where we were building groundbreaking new products and there were little data points available on how the product could do (since few similar products existed).
At startups you usually want fast execution in uncharted spaces, so PMs which are more gut driven and less data driven have better outcomes for the company. In bigger companies with higher stakes, instead you may want data scientists turned PM to ensure that everything is being measured and each step is not degrading the existing business.
One note of caution to people managing or dealing with data scientists turned PMs: they are usually very good at presenting data and pretty charts. Data scientists themselves tend to want to present the data objectively to inform the action of other teams. PMs instead sometimes bias the data to make it seem that their team is doing a good job. Data scientists turned PMs are very good at data-story-spinning to the point that it can fool a lot of executives, turning the company very political.
Program / Project Management
Predictor of success as a product manager: medium / high
Better suited for: Go to market product manager, platform product manager
Type of transition: internal
This is the path that I have followed and hence I am biased. It is usually easy to get a program or project management job coming outside of university and hence makes it a great path to follow for students who are set on pursuing product management. Project managers get to interface with a lot of the teams at the company, especially those that are needed to ship products. As such, they learn what each team needs and understand stakeholder dynamics better than some of the other roles, which are usually more siloed (like software engineers or data scientists). They get to learn a lot of the soft skills needed to get things done. In the case of technical project managers, they might also learn about how the product is made and what are all the steps needed to ship technology. For many companies (most prominently, Amazon), technical project managers and technical product managers are actually the same role.
Strong characteristics:
- Good at taking a problem and breaking it down into tangible milestones that can be clearly defined as achieved (or not) by the team
- Very organized and schedule-driven, making it clear to the teams the milestones and dates that have to be hit
- Good at documenting the progress of the team and providing updates to stakeholders and executives around the progress of the project (which executives usually appreciate)
Weak characteristics:
- Sometimes over index on writing the schedule and hoping that teams will just follow that, not necessarily going into depth and writing detailed requirements that aid the team
- Sometimes lack of ideas; coming of the belief that all projects need to be sourced by stakeholders and not able to discern the relative importance of projects unless stakeholders clearly ask for something.
- Similarly, lack of opinion. Usually acting as a mediator between different parties rather than bringing forth the point of view of the product and the customer
- May frustrate the team with high pressure on (sometimes artificial) deadlines, especially in the case of products which are more explorative and need more creative and iteration time. This is also a strength though on critical projects
Not surprisingly, the characteristics above line up with those of a project manager. People that come from project management usually excel as product managers in teams which have a lot of requests from stakeholders and are used to prioritizing and designing for a specific and clear set of customers. This fits perfectly with platform product management roles in bigger companies. They are also a good fit for go-to-market product managers given a big part of that job is actually project management.
I started my career with the official title of go-to-market product manager, though I was effectively a technical project manager. It helped me become familiar with all the teams and steps needed in the creation, launch and ramp up of the hardware product. In my role, I then used the experience to effectively come up with ideas and propose solutions to problems and challenges that we were facing. I effectively then became a product manager, even though my title didn't change.
In my first role, one of my biggest achievements was to kickstart a modular platform project to serve the needs of the automotive, robotics, medical and 5G teams, with all of whom I had interfaced previously and independently during the launch of other products. My role as a project manager helped me see the commonalities across all platforms (which were all separate previously) and with the launch of a modular platform for the latest chip, helped save the company a lot of money and development time, since we could support development and customers all at once instead of waiting for each platform to be gradually ready.
The weak characteristic of project managers is to treat all products like democracies where different parties need to agree on the next steps. This makes them not the best, especially at startups where fast decision making is a key success factor and product managers which can take decisions independently and sometimes without any data or feedback can drive product progress faster.
Consulting
Predictor of success as a product manager: medium / low
Better suited for: product manager, growth product manager
Type of transition: external, university
When I was in university it was famous for Google to only hire software engineers as product managers. As I understand, that has deeply changed and big companies like Google and also Lyft, hire a lot of MBAs as product managers. Usually, those MBAs have had a previous career in consulting or get hired after a few years in consulting after their MBA.
You can see why this on paper looks like a great choice. People that work in consulting are pretty good with data and understand business metrics, especially when it comes to funnels and conversions. They are amazing at estimating the impact that a product will have on financials, estimating total addressable markets and figuring out whether something is worth investing in or not. For many aspects they are similar to data scientists turned product managers, with the exception that they usually know less how to code and how to use tools for data mining. They can however prepare amazing presentations that usually work great at convincing executives or external stakeholders (don’t discount that, storytelling is important for PMs).
Strong characteristics:
- Strong work ethic. They will work long hours, given they are used to it, and that helps as a product manager
- Strong presentation and storytelling skills, especially towards an executive audience, either internal or external
- Strong data fluency and opinions, usually driving decisions forward
- Good communication, which leads to not shying away from internal conflicts and usually makes for good updates to keep stakeholders aligned. Also makes for better product manager managers
- Great market analysis for justification of product investments and estimation of impact
Weak characteristics:
- Superficial in product requirements and usually don't know how to drive a product to completion
- Hands off in team management. Usually needs to be paired with a strong engineering manager
- Little understanding of technology and design which usually leads them to not participate in those discussions and not prioritizing correctly the impact that those teams can have
- Are usually very competitive and career focused which can foster a political environment
The characteristics should seem fairly obvious. Given consultants are usually only used to interfacing with executives and proposing things but not actually seeing them through, they are good in the strategy phase of the product but then lack in the execution phase. This makes them a better fit for big companies with lengthy planning processes.
A lot of business degrees and communities tend to downplay the importance and relevance of technology (less and less nowadays compared to the past though) in the success of a product. So sometimes consultants turned product managers can look down on technology teams and tend to delegate managing those teams and the exact work that they do to engineering managers and leads.
One aspect to not ignore though is the work ethic. Consultants are used to working long hours and that is also a pro in product management. The ability to be in meetings all day and then work on documents in the evening unlocks a lot of learning, sometimes making consultants turned product managers into learning machines that can rapidly understand everything from product to customer to technology and end up being very successful.
They can also be very career focused, ending up creating political environments where they are trying to maximize their own gain versus the company’s. I have seen consultants turned product managers scale the ranks and become VPs of product and CPOs for this reason. When I interface with consultants turned PMs that are individual contributors though, I tend to note a lot of the weak characteristics above.
Their ability with data also means that some of the characteristics are similar to the data scientists’, though I rate a higher probability of success to data scientists turned product managers since they understand more of how the data is made and can actually request the team to collect the data that is not already available. Their familiarity with technology gives them an edge. In an age of AI and machine learning, this is a big pro that data scientists have on consultants.
Marketing & Sales (incl solutions architects)
Predictor of success as a product manager: low (medium for solution architects)
Better suited for: product manager, platform product manager
Type of transition: internal
Out of all the ones mentioned above, this is definitely the path that is least followed. I have not seen many marketing and sales professionals turn product managers, though I believe this is going to be a more common path in the future. In particular, solutions architects, which effectively are engineers devoted to sales enablement, usually have a good set of skills for product management and sometimes cover de facto product management roles in technical teams that are very close to the customer (in B2B and Saas companies).
This transition is really only prevalent in B2B or SaaS companies. In big companies especially, sales is usually the interface with the customers and product managers don't extensively talk to customers, rather using sales to convey the messages and get feedback on the product. For sales people that understand the technology and the product characteristics, the direct interface with the customer can be a big pro in developing their product sense.
Strong characteristics:
- Understanding of the customer given they spend a lot of time while doing sales into fixing the device
- Understanding of competitor offerings since, in sales, usually the product is always compared against them. This includes especially the parts where competitors are better compared to the company's products
- Understanding not just of the product but also of the process and content that is needed to actually sell it
- Very business and profit focused, making sure to not neglect the business side of product development
Weak characteristics:
- Usually little understanding of technology (doesn’t apply to solutions architects)
- Hands-off approach in dealing with the technical and operations teams
- Usually too focused on the explicit needs of the current customers. Sometimes sales turned product managers cannot say no and this is a problem. They also don't tend to identify radical changes and pivots to the product that may unlock other customer segments while losing the existing ones
- Similarly, this may lead to lack of vision due to too much focus on the current customer pain points
Marketing and sales people can be very customer focused and usually tend to know their customers very well. This can be a big pro in getting started as product managers and in the time right after the change usually leads to prioritizing features that customers really want, unlocking a boost of success for the product. In the longer run, those sales people turned product managers may end up having lack of vision and only developing the product under the explicit request of the customers or to follow competitor moves. This may be the right approach in some industries though may lead the team to miss big left field opportunities and pivots that require drastic changes and potential alienation of customers.
In the case of solutions architects though, a lot of the weak points don't apply, given solutions architects are used to working in a tech team and usually are very familiar with roadmap setting and tracking. This leads them to have the pros of software engineers turned product managers while also being used to interfacing with high stakes customers and developing communication skills related to that (pros of consultants and sales). In small teams without product managers, solutions architects can de facto become the customer-facing product manager and technical contact of the team, paving the way for a natural progression into product management.
If you're looking for product managers in a B2B SaaS company, I would highly recommend you to consider looking at your Solutions Architects.
Conclusion
Hopefully by now you have decided which path you will follow to get into product management. Realistically based on your current career progress, only one or two of the paths above are viable for you. It usually helps to become really good in your current role before asking to move to product management and usually companies, if you're good, will want to keep you around and tend to fulfill your request.
Best wishes with your transition and, once you get the job, come back to check out articles on how to (I personally think you would) be a better product manager!