- Location
- Copenhagen, Hovedstaden, Denmark
- Workplace
- Onsite
- Type
- Full-time
- Department
- Product
- Seniority
- Mid
- Source
- Recruitee
Description
Design for the people in the tiny chairs
At Famly, we build software that takes admin off the plates of early-years educators, so they can spend their time where it matters - with the children. And we make it easier for over a million parents to stay close to their child's day, even while they're at work.
We're looking for a design system builder to join the design team - responsible for the design system, prototyping tools and all other infrastructure with the goal of driving consistency and coherence across the entire product.
About Famly
We’re on a mission to stop admin stealing the joy of working with young children. We do that with our platform, the world’s first proactive assistant for educators and staff that handles admin for them so they can get back to what they love. And we do it with our content (like The Tiny Chair Podcast), reminding educators of the joy and meaning that got them into working with children in the first place.
About the role
You live where design and code meet. With a small team, you'll own Famly's design system: the components, patterns, and documentation that product teams (and increasingly, AI agents) build on every day.
The team's job is coherence. Every feature and every domain should feel like it came from the same place. You'll give builders what they need to design and build to our standards, and keep the conversation going so the system keeps getting better.
You'll bring deep technical knowledge of design systems, and you'll care just as much about how the product feels to the people using it.
The team is based in our Copenhagen office, but we are open to you being based somewhere else.
What you'll be doing
Build production-quality React and TypeScript components for Famly's design system.
Design component APIs that are hard to misuse, and version them so upgrades don't break product teams.
Write the documentation that makes those components self-serve, so a new engineer or an AI agent can pick one up and use it correctly without asking anyone.
Keep the system trustworthy: tests, visual regression, and a release process people don't dread.
Learn Famly's frontend deeply enough to know where a pattern lives, who depends on it, and what breaks if it changes.
Audit and evolve the components we already have, for consistency, accessibility, and reuse across the product.
Own the code side of the design standard with a small team, so design intent survives the trip into production.
Push back when a design won't hold up in code - too many states, no empty case, a pattern that already exists - and say what you'd do instead.
Work with PMs, designers, and engineers across product teams, and bring them ideas before they ask.