Interview drills

Interview Drills for Coverage Closure focuses on coverage gap to target, dominant undetected classes, closure iteration count. The goal is to convert metric movement into mechanism, owner, and release decision.

PROMPT
You observe coverage gap to target, dominant undetected classes, closure iteration count on Coverage Closure. Walk through diagnosis and release decision.

STRONG ANSWER
1. States context and run tags.
2. Explains mechanism: Coverage closure uses targeted analysis of undetected faults, constraints, and design-for-test hooks to close quality gaps without exploding pattern volume.
3. Requests coverage gap report, undetected fault buckets, closure action tracker.
4. Proposes minimal fix and regression.

WEAK ANSWER
Jumps to tool switches without evidence quality, ownership, or regression plan.

Diagram to draw on the whiteboard

ATPG flow

fault models -> constraints -> generation -> coverage closure -> signoff

Root-cause narrative

ROOT-CAUSE TREE - Coverage Closure

coverage gap to target, dominant undetected classes, closure iteration count regresses
        |
  setup changed?
    /        \
  yes         no
  |            |
constraint    silicon or
or ATPG       physical/test path
 /    \          |
SDC   model    chain/clock/power/diagnosis
diff  diff     isolate first failing signature

DFT deep dive

ATPG quality comes from fault model choice plus legal constraints, not raw pattern volume alone.

Concept diagram

ATPG FLOW

fault model -> constraints -> generation -> simulation -> coverage closure -> signoff

Metric graph

COVERAGE GAP

target coverage
  ^
  |      o before closure
  |          o after fixes
  +---------------------> iteration

Reports and artifacts

• fault model coverage

• untestable class report

• constraint legality errors

• pattern signoff memo

Mini case study

Transition coverage stalled due to clock constraints mismatch; updated at-speed capture definitions recovered target.

Debug branches

• Classify untestable faults

• Diff ATPG constraints each run

• Pair coverage with pattern budget

Senior review question

Ask: what evidence proves this DFT decision is safe for production?

Key takeaways

• State metric, lot/corner context, and pattern tag with every claim.

• Treat timing, power, and quality as one signoff problem.

Common pitfalls

• Chasing coverage without legality checks.

• Ignoring test-power side effects of pattern changes.

• Debugging silicon without reproducible tags.

Principal DFT review addendum

Coverage closure uses targeted analysis of undetected faults, constraints, and design-for-test hooks to close quality gaps without exploding pattern volume.

Metric: coverage gap to target, dominant undetected classes, closure iteration count