New ask Hacker News story: I don't get the product manager hiring process
I don't get the product manager hiring process
3 by BrightlyAbsurd | 1 comments on Hacker News.
I started as a technical project manager over 10 years ago and slowly moved into product management in my last job almost 5 years ago. Cannot say it is a very successful product (due to the technology and market choices, both made without me at the very early stage of the product). But the reason I'm writing this post is to say I don't get the hiring process for product managers. And before I go ahead, I accept that the problem can be with me and not the process. But the process feels entirely superficial and arbitrary to me. The typical problem given at the interview is like 'Design a solution to the problem X'. What exactly to do next is an entirely subjective choice. I've read the famous "Decode and Conquer", but even then it leaves a lot to be answered. In the end you are not really solving the problem, you need to please the interviewer instead. Do they want you to challenge the problem first? Do they want you to challenge the suggested technology to solve it (why do we want to build a bot and not a mobile app?) ? Do they want me to dive straight into making hypotheses? Design solutions? It feels that the key to pass a product manager interview is to find an interviewer on the same wavelength with you. Probably I'm just venting, but not sure if anyone else feels the same or maybe you have any tips (including 'change your job!' haha)
3 by BrightlyAbsurd | 1 comments on Hacker News.
I started as a technical project manager over 10 years ago and slowly moved into product management in my last job almost 5 years ago. Cannot say it is a very successful product (due to the technology and market choices, both made without me at the very early stage of the product). But the reason I'm writing this post is to say I don't get the hiring process for product managers. And before I go ahead, I accept that the problem can be with me and not the process. But the process feels entirely superficial and arbitrary to me. The typical problem given at the interview is like 'Design a solution to the problem X'. What exactly to do next is an entirely subjective choice. I've read the famous "Decode and Conquer", but even then it leaves a lot to be answered. In the end you are not really solving the problem, you need to please the interviewer instead. Do they want you to challenge the problem first? Do they want you to challenge the suggested technology to solve it (why do we want to build a bot and not a mobile app?) ? Do they want me to dive straight into making hypotheses? Design solutions? It feels that the key to pass a product manager interview is to find an interviewer on the same wavelength with you. Probably I'm just venting, but not sure if anyone else feels the same or maybe you have any tips (including 'change your job!' haha)
Comments
Post a Comment