Lawful intercept compliance handler
A telecom backend must implement a regulator-mandated lawful-intercept / data-retention handler with exact, audited semantics defined in a compliance document. A PM asks why you won't just let the agent 'build it from the spec doc' like it did for the last CRUD feature. Make the case for when AI is the wrong primary tool here — and where, if anywhere, it still helps.
Implement
choose_authoring_mode(externally_audited: bool, author_minutes: int, verify_minutes: int) → strExamples
in
[true,600,600]out"human_authors"in
[false,120,20]out"ai_primary"What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 18 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.