When should PD return the handoff instead of editing locally?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
Return defects in functional connectivity, synthesis structure, library release, interface timing intent, or mode definitions to their authoritative owner.
Technical Explanation
Treat this as a readiness check. It should produce named objects and a result that another engineer can repeat from the same handoff.
What To Check
• Warning sign: A local edit silences the tool but creates a fork from synthesis or STA signoff intent. • Inspect: Keep at least two possible causes open, then use one named object and the active mode or scenario to separate them. • Correct: Package the smallest reproducer, exact objects, commands, logs, and expected-versus-actual evidence for the owner.
Command Checks & Actions
• current_block: confirms the active design block
• check_netlist: reports structural connectivity problems
• check_timing: finds missing or inconsistent timing setup
Run the commands in order. Each line answers a separate part of the check.Healthy, Suspicious & Hard-stop Results
• Expected: Return defects in functional connectivity, synthesis structure, library release, interface timing intent, or mode definitions to their authoritative owner. • Investigate: A local edit silences the tool but creates a fork from synthesis or STA signoff intent. • Stop before floorplanning when required logic or timing coverage is missing or unexplained. Package the smallest reproducer, exact objects, commands, logs, and expected-versus-actual evidence for the owner.
Common Mistake
Do not assume the check passed just because ICC2 continued: A local edit silences the tool but creates a fork from synthesis or STA signoff intent. Fix or narrowly justify the named objects, then rerun the same command.
What The Interviewer Is Testing
Be ready to explain why this matters before floorplanning: A local edit silences the tool but creates a fork from synthesis or STA signoff intent.
Follow-up Question & Model Response
Model response: “I would save the report, inspect one affected object in the correct block and scenario, and make or request this correction: Package the smallest reproducer, exact objects, commands, logs, and expected-versus-actual evidence for the owner. Then I would reopen the clean checkpoint and rerun the same evidence.”
Practical Example
Symptom: A local edit silences the tool but creates a fork from synthesis or STA signoff intent. Corrective path: Package the smallest reproducer, exact objects, commands, logs, and expected-versus-actual evidence for the owner.
Continue practising