Global vs Detailed Placement — Interview Drills

Interview drills

Practice aloud for Placement → Global vs Detailed Placement. Use METRIC → HYPOTHESIS → FIX → REGRESSION.

Why can detailed placement not fully rescue poor global placement?

[INT][PD][TOPIC]

Q: Why can detailed placement not fully rescue poor global placement?

A:
Detailed placement operates under legal-site constraints and small local movement; it cannot create missing routing capacity from a bad global density pattern.

FOLLOW-UP TRAP: Claiming legalization intrinsically fixes congestion.

Which two metrics convince you GP quality is handoff-ready?

[INT][PD][TOPIC]

Q: Which two metrics convince you GP quality is handoff-ready?

A:
Low/controlled global overflow and stable high-density-bin count, corroborated by manageable displacement in DP.

FOLLOW-UP TRAP: Using only WNS as placement quality proof.

How do you explain displacement thresholds to a reviewer?

[INT][PD][TOPIC]

Q: How do you explain displacement thresholds to a reviewer?

A:
Large displacement indicates unstable optimization and ECO risk; thresholds protect physical continuity and timing comparability across runs.

FOLLOW-UP TRAP: Treating displacement as a cosmetic metric.

10+ year interview answer bar

At senior/principal level, the interviewer is testing ownership judgment more than vocabulary. Answer Global vs Detailed Placement through failure mode, evidence, tradeoff, and release decision.

You inherit a late-stage Global vs Detailed Placement failure one week before release. What do you do in the first hour?

[INT][PD][STAFF]

Q: You inherit a late-stage Global vs Detailed Placement failure one week before release. What do you do in the first hour?

A:
Freeze the database tag, name the failing metric (Placement 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 Global vs Detailed Placement and escalate?

[INT][PD][STAFF]

Q: When would you stop trying to improve Global vs Detailed Placement and escalate?

A:
Escalate when the remaining risk crosses ownership boundaries, consumes shared margin, changes signed-off assumptions, or threatens CTS skew and routing DRV closure depend on this stability.. 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

Placement converts floorplan assumptions into local density, timing, and congestion reality.

Reports and artifacts to inspect

• global placement congestion heatmap by layer and bin

• density map: local cell density vs target utilization

• pre-CTS timing: path wirelength, cell delay, net delay split

• legalization summary: unplaced cells, overlaps, row/site errors

Mini case study

The block average utilization is 68%, but the router reports overflow near a soft macro. The correct read is that local density, not global utilization, is failing. Spread cells, adjust blockages, or revisit macro channels before detailed route.

Debug branches

• If average utilization is fine but route overflows, inspect local bins and macro pin access.

• If detailed placement fails, check hard blockages, row definitions, multi-height rows, and fence size.

• If timing regresses after spreading cells, separate congestion-critical nets from timing-critical nets.

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

Placement converts floorplan assumptions into local density, timing, and congestion reality. 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.