AI & Technical question

Design ethical guardrails for an AI that detects and responds to human emotion.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests AI product design for building ethical guardrails around a capability with clear potential for both benefit and misuse.

Identify the misuse risks specifically: manipulation by tailoring persuasion to a detected emotional state, surveillance of emotional state without consent, and discriminatory use in contexts like hiring or lending.
Separate technical guardrails from policy guardrails, since some risks need to be designed out of the system and others need clear usage restrictions enforced through terms and review.
Propose consent as a core requirement: emotion detection should require clear user awareness and consent, not silent inference from voice or video.
Restrict high risk use cases explicitly: prohibit or tightly control use in hiring, lending, insurance, and other decisions with major life consequences for the person being read.
Add transparency: users should be able to see what emotional signal the system detected and be able to correct or dispute it.
Confirm with the interviewer whether the guardrails are for Hume's own product or for a platform where third party developers build on top, since enforcement differs.

Names specific misuse categories, manipulation, covert surveillance, and discriminatory decision making, rather than discussing ethics in the abstract.
Requires informed consent before emotion detection runs, directly addressing the most common concern with this technology, being read without knowledge or agreement.
Proposes hard restrictions on high stakes use cases like hiring and lending, recognizing some applications carry risk that no amount of technical safeguard fully resolves.
Adds a transparency and dispute mechanism, giving users agency over how they are being interpreted rather than treating detection as an unchallengeable black box.

Discussing ethics only in general terms without naming specific, plausible misuse scenarios.
No consent requirement, treating emotion detection as something that can happen without the user's awareness.
Ignoring enforcement for third party developers building on the platform, who could misuse the capability in ways Hume does not directly control.

How would you enforce these guardrails for third party developers building on Hume's API?
What would you do if a legitimate use case, like clinical research, needed an exception to the consent rule?
How would you detect if a customer was using the technology for a prohibited purpose?