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 is effective utilization in macro-heavy blocks?
A:
It is usable std-cell area after subtracting macros, halos, keepouts, and reserved corridors from core area.
FOLLOW-UP TRAP: Using raw core area without reserved exclusions.[INT][PD]
Q: Why does aspect ratio matter beyond area?
A:
It changes wirelength distribution, channel pressure, clock spine feasibility, and package alignment.
FOLLOW-UP TRAP: Treating aspect ratio as cosmetic.[INT][PD]
Q: How do you spot false confidence in utilization metrics?
A:
Compare global utilization with regional hotspots and channel track deficits.
FOLLOW-UP TRAP: Approving based on one average number.[INT][PD]
Q: What is a practical macro channel planning metric?
A:
Required-versus-available tracks with margin for CTS and ECO growth.
FOLLOW-UP TRAP: Checking only geometric spacing.[INT][PD]
Q: Why can hard blockages hurt early floorplanning?
A:
They remove flexibility and may force detours before true congestion root cause is known.
FOLLOW-UP TRAP: Hard-blocking everything to be safe.[INT][PD]
Q: How should macro orientation be chosen?
A:
By pin-access and interface wiring demand, not symmetry preference.
FOLLOW-UP TRAP: Centering macros visually without pin analysis.[INT][PD]
Q: When should ring width be adjusted first?
A:
When IR droop is edge-dominant and indicates weak boundary delivery.
FOLLOW-UP TRAP: Tightening stripes globally for edge-only droop.[INT][PD]
Q: What is a sign of overbuilt strap planning?
A:
Signal route resources collapse while IR margin improves only marginally.
FOLLOW-UP TRAP: Assuming more straps are always better.[INT][PD]
Q: Why version pin contracts for abutment?
A:
To prevent silent interface incompatibilities and allow deterministic rollback.
FOLLOW-UP TRAP: Relying on chat/email confirmations.[INT][PD]
Q: What makes a pin edge high-risk?
A:
High pin density, many crossovers, and limited escape tracks on preferred layers.
FOLLOW-UP TRAP: Judging risk by pin count alone.[INT][PD]
Q: How does hierarchical revision skew manifest?
A:
Parent/child overlap, blocked channels, or unexpected timing budget violations.
FOLLOW-UP TRAP: Thinking tool import glitches are random.[INT][PD]
Q: What should be tracked in hierarchy integration matrix?
A:
Consumed abstract revision, compatibility status, boundary deltas, and owner approvals.
FOLLOW-UP TRAP: Tracking only latest release tag.[INT][PD]
Q: Why are feedthrough quotas useful?
A:
They prevent long-haul traffic from silently consuming local channel capacity.
FOLLOW-UP TRAP: Allowing unrestricted feedthrough usage.[INT][PD]
Q: What early warning indicates channel collapse?
A:
Rising feedthrough share and shrinking spare-track percentage across milestones.
FOLLOW-UP TRAP: Watching only WNS trends.[INT][PD]
Q: How do AMS keepouts fail in practice?
A:
Soft constraints get violated under optimization pressure and noisy trunks creep closer.
FOLLOW-UP TRAP: Assuming AMS notes are self-enforcing.[INT][PD]
Q: What is the first physical check for AMS noise regressions?
A:
Overlay keepout compliance and high-activity trunk proximity before circuit-level blame.
FOLLOW-UP TRAP: Immediately requesting analog redesign.[INT][PD]
Q: Why should checklist items be evidence-based?
A:
Evidence supports objective go/no-go decisions and prevents assumption drift.
FOLLOW-UP TRAP: Allowing verbal status without artifacts.[INT][PD]
Q: How do you handle conditional pass items?
A:
Track as explicit risk with owners, deadlines, and revalidation criteria.
FOLLOW-UP TRAP: Treating conditional pass as done.[INT][PD]
Q: What blocks placement entry despite schedule pressure?
A:
Any unresolved high-impact floorplan issue with likely downstream closure instability.
FOLLOW-UP TRAP: Proceeding because fixes can be 'done later'.[INT][PD]
Q: What is the core floorplanning principle for senior PD?
A:
Every geometry decision should state mechanism, measurable impact, and downstream risk.
FOLLOW-UP TRAP: Tool-command-centric explanations.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>Floorplan quality is the earliest predictor of place-and-route pain. 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.