Pattern Volume Tradeoffs: Interview Drills

Interview drills

Interview Drills for Pattern Volume Tradeoffs focuses on pattern count, tester memory usage, test application time. The goal is to convert metric movement into mechanism, owner, and release decision.

PROMPT
You observe pattern count, tester memory usage, test application time on Pattern Volume Tradeoffs. Walk through diagnosis and release decision.

STRONG ANSWER
1. States context and run tags.
2. Explains mechanism: Pattern volume is a tradeoff between coverage closure aggressiveness, X-handling policy, and compression settings constrained by tester resources.
3. Requests ATPG pattern summary, tester memory estimate, runtime trend.
4. Proposes minimal fix and regression.

WEAK ANSWER
Jumps to tool switches without evidence quality, ownership, or regression plan.

Diagram to draw on the whiteboard

Pattern volume tradeoff

coverage target up  -> pattern count up
X-masking strict   -> pattern count up
compression ratio up -> pattern count down (to a limit)

Choose target with ATE budget in loop.

Root-cause narrative

ROOT-CAUSE TREE - Pattern Volume Tradeoffs

pattern count, tester memory usage, test application time regresses
        |
  setup changed?
    /        \
  yes         no
  |            |
constraint    silicon or
or ATPG       physical/test path
 /    \          |
SDC   model    chain/clock/power/diagnosis
diff  diff     isolate first failing signature

DFT deep dive

Compression saves tester time only when diagnosis observability remains credible.

Concept diagram

COMPRESSION LOOP

EDT/decompressor -> compressed patterns -> compactor responses -> diagnosis

Metric graph

PATTERN vs COVERAGE

coverage up   -> pattern count up
compression up -> pattern count down (until aliasing risk)

Reports and artifacts

• compression ratio dashboard

• pattern count trend

• X-source report

• diagnosis bucket summary

Mini case study

Compactor overflow plus unknown inflation caused false diagnosis; masking policy and channel map corrected.

Debug branches

• Separate X issues from silicon defects

• Replay failing patterns uncompressed

• Track tester memory budget

Senior review question

Ask: what evidence proves this DFT decision is safe for production?

Key takeaways

• State metric, lot/corner context, and pattern tag with every claim.

• Treat timing, power, and quality as one signoff problem.

Common pitfalls

• Chasing coverage without legality checks.

• Ignoring test-power side effects of pattern changes.

• Debugging silicon without reproducible tags.

Principal DFT review addendum

Pattern volume is a tradeoff between coverage closure aggressiveness, X-handling policy, and compression settings constrained by tester resources.

Metric: pattern count, tester memory usage, test application time