← Back to Work 1 / 15
Meghana Gautam and teammates holding the Shark Tank trophy and sketch board
🏆 1st Place — Shark Tank

HAI — Hello, AI.
Designing the voice interview of tomorrow.

A 20-minute live design sprint at UX Camp Amsterdam that turned into the concept I couldn't stop thinking about.

📍 UX Camp Amsterdam 📅 4 July 2026 ⏱️ 20-min live sprint
The Format

Shark Tank: a 20-minute design challenge, judged live

Teams of UX Camp attendees — strangers an hour earlier — were given a brief, a timer, and a stage. The challenge: design a human ⟷ voice AI agent interview that feels immersive and meaningful, not shallow.

Timeline

  • 5–10 min — Setup, intro, team formation
  • 20–25 min — Live design challenge
  • 20 min — 3-min pitch + 2-min Q&A, 4 teams
  • 10 min — Scoring & results

Judged on

  • Problem Depth — new dimensions uncovered?
  • Solution Fitness — quality, reasoning?
  • Out of the Box — something original?
  • Engaging Delivery — clear, and fun?
Why This, Why Now

Voice AI interviews are already here. They just aren't good yet.

78%
of applicants preferred an AI interviewer over a human, when given the choice
Jabarian & Henkel, 2025 — Chicago Booth / Erasmus Rotterdam
12%
more likely to receive a job offer when interviewed by AI vs. a human
Same field study — SSRN working paper

The brief was blunt about it: this is a win-win on paper — lower cost, more scalability, less human bias. But today's voice AI interview experiences feel shallow. That gap was the actual design problem.

Where I Started

Before sketching anything, I mapped the candidate's experience

My first move wasn't a wireframe — it was empathy. What does a candidate think before an AI interview starts? How do they feel mid-conversation? What do they do when they're stuck? What do they say about it afterward?

Think
"Will it actually understand me?" "What happens to this recording?"
Say
What they tell friends, recruiters, or reviews afterward — the story that spreads.
Do
Pause. Re-read the question on screen. Try to fill silence they don't understand.
Feel
Uncertain whether silence is being read as confidence or as a wrong answer.
💡 A deliberate choice: the brief already included research data (78% / 12% preference stats). Rather than re-researching from scratch in a 20-minute window, I treated that as ground truth and spent the time on depth, not validation.
The Core Principle
Glass box.
Not black box.

This was the principle I introduced: the interview should be a glass box, where candidates can see what's happening inside it — not a black box that leaves them confused about what's coming next. Every feature decision that followed traced back to that one line.

📦
Black Box
Candidate can't see how they're read, scored, or stored. Confusion, by default.
🔍
Glass Box
What's inside is visible — mood, status, data handling. Nothing to guess at.
Team & Naming

HAI — a name that came from someone new to this space entirely

I led the empathy mapping, introduced the "glass box, not black box" principle, and sketched the concept live during the 20-minute window — but I didn't do it alone. I worked alongside a teammate who'd never been interviewed by a voice AI before that morning. His outside view didn't just add polish — he questioned assumptions I made in real time, contributed several of his own feature ideas, and it was his idea to name the product Humantic AI — a wink at "Agentic," built around the idea that the whole concept centered humans, not just AI capability. We won with that name.

Why I renamed it to "Hello, AI" for this write-up

For this write-up, I've renamed it HAI: Hello, AI — a decision I made afterward, on reflection. "Humantic AI" is clever once you know the wordplay behind it, but it needs that explanation to land; without it, it reads as a typo of "humanistic," not a deliberate idea. "Hello, AI" doesn't need footnotes — it's instantly legible, and it does real work for the concept itself: it's literally the first thing a transparent, human-facing AI interviewer would say to you, which ties straight back to the "glass box" principle the whole idea is built on. This is a piece meant to be read cold, by someone with zero context on the room or the joke — clarity earns its keep here more than cleverness does.

DS
Danny Sukdeo
Software Development Specialist
Danny didn't just name the product. Coming at the brief with no prior context on AI interviewing tools, he pushed back on several of my early feature ideas, added his own to the sketch, and it was that back-and-forth that led him to suggest "Humantic AI" for the pitch — the name we actually won with.
Straightened close-up of the pink sketch board showing the HAI wireframes and glass box quadrant

The actual board from the 20-minute sprint — sketched live, presented as-is.

The Concept — Part 1

Features built around trust & transparency

