Part 11 · Senior Prep · Intermediate
Risk Communication Interview Q&A
Model answers on reporting verification risk to PM and design leads, translating coverage holes to product impact, and schedule negotiation with evidence.
Stakeholder communication
Q: How do you report verification risk to non-technical leads?
diagram
[INT][SENIOR][UVM] MODEL ANSWER
Q: Risk to non-technical lead?
A:
FRAME: Risk = unverified plan feature + impact if wrong + mitigation date.
EXAMPLE: "Interrupt storm cross uncovered — if HW mishandles, firmware boot
fail (P0). Closure test lands Wed; waive needs design VP if miss."
AVOID: jargon (objection, binsof) without translation.
SENIOR SIGNAL: connects coverage hole to product impact and dated mitigation.
PITFALL: 'We need two more weeks' with no prioritized hole list.Q: Weekly status — what three numbers do you lead with?
diagram
[INT][SENIOR][UVM] MODEL ANSWER
Q: Weekly status headline?
A:
THREE NUMBERS: P0 hole count, merged plan cov delta vs last week, nightly pass rate.
NARRATIVE: "P0 holes 3→1; plan cov +2.1%; nightly 97% pass — DMA closure Thu."
MOTIVATION: Executives scan numbers; engineers need narrative behind them.
PITFALL: Ten-slide deck without headline — meeting runs over, message lost.Q: Design lead says verification is blocking tape-out unfairly — respond?
diagram
[INT][SENIOR][UVM] MODEL ANSWER
Q: 'Verification blocking tape-out'?
A:
RESPONSE: Show sign-off checklist vs current state — objective gap list.
OFFER: Parallel closure on their open ECO while you close P0 holes.
TONE: Partner framing — same ship date, shared risk register.
PITFALL: Defensive 'you do not understand verification' — destroys alliance.diagram
[INT][SENIOR][UVM] risk register row template
ID: RISK-07
SCENARIO: DMA + IRQ storm under cache pressure
IMPACT: firmware boot hang (P0)
EVIDENCE: PLAN-FP-12 uncovered in merged UCDB
MITIGATION: hole_FP_12_vseq + closure test ETA Wed
OWNER: verification (Jane) + firmware review (Bob)Key takeaways
Risk frame: unverified feature + product impact + mitigation date.
Weekly status: P0 holes, cov delta, pass rate — then narrative.
Design partnership — shared checklist, not adversarial gatekeeping.
Common pitfalls
Jargon-heavy status to PM — eyes glaze, trust drops.
Risk register without owner and date — not actionable.
Schedule negotiation and escalation
Q: PM cuts verification time by 30% — what do you cut?
diagram
[INT][SENIOR][UVM] MODEL ANSWER
Q: 30% schedule cut?
A:
DO NOT CUT: P0 smoke, merged closure review, assertion regressions.
CAN CUT: weekly exploratory tests, redundant directed variants, nice-to-have cov.
COMMUNICATE: Written risk on each cut — which plan rows weaken.
EXAMPLE: Dropped duplicate addr-alignment directed — kept cross closure suite.Q: When do you escalate verification risk above your manager?
diagram
[INT][SENIOR][UVM] MODEL ANSWER
Q: Escalate above manager?
A:
WHEN: P0 hole with no mitigation path before fixed tape-out date;
silent waiver pressure from design without verification concurrence.
HOW: Factual risk memo — not emotional email; manager informed first.
PITFALL: End-run manager routinely — burns political capital.
EXAMPLE: VP risk sign-off requested when closure test cannot land before freeze.Q: Emulation results disagree with simulation sign-off — communicate how?
diagram
[INT][SENIOR][UVM] MODEL ANSWER
Q: Emulation vs sim mismatch?
A:
MECHANISM: Emulation found scenario sim seeds missed — different abstraction or timing.
ACTION: File sim gap as new plan row; add emulation-derived directed to nightly.
MESSAGE: 'Emulation extended sign-off evidence — sim hole now closed, not sim wrong.'
PITFALL: Hiding emulation fail because sim dashboard was green — escape risk.bash
# weekly status artifact — numbers PM can scan
P0_HOLES=$(wc -l < p0_holes.txt)
COV_DELTA=$(python3 cov_delta.py --this merged.ucdb --last last_week.ucdb)
PASS_RATE=$(grep PASS nightly.manifest | wc -l)
echo "P0=${P0_HOLES} COV_DELTA=${COV_DELTA}% PASS=${PASS_RATE}%"Key takeaways
Schedule cuts: protect P0 smoke and closure — cut redundant tests with risk log.
Escalate with factual memo — inform manager first.
Emulation extends evidence — report gaps it finds honestly.
Common pitfalls
Cutting closure tests to meet date — post-silicon bill arrives later.
Escalation without mitigation proposal — sounds like complaint only.