compliance

Large companies have delayed EU launches for different reasons. Name the specific blocker, ship the subset that clears it, and set dated exit criteria for the rest.

A design question with a constraint dropped halfway. The interviewer wants to see residency flow through every component: model calls, logs, caches, embeddings, evals and support access.

Hiring is one of the clearest high-risk uses under the EU AI Act. The interviewer wants to see you turn obligations into product requirements and a roadmap, with dates stated carefully.

US AI regulation is a moving patchwork on top of long-standing lending law. The interviewer wants a product plan that holds up whichever way state laws go: explainability, fairness testing, human review and documentation.

Users type sensitive data into chat boxes whatever the instructions say, and debug logs keep it forever. The interviewer wants immediate containment, a redaction design, and a balance between privacy and the ability to debug.

Several clocks start at once, some measured in hours. Classify the incident against each regime, start each clock at awareness and file before causation is settled.

AI launches increasingly run into legal, privacy and compliance review. Panels want a partner, not an adversary: someone who turns concerns into requirements and finds a path that works for both sides.