Timed mock (45 minutes)

Spec snippet → env sketch → sequence → scoreboard for simple APB peripheral.

Timer breakdown

1. 0–5 min: Read spec — APB regs CTRL/STATUS, one RW data reg

2. 5–15 min: Env box diagram — active master, monitor, reg model, scoreboard

3. 15–25 min: Sketch basic read/write sequence + driver handshake

4. 25–35 min: Scoreboard FIFO compare for read data

5. 35–45 min: Pitfalls + 5-minute smoke test plan

RUBRIC (score 1–5 each)

  Mechanism accuracy — correct UVM pattern, no magic
  Communication — narrates while sketching
  Pitfalls — cites unprompted
  Test mindset — smoke test + regression hook

STRONG HIRE: mechanism + pitfall + test without prompting
NO HIRE: silent coding, wrong TLM direction, no test plan

Interviewer follow-up traps (sample 10)

• What if PREADY never comes?

• Reset during active transfer?

• Byte lane on narrow APB?

• Who raises objection?

• How regress this smoke?

Strong hire signals

• Narrates DECLARE→TEST without prompting

• Names pitfall unprompted

• Smoke test and regression hook stated

• Asks clarifying protocol questions early

No hire signals

• Silent coding

• Wrong TLM direction on diagram

• No test plan after sketch

• Cannot recover when stuck

CODE LAB FOLLOW-UP: uvm-l10-mock-apb

Key takeaways

• Complete mock in 45 min wall clock.

• Self-score rubric honestly.