🤝 Setting Expectations
01 · Upfront, in plain language

Candidates are told what to expect and how their data is used, before anything starts — no hidden consent checkboxes.

03 · Silence as opportunity

A visible "Pause & Think" control means 30 seconds of silence reads as thinking, not failure.

📊 Candidate Signals
02 · Self-Reported Mood

Candidates flag their own comfort level, live, so the AI reads their actual state instead of guessing from silence.

05 · Sentiment shown live

Real-time nudges — "slow down," "be concise" — instead of letting nerves build silently.

🎛️ Choice & Control
04 · Record & send to candidate

Candidates can opt into their own copy of the recording, sent instantly and paired with feedback later.

06 · Applicant's choice

Self-view is a toggle, not a default — one of the only controls that's fully the candidate's.

HAI — INTERVIEW IN PROGRESS
SELF-VIEW: ON You
Your comfort level
Self-reported · private to you
CalmComfortableOverwhelmed
⏸ Pause & Think Respond Now →
The Concept — Part 2

Features built for confidence & access

🎯 Confidence Before It Starts
07 · Practice sessions
  • Same logic as a psychometric warm-up
  • Nothing counts until the real thing
  • Builds comfort before it matters
08 · Customization, not choice
  • Adjust pacing & intensity only
  • Never who's asking the questions
  • Boundary kept to avoid reintroducing bias
🌐 Access & Clarity
09 · Repeat / re-iterate
  • Rephrase or example, on request
  • Not just a replay of the same audio
10 · Transcription
  • Audio alone isn't always enough
  • Covers accent variation & international candidates
⏱️ Pacing & Feedback
11 · Status bar
  • Introduction / Technical / Behavioral shown as progress
  • Neither party watches the clock
12 · Pre/post-interview feedback
  • Quick calibration question, before starting
  • "How was that for you?" — feeds the product, not a survey
HAI — PRACTICE ROUND
Before we begin — a quick practice round
Nothing here counts toward your interview. Get comfortable first.
✓ Introduction
Technical
Behavioral
🎧 Repeat Question 📝 Show Transcript Start Practice →
The Result

First place — scored on problem depth, fitness, originality, and delivery

Four teams, one shared brief, twenty minutes on the clock. HAI won on the strength of the "glass box" framing and the density of candidate-first details packed into a single sketch.

The team celebrating with the trophy after presenting HAI
Meghana Gautam at the UX Camp Amsterdam banner
Full UX Camp Amsterdam 2026 group photo, 4 July 2026
What Stayed With Me

Winning wasn't the end of it. The harder questions came after.

Twenty minutes is enough to sketch a concept. It's not enough to interrogate whether the AI underneath it can be trusted to be fair. That's what I kept coming back to in the weeks after.

🗣️
Accent & dialect coverage
  • Needs data spanning most English accents & dialects
  • Regional, non-native, code-switched
  • Risk: fumbles candidates from certain backgrounds
🎭
Tone assessment is unproven
  • How is tone actually being read?
  • Varies hugely by person & culture
  • Needs better, or licensed, training data
🎲
LLMs are non-deterministic
  • Same question, different answer each time
  • Different judgment risk per candidate
  • Are two candidates even graded the same way?
⏱️
Right question, right time?
  • Being "in the script" ≠ well-timed
  • Timing & relevance aren't guaranteed
🔬 A study I'd want to run: one fixed candidate script, run through Claude, Gemini, and other models as interviewers. Compare what each asks, when, and how each judges identical answers. Convergence = a stable category. Divergence = proof it's just a proxy for whichever model got licensed.
Where This Sits

The category already exists. The trust problem is exactly where I focused.

🏢 HireVue — scale, not depth
  • Biggest name — AI video interviews in 40+ languages
  • Already has practice sessions
  • Candidates still call it impersonal — the "shallow" gap
hirevue.com · HireVue Review 2026
📝 Metaview — after the call
  • Focuses on notes & summaries, post-interview
  • Doesn't touch what happens during
  • HAI's live mood/transparency ideas fill that gap
metaview.ai, 2026
⚖️ Bias is real
  • Measurable gender bias in AI voice interviewers
  • Argues for visible sentiment, not a hidden score
CHI 2025 Extended Abstracts, ACM
📉 Accuracy gaps, self-reported
  • 19% of orgs admit missing qualified candidates
  • Echoes the accent & tone concerns raised earlier
