How to hire a product design, r&d & program management team

Start with responsibility

Hiring in product design, r&d & program management starts with the work your team cannot leave uncovered. Related jobs can require different judgment about technical direction connecting product architecture with the business plan. Decide which decisions about development scientists or engineers and their project priorities this hire must own and which stay with a manager or specialist. That distinction keeps an impressive title from becoming the wrong answer to a vacancy involving technical direction connecting product architecture with the business plan.

Build the product design, r&d & program management brief with the manager who will use the hire's judgment. Agree the operating conditions and approval limits around technical direction connecting product architecture with the business plan before interviews. The roles below help separate responsibility for technical direction connecting product architecture with the business plan from responsibility for development scientists or engineers and their project priorities. Use those differences to design your team, not to assume every product design, r&d & program management position must be added.

Chief Technology Officer (CTO)

In the Chief Technology Officer (CTO) opening, establish who owns technical direction connecting product architecture with the business plan. A candidate can contribute to technical direction connecting product architecture with the business plan without being accountable for the decision. Ask for a choice between product development paths with different manufacturing consequences and identify the part they personally controlled. That helps you choose the independence needed for technical direction connecting product architecture with the business plan, instead of using seniority words as a substitute for the remit.

The important boundary for Chief Technology Officer (CTO) is enterprise technology responsibility rather than supervision of one engineering group. Explain enterprise technology responsibility rather than supervision of one engineering group in the interview and in the offer. Someone working in technology leaders in manufacturers with proprietary engineered products may be familiar with similar work but have different authority. Ask what support they would need for technical direction connecting product architecture with the business plan, then check whether that support exists rather than assuming the transfer is automatic.

• Read the Chief Technology Officer (CTO) hiring brief

R&D Manager

In the R&D Manager opening, establish who owns development scientists or engineers and their project priorities. A candidate can contribute to development scientists or engineers and their project priorities without being accountable for the decision. Ask for a decision to stop a trial that was not producing usable examples and identify the part they personally controlled. That helps you choose the independence needed for development scientists or engineers and their project priorities, instead of using seniority words as a substitute for the remit.

The important boundary for R&D Manager is people and laboratory management rather than only personal research work. Explain people and laboratory management rather than only personal research work in the interview and in the offer. Someone working in R&D managers with products that moved into plant production may be familiar with similar work but have different authority. Ask what support they would need for development scientists or engineers and their project priorities, then check whether that support exists rather than assuming the transfer is automatic.

• Read the R&D Manager hiring brief

R&D Engineer

In the R&D Engineer opening, establish who owns technical experiments and product concepts before production release. A candidate can contribute to technical experiments and product concepts before production release without being accountable for the decision. Ask for a failed experiment that changed the next design or test and identify the part they personally controlled. That helps you choose the independence needed for technical experiments and product concepts before production release, instead of using seniority words as a substitute for the remit.

The important boundary for R&D Engineer is exploratory development rather than support of a stable production line. Explain exploratory development rather than support of a stable production line in the interview and in the offer. Someone working in development engineers in product laboratories and pilot manufacturing may be familiar with similar work but have different authority. Ask what support they would need for technical experiments and product concepts before production release, then check whether that support exists rather than assuming the transfer is automatic.

• Read the R&D Engineer hiring brief

Mechanical Engineer

In the Mechanical Engineer opening, establish who owns mechanical calculations and equipment or product engineering decisions. A candidate can contribute to mechanical calculations and equipment or product engineering decisions without being accountable for the decision. Ask for a load, heat or motion calculation checked against actual operating conditions and identify the part they personally controlled. That helps you choose the independence needed for mechanical calculations and equipment or product engineering decisions, instead of using seniority words as a substitute for the remit.

The important boundary for Mechanical Engineer is product engineering versus plant equipment work stated in the brief. Explain product engineering versus plant equipment work stated in the brief in the interview and in the offer. Someone working in mechanical engineers working on comparable manufactured equipment may be familiar with similar work but have different authority. Ask what support they would need for mechanical calculations and equipment or product engineering decisions, then check whether that support exists rather than assuming the transfer is automatic.

• Read the Mechanical Engineer hiring brief

Product Design Engineer

In the Product Design Engineer opening, establish who owns product geometry and interfaces that can actually be manufactured. A candidate can contribute to product geometry and interfaces that can actually be manufactured without being accountable for the decision. Ask for a design change connecting tolerance choices with assembly performance and identify the part they personally controlled. That helps you choose the independence needed for product geometry and interfaces that can actually be manufactured, instead of using seniority words as a substitute for the remit.

The important boundary for Product Design Engineer is detailed design rather than ownership of the entire product program. Explain detailed design rather than ownership of the entire product program in the interview and in the offer. Someone working in design engineers from product OEMs and component engineering teams may be familiar with similar work but have different authority. Ask what support they would need for product geometry and interfaces that can actually be manufactured, then check whether that support exists rather than assuming the transfer is automatic.

• Read the Product Design Engineer hiring brief

Choose the handoff and hiring sequence

A move from technical direction connecting product architecture with the business plan to development scientists or engineers and their project priorities is not automatically a seniority ladder. Your organization may need both technical direction connecting product architecture with the business plan and development scientists or engineers and their project priorities, or may divide the work differently. State the handoff for technical direction connecting product architecture with the business plan before deciding which vacancy goes first. A candidate should understand who decides when technical direction connecting product architecture with the business plan conflicts with development scientists or engineers and their project priorities. That is a product design, r&d & program management team-design question, not something to answer by choosing the more impressive title.

Find the relevant background

The product design, r&d & program management search should use a different qualification discussion for each remit. For Chief Technology Officer (CTO), start with a choice between product development paths with different manufacturing consequences. For R&D Manager, start with a decision to stop a trial that was not producing usable examples. Then ask whether the person wants responsibility for technical direction connecting product architecture with the business plan under your working conditions. Moving from technology leaders in manufacturers with proprietary engineered products may bring useful experience, but it does not automatically establish people and laboratory management rather than only personal research work. Investigate the gap around development scientists or engineers and their project priorities rather than stretching the candidate's title.