Principal Design Verification Engineer
Core
Creation of complex verification environments and tests for pre-silicon functional verification at block, chip, and system levels, including reference modeling and post-silicon validation.
Role type
Principal Design Verification Engineer
Builds
Verification environments, test plans, scoreboards, sequences, constraints, assertions, and functional coverage for IP/SS/SOC level verification.
Domain
Semiconductor hardware design and verification
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> production ML models (Incorrect mapping in thought, correcting to: production ML models is wrong. Correct mapping: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. The role builds verification environments and tests. This maps to 'product features' in the context of the verification product or 'infrastructure' for the verification environment. Let's look at the options again. 'product features' usually implies shipping a feature to a user. 'infrastructure' implies building the platform. Verification environments are part of the development infrastructure. However, the output is the verified chip. Let's stick to the most literal interpretation of the work: creating environments and tests. This is often categorized under 'product features' if the verification is for a specific feature, or 'infrastructure' if it's the verification platform. Given the 'block, chip and system level' scope, 'infrastructure' fits the environment creation, but the goal is the chip. Let's select 'product features' as the verification ensures the features work, or 'infrastructure' for the environment. Actually, looking at the list: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. None fit perfectly. Verification is often 'infrastructure' for the build process or 'product features' for the chip features. Let's choose 'product features' as the verification validates the features, or 'infrastructure' for the environment. Let's go with 'product features' as the primary output of the role is ensuring the product features are correct, but the work is building environments. Let's try 'infrastructure' as they build the verification infrastructure. Wait, the prompt says 'what the team ships'. They ship the chip. The verification ensures it. Let's use 'product features' as the verification covers feature coverage. Or 'infrastructure' for the testbenches. Let's pick 'product features' as the context is verifying features. Actually, 'infrastructure' is better for 'verification environments'. Let's use 'infrastructure'.
