In fields like biomedical engineering, while deep technical expertise may not be mandatory, having foundational knowledge is crucial for understanding the complexities of projects and managing teams effectively.

For a PM in biomedical engineering, the basics should include a working knowledge of the field’s core concepts, such as medical devices, regulatory requirements (e.g., FDA approval processes), and general scientific principles. You should also understand the stages of research, product development, and clinical testing. For example, if a project involves developing a new prosthetic device, a PM should know the different phases of product development, from initial research and design to clinical trials and market release.

While not having direct technical or lab experience may be acceptable, it’s important for a PM to be able to communicate effectively with subject-matter experts (SMEs) and understand their challenges. This allows for faster problem-solving and better decision-making. For instance, if a developer reports an issue with integrating a sensor into a medical device, a PM with basic biomedical knowledge can quickly grasp the problem, ask relevant questions, and coordinate a timely response.

In essence, while you don’t need to be a biomedical engineer, a strong grasp of the field’s basics ensures you can anticipate challenges, foster collaboration, and guide the project to successful completion.

I agree with the idea that while deep technical knowledge may not be required for a project manager in biomedical engineering, having a strong foundational understanding is essential for managing projects effectively. Being able to grasp core concepts such as medical devices, regulatory processes, and the stages of product development is critical for ensuring smooth communication with the team and subject-matter experts (SMEs). A PM with this knowledge can ask the right questions and make informed decisions without needing to delve into the technical details themselves. In biomedical fields, where projects often involve complex research, design, and testing phases, it’s particularly important for the PM to understand the broader landscape to anticipate potential challenges and guide the team efficiently. Ultimately, while hands-on technical experience may not be necessary, a PM’s ability to bridge the gap between the team and the project's goals is key to its success.

I agree that while a PM in biomed engineering doesn't need deep technical knowledge, having a solid grasp of the basics is crucial. One thing I'd add is that in fields like biomed engineering, projects often involve a lot of cross-disciplinary collaboration between engineers and clinicians and many others. So, understanding how to navigate those different perspectives and needs is key for a PM. Beyond just knowing about product development and regulatory requirements, it’s also helpful to understand the human factors side of things. For example, how a medical device might be used in a clinical setting, and how to balance technical innovation with usability and patient safety.

Also, with the fast pace of innovation in this field, it’s important for PMs to stay updated on emerging trends or technologies, so they can guide projects that aren’t just solving today’s problems but are good for the future. So, while hands-on lab experience might not be necessary, a willingness to continuously learn is what can really set a PM apart in this space.