Product Designer

We're building the operating system for video production agencies — one platform replacing the Notion + Slack + Drive + spreadsheet stack these teams run on today. Bootstrapped, founded in Belgium, and we run our own production agency on the product, so the people using what you design are down the hall or one message away.

The product has been designed by the founder who builds it. That got us a coherent system — tokens, a component library, a design contract the whole app follows — and it is now the thing holding us back, because he cannot both decide what the product does and draw every screen. We want a designer one or two days a week, every week, to take the second half.

What you'd own

The surfaces where design decides the outcome. Not a redesign, and not decoration on top of finished work. The parts of the product where a confused screen costs a customer: first-run and onboarding, the client portal, the planner, and the mobile app.

In a normal week that looks like:

• One flow, taken from "this is awkward" to something we can build — screens, states, the empty and error cases nobody enjoys drawing
• A pass over what shipped since you were last here, telling us where it drifted from the system
• Extending the design system rather than working around it: a new pattern gets added deliberately, or it gets refused
• Sitting in on a call with an agency using the product, because the fastest way to find the bad screen is to watch someone hit it

You will not be handed a backlog of tickets. You will be handed a problem, the people who have it, and the freedom to decide what the answer looks like.

What we already have

• A design system with rules, not just a component folder: named type scale, semantic colour tokens that theme themselves, one separation device per edge, motion tokens. It is written down and CI enforces it
• A live gallery of every primitive, so you can see the whole vocabulary in one page before you draw anything
• Real users, today — our own agency team plus the studios on the platform, all reachable the same day
• Engineers who read design carefully. Handover is a conversation, not a Figma link thrown over a wall

Who we're looking for

• You have designed software that shipped, and you can point at it. Not concepts — things people used and complained about
• You design the unglamorous states. Empty, loading, error, permission-denied, the list with 400 rows. This is most of the work in a real product and it is where most portfolios go quiet
• You work inside an existing system without either ignoring it or being paralysed by it, and you can say clearly when a rule should change
• You write. A design that needs you present to be understood does not survive a week where you're not here
• Comfortable being the only designer. You will not have a design team to review with; you will have engineers, users and your own judgment
• Bonus: you design in code, or read it well enough to know what a change costs

Whether you call yourself a product designer, a UX designer or a design engineer matters less to us than the work you can point at.

Why part-time, and why it works

We don't have a full-time design job yet, and pretending otherwise would waste your time. What we do have is a steady stream of decisions that are worth a designer's attention, week after week — enough for one or two days, indefinitely, with the same person. That's better for both of us than a project that ends and a relationship that has to restart.

If it grows into more, we will both be able to see it coming.

The setup

• Part-time contractor, one or two days a week, ongoing, invoicing monthly in EUR
• You name your day rate in the form. We'd rather hear your number than post a range you'd have to argue with
• Remote, with enough overlap with European hours that we can talk on the same day

How to apply

Apply through the form — it takes about ten minutes.

One question asks you to take something you designed and describe what you got wrong the first time. That is the question we actually read. A portfolio shows us the version that worked; that answer shows us how you got there.

Rather ask something first? Mail jobs@contentmaker.space. A sharp question is a fine way to apply.