Practice aloud for Power Planning → Decap Planning. Use METRIC → HYPOTHESIS → FIX → REGRESSION.
[INT][PD][TOPIC]
Q: When does decap insertion provide limited value?
A:
When droop root cause is poor distribution path impedance or weak connectivity rather than local charge shortage.
FOLLOW-UP TRAP: Using decap as universal IR fix.[INT][PD][TOPIC]
Q: How do you defend decap overhead in review?
A:
Show hotspot-specific dynamic IR reduction relative to leakage and area cost.
FOLLOW-UP TRAP: Reporting only total decap count.[INT][PD][TOPIC]
Q: Why revisit decap after CTS?
A:
Clock-tree and buffering alter switching concentration, changing transient hotspot locations.
FOLLOW-UP TRAP: Assuming floorplan-stage decap remains optimal.At senior/principal level, the interviewer is testing ownership judgment more than vocabulary. Answer Decap Planning through failure mode, evidence, tradeoff, and release decision.
[INT][PD][STAFF]
Q: You inherit a late-stage Decap Planning failure one week before release. What do you do in the first hour?
A:
Freeze the database tag, name the failing metric (Dynamic droop improvement versus decap overhead report), 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.[INT][PD][STAFF]
Q: When would you stop trying to improve Decap Planning and escalate?
A:
Escalate when the remaining risk crosses ownership boundaries, consumes shared margin, changes signed-off assumptions, or threatens Dynamic timing stability and power signoff margin rely on effective decap strategy.. 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.Interview performance is structured closure thinking under time pressure.
one-slide metric dashboard for the scenario
hypothesis list sorted by likelihood and cost
one report/map per experiment
regression list after the proposed fix
A strong answer to any scenario starts with the failing metric and signoff context. A weak answer starts with a tool command or random optimization knob.
If you are stuck, restate the metric and ask for corner/mode/stage.
If multiple failures exist, separate hard gates from tracked risks.
If pressured to waive, describe approval path and silicon risk.
Ask yourself: what single report line would prove this page's concept is either passing or failing?
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.
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.
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>Interview performance is structured closure thinking under time pressure. 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.