Fairness in AI-Driven Recruitment, arXiv 2405.19699
⚖️ This won't be optional much longer. EU AI Act classifies hiring AI as "high-risk" — enforcement from 2 Aug 2026, fines up to €15M or 3% of global revenue. The "glass box" instinct is about to become a legal requirement.
Official EU AI Act guidance · 2026 Enforcement Guide
What This Taught Me

A 20-minute sprint is a stress test for judgment, not knowledge

⚡ The Sprint Instinct
  • Brief's data treated as ground truth — no re-research
  • Empathy map as compass, not a literature review
  • One held-to principle: glass box, not black box
🔬 What Deeper Research Confirmed
  • Practice sessions, visible sentiment, data retention — still the hard problems
  • Same features the post-event questions kept circling back to
  • Instincts held up. Defensibility needs the deeper work.

That's HAI.

Sketched in 20 minutes. Still on my mind a week later. Thanks to UX Camp Amsterdam and the judges who scored it 1st place.

Appendix

The full reasoning — trust & transparency, in detail

01
Setting expectations upfront
The idea was to tell candidates upfront — before the interview even begins — exactly what the interview would look like, and how their data would be used and stored, rather than burying it in a consent checkbox nobody reads. If a candidate is about to talk to an AI for the first time, they shouldn't have to wonder what happens to the recording after they hang up, or what to do if something goes wrong.
02
Self-Reported Mood Indicator
The idea was a mood indicator candidates control themselves — flagging their own comfort level, from calm to overwhelmed, as the interview moved forward. Since everyone experiences pressure differently, a single AI-inferred read guessed from pauses risks being wrong for any individual candidate; a self-reported signal keeps the data honest, calibrated against what the candidate actually says instead of what the AI assumes from silence.
03
Silence as opportunity, not failure
The idea was a visible "pause and think" control the candidate could activate, so that 30 seconds of silence reads as deliberate thinking — not as the AI quietly scoring it as hesitation or a wrong answer.
04
Record & send interview to candidate
The idea was to ask candidates upfront whether they want their own copy of the recording, and share it with them instantly if they do — and later, once results are out, pair the decision with the actual recording as feedback, not just a scorecard.
Flagged as a wild thought — businesses may resist this at mid-to-senior level, but it could be genuinely useful for junior and entry-level candidates still learning how to interview.
05
Sentiment shown to candidate
Candidates are often nervous from the very first question — whether it's their first interview out of college or a big-name company intimidating someone experienced. The idea was small, real-time nudges between question and answer — "slow down," or "be more concise, there's more to cover" — instead of letting that nervousness compound silently for the rest of the interview.
06
Applicant's choice (self-view)
The brief named self-view as a required design element, and the idea was to make it the candidate's choice, not a default — letting them turn their own camera preview on or off during the interview. Watching yourself on screen while also being watched adds a second layer of self-consciousness on top of the interview itself; in a conversation with only one human in the room, that's one of the few controls that belongs to them.
Appendix

The full reasoning — confidence & access, in detail

07
Practice sessions
The same warm-up logic as a psychometric test or a game's practice round — before anything counts.
08
Customization, not choice of interviewer
The idea was letting candidates adjust pacing and intensity — not who's asking the questions. Someone who processes information more slowly, or gets thrown by a rapid-fire tone, shouldn't be assessed on something that has nothing to do with the job. The boundary mattered: letting candidates pick an interviewer's voice, energy, or persona would reintroduce the same bias AI interviews are supposed to reduce, so that line was deliberately not crossed.
09
Repeat / re-iterate the question
On request, with the option to rephrase or give an example — not just replay the same audio.
10
Transcription when not understood
Audio alone isn't always enough — especially under interview pressure, with accent variation, or for international candidates.
11
Status bar — what, and how much is left
Sections like introduction, technical, and behavioral shown as progress — so neither party is watching the clock.
12
Pre- and post-interview feedback
The idea was to have the AI itself ask a couple of quick questions — before starting, and again once it's done — instead of routing that feedback into a separate survey most candidates would skip. A pre-interview question like "have you done an AI interview before?" lets the system calibrate on the spot — a first-timer might get a bit more reassurance or context than someone who's done this five times. A post-interview "how was that for you?" captures the candidate's actual experience while it's still fresh, feeding back into the product instead of disappearing into a survey nobody fills out.
Use ← → arrow keys to navigate