Answer with mechanism, pitfall, regression check, and release judgment. At 10+ years, a correct definition is not enough.
Start with the failing metric and analysis context.
Explain the physical or constraint mechanism.
Name the cheapest evidence-gathering experiment.
Choose a bounded fix and state what it can regress.
Close with signoff, waiver, or escalation criteria.
[INT][PD]
Q: What metric best predicts detailed-route pain early?
A:
Persistent global overflow clusters that survive incremental placement/route guide tuning.
FOLLOW-UP TRAP: Waiting for full detailed route to discover capacity issues.[INT][PD]
Q: Why should DRC be tracked by class, not only total count?
A:
Class trends identify systemic causes and proper fix strategies; totals hide critical patterns.
FOLLOW-UP TRAP: Declaring progress from small total-count drops.[INT][PD]
Q: How do antenna fixes impact timing?
A:
Diodes and reroutes can alter capacitance and delay, so post-fix extraction is mandatory.
FOLLOW-UP TRAP: Assuming antenna fixes are timing-neutral.[INT][PD]
Q: When is layer promotion the right timing fix?
A:
When delay is wire-dominant and upper-layer capacity is available without severe congestion side effects.
FOLLOW-UP TRAP: Promoting nets without RC diagnosis.[INT][PD]
Q: What is a strong signal that via planning is insufficient?
A:
Recurring via-related EM hotspots and high single-cut usage on high-current nets.
FOLLOW-UP TRAP: Relying only on DRC-clean status.[INT][PD]
Q: How do shielding decisions affect routability?
A:
Shielding consumes routing tracks; targeted application is required to avoid congestion inflation.
FOLLOW-UP TRAP: Assuming shielding cost is negligible.[INT][PD]
Q: Why do special nets need separate review gates?
A:
They carry higher reliability and integrity risk than ordinary signals and can fail despite general route health.
FOLLOW-UP TRAP: Treating them as normal data nets.[INT][PD]
Q: How should you triage thousands of DRC violations quickly?
A:
Rank by class/severity/systemic origin, fix high-impact generators first, then clean residuals.
FOLLOW-UP TRAP: Manual one-by-one triage.[INT][PD]
Q: What indicates routing ECO churn is too high?
A:
Violation classes move between regions without net reduction and timing/extraction become unstable between iterations.
FOLLOW-UP TRAP: Continuing the same recipe indefinitely.[INT][PD]
Q: How do you prove routing improvements are real?
A:
Show class-wise DRC reduction, overflow improvement, and stable or improved extracted timing.
FOLLOW-UP TRAP: Using GUI snapshots without report deltas.[INT][PD]
Q: Why can post-route WNS collapse despite clean pre-route timing?
A:
Extracted RC and coupling effects reveal interconnect delays not captured in pre-route estimates.
FOLLOW-UP TRAP: Blaming STA setup only.[INT][PD]
Q: How do you prevent route-driven timing fixes from creating new DRC?
A:
Use bounded ECO regions, rule-aware fix recipes, and immediate class-wise DRC regression checks.
FOLLOW-UP TRAP: Running unconstrained global optimization passes.[INT][PD]
Q: What is the role of jog/detour metrics in route analysis?
A:
They expose inefficient topology and layer-policy conflicts that degrade delay and manufacturability.
FOLLOW-UP TRAP: Ignoring geometry quality when connectivity exists.[INT][PD]
Q: When should placement be revisited during routing?
A:
When overflow and DRC remain structurally tied to capacity/geometry limits that route-level tuning cannot resolve.
FOLLOW-UP TRAP: Forcing routing-only closure on structural congestion.[INT][PD]
Q: How do tie-cell issues surface during routing signoff?
A:
Floating input and LVS/precheck violations appear, often coupled with unreliable logic behavior risk.
FOLLOW-UP TRAP: Assuming tie-cell mistakes are synthesis-only.[INT][PD]
Q: Why is route recipe traceability critical for DRC closure?
A:
It enables causal debugging and reproducible convergence across runs.
FOLLOW-UP TRAP: Changing many knobs without logging.[INT][PD]
Q: How do you choose between reroute and waiver for residual DRC?
A:
Assess rule severity, manufacturability impact, and waiver policy; reroute critical classes whenever feasible.
FOLLOW-UP TRAP: Waiving by count pressure alone.[INT][PD]
Q: What minimum artifacts belong in a routing signoff packet?
A:
DRC class report, overflow summary, extraction-based STA, EM/IR evidence, and ECO/change log.
FOLLOW-UP TRAP: Submitting only timing numbers.[INT][PD]
Q: How do power routing defects affect timing teams indirectly?
A:
IR-drop hotspots alter cell delay behavior, causing path instability and corner surprises.
FOLLOW-UP TRAP: Treating power and timing as independent.[INT][PD]
Q: How should you narrate routing closure in an interview?
A:
Explain class-based triage, systemic fixes, extraction validation, and quantified regression control.
FOLLOW-UP TRAP: Describing only tool command sequence.Use each question as a two-minute mock. The target answer is not an essay; it is a structured closure response with a metric, mechanism, risk, and follow-up check.
MECHANISM: what physical effect or tool step is involved
WHEN: where it appears in the flow
PITFALL: one wrong junior answer
CHECK: report/map/checklist item that proves the answer5/5: metric, mechanism, experiment, regression, and release decision named without prompting.
4/5: technically correct and names regression, but misses ownership or escalation criteria.
3/5: correct concept but no decision framework.
1/5: tool command or buzzword with no mechanism.
Q&A bank 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.
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.
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>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.
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?
"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>."Always connect the concept back to a measurable signoff artifact.
A fix is not complete until you can name the regression checks.
Optimizing by habit instead of reading the current report.
Forgetting that a local fix can regress timing, routing, power, or PV elsewhere.