Interview Prep & Tips /Semiconductor Validation

Post-silicon validation fundamentals

BeginnerFundamentals

Sample guide. Edit or replace it with your own material.

These questions test whether you understand why post-silicon validation exists and where it fits in the product flow. For each one, answer in your own words and give an example from a project where you can.

1. Verification vs validation vs production test

What a good answer covers:

• Pre-silicon verification: checks the design against the specification using simulation, emulation, and formal methods, before tape-out.
• Post-silicon validation: checks real silicon on the bench. It finds bugs that simulation missed: analog effects, timing across process corners, and system-level interactions.
• Production test: screens every manufactured part for fabrication defects on ATE. Its job is to screen parts, not find design bugs.

2. What is PVT, and why test at corners?

• Process, Voltage, Temperature. Circuit speed and leakage change with each of them.
• Testing at the corners (for example slow process, minimum voltage, hot) shows whether the design still meets spec at the edges of its operating range.
• Mention margin: how far past the spec limit the part still works.

3. What is a shmoo plot?

• A 2D pass/fail map that sweeps two parameters, typically voltage against frequency.
• It shows the operating window and how much margin there is. An unexpected hole or a ragged edge in the plot usually points to a bug worth investigating.

4. A test fails only at hot temperature. How do you approach it?

A structured answer:

1. Reproduce it and find out how often it fails. Does it fail every time or only sometimes?
2. Isolate it: check whether it follows the part (swap the samples) or the setup (swap the board).
3. Sweep one variable at a time (temperature, voltage, frequency) to find the threshold.
4. Form hypotheses: timing path, leakage, analog drift, or a firmware race.
5. Narrow it down with registers, debug trace, and scope captures. Escalate to the design team with data.

Practice

• Explain a shmoo plot to a non-engineer in two minutes.
• Pick one project and describe the validation plan you would write for it.