Product Engineer

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. What you ship on Monday, real editors use on Tuesday.

One founder has built the entire platform so far. He's now moving to product design and direction, which means the delivery of the product needs an owner. That's the job.

What you'd own

The backlog, end to end. Something breaks or a customer asks for something. You reproduce it, you decide what it actually is, you write the issue, you scope it, you ship it, you verify it in production. Nobody hands you a groomed ticket — you're the one who grooms it.

Concretely, in a normal week:

• Triage what came in over the weekend: bug reports from the agency team, Sentry errors, Featurebase feedback
• Turn vague reports into GitHub issues that someone could actually pick up — including the ones our overnight AI builder picks up while you sleep
• Ship the fixes and the small features yourself
• Review what the AI agents produced overnight and decide what merges
• Tell the founder what you're seeing: which parts of the product keep breaking, and what that means for what we build next

You're not a project manager and you're not a maintenance engineer. You're the person who makes sure the thing keeps moving while the founder is thinking two months ahead.

Our stack

React and TypeScript on the front, Supabase behind it — Postgres with Row Level Security on everything. Around that: Stripe, React Native, a desktop app, and AI tooling woven through the workflow.

You don't need all of it. Solid React + TypeScript and real comfort with SQL gets you most of the way; we'll go through the rest on a call.

Who we're looking for

• 3–6 years building and shipping web applications with React and TypeScript
• You debug well. Given a vague report — "the kanban card doesn't update sometimes" — you can get from that to a reproduction and a root cause without someone holding your hand. This is the single most important thing on this list
• Comfortable in SQL: you've read a query plan, you know what an index and a transaction do
• You write clearly. A good issue is half the work here, and a bad one costs everyone a day
• You've supported something in production and know what it feels like when a customer is blocked
• Strong written English, and you say something before you're asked. Silence is the only thing that doesn't work on a team this small
• Real overlap with European hours (CET ±2)
• You work with AI tools and read every line before it ships. Our agents open PRs; we need your judgment on top, not your typing speed
• Bonus: Supabase, Stripe, Sentry, or React Native in production

We care far more about how you think and ship than about your CV or where you live.

Why this is a good job and not a chore

You'll see every part of a real SaaS in the first month — billing, auth, multi-tenancy, mobile, the lot. You'll have direct access to the founder and to the agency team that uses the product all day, so you find out within hours whether what you shipped was right. And the ceiling isn't fixed: as the team grows, the person who knows every corner of this codebase is the person who leads it.

The setup

• Contractor, full-time (32–40h/week), invoicing monthly in EUR
• Compensation depending on experience, reviewed after six months
• Fully remote, flexible hours around a European overlap window

How to apply

Apply through the form — it takes about ten minutes.

One of the questions asks you to describe a bug you found hard: what the report said, how you tracked down the cause, and what it turned out to be. That is the question we actually read, so give it the time. Another question asks which word the job post tells you to start with. It's deliverable.

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