When I was interviewing for PM positions a couple of years ago, I wanted to do what I do now – build exciting real-world products soup to nuts, concept to manufacturing to deployment, algorithms to software and hardware design to manufacturing and to operations. Yet, when I interviewed for such roles, my lack of experience with one particular aspects of this – manufacturing – was oftentimes the ultimate deal breaker. Luckily, for my current role my experience in successfully running interdisciplinary research software-hardware projects outweighed this particular missing part of my background, and I got a chance to learn, on the job, the negotiations, vendor relationships, and manufacturing.
And, knowing what I know now, I see 100% why companies see the experience with manufacturing as supremely important. Hardware is hard. Manufacturing is hard. While it may be relatively straightforward to reason through how that would be the case and how hardware is different from software (e.g., you’ll clearly need more up-front investments and more planning), it is equally easy to not zoom in on important considerations and pay for it later. Thankfully, people who have been burned – or have succeeded – in this are oftentimes prepared to share their experiences.