Coverage Closure Engineer

Project

Work done for a product or program.

• Merge functional, code, assertion and formal coverage databases across simulation, emulation and formal runs into a unified programme-level coverage view.
• Analyse uncovered code and functional bins to classify them as reachable-but-unstimulated, structurally unreachable or genuinely dead code.
• Author and maintain coverage exclusion and waiver files with technical justification traceable to a named approver.
• Identify stimulus gaps and write or commission targeted directed tests and constraint changes to hit stubborn coverage holes.
• Use coverage-driven test ranking and seed optimisation to reduce regression compute while preserving coverage.
• Apply formal unreachability analysis to legitimately eliminate bins that no stimulus could ever reach.
• Produce weekly coverage trend charts and convergence forecasts so leadership can see whether signoff is on track.
• Maintain the coverage taxonomy and naming conventions so that results roll up consistently from block to subsystem to chip.
• Run signoff coverage reviews with design and verification owners and record the disposition of every remaining hole.

Function

Work that keeps the discipline running: methods, tools, suppliers and people.

• Audit coverage models for quality, flagging covergroups that are trivially hit or that fail to reflect real design intent.

Project

1. Produce and hand over the role's key deliverables
   • Merged programme-level coverage database and dashboard
   • Coverage exclusion and waiver file with justifications
   • Coverage convergence forecast and weekly trend report
   • Targeted test and constraint changes closing identified gaps
   • Coverage signoff review minutes and hole disposition record
2. Plan verificationGeneral
   • Extract the features to verify from the specification
   • Define coverage goals and the test strategy
   • Review the plan with design and architecture
3. Close verificationGeneral
   • Build testbenches and tests
   • Run and triage regressions
   • Report coverage and sign off

Function

1. Keep the methodology currentGeneral
   • Maintain reusable verification components
   • Update guidelines after each project
2. Improve the infrastructureGeneral
   • Reduce regression run time
   • Improve debug and coverage tools