Routing DRC Debug and Forensic Workflow — Interview Drills

Interview drills

Practice aloud for Routing → Routing DRC Debug and Forensic Workflow. Use METRIC → HYPOTHESIS → FIX → REGRESSION.

Why should DRC debug start with classification?

[INT][PD][TOPIC]

Q: Why should DRC debug start with classification?

A:
Class analysis reveals systemic generators, enabling large-count reductions efficiently.

FOLLOW-UP TRAP: Jumping to manual edits immediately.

How do you know a DRC class is systemic?

[INT][PD][TOPIC]

Q: How do you know a DRC class is systemic?

A:
Violations share rule type, geometry signature, and concentrated origin from a specific route recipe or region.

FOLLOW-UP TRAP: Labeling every repeated violation as random.

What is the biggest process mistake in late DRC closure?

[INT][PD][TOPIC]

Q: What is the biggest process mistake in late DRC closure?

A:
Uncontrolled recipe changes that erase traceability and cause oscillating violation patterns.

FOLLOW-UP TRAP: Iterating without change logs.

10+ year interview answer bar

At senior/principal level, the interviewer is testing ownership judgment more than vocabulary. Answer Routing DRC Debug and Forensic Workflow through failure mode, evidence, tradeoff, and release decision.

You inherit a late-stage Routing DRC Debug and Forensic Workflow failure one week before release. What do you do in the first hour?

[INT][PD][STAFF]

Q: You inherit a late-stage Routing DRC Debug and Forensic Workflow failure one week before release. What do you do in the first hour?

A:
Freeze the database tag, name the failing metric (Routing closure dashboard), confirm corner/mode/stage, cluster the issue, assign the first experiment, and publish a regression/owner plan before making broad tool changes.

FOLLOW-UP TRAP: Jumping directly to optimization knobs without preserving evidence.

When would you stop trying to improve Routing DRC Debug and Forensic Workflow and escalate?

[INT][PD][STAFF]

Q: When would you stop trying to improve Routing DRC Debug and Forensic Workflow and escalate?

A:
Escalate when the remaining risk crosses ownership boundaries, consumes shared margin, changes signed-off assumptions, or threatens PV signoff and tapeout readiness depend on forensic-grade DRC closure.. Bring exact report lines and options, not vague concern.

FOLLOW-UP TRAP: Escalating without data or continuing alone after a cross-team decision is needed.

Deep dive: how this shows up in real closure

Routing decides whether the placed design is manufacturable and extractable.

Reports and artifacts to inspect

• global route overflow by layer and region

• detailed route DRC/DRV summary grouped by rule

• antenna report: gate area, metal area, ratio, suggested diode

• post-route extraction delta on critical nets

Mini case study

Detailed route completes with 4,000 spacing violations around a macro channel. The design is not 'routed'. Cluster by rule and region, fix the channel or layer plan, then re-route locally.

Debug branches

• If antenna violations cluster on long lower-metal routes, jump to upper metal earlier or insert diode cells.

• If via violations dominate, inspect via arrays and preferred via stacks, especially on power transitions.

• If crosstalk worsens timing, space, shield, or layer-promote the victim nets.

Senior review question

Ask yourself: what single report line would prove this page's concept is either passing or failing?

What changes at 10+ years

• You are expected to predict what your fix can break before running it.

• You should recognize when the issue is methodology, not one block's implementation.

• You should communicate risk in tapeout language: owner, evidence, impact, mitigation, and decision date.

Principal-level review bar

Deep subpage pages in this course should be read like real closure review material. For a 10+ year PD engineer, the bar is not remembering terminology; it is making a release-quality decision under ambiguity.

What excellent looks like

• Names the failing metric, corner/mode, database tag, and analysis switches before proposing a fix.

• Separates data, constraint, physical, tool, and methodology root causes instead of treating all failures as optimization problems.

• Chooses experiments by information gain and reversibility, not by habit.

• States regression blast radius across timing, route, power, PV, DFT, package, and tapeout manifest.

• Turns recurring failures into methodology guardrails, dashboards, or checklist items.

Closure note template

STAFF / PRINCIPAL CLOSURE NOTE

Context:
  stage: <pre-CTS | post-CTS | post-route | post-fill | signoff>
  tag: <database / netlist / SDC / library stack>
  failing metric: <exact report line>
  affected scope: <block / hierarchy / path group / power domain / region>

Hypotheses:
  H1: <most likely physical or constraint mechanism>
  H2: <competing explanation>
  H3: <methodology or input-data issue>

Decision:
  next experiment: <cheap check that can falsify H1>
  fix candidate: <minimal reversible change>
  rollback trigger: <metric that says the fix is wrong>
  regression set: <timing / route / power / PV / DFT / package>
  escalation owner: <team or reviewer>

Tradeoffs a senior engineer must discuss

Technical tradeoff

Routing decides whether the placed design is manufacturable and extractable. Explain not only the preferred fix, but what margin or schedule you are spending to get it.

Cross-team tradeoff

• What must RTL, synthesis, CAD, STA, DFT, package, IP, or foundry agree to before this decision is final?

• Which artifact becomes the source of truth after the decision: report, waiver, manifest, ECO script, or methodology deck?

• What is the cost of being wrong: one rerun, ECO churn, mask risk, performance loss, or silicon escape?

Leadership communication

"The current blocker is <metric> in <corner/mode/stage>. The leading cause is <mechanism>. I recommend <fix> because it is bounded and reversible. The regression surface is <domains>. If it fails, we escalate to <owner> with <evidence>."

Key takeaways

• Always connect the concept back to a measurable signoff artifact.

• A fix is not complete until you can name the regression checks.

Common pitfalls

• Optimizing by habit instead of reading the current report.

• Forgetting that a local fix can regress timing, routing, power, or PV elsewhere.