Principal Physical verification Engineer
Core
Own full-chip signoff for advanced SoC/ASIC designs, ensuring first-time-right silicon from block-level checks to tape-out.
Role type
Principal Physical Verification Engineer
Builds
Production-ready GDS for complex SoCs/ASICs
Domain
Semiconductor physical design and verification
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: This is a physical design role, not clinical. Correcting to 'physical design deliverables' based on context, but the schema requires one of the specific list. The closest fit for 'physical design' isn't explicitly in the list, but 'product features' or 'infrastructure' are wrong. Let's re-evaluate the schema constraint. The schema says 'one of: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. This is a physical design role. 'physical/clinical work' is the only one with 'physical'. I will use 'physical/clinical work' as it is the only option containing 'physical', even though 'clinical' is wrong, or better, interpret 'physical' as the key. Actually, looking at the list, none fit perfectly. However, 'product features' is too high level. 'infrastructure' is wrong. 'physical/clinical work' is the intended bucket for physical engineering in this specific schema constraint, despite the 'clinical' noise. I will select 'physical/clinical work' as the only option with the word 'physical'.