1–10 of 133 posts
I need some advice from all the wonderful people on Hacker News. I am a Backend engineer looking to move into a product management role. I have no experience in product management. In addition, I am 35. Does age matter? Are certifications such as the one from Product School worth it and help in the transition process? How do engineers typically transition to the role? I’d appreciate any advice from anyone. Thank you.
To answer one of your questions: Age doesn't matter.
Read Cracking the PM Interview [1] (for an overview of the job, not the actual interview tips) and The Lean Startup [2] (for general philosophy).
35 is a great age for a PM, especially since PM's often start elsewhere -- maturity is a plus here. I'd say there are 3 main ways into it -- as an engineer, who starts to do PM-type stuff on a team where there's no PM. As a designer, who starts to do PM-type stuff on a team where there's no PM. Or as an MBA who has a good sense for engineering and design. Certifications generally don't mean anything -- communication and leadership skills, good judgment, experience and a proven track record are what matter. But all those things can be demonstrated in previous non-PM roles, in order to make the initial switch.
Also, if you want to be a PM then you'd better enjoy meetings, slides, people, and communicating & convincing all day long, day-in day-out. If those make you say an enthusiastic "yes that's me!" then jump right in. If not... you're gonna have a bad time...
[1] https://www.amazon.com/Cracking-PM-Interview-Product-Technol...
[2] https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous...
Then a PM role might be right for you.
If you love coding/technology or don't have good presenting/selling skills then stick to engineering... my $0.2.
B. In Google, for example, many people take a path similar to what you describe, gradually moving to product management from an engineering background. It usually requires demonstrating leadership, and doing some 'rotations' in which you perform a PM role on smaller projects before taking on a full product. Perhaps your best shot is asking your current management to take on product management and ownership duties in a project you are familiar with, maybe even being mentored by an experienced PM.
(Source: was a PM at Google)
What does matter is what you like to do. If you are technical, like to try new things, implement, build , etc... things, then you might find Product Management quite boring.
If you are a « people » person and view yourself in a role between Marketing and Engineering, then go for it!
At 35, you might not know what you really like, yet... Might simply go for it for some time, and then if you decide to go back to a “builder” position, you will know _why_.
You are asking the wrong question, IMHO. What does matter is what you like to do. If you are technical, like to try new things, implement, build , etc... things, then you might find Product Management quite boring. If you are a « people » person and view yourself in a role between Marketing and Engineering, then go for it! At 35, you might not know what you really like, yet... Might simply go for it for some time, an…
If you stay in tech, you will be forever slinging code and at the whim of the business. You will forever be on the tech treadmill, learning new frameworks, languages, and programming languages. You will have an artificial compensation ceiling.
If you move into management, those problems turn into different problems, but with more upside. You develop your soft skills. You network. You learn to manage, shielding your team from bullshit above while helping your ICs develop themselves. If you're a good manager, they will follow you for the rest of your career to where ever you go. This is an asset not to be understated. No 10x developer can ever compete with a manager bringing a solid team with them.
Your potential is then limited less by what you know, and more who and what opportunities you're aware of. Your skills will be transferable to other industries, even the public sector. Again, I can't stress this enough. Could you take a year off as a developer or other technologist and have an easy time coming back into the market? From my research, the answer is no.
With time, you won't just be a product owner/manager; if done properly, you will be able to demonstrate that you can solve business problems while having a solid foundation of the technical underpinnings required to solve those problems. And everyone is looking for competent business problem solvers.
You are asking the wrong question, IMHO. What does matter is what you like to do. If you are technical, like to try new things, implement, build , etc... things, then you might find Product Management quite boring. If you are a « people » person and view yourself in a role between Marketing and Engineering, then go for it! At 35, you might not know what you really like, yet... Might simply go for it for some time, an…
EDIT: I realize this is directed more towards IC->management, and less IC->product manager. I'm still leaving it, as it feels like it will have value to OP. If you stay in tech, you will be forever slinging code and at the whim of the business. You will forever be on the tech treadmill, learning new frameworks, languages, and programming languages. You will have an artificial compensation ceiling. If you move into ma…
Cheers!