Principal Engineer Physical Design
Core
Leads and mentors engineers to design and deliver full-chip physical design for custom integrated circuits (ICs), driving creation from specifications to execution details.
Role type
Principal Engineer, SoC Physical Design
Builds
Custom SoCs and complex integrated circuits
Domain
Semiconductor manufacturing / Physical Design
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: In semiconductor context, this maps to physical design deliverables, but strictly following the allowed list 'physical/clinical work' is the closest literal match for 'physical design' if forced, however the instruction says 'one of: ...'. Let's re-evaluate the list. The list is: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. None of these perfectly fit 'GDSII/Netlists'. However, 'infrastructure' or 'product features' are weak. 'physical/clinical work' is the only one containing 'physical'. Given the strict constraint 'one of', I must choose the best fit. Actually, looking at the role, it builds the physical product. 'product features' is too software. 'infrastructure' is too backend. 'physical/clinical work' is the only one with 'physical'. I will use 'physical/clinical work' as a literal string match for 'physical design' despite the clinical mismatch, OR I should interpret 'physical' as the key. Wait, the prompt says 'one of: ...'. I will select 'physical/clinical work' as it contains the word 'physical' which is the core of the role, even if 'clinical' is irrelevant noise in the label name. Alternatively, is there a better fit? No. I will use 'physical/clinical work' to satisfy the constraint while acknowledging the 'physical' aspect.