CDC/RDC Framework Drills

CDC/RDC whiteboard flow

1. Draw source and destination domains.
2. Label crossing type (level/pulse/bus/reset).
3. Mark synchronizer/protocol path.
4. State failure mechanism and metric.
5. Request evidence (report + assertion + waveform).
6. Propose fix or bounded waiver.
7. State regression matrix and signoff owner.

Key takeaways

• Strong answers always tie mechanism to evidence.

• Schedule pressure never replaces technical risk framing.

CDC/RDC deep dive

Interview performance reflects production signoff thinking quality.

Concept diagram

INTERVIEW FLOW

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

Metric graph

PRACTICE SCORE

session1 62%
session2 78%
session3 89%

Reports and artifacts

• scenario completion

• answer rubric scores

• trap recovery quality

Mini case study

Candidate gave command-heavy answer but missed risk framing and waiver governance.

Debug branches

• Use mechanism-first structure

• name ownership and evidence

• close with signoff decision

Senior review question

Ask: what evidence proves this risk is closed for silicon, not just tool-clean?

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.