About this role
About us Rentman is a B2B SaaS scale-up building a smart, powerful operations management platform to support event and media production teams. Our users plan everything from small shoots to massive festivals in 70+ countries, and they all rely on Rentman to keep their gear, people, and timing perfectly in sync. We’re based in Utrecht (NL) with a second office in Toronto (CA), and our 100+ team members work in a culture that’s open, flat, and inclusive, where curiosity drives us, ownership matters, and everyone has the freedom to challenge ideas and make an impact. Check out our public roadmap to see what’s coming next! Mission of this role Own the code side of Rentman's design system and build it as a versioned product with real consumers. You'll build, test, release, and drive adoption of the Angular component library and token pipeline, turning today's Storybook source of truth into a semver-governed package with release discipline, DTCG-based tokens, and CI gates for visual regression, accessibility, and interaction tests. Working in a two-person team alongside a Design System Designer, you'll make adoption measurable in product code and increasingly legible to AI tooling, so teams build from the system rather than around it and the legacy UI is replaced release by release. What you'll do Our design system is young. The Angular component library and Figma library exist, but the governance model, token pipeline, and adoption strategy are still taking shape. To define those will also be yours to own. Run it like a real product: versioned, with semver, changelogs, and honest deprecations, so teams can upgrade with confidence. Engineer the token pipeline from a DTCG source of truth into code, so one decision about color, spacing, or type lands everywhere it should. Turn today's Storybook addons into CI gates that actually block: visual regression, accessibility as a mandatory check, and interaction tests. Drive code-side adoption. Make it easier to build from the system than around it, and prove it with adoption measured in real production code. Make the system AI-ready: machine-readable component metadata, docs-as-code, and an MCP/AGENTS.md surface so coding agents can build with it as fluently as a new engineer. Pair daily with the Design System Designer: spec handshake on new components, one shared source of truth, joint ownership of the Definition of Done.