Product Owner

We ship quickly and the surface is already wide: recording, editing, translation, guides, hubs, sharing. The hard part is not ideas. It is choosing, sequencing, and saying no clearly enough that engineering can move.

What you will do

• Own the roadmap with the founders, and keep it honest about the capacity we actually have.
• Turn vague requests into specs an engineer can build from, including the cases meant to fail.
• Talk to customers every week and bring back what they did, not only what they asked for.
• Decide what not to build, and write down why, so the question stays settled.
• Sequence work so each release stands on its own rather than needing the next one to make sense.
• Close the loop after launch. A feature nobody adopted is information, not a finished ticket.
• Keep support, sales and engineering looking at the same list of priorities.

What we look for

• You have shipped software products and can describe something you cut, and why.
• Enough technical depth to argue with engineers usefully and to know when the estimate is the real constraint.
• Clear writing. Most of this job is written.
• Comfort making a call with incomplete information, and revisiting it when the information arrives.
• Willingness to sit with the actual product daily rather than manage it from a board.

Nice to have

• Video, localisation, or developer facing tools.
• Experience being the first product hire.
• Having run customer interviews yourself rather than reading a summary.