Scenario: RDC Waiver Under Tapeout Pressure

Scenario

Program requests waivers for reset crossings judged low frequency. Verification has partial evidence; integration team worries about boot sequencing on one derivative.

OBSERVED METRIC
20 open RDC violations with milestone in 36 hours

45-MINUTE INTERVIEW FLOW
0-5: classify crossing/reset scope
5-15: explain mechanism and assumptions
15-25: request and interpret evidence
25-35: propose fix/waiver/escalation
35-45: define regression + signoff

Common pitfalls

• Approve waivers without containment evidence

• Use schedule urgency as technical justification

• Ignore chip-level reset dependency graph

Scenario debrief

Score each response on mechanism clarity, evidence quality, and signoff decision discipline.

INTERVIEW FLOW

classify -> explain mechanism -> propose fix -> state regression

PRACTICE SCORE

session1 62%
session2 78%
session3 89%

Debrief prompts

1. Which crossing class or reset dependency failed first?

2. What evidence changed your decision?

3. Fix, waive, or escalate and why?

Key takeaways

• State crossing class, assumptions, and owner with every issue.

• Run structural and dynamic regressions after each fix.

Common pitfalls

• Treating all warnings as equivalent risk.

• Waiving issues without containment evidence.

• Skipping reset and reconvergence stress after CDC fixes.