Lead Design Technologist, Design Systems - Remote

External candidates: In order for your application to be correctly processed please sign-in before you apply

Internal candidates: Please go to Workday and click "Find Jobs" link under Career

Thank you for considering opportunities with us!

Job Title

Lead Design Technologist, Design Systems - Remote

Requisition Number

R8030 Lead Design Technologist, Design Systems - Remote (Open)

Location

Arizona - Home Teleworkers

Additional Locations

Alabama - Home Teleworkers, Alabama - Home Teleworkers, Arkansas - Home Teleworkers, California - Home Teleworkers, Colorado - Home Teleworkers, Connecticut - Home Teleworkers, Delaware - Home Teleworker, District of Columbia - Home Teleworkers, Florida - Home Teleworkers, Georgia - Home Teleworkers, Idaho - Home Teleworkers, Illinois - Home Teleworkers, Indiana - Home Teleworkers, Iowa - Home Teleworkers, Kansas - Home Teleworker, Kentucky - Home Teleworkers, Louisiana - Home Teleworkers, Maine Home Teleworkers, Maryland - Home Teleworkers, Massachusetts - Home Teleworkers, Michigan - Home Teleworkers, Minnesota - Home Teleworkers, Mississippi - Home Teleworker, Missouri - Home Teleworker, Montana - Home Teleworkers {+ 21 more}

Job Information

CSAA Insurance Group (CSAA IG), a AAA insurer, is one of the leading personal lines property and casualty insurance groups in the United States. Here, every employee shapes our mission. We build innovative, human-centered solutions that help AAA members prevent, prepare for, and recover from life's uncertainties. You will join a collaborative, inclusive culture where your strengths have room to grow and your ideas can drive real impact. Step into a role where you can contribute to our shared success through meaningful work.

We are actively hiring for a Lead Design Technologist, Design Systems - Remote!

Your Role: The Lead Design Systems Technologist is a senior individual contributor responsible for building and evolving the technical foundation that enables consistent, high-quality digital and AI experiences across CSAA. This role translates UX standards, interaction patterns, and future-state system designs into scalable, reusable technical assets such as components, design tokens, APIs, shared packages, and implementation patterns that can be used by both development teams and AI-enabled systems. Working closely with UX, CX, Engineering, Architecture, and Workflow and Systems Design, this person connects design intent with technical implementation, helping ensure solutions can be reused across applications, channels, workflows, and AI experiences rather than rebuilt each time.

Your Work:

Lead the Technical Structure of the Enterprise Design System

• •Define and maintain the technical structure of the design system, including how components, tokens, patterns, shared packages, reusable capabilities, and reference implementations are organized and relate to one another.
• •Partner with UX Design to translate approved patterns, templates, and design decisions into scalable structures in code, including component APIs, design tokens, shared packages, and implementation standards.
• •Maintain the connection between design tooling and code so approved UX definitions can be implemented accurately and consistently in production.
• •Define how design-system assets are structured, composed, governed, and versioned in code so they can be reused consistently across products and applications.
• •Partner with UX and platform teams to resolve how CSAA's design standards and technical system assets translate into third-party platforms such as Pega and Guidewire, where CSAA does not control the underlying design system. Define what can be reused directly, what requires platform-specific implementation, and where documented extensions or exceptions are needed.
• •Define clear ways to contribute, update, deprecate, and version shared system assets without disrupting the teams that depend on them.
• •Set clear criteria for what should become a shared system asset versus what should remain specific to one product, platform, or solution.

Extend the Design System to AI

• •Define and maintain the technical design-system foundations needed for AI models and AI agents, including:
• •Foundations - shared system prompts, voice and tone standards, refusal and escalation behavior, and safety policies that downstream AI experiences inherit.
• •Capabilities - reusable skills, tool and function definitions, Model Context Protocol (MCP) servers, and approved retrieval and context sources.
• •Interfaces & contracts - standards for how AI agents exchange context, call tools and services, return structured outputs, handle permissions, and interact with other systems and AI agents.
• •Patterns - reusable prompt templates, reasoning and orchestration patterns for handoffs, delegation, human review, and other common workflows.
• •Reference implementations - example AI agents and starter structures that teams can adapt instead of building from scratch.
• •Evaluation - shared evaluation suites that help teams check whether AI behavior stays within expected quality and performance ranges as the system changes.
• •Observability - tracing and instrumentation that make it possible to understand what an AI agent did, which tools and context it used, and where problems occurred.
• •Make system assets easy for both people and AI agents to discover and understand, with clear descriptions of what each asset does and when to use it.
• •Define guardrails and governance for how teams use approved AI capabilities, in partnership with AI governance and the AI Council.
• •Keep one coherent system across internal and customer-facing experiences, whether the end user is a person or an AI agent.

Enable Design-to-Development Readiness

• •Put the tooling and technical connections between design and code in place before development begins, including component connection tooling, design and component MCP servers, shared packages, and token distribution.
• •Decide how tightly approved design definitions and code need to be connected for each component set rather than applying the same level of integration everywhere.
• •Stay engaged during delivery to trace issues to the right source - the design definition, base component code, connection tooling, shared packages, tokens, or platform constraints.
• •Help UX and engineering teams understand how design decisions flow into the technical system, and close gaps that lead teams to bypass shared assets or create avoidable rework.
• •Make the system easier to adopt, including reducing the time it takes a new team to get from setup to first successful use.

Partner with Engineering and Architecture on Realization

• •Define the structure and technical requirements for shared system assets, then partner with Engineering to build and operate them and with Architecture to determine how they are integrated and placed within the enterprise technology ecosystem. This role is not expected to own the full production code lifecycle or enterprise architecture decisions.
• •Work with Engineering and Architecture on feasibility, dependencies, sequencing, and estimates for system-level work.
• •Clarify ownership across shared design-system assets, enterprise architecture, and production application code, and make those responsibilities explicit to partner teams.
• •Build prototypes and proofs of concept when that is the fastest way to test a structural decision or reduce risk.
• •Stay connected through delivery so the implementation reflects the approved UX intent, the design system's technical standards, and agreed enterprise architecture decisions.

Drive Adoption and Self-Sufficiency

• •Work across the team's engagement models - stewarded, consultative, and self-service - based on the complexity and needs of the work.
• •Build the system, documentation, and tooling so more teams can use it independently over time, and treat that shift toward self-service as a key measure of success.
• •Create documentation,