You'll build across the entire product surface, from mobile capture to editing pipelines to the orchestration layer connecting it all.
This is not a narrow IC role. In addition to shipping core product, you will co-own engineering execution and delivery reliability. You are accountable for predictable weekly output, early risk visibility, and zero surprise misses across the dev team.
You will
- Expect to ship multi-agent orchestration, FFmpeg stitching, Remotion video timelines, and LLM/VLM integrations in the same week, with clear scope, release notes, and quality bars.
- Build across the entire product: web app (Next.js), mobile app (React Native), admin tools, pricing flows, and dashboards.
- Ship real features fast: multi-agent orchestration, FFmpeg video stitching, Remotion pipelines, and LLM/VLM integrations.
- Architect systems that don't fall over when we hit one million users in a day.
- Work directly with founders on product decisions, UX flows, and technical direction — co-owning delivery commitments, tradeoffs, and execution outcomes.
- Own and evolve the core dev team execution loop — scoping, CI/CD, shipping rituals, and delivery commitments — so the team moves fast without surprises or quality regressions.
- Dive into anything that moves the product forward — UI, backend, infra, orchestration, computer vision, ML, or devops.
- Maintain delivery predictability: if something is at risk of slipping, it is flagged early with options. There are no surprise misses. Ever.
- Own problems end-to-end without waiting for permission or detailed instructions.
You're right if you
- Work fast, care deeply, and take extreme ownership.
- Bias toward action and learning — you figure things out quickly and hate waiting.
- Can move between frontend, backend, and light infrastructure without drama.
- Velocity > experience - Even if you have 1–3 years experience, you are perfect if you’re hungry and have shipped AI products.
- Communicate clearly and proactively — flagging risks early, providing options, and keeping founders unblocked at all times.
- Want to build a rocketship in person with the founders, not a cozy nine-to-five.
You're wrong if you
- Need hand-holding.
- Want big-company structure.
- Move slowly or over-intellectualize instead of shipping.
- See yourself as just a backend dev or just frontend.
- Are uncomfortable being accountable for team-level delivery, not just your own code.
Why builders join
- Meaningful ownership and early-exercise equity.
- Real responsibility for shipping, delivery reliability, and team velocity — not just writing code.
- In-person build hub in San Francisco with the full team.
- Be part of a team that has a track record of success.