How DOR POs Work
At DOR, a PO is the person who defines the problem, prototypes it directly, runs the experiment, and proves outcomes.
- Contribute flexibly across Creator · Community · Growth, aligned with company priorities.
- Define sharp problems from quantitative data and qualitative VOC, and set priorities.
- Build prototypes directly with AI coding tools to validate hypotheses before engineering picks it up.
- Make simple designs, UX wireframes, and landing/experiment pages yourself to iterate fast.
- Run 1–2 week hypothesis-build-learn cycles to adjust product direction.
- Move real user metrics as one team with engineers, designers, and growth managers.
AI Vibe Coding
POs use Cursor, Claude Code, and other AI coding tools to ship prototypes and real features directly. You validate hypotheses with code, not documents, and you contribute across the whole product, not just inside one lane. We don't expect engineer-level coding. Getting your own hypothesis running with AI tools is enough. We hold the higher bar on problem definition, judgment, and obsession with users.
- Prototype hypotheses in code yourself before handing anything to engineering.
- Build the experiment pages, landings, internal tools, and automations you need, with AI alongside.
What You'll Ship
Based on your strengths and our priorities, you may own PO responsibility in one or more of these product areas at a time.
Creator · Gameplay into content
- Design the full creator flow from auto-record · highlight detection · clip generation · editing · sharing.
- Aim for "great captures without any setup, satisfying clips without manual editing."
- Move metrics like clip count, edit completion rate, creation→share conversion.
Community · Where gamers connect
- Design feed · profile · follow · notification · reaction core experiences.
- Frame retention, engagement, and relationship-formation flows as concrete problems.
- Lead experiments that move retention, participation, and network effect metrics.
Growth · Acquisition and scale
- Design and optimize acquisition · onboarding · retention · virality · partnership funnels.
- Plan growth experiments and run small hypotheses fast to learn.
- Build growth loops combining channels, content, and product hooks.
How Our Team Works
- DOR builds what customers want, not what the CEO wants.
- 1–2 week iterations: define, hypothesize, execute, measure, learn.
- Decisions grounded in data and user voice, not hunches.
- POs define problems and create outcomes.
- No squads, one team across the whole product.
- Build fast, validate fast, change direction fast.
Requirements
- 2+ years in product development or related roles
- Shipped and iterated at least one product directly
- Problem definition. You narrow a problem using both quantitative data and VOC, and turn it into a testable hypothesis
- Judgment. You decide what not to build as deliberately as what to build, and explain the reasoning so it becomes a standard the team can use
- Obsession with users. You watch where people hesitate and dig until that friction is gone
- Moves products forward fast by collaborating across functions
- Willing to push your own hypothesis into a working prototype with AI tools. We look for the instinct to try it yourself, not engineering skill
Nice to Have
- Open to working in San Francisco, CA (U.S. work is optional)
- Hands-on with at least one of: video/UGC/creator tools, social/community, growth/funnels
- Made wireframes and landing pages yourself
- Proven experimentation with numeric results
- Shipped web/app/desktop products you planned yourself
- Drove a specific problem end-to-end into real impact
- Fluent in English
- Gamer or deep understanding of gamer behavior
You'll Fit Well If
- You solve problems, not organize features
- You want to be a PO who builds and validates with AI tools
- You prefer fast validation and learning over perfect plans
- You see both detailed UX and broad direction
- You read the numbers and user context together
- You want to build products people keep coming back to
In Your Resume, Tell Us
- Problem · Hypothesis · Action · Result for products you've worked on
- Which metrics you used to judge success or failure
- Concrete prototypes or features you built/validated with AI tools
- Problems you defined and solved yourself from data and VOC
- Your motivation, thinking, action, learning, outcomes, more than a job list
Hiring Process
01
Application
Resume and portfolio submission
02
Role / Culture Interview
Values and working-style alignment
03
Task Interview
If needed, with reference checks
04
Offer
Compensation and stock options, then onboarding
Apply Now
Ask via Coffee Chat