AI Onboarding Experience Designer
An AI Onboarding Experience Designer crafts the first-touch journeys that turn confused first-time users into confident power user…
Skill Guide
Conversational UX design and prompt template architecture is the systematic design of user interaction flows, dialogue logic, and reusable prompt structures to guide AI systems toward predictable, high-quality, and contextually appropriate outputs.
Scenario
A retail company needs a bot to answer 10 common questions about return policy, shipping, and sizing, escalating to a human for complex issues.
Scenario
Create a conversational flow for booking a hotel room that requires collecting dates, location, room type, and guest details, with slot-filling and confirmation.
Scenario
A fintech's support bot has a 30% escalation rate and low customer satisfaction. Users report the bot misunderstands context in multi-turn conversations about transaction disputes.
Used for visually mapping conversation flows, prototyping dialog trees, and collaborating on UX before writing a single prompt. Essential for stakeholder alignment.
Frameworks for building, logging, and managing complex prompt templates and multi-step interactions. LangChain is key for chaining prompts and integrating tools; PromptLayer for versioning and testing.
Tools for systematic prompt testing, evaluation, and monitoring in production. Humanloop allows prompt iteration with user feedback; Evals for benchmarking against test cases.
Answer Strategy
Use the STAR method (Situation, Task, Action, Result). Focus on the architectural breakdown: system prompt for core persona, separate sub-prompt templates for each core task (booking, modification, refund), a shared context/state manager to track slots (PNR, dates), and a router logic to select the correct template. Emphasize using few-shot examples for each airline's policy constraint and a fallback to human escalation.
Answer Strategy
This tests systems thinking and cross-functional collaboration. The answer should cover: 1. UX: Transparency (how users are informed memory is stored), control (how to view/delete memory), and potential for implicit bias reinforcement. 2. Technical: Memory scope (session vs. persistent), storage architecture (vector DB vs. key-value), and prompt injection risks from stored memories. 3. Compliance: Data privacy regulations (GDPR/CCPA) and audit trails. You would propose a phased rollout starting with short-term, session-based memory.
1 career found
Try a different search term.