Summary

The Director of Hardware Product Lifecycle will be the source of truth for product hardware configurations. They will own the Bills of Materials (BOMs), run the engineering change process end-to-end, keep certification records aligned with every revision, and make sure only released, qualified parts get purchased and built.

They will create and implement durable processes across the product lifecycle, publish a clear release calendar, and report ECO board status so everyone knows what’s shipping when and why. The Director will be the right hand of the head of hardware for all processes: practical, organized, and relentless about closing loops.

What you’ll own

• Process Implementation: Define and implement lightweight, scalable hardware processes from scratch. Own the operating playbook for change control, release, build readiness, vendor/deviation handling, and turn ad-hoc habits into clear, repeatable steps
• BOMs (Bills of Materials): single source of truth; manage versions, effectivity (which builds a change applies to), and where-used impacts across all products.
• Change control (ECR/ECO): run Engineering Change Requests/Orders from proposal → approval → implementation → verification.
• Release management: define “ready to release” criteria; map revisions to build numbers; publish a Release Calendar (what rev, when, where).
• Vendor revisions & deviations: issue controlled drawings/specs to vendors; receive/track deviations (temporary exceptions) with clear expiry and controls.
• Qualification of alternates: create lean test plans with Product/QA (pass/fail, sample size, acceptance limits); archive results and decisions.
• Certification artifacts: keep test reports, declarations, and compliance matrices synced with current product revs.
• PDM discipline: administer CAD/PDM (SolidWorks + PDM) lifecycles, templates, and naming; eliminate “shadow BOMs.”

What you’ll drive with others

• Build coordination: translate what’s released into what gets built: the right rev of the right parts with the right timing;
• Build readiness: work directly with Ops and Product on establishing build timelines, no-later-than ordering deadlines, overage estimations and shortage alerts;
• Approved Vendor List (AVL): you’re the gatekeeper for suppliers and acceptable alternates but will work tightly with OPS to maintain proofs of equivalency.
• Ops / Supply Chain: ensure Ops is only buying released, qualified configurations; communicate effectivity cut-ins, last-time-buys, and retrofit plans.
• Production / Test: implement traveler updates, inspection points, and test coverage with the production team when a change lands.
• Quality: nonconforming material control, MRB decisions (Material Review Board: accept/rework/scrap), deviation limits, and Corrective Action / Preventative Action (CAPA) follow-through.
• Design: deliver actions to the design team that respond to manufacturing or supply chain issues or foresight
  
  

Cadences you’ll run

• Weekly: Release Calendar update; ECO board with aging, risks, and decisions needed.
• Per build: Build Readiness, on-hand/on-order/gaps, ETAs, risks, owners; confirm rev-to-build match.
• Per change: impact analysis (BOM, drawings, test, compliance, supply); implementation plan and proof of completion.
  
  

Required experience

• 10+ years in hardware configuration/change management or Product Lifecycle Management (PLM), New Product Introduction (NPI), and/or manufacturing operations for complex electromechanical products.
• Demonstrated experience creating and implementing new processes across a multidisciplinary organization.
• Exceptionally detail oriented; someone that actively seeks order from chaos.
• Direct ownership of ECR/ECO implementation (effectivity, cut-ins, retrofits).
• Strong BOM fundamentals: EBOM, MBOM (engineering vs manufacturing BOM), where-used, effectivity, alternates/obsoletes.
• Demonstrated operating cadence: pre-reads, drumbeats, decision logs, action tracking, closure.
• Hands-on with PDM/PLM (SolidWorks PDM or similar): lifecycles, permissions, templates, and revisioning.
• Clear, concise communicator; can frame trade-offs and drive decisions with just enough process.

Nice-to-haves

• Experience with federally tested/certified products (e.g., FCC, EMC, safety) and syncing certification docs to revs.
• Scripting/automation for reports (SQL/Excel/PowerQuery/Python) and doc generation
• MRP/ERP familiarity (effectivity dates, substitutions, inventory disposition).
  
  

Tool stack you’ll touch

• SolidWorks + PDM (vaults, lifecycles, data cards)
• PLM/Change tools (if separate), MRP/ERP (effectivity, purchasing)
  
  

30/60/90 plan

• 30 days
  
  
  • Map current BOMs, revs, and certification artifacts; identify mismatches.
  • Sync to the current build milestones
  • Stand up ECO board and a simple Release Calendar (sheet + weekly review)
  • Freeze naming, rev, and status conventions in PDM; eliminate duplicate sources.
    
    
• 60 days
  
  
  • Implement lean Change Playbook: templates, entry/exit criteria, checklists.
  • Define Build Readiness checklist and shortage/risk report; pilot on next build.
  • Publish AVL + alternates policy; add quick-turn qual template.
    
    
• 90 days
  
  
  • Automate Release Calendar + ECO metrics; add effectivity to MRP.
  • Close top 5 process gaps (deviations aging, cert drift, late cut-ins, etc.).
  • Deliver quarter plan of record (POR) for changes with risks and mitigations.