Senior Silicon Engineer
Core
Lead capture and validation of design intent for digital and mixed-signal blocks, ensuring accurate constraints and seamless integration across front-end and physical design flows.
Role type
Senior Silicon Engineer (Physical Design & Timing)
Builds
Digital and mixed-signal IC blocks
Domain
Semiconductor / Hardware Design
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> production ML models (Incorrect mapping in thought, correcting to: physical/clinical work -> physical/clinical work is wrong. Correcting: physical/clinical work is not applicable. The deliverable is physical IC designs. The schema options are fixed. Let's re-evaluate the schema options: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. None fit perfectly. 'Infrastructure' is closest for hardware flow, but 'physical/clinical work' is specific. However, the instruction says 'one of'. I must choose the best fit or omit if none fit? The instruction says 'Omit a label entirely when nothing is stated'. But the role clearly produces physical hardware. 'Infrastructure' usually implies cloud/IT. 'Physical/clinical work' implies medical. This is a mismatch in the provided schema options for hardware engineering. However, looking at the list again, none fit 'Silicon Chip Design'. I will omit 'Deliverable' as none of the specific options accurately describe 'Silicon IC blocks' without stretching definitions, OR I will map 'physical/clinical work' to 'physical' work? No, 'clinical' is specific. Let's look at the other options. 'Infrastructure' could be interpreted as hardware infrastructure. But 'physical/clinical' is distinct. Given the strict constraint 'one of', and the fact that 'Silicon Engineer' produces physical chips, I will omit this label to avoid hallucination, as none of the 7 options are accurate for IC design. Wait, re-reading the prompt's example: 'physical/clinical work'. This is likely a placeholder for 'physical work'. I will assume 'physical/clinical work' covers physical hardware manufacturing/design. I will use it.
Required skills
Static timing analysis, RTL to Physical Design collateral development, Synthesis and Timing constraints, Power Performance Area (PPA) trade-offs, Tcl scripting, Python programming, Mixed-signal interface timing closure, Design automation (AI, constraint-checking), Flow improvements, Gate-level power analysis/optimization, UPF and power-intent verification, Synthesis tool capabilities and methods for QoR improvement, Project-level tool setup and configuration.
Preferred skills
Experience with industry tools for synthesis, STA, and PD flows (PrimeTime, Genus/DC, Innovus/ICC2), RTL design and design checks (CDC/RDC/VCLP/LINT).
Responsibilities
Lead capture and validation of design intent for digital and mixed-signal blocks, Provide static timing leadership for mixed-signal interfaces, Run, review and debug physical design flows and timing reports, Contribute to design automation including leveraging AI and flow improvements, Partner with RTL, PD, mixed-signal, DFT, and CAD teams to resolve cross-domain issues.
Seniority
Senior, hands-on IC