Senior UX Designer

Senior UX Designer

Design Systems · Embedded AI · Remote / LatAm (Colombia, Brazil)

Remote/LatAm · 5+ Yrs Exp. · English Required · Full-Time

THE ROLE

We’re looking for a Senior UX Designer who builds and scales the design system for enterprise products. You will own the components and patterns that teams use to modernize legacy tools, inside platforms those users already work in every day, and within new applications as they are built. Every pattern you build shows up in hundreds of screens.

WHAT YOU’LL ACTUALLY DO

• Audit and map the existing UI — inventory components, patterns and inconsistencies across the client platform, and ground the system in how operators actually work.
• Build and maintain the component library — Figma components with variants, states and documented usage, matched one-to-one with coded components.
• Own the design token architecture — color, type, spacing, elevation and motion tokens, structured for theming and multi-brand use inside the client’s UI framework.
• Define reusable AI interaction patterns — recommendation cards with reasons, confidence indicators, drill-into-logic flows and structured feedback capture, built once and used everywhere.
• Systematize alerts, scenarios and comparisons — ranked notifications, what-if tools and comparison views as system components, not one-off screens.
• Build accessibility into the system — WCAG 2.2 AA at the component level, so every team that uses the system inherits it.
• Write the documentation and run governance — usage guidelines, a contribution model, versioning and release notes that keep designers and engineers aligned.
• Partner with fullstack engineers — keep Figma and Storybook in sync, review implementations and ship in the same sprint. You sit in the standup.
• Measure system adoption — component coverage, detached-instance rates, design-to-code drift and time-to-ship for new features. A design system is a product, and you track it like one.

THE TECHNICAL BAR

You will be expected to execute hands-on technical work from day one. The requirements below reflect the actual skills needed to deliver outcomes for enterprise clients.

Must-Haves

• Design Systems — 5+ years in product design, including 2+ years building or leading a design system
• Tokens & Theming — Designed token architectures (primitive, semantic, component) and multi-brand or white-label theming
• Enterprise UI — Extended a design system inside an existing enterprise platform, starting from a UI audit and user research
• Accessibility — Builds WCAG 2.2 AA compliance into components; comfortable running audits and assistive-tech testing
• Prototyping — Advanced Figma (variables, variants, auto layout, libraries); usability testing on real users
• Front-End Literacy — Reads HTML/CSS and React components; works in Storybook alongside engineers
• Stakeholder Comms — Presents system decisions to senior leaders and product teams; drives adoption with evidence

CORE TECH STACK

• Design — Figma · FigJam · Tokens Studio
• Prototyping — Figma · ProtoPie · Framer
• Research — Dovetail · UserTesting · Lookback · EnjoyHQ
• Documentation — Zeroheight · Supernova · Storybook Docs
• Collaboration — Notion · Miro · Linear · Jira
• Engineering-adjacent — HTML/CSS · React · Storybook · Style Dictionary · Chromatic

NICE TO HAVE

• Took a design system from zero to adoption across multiple product teams
• Data viz expertise — chart components and visualization guidelines inside a design system
• Conversational AI / chatbot patterns (a smaller part of this role, but useful)
• Design-to-code tooling: Figma Code Connect, token pipelines, Style Dictionary
• Published talks or writing on design systems

WORKING CONTEXT

This is an active, client-embedded delivery engagement. You will run discovery and ship production designs throughout.

• All team members operate within client timezone hours. LatAm candidates are strongly preferred.
• Your work is embedded in an existing enterprise platform. We extend, we don’t replace. That’s a constraint and a craft.

THE HUMAN BAR

Craft is necessary. Systems thinking is the differentiator.

The designers who thrive here notice the same button built five different ways across a product and want to fix it for good. They can sit in a user’s chair, watch how operators actually work, and turn what they learn into patterns every team can reuse.

• Adoption-first — you measure a design system by how many teams use it, not by how complete the Figma file looks.
• Constraint-driven — you build inside existing platforms, frameworks and brand languages, and make those constraints serve users.
• Delivery ownership — you audit, design, document, ship and maintain. You don’t hand off a library and walk away.