Technical practice
How would you design an entry point for a task involving multiple AI agents?
What to coverRole basis: The posting names multi-agent entry points. Suggested answer: Explain how users would understand each agent’s role, the available actions, and when control passes between agents or returns to the user.
How would you design an agentic workflow that crosses product domains?
What to coverRole basis: The role includes cross-domain surfaces for technical and product teams. Suggested answer: Map where context must carry across interfaces, then discuss the trade-off between a consistent interaction pattern and domain-specific needs.
When should an AI experience show its reasoning and provenance?
What to coverRole basis: The posting calls for reasoning that is visible and trustworthy, and for provenance to be surfaced. Suggested answer: Distinguish information needed to make a decision from distracting detail, and show how users could inspect the basis for an output.
How would you decide where an agent needs guardrails or human approval?
What to coverRole basis: Designing trust, autonomy, guardrails and human-in-the-loop moments is an explicit responsibility. Suggested answer: Describe how the consequences of an action affect the level of autonomy, and how a user can review, intervene or stop it.
What would you put in a rapid prototype of an agentic concept?
What to coverRole basis: The designer builds fast demonstrations for internal feedback, with advanced Figma proficiency required and code prototyping listed as a plus. Suggested answer: Identify the interaction assumptions to test, explain the prototype fidelity you would choose, and distinguish demonstrated behaviour from functionality not yet built.
How would you map a complex workflow before designing its screens?
What to coverRole basis: The posting expects high-quality journey maps and flows, with attention to more than one user or interface. Suggested answer: Show how you would represent actors, handoffs and decision points, then use the map to identify gaps an interface alone might conceal.
How would you assess whether an interaction pattern can work across teams?
What to coverRole basis: Patterns must hold up across multiple teams and use cases; design-system contribution is a plus. Suggested answer: Compare common needs with meaningful exceptions, and explain what evidence would justify a shared pattern versus a local variation.
How would you check an agentic flow against accessibility needs?
What to coverRole basis: Working knowledge of WCAG is required. Suggested answer: Discuss how you would review keyboard access, focus, status updates and understandable controls in a changing flow, without assuming that a visually clear prototype is accessible.
How would you design while the underlying model or platform is still changing?
What to coverRole basis: The posting explicitly describes designing against unfinished models or platforms. Suggested answer: Separate stable user needs from uncertain technical behaviour, make assumptions visible in the design, and identify what to revisit as capabilities become clearer.
How would you choose between an established UX approach and inventing a new one?
What to coverRole basis: The role calls for learning from industry approaches while developing methods where precedents do not fit. Suggested answer: Explain how you would evaluate an existing pattern against the task and trust needs, then test a new approach before treating it as reusable.
Behavioural practice
Tell me about a time you brought structure to an ambiguous design problem.
What to coverRole basis: Comfort with ambiguity is central to this role. Suggested answer: Use a real situation, the structure you introduced and the resulting decision or learning; distinguish what was known from what remained uncertain.
Describe a time you shaped an early idea with product and engineering partners.
What to coverRole basis: The designer works with both groups to turn early ideas into product direction. Suggested answer: Give the situation, your specific actions to reconcile needs or constraints, and the resulting direction or outcome.
Tell me about a time feedback changed a prototype or design direction.
What to coverRole basis: Fast demonstrations are intended to give internal teams something concrete to react to. Suggested answer: Identify the situation, what you showed, how you acted on the feedback and what changed as a result.
Describe a time you tested whether a design could serve more than one team.
What to coverRole basis: The posting emphasizes systems-level patterns beyond an initial use case. Suggested answer: Explain the original situation, how you investigated other teams’ needs and the result, including any limits you found.
Tell me about a consequential design decision you had to explain to others.
What to coverRole basis: The posting values explaining why a decision was made, not just presenting final screens. Suggested answer: Set out the situation, the trade-offs and evidence you communicated, and the resulting decision or response.