Physical Design · All levels
Placement Tricky Q&A
20+ senior Placement 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 fastest way to distinguish demand-side vs capacity-side congestion?
[INT][PD]
Q: What is the fastest way to distinguish demand-side vs capacity-side congestion?
A:
Compare demand/capacity maps and correlate with fixed geometry. Capacity-side issues cluster around channels/blockages; demand-side issues track cell/net density.
FOLLOW-UP TRAP: Assuming every hotspot is solved by spreading cells.Why is displacement a critical ECO metric?
[INT][PD]
Q: Why is displacement a critical ECO metric?
A:
It measures physical churn and indicates whether unrelated logic moved enough to invalidate previous correlation.
FOLLOW-UP TRAP: Treating displacement as irrelevant after legality pass.How do you justify reducing utilization by 3-5 percent?
[INT][PD]
Q: How do you justify reducing utilization by 3-5 percent?
A:
When repeated hotspot fixes fail and overflow remains structural, lowering utilization can restore route headroom with lower iteration cost.
FOLLOW-UP TRAP: Reducing utilization without hotspot evidence.When is timing-driven placement likely to hurt final closure?
[INT][PD]
Q: When is timing-driven placement likely to hurt final closure?
A:
When aggressive net weighting creates dense islands that later route with long detours and SI penalties.
FOLLOW-UP TRAP: Believing pre-CTS slack gain guarantees post-route timing.Why should scan-chain metrics be reviewed during placement?
[INT][PD]
Q: Why should scan-chain metrics be reviewed during placement?
A:
Scan physical topology affects routing demand and shift timing; fixing late becomes expensive and destabilizing.
FOLLOW-UP TRAP: Leaving scan concerns solely to DFT after route.What evidence shows partition boundaries are poorly chosen?
[INT][PD]
Q: What evidence shows partition boundaries are poorly chosen?
A:
High crossing-net counts, boundary pin crowding, and repeated inter-partition timing failures despite buffering.
FOLLOW-UP TRAP: Judging boundary quality only by module hierarchy names.How do you know a legalization failure is structural?
[INT][PD]
Q: How do you know a legalization failure is structural?
A:
Failures persist across reruns and map to row/blockage/site mismatches rather than random optimizer behavior.
FOLLOW-UP TRAP: Retrying legalize endlessly with unchanged constraints.What should be frozen in incremental placement ECO runs?
[INT][PD]
Q: What should be frozen in incremental placement ECO runs?
A:
Unchanged macros, stable clock regions, and major placement anchors outside ECO scope.
FOLLOW-UP TRAP: Allowing global freedom to optimizer in small ECOs.Why track high-density-bin count in addition to global overflow?
[INT][PD]
Q: Why track high-density-bin count in addition to global overflow?
A:
Localized high-density pockets can be hidden by acceptable global averages and still break route closure.
FOLLOW-UP TRAP: Using only average utilization for signoff confidence.How do you communicate placement risk to CTS owners?
[INT][PD]
Q: How do you communicate placement risk to CTS owners?
A:
Provide quantified hotspots, expected buffer pressure regions, and watch metrics with owners and checkpoints.
FOLLOW-UP TRAP: Handoffing without structured risk notes.What indicates that a macro channel, not standard cells, is the congestion bottleneck?
[INT][PD]
Q: What indicates that a macro channel, not standard cells, is the congestion bottleneck?
A:
Overflow aligns with fixed channel boundaries and remains after local spread; pin access and channel width dominate.
FOLLOW-UP TRAP: Spreading cells globally before checking channel geometry.How do you avoid overfitting placement to one corner?
[INT][PD]
Q: How do you avoid overfitting placement to one corner?
A:
Use multi-corner trend checks and ensure chosen fixes do not regress representative setup/hold scenarios.
FOLLOW-UP TRAP: Closing only a single scenario and declaring success.Why are pin-access reports important at placement stage?
[INT][PD]
Q: Why are pin-access reports important at placement stage?
A:
Poor pin accessibility predicts routing detours and localized overflow even when placement legality passes.
FOLLOW-UP TRAP: Ignoring pin-access until detail route errors appear.What is a strong stop rule for incremental congestion tuning?
[INT][PD]
Q: What is a strong stop rule for incremental congestion tuning?
A:
No new hotspot clusters, stable overflow below threshold, and preserved timing/power trends across consecutive runs.
FOLLOW-UP TRAP: Stopping after any single small metric improvement.How can excessive fencing break placement quality?
[INT][PD]
Q: How can excessive fencing break placement quality?
A:
Fences over-constrain legal area, create local overutilization, and force long inter-region interconnect.
FOLLOW-UP TRAP: Assuming finer partitions always improve closure.What should a placement scorecard include before CTS?
[INT][PD]
Q: What should a placement scorecard include before CTS?
A:
Legality, overflow, density outliers, displacement stability, pre-CTS timing trend, and risk register status.
FOLLOW-UP TRAP: Presenting only one chart like WNS.Why are two stable passes better than one excellent pass?
[INT][PD]
Q: Why are two stable passes better than one excellent pass?
A:
Stability proves reproducibility and lowers risk of optimizer randomness or hidden constraints.
FOLLOW-UP TRAP: Optimizing for one best run without variance analysis.How do you detect that timing fixes are masking congestion issues?
[INT][PD]
Q: How do you detect that timing fixes are masking congestion issues?
A:
Slack improves while overflow worsens or shifts into new bins, indicating structural routability debt.
FOLLOW-UP TRAP: Accepting timing gain as unconditional win.What is the minimum artifact set for a placement review?
[INT][PD]
Q: What is the minimum artifact set for a placement review?
A:
Database tag, congestion map, legality report, timing summary, displacement histogram, and change log.
FOLLOW-UP TRAP: Reviewing from memory without artifacts.How do you explain placement maturity to an interviewer?
[INT][PD]
Q: How do you explain placement maturity to an interviewer?
A:
Describe metric-driven iteration: diagnose map/report root cause, apply minimal fix, and verify with regression deltas.
FOLLOW-UP TRAP: Listing tool commands without decision logic.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
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.