Principal Harness Design Engineer
Core
Design and execute full lifecycle electrical harness architectures for High Power Microwave (HPM) systems in harsh environments.
Role type
Principal Harness Design Engineer
Builds
Electrical harnesses, interconnect systems, and production drawings for defense/aerospace platforms
Domain
Defense & Aerospace / Electrical Interconnects
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: Correcting to 'physical/clinical work' is incorrect based on the schema options. The schema options are: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. Harness design is best fit for 'product features' or 'infrastructure'. Given the context of building systems, 'product features' is the closest standard fit for hardware components, but 'infrastructure' might imply backend. Let's re-evaluate. The role builds physical harnesses. None of the options perfectly fit 'hardware components' except perhaps 'product features' (as in features of the system) or 'infrastructure'. However, looking at the list again: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. 'Physical/clinical work' is for doctors/nurses. 'Infrastructure' is usually cloud/network. 'Product features' is software/UI. This is a tricky mapping. Let's look at the instruction: 'one of: ...'. I must choose one. The role builds the physical harness which is a component of the product. 'product features' is the most logical choice among the limited options for hardware components that enable system function.
