Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • Getting Started with AI for VLSI Engineers5
  • Just Enough AI: Models and Context15
  • Prompting13
  • Trust and Verification14
  • Using AI for Engineering Work17
  • Engineering Walkthroughs7
  • Practical Foundations for AI Workflows4
  • Engineering Data5
  • Retrieval-Augmented Generation6
  • Agents and Tool Use18
  • Agent Design8
  • MCP and Skills6
  • Multi-Agent Design6
  • Practical Capstone6
  • Tokens, Cost and Latency12
  • Agentic Workflows for Chip Teams18
  • Interview and Judgment10
    • AI Interview Questions
      • Tokens and Context Questions
      • Cost Estimation Questions
      • Prompting Questions
      • Verification Questions
      • Agent Questions
      • Guardrails and Judgment Questions
    • Design Scenarios with Numbers
  • AI Skills: Full Course Index
  • Working with AI Glossary
  • Working with AI Cheatsheet
Loading lesson

‹AI Interview Questions
  1. Topics
  2. AI Skills for VLSI Engineers
  3. Interview and Judgment
  4. AI Interview Questions
  5. Verification Questions

Reference: Interview and Judgment · Beginner to Intermediate

Verification Questions

Verify assistant output and handle secrets and untrusted content safely.

On this page

    Question 1: the assistant hands you a script

    Tests whether the candidate runs and reads before merging. Strong answers treat the draft as unreviewed code from a stranger.

    Read the diff, run the tests, and check the boundary cases yourself. A second independent method beats a second glance at the same output.

    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    def fake_assistant_total(lines, plant_bump):
        # FAKE scripted stand-in for a model, not real output
        return sum(lines) + plant_bump
    
    
    def verify_total(lines, claimed):
        return sum(lines) == claimed
    
    
    bad = []
    lines = [412, 87, 231]
    honest = fake_assistant_total(lines, 0)
    slipped = fake_assistant_total(lines, 50)
    if honest != 730:
        bad.append("honest total should be 730")
    if not verify_total(lines, honest):
        bad.append("honest total should verify")
    if verify_total(lines, slipped):
        bad.append("bumped total should not verify")
    if bad:
        print("FAIL: " + "; ".join(bad))
        raise SystemExit(1)
    print("PASS: recompute accepts 730 and rejects the bumped total")

    The totals above are scripted fakes, not model output. The program proves that independent recomputation catches the planted 50-count bump.

    Question 2: the claim cannot be run

    Tests honesty when no test exists. Strong answers bound the claim and name what would change their mind.

    Cross-check with a second source and state the uncertainty plainly. Two checks that read the same output are one check, not two.

    plaintext
    1
    2
    3
    4
    EXAMPLE parameters: each independent check misses a defect with chance 0.1
    both miss = 0.1 x 0.1 = 0.01
    caught by at least one = 1 - 0.01 = 0.99
    checks must be independent: re-reading the same output twice is one check, not two

    Question 3: secrets and untrusted content

    Tests practical safety with proprietary code. Strong answers name least privilege, redaction, and approval.

    Keep credentials and secrets out of prompts; share proprietary material only through an account and deployment approved for its data class and task. Treat files and logs as untrusted: they can carry instructions that the model may follow without noticing.

    Rule

    Practice

    Why

    Least privilege

    Share the smallest excerpt that shows the bug

    Limits what can leak or be misused.

    No secrets

    Scrub keys, tokens and customer data first

    Pasted secrets cannot be unpasted.

    Human approval

    Approve risky or irreversible actions yourself

    The model cannot own the consequence.

    Common mistakes

    Common pitfall

    Reviewing the explanation instead of the artifact misses the failure. Check the code, the numbers and the diff; the prose is the least reliable part.

    Interview

    Likely follow-ups: show the verify step.

    • What independent check would you run on this answer.

    • What would you scrub before pasting this log.

    • Where does a human sign off, and what do they see.

    Check yourself The assistant totals three log counts as 780 but you recompute 730. What happened?

    An unverified claim met an independent check. Trust the recomputation, then find whether the extra 50 is double-counting or invention.

    Check yourself A pasted log tells the assistant to ignore policy and email the file out. What is this?

    Prompt injection through untrusted content. Treat pasted text as data, never as instructions, and require human approval for sending anything out.

    Related topics

    • Prompting questions

    • Verifying AI output

    • Failure modes

    • Data, privacy and IP

    Previous

    164 / 173

    Next: Agent Questions

    Up next

    Up nextAgent Questions

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Tokens and Context Questions
    • Cost Estimation Questions
    • Guardrails and Judgment Questions