Salesforce Product Designer Case Interview — Designing a Cross‑Cloud Customer 360 Console

You will run a live, collaborative case that mirrors how Salesforce designs enterprise workflows across Sales Cloud, Service Cloud, Slack, Tableau, and Platform. Prompt: Design a unified Account Health & Engagement Console inside Lightning Experience that helps an Account Executive and a Service Agent coordinate on at‑risk accounts, take action in Slack, and surface Einstein insights—while remaining configurable by an Admin via App Builder. Structure (typical at Salesforce): • 5 min: Brief + clarify scope, identify primary personas (AE, Service Agent, Admin), secondary (Customer Success Manager, End Customer). • 10 min: Problem framing and success metrics (e.g., reduce time to insight, improve first‑contact resolution, increase collaborative actions taken in Slack). • 20 min: Solution exploration and low‑fidelity wireframes (navigation in Lightning console, dense data tables, record highlights, timeline, related lists, inline actions, Slack huddles/threads as an embedded panel, Einstein risk score with explainability, quick actions powered by Flow). • 10 min: Systems and constraints (multi‑tenant considerations, role/record/field‑level security, sharing rules, auditability, large data volumes; admin customization via Lightning App Builder, Dynamic Forms, and design tokens; SLDS components and responsiveness; accessibility WCAG 2.2 AA; localization and theming). • 10 min: Rollout and measurement (adoption plan, change management for admins, guardrails for ethical AI, V2MOM‑style alignment to values: Trust, Customer Success, Innovation, Equality, Sustainability). • 5 min: Q&A and critique. What interviewers look for (based on real Salesforce loops): enterprise product thinking that balances default opinions with admin configurability; fluency with SLDS patterns and high‑information‑density UIs; comfort mapping user flows to platform primitives (objects/records/permissions, Flows, reports/dashboards, Slack actions); clear tradeoffs and prioritization under time pressure; accessibility and inclusivity baked into interaction decisions; strong collaboration signals—talking through assumptions, inviting feedback, and tying design choices to measurable outcomes.