We're not hiring yet. Join the talent network.

The honest posture

Why isn't there a job listed?

Three things to know before you decide whether to give us your email.

• Why nothing is posted

  DSP Watch is one founder and a closed-beta cohort. We're not hiring because we haven't yet earned the right to — the next 2-3 hires will be funded by paying customers, not a fundraise. Posting a role we can't yet pay for would waste your time.

• What changes when we open roles

  When the customer base supports a second engineer, we will post a public role with a band and a written rubric. The talent-network signup below is how we tell you first. No mass blast to every inbox we have — only people who selected a matching role get the note.

• What we will not do

  No unpaid trials. No 4-hour take-homes. No 6-round loops. No equity in lieu of salary. Hiring will look like: a 30-minute call with the founder, a 90-minute paid scoped project, references, offer. That's the whole loop.

Likely first roles

What will we hire for first?

Not a commitment, not a posting — a directional read so you can decide whether your background is in scope.

• Senior fullstack engineer (TypeScript, Postgres, Cloudflare)

  Likely the first hire. Comfortable across Astro / Workers / Supabase, opinionated about correctness, and happy to write SQL by hand. The job is half product engineering, half ops on the takedown pipeline.

• Rights operations specialist

  Experience inside an indie label, distributor or rights management agency. You've filed §512(c)(3) takedowns; you know what a good evidence bundle looks like; you can spot a bad finding from across the room. The job is part product, part customer success.

• Product designer (part-time / contract)

  Comfortable shipping a Tailwind-driven design system with one engineer reviewing the PR. You care about information density, you can defend a layout decision in writing, you don't need a design ops team to be productive.

• Something else you think we need

  Tell us. We're a small team and we don't pretend to know every gap. If the role you'd want here doesn't appear above, write the pitch in the form below.

How we work

What's it like inside DSP Watch?

• Remote-first, AU-friendly hours

  DSP Watch runs on Australian business hours (UTC+10). We don't require you to be in AU — we do require a working window that overlaps with most of the AU day.

• Written before synchronous

  Decisions land in writing — ADRs in the repo, session logs in shared memory, PR descriptions that explain the trade. Meetings are short, scheduled and follow an agenda.

• Small surface, deep correctness

  We refuse features that don't earn their complexity. The reward for shipping less code is the privilege of being able to reason about every part of the system in one afternoon. You will be expected to push back on scope.