3 ms·
Great perspective! From my own experience, having a strong grasp of the overall architecture and implications thereof is very important, however, thinking that
by sologoub 11y ago
Great perspective! From my own experience, having a strong grasp of the overall architecture and implications thereof is very important, however, thinking that you can do better than the Engineering team or that you know how that system should be designed is a liability. Collaboration is the name of the game.
- stvswn 11y agoRight, I don't mean to imply that technical knowledge isn't central to the job. It is. But it can be learned. A lot of engineers on this thread might not realize that within MBA programs, the word is out -- "don't even try to be a PM, you need a technical background." As if "coding" is something ultra-intimidating and therefore if you can't already do it, you can't be a PM. My company has a reputation for this constraint, like we only hire people who were full-time SWEs in a past life. It's simply not true. Once you get here, though, you have to understand the technical architecture, for sure. But being a PM isn't alone among careers, here -- most careers have a steep learning curve when you're starting out.