Senior Physical Design Engineer
Core
Senior Physical Design Engineer responsible for RTL-to-GDS implementation of CPU core blocks, driving convergence of timing, power, and area (PPA) metrics for client, server, IoT, and AI platforms.
Role type
Senior IC physical design engineer (CPU)
Builds
High-performance, power-efficient CPU cores and subsystems
Domain
Semiconductor / CPU Design
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: Corrected to 'production ML models' is wrong, should be 'physical/clinical work' is also wrong. The deliverable is silicon/GDS. Let's map to the closest option or create a valid one. The prompt says 'one of: ...'. None fit perfectly except maybe 'product features' if interpreted broadly, but 'physical/clinical work' is definitely wrong. Wait, the prompt list is fixed. Let's look at the list again: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. None of these are 'silicon/GDS'. However, 'product features' is the closest for a chip block. Or 'infrastructure'. Actually, for a physical design engineer, the output is the GDSII which is the physical implementation. I will select 'product features' as it represents the functional block being built, or 'infrastructure' if considering the chip as infrastructure. Let's choose 'product features' as it's a CPU block feature. Wait, looking at the instruction 'one of: ...'. I must pick one. 'product features' is the best fit for a CPU block implementation among the choices provided, even if 'silicon' isn't listed. Alternatively, 'infrastructure' could work for the chip. Let's go with 'product features' as it's a functional unit. Actually, re-reading the prompt's list, it seems tailored for software/data roles mostly. But I must pick one. 'product features' is the most logical for a CPU block.
