AI talent
Generative AI Experience Designer
Designs the interaction for systems that are uncertain: how confidence, correction, hand-off and refusal are shown to a user.
The role
What the job actually is.
Conventional interface design assumes the system knows the answer. This role designs for the case where it might not. That means showing confidence without implying precision, making correction cheap enough that people actually do it, designing the hand-off to a human so it does not read as failure, and handling refusal so a user understands why rather than concluding the product is broken. The work is mostly about the wrong answer, which is why a portfolio full of polished happy paths tells you very little.
What we screen for
The questions that separate the field.
Asked by someone who has built the thing, and designed to catch this role's specific failure rather than to confirm a general impression.
- Whether they design for the wrong answer, not only the right one. Ask to see the error and refusal states.
- Whether they have tested with users who distrust the system, rather than with enthusiasts.
- How they represent uncertainty without either hiding it or making it unusable.
- What the correction path costs a user, in clicks and in dignity.
The common mis-hire
The one you have probably already made.
A visual designer producing a chat window. The surface is attractive, every state assumes success, and the first time the system is wrong the user has nowhere to go.
In the estate
Where this role works, and what we screen it against.
The layers this family works at, lit. These are the tools we screen against. Naming one says we can test for it, not that we have delivered on it.
Evaluation and observability
Spans every layer. Without it a system is shipped on impressions.
Experience and delivery
Copilots and agents inside a business process, and the interaction design that makes an uncertain system usable.
- Salesforce Agentforce
Orchestration and agents
Where an agent's steps, tools and state are defined, and where its failures are caught before a user meets them.
Models
The models themselves, and the platforms an enterprise hosts them through.
Data and grounding
What the model is grounded in, and the integration work that gets enterprise data to where it can reach it.
Systems you already run
The seven platform desks Yallo staffs. Almost no AI work is greenfield; it lands here.
Governance, risk and safety
Spans every layer. Named as what governance roles are screened against; what any of them obliges is your counsel's call.
- EU AI Act
- ISO/IEC 42001
- ISO/IEC 23894
- NIST AI Risk Management Framework
- OWASP Top 10 for LLM Applications
Seniority
What changes between mid, senior and lead.
The grade is a description of what the person owns, not a band. Rates come with the shortlist.
- Mid
- Designs flows and states against an established interaction pattern for uncertainty.
- Senior
- Sets the interaction pattern itself, including confidence, correction and refusal, and validates it with sceptical users.
- Lead
- Owns the pattern across products so that trust behaves consistently wherever a user meets the system.
In a programme
When this role is needed, and what blocks it.
Needed at design, and needed again once real outputs exist, because the states that matter cannot be designed against imagined answers. The dependency is a working system to react to, so plan for a second pass rather than one hand-off.
Adjacent
The roles this one is confused with.
Ask
Send the brief, get a screened AI Experience Designer shortlist.
Tell us the programme, the stack and the timeline.