UX/UI Designer 12 month contract - name

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.