Senior Product Designer

We’re looking for a Senior Product Designer, Design Systems to evolve the shared foundations behind our enterprise product experience, including the standards our increasingly agentic products need. You’ll turn recurring experience problems into reusable patterns and codify the intent behind them, helping designers, engineers, and AI-assisted development tools work from the same standards. This systems-and-behavior role spans experience standards, machine-readable specifications, working prototypes, verification, and implementation. You’ll independently own significant system initiatives while partnering with Design Systems leadership and engineering on system strategy, governance, and platform architecture. Responsibilities Key Responsibilities Turn product problems into system standards. Own complex initiatives from problem definition through implementation. Decide what becomes a shared pattern, what stays product-specific, and why. Use accessibility requirements, product usage, adoption, and implementation friction to determine what the system should standardize, change, or retire. Contribute to governance and contribution models that keep those decisions durable. Codify and verify standards humans and agents can use. Help define the experience requirements and standards that should become consumable by AI-assisted development tools. Turn recurring experience decisions, including approval, agent status, recovery, and accessibility requirements, into structured rules, metadata, examples, and tests. Partner with Design Systems leadership and engineering to shape the machine-readable contract and how conformance is evaluated. Establish reusable agentic patterns. Define how delegation works in our products and how the system earns greater autonomy through demonstrated reliability. Design complex, stateful interactions that make oversight, intervention, edge cases, and recovery clear and consistent. Prototype working behavior. Move beyond static screens when behavior is the problem. Prototype interactions, states, transitions, and agentic behaviors at the fidelity needed to make sound decisions. Partner closely with engineers to ensure the intended experience carries through into production. Independently own significant design-system initiatives while partnering with Design Systems leadership and engineering on strategy, governance, platform architecture, and implementation. Use technical fluency in service of experience judgment and verification. Be comfortable prototyping interactive behavior and working with component architecture, structured specifications, and modern frontend constraints. Engineering provides production implementation depth. Success in the first-year means recurring experience problems are solved through reusable standards, product teams choose shared patterns because they are the best path, design intent carries clearly into production, and agentic products share a common vocabulary for delegation, oversight, and recovery. Years of Experience Typically, 5+ years of product design experience, with substantial experience designing or evolving systems used across multiple products or teams. Equivalent evidence of scope and accomplishment matters more than years alone. Education & Certification Requirements Bachelor's degree is required; equivalent evidence of scope, systems judgment, and accomplishment is valued. Required Qualifications (Non-Negotiable) *Highlight or Bold your Top 3 “Must-Haves” from this section Created a system standard, pattern, or capability used by teams beyond your immediate product team. Designed sophisticated interactions across states, edge cases, accessibility, failure, and recovery. Translated design intent into structured specifications, tokens, rules, metadata, or other artifacts that support consistent implementation. Worked extensively with design tokens and understand how they connect design decisions to implementation across a system. Worked closely with engineering from concept through implementation. Portfolio must include one system pattern presented end to end, from the experience problem and alternatives considered through the resulting standard and implementation. Portfolio should clearly show the boundaries between what belonged in the shared system, what remained product-specific, and why. Nice-to-Have Qualifications (Desired but Not Required) Experience with AI, automation, or agentic products. Familiarity with machine-readable design systems standards, metadata, schemas, conformance rules, or verification approaches is valuable, as is familiarity with MCP and AI-assisted developmental tooling. Preferred Industry Experience Experience working in complex enterprise product environments or on design systems serving multiple products and teams. No salary, pay range, or compensation information was provided in the original job description. No equal opportunity statement was provided in the original job description. #J-18808-Ljbffr