SI Signoff Reports: Interview Drills

Interview drills

Interview Drills for SI Signoff Reports focuses on SI-clean path %, remaining aggressor violations, signoff waiver count. The goal is to connect the observable symptom to timing mechanism, ownership, and regression risk.

PROMPT
You see SI-clean path %, remaining aggressor violations, signoff waiver count on SI Signoff Reports. Walk through root cause and fix.

STRONG ANSWER
1. Names corner/mode/view and path group.
2. Explains SI signoff aggregates delta delay and noise against foundry rules and product margin; reports must map to fix ownership.
3. Requests SI signoff summary, foundry SI checklist, waiver log.
4. Proposes one reduced sequence and one system regression.

WEAK ANSWER
Jumps to upsizing cells, widening routes, or blaming tools without reading constraints and path delay.

Diagram to draw on the whiteboard

SI signoff summary

SI SIGNOFF DASHBOARD

delta delay violations : 12  (owner: PD)
noise violations       : 3   (owner: SI)
waivers pending        : 1   (owner: STA lead)

Root-cause tree to narrate

ROOT-CAUSE TREE — SI Signoff Reports

SI-clean path %, remaining aggressor violations, signoff waiver count looks wrong
        |
   same netlist tag?
     /        \
   no          yes
   |            |
 view/SDC     real path or
 mismatch     constraint bug
 /    \           |
lib   SPEF    delay breakdown
diff  diff    cell vs net

STA deep dive

Coupling makes delay a function of neighbors, not just wire RC.

Concept diagram

SI ON VICTIM

victim net delay = base_RC + coupling_from_aggressors

Metric graph

DELTA DELAY ON CRITICAL PATHS

no SI   ████████  1.2ns
with SI ██████████  1.35ns  (+150ps)

Reports and artifacts

• delta delay report

• aggressor list

• noise peaks

• SI WNS delta

Mini case study

Setup fixed by upsize but SI worsened — spacing ECO on bus bits recovered margin.

Debug branches

• Re-run SI after every timing ECO

• Shield wide switching buses

Senior review question

Ask: what corner/mode/view proves this topic is closed or failing?

Key takeaways

• State corner, mode, view, and database tag with every slack claim.

• Run setup and hold plus MMMC regression after every ECO.

Common pitfalls

• Comparing STA runs with different SPEF or SDC tags.

• Broad false_path to green-wash violations.

• Setup-only ECO without hold check.

Principal STA review addendum

SI signoff aggregates delta delay and noise against foundry rules and product margin; reports must map to fix ownership.

Metric: SI-clean path %, remaining aggressor violations, signoff waiver count