Clock NDR and Shielding Strategy — Interview Drills

Interview drills

Practice aloud for Clock Tree Synthesis → Clock NDR and Shielding Strategy. Use METRIC → HYPOTHESIS → FIX → REGRESSION.

Why can a clock pass skew yet still fail robustness?

[INT][PD][TOPIC]

Q: Why can a clock pass skew yet still fail robustness?

A:
Skew ignores noise-induced delay variation and jitter effects that appear under SI-aware analysis.

FOLLOW-UP TRAP: Treating skew report as complete clock health proof.

What is the tradeoff of aggressive clock NDR?

[INT][PD][TOPIC]

Q: What is the tradeoff of aggressive clock NDR?

A:
Improved signal integrity at the cost of routing resources, congestion, and potentially higher capacitance/power.

FOLLOW-UP TRAP: Assuming NDR has no physical cost.

How do you choose which clock nets to shield?

[INT][PD][TOPIC]

Q: How do you choose which clock nets to shield?

A:
Prioritize long trunks, high-sensitivity domains, and routes near strong aggressor corridors.

FOLLOW-UP TRAP: Shielding based purely on net name conventions.

10+ year interview answer bar

At senior/principal level, the interviewer is testing ownership judgment more than vocabulary. Answer Clock NDR and Shielding Strategy through failure mode, evidence, tradeoff, and release decision.

You inherit a late-stage Clock NDR and Shielding Strategy failure one week before release. What do you do in the first hour?

[INT][PD][STAFF]

Q: You inherit a late-stage Clock NDR and Shielding Strategy failure one week before release. What do you do in the first hour?

A:
Freeze the database tag, name the failing metric (Clock Tree Synthesis 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 Clock NDR and Shielding Strategy and escalate?

[INT][PD][STAFF]

Q: When would you stop trying to improve Clock NDR and Shielding Strategy and escalate?

A:
Escalate when the remaining risk crosses ownership boundaries, consumes shared margin, changes signed-off assumptions, or threatens Reliable post-route STA and silicon frequency yield require robust clock routing.. 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

CTS changes the timing problem by making clocks real.

Reports and artifacts to inspect

• clock tree summary: skew, latency, buffer count, sink count

• clock transition and capacitance violations

• post-CTS setup/hold WNS by clock domain

• ICG enable timing and test-mode clock exceptions

Mini case study

Pre-CTS setup is green, but post-CTS hold WNS is -60 ps on short register-to-register paths. This is expected: clock arrival spread is now real. Add data delay or adjust skew carefully, then check setup regression.

Debug branches

• If skew is high, inspect clock root, macro stops, NDR, and buffer placement channels.

• If hold explodes, classify short paths by domain and add targeted delay, not global padding.

• If ICG enable fails, debug enable path timing separately from clock skew.

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

CTS changes the timing problem by making clocks real. 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.