Lead product direction
● Write clear PRDs, user stories, and acceptance criteria that engineers can build from confidently.
● Own and prioritize the backlog for your initiatives.
Decide what gets built, what waits, and what success looks like before work begins.
● Use product analytics, creator interviews, and SQL queries to ground prioritization in evidence.
● Run weekly sprint planning and retros, keeping the team focused on outcomes that ship to users.
Partner on technical decisions
● Work alongside the lead backend engineer as a technical peer.
Join architecture and API design discussions to keep technical direction and product direction aligned.
● Review PRs where product context matters.
Speak up when scope drifts or when a shortcut might affect creators downstream.
● Translate fuzzy business needs into clear, actionable technical tasks — so the team spends less time clarifying and more time building.
Build when it helps
● Prototype and validate ideas before they enter the engineering queue.● Ship small features end-to-end when it's faster than handing off.
● Use AI tools (Claude, Cursor, Copilot) as part of your daily workflow — for PRD drafting, code analysis, prototyping, and moving faster overall.
You'll likely have:
● 5+ years shipping production SaaS, AI, or B2C products end-to-end. You've seen features go from idea to real impact, not just from ticket to deploy.
● 2+ years owning product decisions or leading technical delivery. You've written PRDs that got built. You've been comfortable saying "let's cut this" when it was the right call.
● Solid experience with Laravel + one modern JS framework (Vue preferred; React or Next.jsalso great). You can read and write production code confidently, even if you're not the primary builder anymore.
● Strong product instincts. When you look at a user workflow, you can see which step to improve first.
● Comfort with data. You read dashboards, define KPIs, and write your own SQL when you have a question.
● Strong written English. Spoken English good enough for direct collaboration with the CTO and team.
● Real fluency with AI tools. You've made them a genuine part of how you work day-to-day.
Nice to have:
● Background in creator tools, gaming, streaming platforms, short-form video, or AI products. If you've built for Twitch/YouTube/Kick/TikTok creators, we'd love to chat.
● Familiarity with MySQL, MongoDB, Linux, basic infrastructure, and CI/CD.
● Experience improving activation or retention on a SaaS product.
● You're a gamer or stream viewer yourself. You get why a 12-second clip with the right music hits differently than a 30-second one.
Why this role exists
Our engineering team is strong and ships quickly. What we're looking to add is someone who can sharpen the connection between what we build, what creators actually do with it, and what moves the business.
You'll be the person who decides what to build based on user behavior and impact — and then makes sure it lands well with real creators, not just in production.
This isn't a pure engineering role with PM tasks added on. It's a product-minded technical leader who codes when it helps, prototypes when it's faster than explaining, and leads through clarity rather than control.
Why choose us:
● Real product, real users. Creators rely on us every day. What you build ships to a live audience right away.
● AI at the core, not bolted on. Our product wouldn't exist without modern AI. You'll work with a team that takes AI seriously — both as product and as a way of working.
● Small team, large surface area. You'll have visible ownership from week one. No layers, no long approval chains.
● Direct line to the CTO. Decisions happen quickly. If you've felt slowed down by approval loops elsewhere, you'll feel the difference here.