First and foremost, you're a builder. You think in systems, you ship production code, and you care deeply about what actually makes it into the hands of users. You're not waiting for a spec to land in your lap. You're looking at the product, the design system, and the way the team works, and you're finding the leverage points that make everything better.
This role is about multiplying. You'll work alongside a design engineer already on the team, and together you'll own the bridge between design intent and shipped experience across our core product. You'll build and evolve the design system in code, raise the quality bar for UI that ships, and create the tooling and workflows that help the entire design and engineering org move faster. When you see something slow or broken in how we work, you'll redesign it. When the design system has gaps, you'll fill them with production-ready components. When there's a better way to prototype, test, or ship, you'll find it and champion it.
This role reports into Design, not Engineering. That's intentional. We believe the person responsible for UI quality, interaction polish, and design system integrity should be embedded in the team that sets the craft bar, not downstream from it. You'll have the opportunity to help shape what design engineering becomes at Luxury Presence as the function grows.
Design system, across Figma and code. You'll own the integrity of the design system across both surfaces. In code, that means the React components, tokens, and patterns that engineers actually use to build. In Figma, it means ensuring the design system library stays in sync with what's in production, making design-level tweaks as the system evolves, and partnering with product designers to evolve the system over time. You're comfortable in Figma and can make design decisions there, especially at the system level. You'll close the gap between design specs and production reality, and you'll make that gap smaller over time.
UI quality across the product. You'll be the person who cares about the last 10%: transitions, micro-interactions, responsive behavior, loading states, edge case UI, accessibility. When something ships, you'll make sure it meets the bar.
Tooling and ways of working. You'll look at how the design and engineering teams collaborate, prototype, and ship, and you'll build tools and processes that make it better. Internal tooling, prototyping workflows, component documentation, dev environment improvements. If it makes the team faster or the product better, it's in your scope.
Production-ready code. You're capable of shipping production-ready code. Whether that's components in the design system, UI improvements in the product, or internal tooling, the work you do is built to the standard of something that goes in front of users.
You'll partner closely with product designers, but the collaboration model isn't a handoff. Designers own the problem space, user insight, and experience strategy. You own making that strategy real at the highest level of craft. Sometimes that means pairing early to explore what's feasible. Sometimes that means taking a rough direction and running with it. The relationship is collaborative, not sequential.
You'll also work directly with frontend and full-stack engineers. You'll establish patterns and components they can build on, review UI implementations, and raise the standard for what "done" looks like in the codebase.