Our Company
At Teradata, we believe that people thrive when empowered with better information. Teradata Autonomous Knowledge Platform activates enterprise intelligence by unifying data, knowledge and business context to achieve tangible outcomes. With Teradata, organizations can provide agents with full context for impact when it matters. Our solution lets businesses connect and scale on premises, in the cloud, or through a hybrid approach. Teradata delivers real business value with AI.

What You’ll Do
Experience Platform Strategy & Roadmap

Define the vision, principles, and multi-quarter roadmap for the experience platform, including the design system, interaction standards, and enablement model.

Determine when a request should become a platform standard versus a local experiment, with a clear path for graduation into shared system patterns.

Maintain a prioritized backlog of foundational patterns, AI-native primitives, and design-to-code capabilities.

Benchmark competitor AI studios and agentic platforms to ensure the system remains world-class.

AI-Native Interaction Standards

Architect and standardize interface patterns for Tera and other agentic workflows.

Define patterns for:

Agent-to-human handoffs

Confirmations and override controls

Streaming states

Latency handling

Progress feedback across short and long “thinking” periods

Explainability and transparency patterns, including what happened, why it happened, what changed, and what the user should do next

Trust and safety guardrails, including uncertainty cues, reversible actions, and safe defaults

Feedback loops that improve agent quality through structured user feedback and telemetry hooks

Experience Contracts & Governance

Create and maintain experience contracts that define:

Required behaviors of shared patterns

Usage rules, including when to use a pattern, when not to use it,



and acceptable variation boundaries

GA-readiness expectations for system-dependent experiences, including quality bars, accessibility, localization, and instrumentation

Run lightweight governance processes to prevent experience fragmentation across the product suite.

Guide patterns through proposal, review, ratification, release, and adoption tracking.

Conduct design system reviews on in-flight projects to protect UX integrity and ensure alignment with shared standards.

Pattern Authorship & Source of Truth

Own living guidelines and documentation that are clear, concise, and decision-oriented, explaining both the “why” and the “how. ”

Define and maintain standard artifacts such as:

Pattern specifications

Do/don’t usage rules

Interaction states

Accessibility requirements

Implementation notes

Maintain semantic consistency across the suite, including naming conventions, terminology, and interaction language.

Design-to-Code Pipeline & Tooling Operations

Ensure Figma libraries are scalable, organized, and synchronized with code repositories.

Partner with engineering to deliver production-grade components, including APIs, props, and tokens, that faithfully represent design intent.

Own versioning, publishing cycles, and release communications for design system updates.

Minimize breaking changes and manage migrations with clear rollout plans.

Developer Experience Enablement

Treat the design system as a product, with developers as primary users.





Optimize component packages and APIs for fast assembly and predictable behavior.

Provide templates, starter kits, and reference implementations for common AI workflows.

Improve discoverability through usage guidance, examples, searchable documentation, and copy/paste patterns.

Evangelism, Education & Adoption

Lead office hours, training sessions, and internal coaching for product managers and engineers.

Create demos and “what’s possible” tours that show teams how to build complex AI Studio experiences using system components.

Drive adoption through enablement rather than policing by removing friction, clarifying guidance, and making the right path the easiest one.

Scope & Operating Boundaries
To avoid ambiguity, this role does not own:

Feature roadmaps for individual products or vertical teams

Product-specific business logic, backend services, or domain rules

Revenue targets, customer commitments, or release dates for vertical products

Day-to-day delivery execution for individual product pods

This role influences these areas by defining shared patterns, standards, and contracts, but does not replace vertical product management ownership.

Key Artifacts & Outcomes
You will produce and maintain:

Experience platform roadmap and prioritized backlog

Pattern specifications, including states, rules, accessibility guidance, and content guidance

Experience contracts and parity rules

Component readiness criteria and release notes

Reference implementations, starter kits, and demos

Adoption dashboards and system health reports

Success Measures
Success in this role will be measured through:

Adoption and reuse of design system components versus custom overrides

Pattern reuse across pods and reduction of one-off implementations

...
#J-18808-Ljbffr

📌 Staff Product Experience & Design System Architect (Centro-Norte)
🏢 Teradata
📍 Centro-Norte