Interview drills

Interview Drills for Bump Map & Escape Planning focuses on bump congestion, reroute churn, escape DRC violations. The goal is to map symptoms to boundary contracts, owner actions, and regression-proof closure.

PROMPT
You observe bump congestion, reroute churn, escape DRC violations in Bump Map & Escape Planning. Explain root cause and closure plan.

STRONG ANSWER
1. Names baseline manifest and failing boundary.
2. Explains Bump maps and escape strategy determine routability, IR quality, and package feasibility before final pad-ring freeze.
3. Requests bump map revision, escape routing plan, package feasibility report.
4. Proposes minimal reversible fix + full regression scope.

WEAK ANSWER
Suggests broad optimizations or owner blame without baseline and artifact evidence.

Diagram to draw on whiteboard

Bump escape planning

BUMP + ESCAPE

die bumps -> redistribution -> package balls
      |             |
   power grid    high-speed lane escape

Early escape planning prevents late route deadlock.

Root-cause tree to narrate

ROOT-CAUSE TREE — Bump Map & Escape Planning

bump congestion, reroute churn, escape DRC violations regressed
         |
   same baseline manifest?
      /           \
    no             yes
    |               |
version/collateral  real integration
mismatch            contract break
 /       \            |
inputs    env      isolate domain
drift     drift    and first failure

SoC deep dive

Package assumptions must be treated as first-class chip constraints.

Concept diagram

PACKAGE CO-DESIGN
die io <-> package routing <-> board constraints

Metric graph

PACKAGE RISK MIX
SI margin █████
power integrity ████
lane mapping ███

Reports and artifacts

• bump map revision log

• SI/PI margin report

• IO co-design checklist

• package bring-up failures

Mini case study

Link degradation on product board came from package routing assumptions not reflected in pre-silicon model.

Debug branches

• Compare package model versions

• Audit lane mapping

• Correlate SI/PI margins to failures

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

• State baseline manifest and owner with every closure metric.

• Run cross-domain regression after every top-level fix.

Common pitfalls

• Comparing results across different manifests.

• Unowned issues slipping through review cycles.

• Waiving risks without expiry and validation plan.

Principal SoC review addendum

Bump maps and escape strategy determine routability, IR quality, and package feasibility before final pad-ring freeze.

Metric: bump congestion, reroute churn, escape DRC violations