UX/UI Designer (12 month contract)

About the role

Token Tamer Wanted: You're not just comfortable using design systems. You know how to rebuild them. You understand how a single component decision can ripple across dozens of pages, multiple brands, future launches, and developer workflows. You've worked with tokens, variables, component properties, variants, libraries, and documentation - and you know the difference between a tidy Figma file and a system that can actually scale. In this 12-month contract, you'll help restructure our existing single-brand design system into a scalable multi-brand architecture. That means separating shared platform foundations from brand-specific expression, building a net-new brand library, refactoring components, and supporting the prototype of a new e-commerce experience using the system you've helped create. If that sounds like the kind of challenge you love, you might have what it takes to be our new UX/UI Designer. What You Bring to the Table... A portfolio that proves you can build systems, not just screens: When we look at your work, we'll see more than polished pages. We'll see structured components, thoughtful patterns, scalable libraries, and design decisions that make life easier for everyone who uses the system after you. And your portfolio shows that you understand how tokens, variables, components, documentation, and governance all work together. Beautiful screens are great. But for this role, we need to see the architecture behind them. A serious design systems mindset: You don't just use design systems. You think in systems. Core foundations. Brand libraries. Experience libraries. Primitive tokens. Semantic tokens. Component-level decisions. Naming conventions. Library relationships. Governance. Versioning. This is the stuff that makes your brain light up. You understand how to separate what should be shared from what should stay brand-specific. You can spot unnecessary duplication, messy component logic, and brittle structures before they become expensive problems. Advanced Figma instincts: Figma is deep in your muscle memory. You're highly comfortable with components, variants, component properties, nested instances, auto-layout, variables, tokens, and responsive behaviour. You know how to structure files so other designers can find what they need, understand how things work, and contribute without creating chaos. And when you create something, it is clean, logical, documented, and built to be used. Strong component architecture skills: You know the difference between a component that looks good once and a component that holds up across brands, states, edge cases, and real-world use. You think carefully about variants, properties, states, flexibility, and maintainability. You know when to standardize and when to allow variation. You understand how one overcomplicated component can slow a team down - and how one underbuilt component can create a mess six months later. Token and variable experience: You've built or worked deeply with token architecture using Figma variables. You understand primitive, semantic, and component-level tokens. You know how color, typography, spacing, radius, elevation, and other foundations need to be structured so multiple brands can operate from one shared platform without everything becoming a tangled mess. For this role, this is not a nice-to-have. It matters. Experience refactoring existing systems: You don't need a perfectly blank canvas to do great work.You can audit an existing component ecosystem, classify what belongs where, separate brand-specific assets from shared foundations, and migrate work without introducing a trail of inconsistencies behind you. Design fundamentals you can feel: Typography, hierarchy, alignment, spacing, layout, visual balance - this is second nature to you. You care about polish. You care about consistency. You care about the small details that make a system feel professional instead of patched together. An understanding of e-commerce: You understand the basic building blocks of e-commerce experiences: product pages, offers, promotions, bundles, pricing hierarchy, content modules, CTAs, comparison sections, and purchase paths. You don't need to be a conversion copywriter or a CRO strategist. But you do need to understand that the system you build will be used by teams creating real customer-facing commerce experiences - not theoretical design exercises. Front-end awareness: You do not need to be a full-time developer. But you do need to understand how front-end code works well enough to collaborate intelligently with developers. You're comfortable with HTML and CSS. You can reason about component-based frameworks like React. You understand why certain design decisions are easy to implement, why others create headaches, and why handoff details matter. If you've worked with Storybook, Chromatic, or a similar component/UI-kit environment, even better. Clear documentation and handoff habits : You do not leave people guessing. Your component specs a

Your Match

How well this role fits your profile.

Company Intel

What employees say

Worked at AlgaeCal? Share your experience