PDK Technology Files — Interview Drills

Interview drills

Practice aloud for Data and Libraries → PDK Technology Files. Use METRIC → HYPOTHESIS → FIX → REGRESSION.

What does a technology file mismatch look like in late stages?

[INT][PD][TOPIC]

Q: What does a technology file mismatch look like in late stages?

A:
You see non-reproducible DRC/LVS or RC shifts between implementation and signoff. Root cause is usually layer map or deck version skew.

FOLLOW-UP TRAP: Saying only 'tool bug' without checking deck stack identity.

How do you freeze PDK collateral in a large team?

[INT][PD][TOPIC]

Q: How do you freeze PDK collateral in a large team?

A:
Publish a signed manifest and consume only that tag in CI and local runs. Disallow ad-hoc deck overrides except through reviewed patches.

FOLLOW-UP TRAP: Relying on shared filesystem latest symlink.

Why compile decks in bring-up instead of waiting for full-chip?

[INT][PD][TOPIC]

Q: Why compile decks in bring-up instead of waiting for full-chip?

A:
Deck compile validates syntax and include reachability early; it catches broken environment assumptions before expensive route/signoff runtime.

FOLLOW-UP TRAP: Treating deck validation as a final signoff-only activity.

10+ year interview answer bar

At senior/principal level, the interviewer is testing ownership judgment more than vocabulary. Answer PDK Technology Files through failure mode, evidence, tradeoff, and release decision.

You inherit a late-stage PDK Technology Files failure one week before release. What do you do in the first hour?

[INT][PD][STAFF]

Q: You inherit a late-stage PDK Technology Files failure one week before release. What do you do in the first hour?

A:
Freeze the database tag, name the failing metric (Technology manifest and deck compile 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.

When would you stop trying to improve PDK Technology Files and escalate?

[INT][PD][STAFF]

Q: When would you stop trying to improve PDK Technology Files and escalate?

A:
Escalate when the remaining risk crosses ownership boundaries, consumes shared margin, changes signed-off assumptions, or threatens Floorplan, route, extraction, and PV become deterministic only after this stack is frozen.. 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

Interview performance is structured closure thinking under time pressure.

Reports and artifacts to inspect

• 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

Mini case study

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.

Debug branches

• 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.

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

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.