Physical Design · All levels
Power Planning Tricky Q&A
20+ senior Power Planning interview questions.
Q&A bank
Answer with mechanism, pitfall, regression check, and release judgment. At 10+ years, a correct definition is not enough.
Senior answer rubric
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.
What is the first objective of core ring design?
[INT][PD]
Q: What is the first objective of core ring design?
A:
Provide low-resistance boundary current delivery with continuous VDD/VSS paths and robust corners.
FOLLOW-UP TRAP: Treating ring as decorative boundary metal.Why not use symmetric ring widths by default?
[INT][PD]
Q: Why not use symmetric ring widths by default?
A:
Current demand is often directional; asymmetric sizing can improve IR without excess blockage.
FOLLOW-UP TRAP: Forcing equal widths everywhere for convenience.How do straps impact routing closure?
[INT][PD]
Q: How do straps impact routing closure?
A:
Tighter pitch improves IR but consumes tracks and may increase congestion overflow.
FOLLOW-UP TRAP: Assuming strap insertion has no route cost.When should strap pitch vary by region?
[INT][PD]
Q: When should strap pitch vary by region?
A:
When activity/current density differs significantly across the block.
FOLLOW-UP TRAP: Keeping uniform pitch despite clear hotspot regions.What is the role of follow-pin rails in IR health?
[INT][PD]
Q: What is the role of follow-pin rails in IR health?
A:
They bridge power from upper mesh into standard-cell rows; weak rails cause local droop.
FOLLOW-UP TRAP: Ignoring rails because top-metal grid looks strong.How do you detect row-level rail weakness?
[INT][PD]
Q: How do you detect row-level rail weakness?
A:
Use continuity and rail-to-strap via coverage reports correlated with local hotspots.
FOLLOW-UP TRAP: Checking only block-level max IR number.Why are macro power hookups high-risk?
[INT][PD]
Q: Why are macro power hookups high-risk?
A:
Large concentrated current enters through limited pin locations, creating local bottlenecks.
FOLLOW-UP TRAP: Treating macro hookups like ordinary std-cell rails.What proves macro hookup quality?
[INT][PD]
Q: What proves macro hookup quality?
A:
Domain-correct connectivity plus macro-local IR/EM metrics and robust via ladders.
FOLLOW-UP TRAP: Declaring done once nets are connected.How should decap insertion be targeted?
[INT][PD]
Q: How should decap insertion be targeted?
A:
By dynamic hotspot and impedance analysis, balancing droop improvement versus leakage/area.
FOLLOW-UP TRAP: Blanket decap fill everywhere.When does decap fail to help much?
[INT][PD]
Q: When does decap fail to help much?
A:
When root cause is distribution topology weakness rather than local charge shortage.
FOLLOW-UP TRAP: Expecting decap to fix all IR issues.Why is domain partitioning a physical design problem?
[INT][PD]
Q: Why is domain partitioning a physical design problem?
A:
UPF intent must map to real grid connectivity, switch placement, and always-on paths.
FOLLOW-UP TRAP: Assuming low-power intent is purely logical.What is a dangerous domain-grid mistake?
[INT][PD]
Q: What is a dangerous domain-grid mistake?
A:
Feeding retention/isolation through switched supply paths.
FOLLOW-UP TRAP: Checking only domain net names.How do you evaluate wake-up robustness?
[INT][PD]
Q: How do you evaluate wake-up robustness?
A:
Run wake-up IR stress and inspect switch current balance and trunk strength.
FOLLOW-UP TRAP: Looking only at static IR in steady state.What is early IR best used for?
[INT][PD]
Q: What is early IR best used for?
A:
Finding structural weaknesses early and steering grid topology before expensive stages.
FOLLOW-UP TRAP: Using early IR as final signoff.How do you avoid false early-IR conclusions?
[INT][PD]
Q: How do you avoid false early-IR conclusions?
A:
Keep assumptions controlled and compare deltas across consistent scenarios.
FOLLOW-UP TRAP: Changing activity models every run.Why track hotspot persistence across scenarios?
[INT][PD]
Q: Why track hotspot persistence across scenarios?
A:
Persistent hotspots likely reflect true structural risk; transient ones may be model noise.
FOLLOW-UP TRAP: Prioritizing the single worst transient hotspot.Which report combination is most actionable for power planning?
[INT][PD]
Q: Which report combination is most actionable for power planning?
A:
IR map, congestion/overflow impact, and connectivity integrity together.
FOLLOW-UP TRAP: Reviewing IR without routability context.What is a sign of overdesigned power grid?
[INT][PD]
Q: What is a sign of overdesigned power grid?
A:
Marginal IR gains with significant routing and area penalties.
FOLLOW-UP TRAP: Assuming overdesign has no downside.How should power planning decisions be documented?
[INT][PD]
Q: How should power planning decisions be documented?
A:
With assumptions, evidence reports, chosen tradeoffs, and downstream risk notes.
FOLLOW-UP TRAP: Capturing only tool commands used.What is the senior-level power planning mindset?
[INT][PD]
Q: What is the senior-level power planning mindset?
A:
Optimize grid as a system across electrical robustness, routability, and integration constraints.
FOLLOW-UP TRAP: Chasing one metric in isolation.How to drill this Q&A bank
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.
Answer template
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 answerScoring
5/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.
Principal-level review bar
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.
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
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.
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.