Vibe Product Owner

🏢 About the company Unimatch Lab - an AI-driven venture studio and fund from Silicon Valley. We are building a horizontal portfolio of AI products: hardware and smart devices, kid-tech, personalized AI assistants around health and productivity, our own AI-media and other verticals. In parallel, we conduct R&D around local and distributed data centers and distributed computing, as well as fundamental layers: memory layer, RAM/VRAM, orchestration, AI-software for infrastructure and computing. How we choose what to build: we make products that we ourselves are, first and foremost, users and fans of: we regularly use them in life and at work. The primary driver is not commercial gain, but impact: quality of life, financial state, health, productivity, safety, freedom from routine - products that help maintain a calm, clear mind. Commercial results are important, but not as the sole framework for initial decisions. The goal is to be among the top 50 AI companies by total asset valuation by 2032. We work with OKR logic: speed, transparency, ownership, measurable results. The culture is about corporate entrepreneurship within the team and traction by numbers, not process for process's sake. The studio acts as a strategic partner and investor: finance, network, technology, expertise, PR/GR. The format is closer to a partnership with clear agreements than to classic employment.

🎯 Role overview Vibe Product Owner - a product leader with the mindset of a founder within the portfolio: you define the meaning of the direction, priorities and metrics, and lead delivery as if it were your own startup. Your area - the full 0→1 cycle from discovery to production-ready; the pace target - 14-21 days for the "idea - working product" cycle. In tools - vibe-coding as solo execution where appropriate, and designing the agent layer of the product function. Product ownership, UI/UX and coordination of engineering delivery remain with you, without diluting responsibility for the result. After launching to production, the focus shifts to validating demand, first revenue, sustainable unit economics and scaling channels - with transparent metrics and a plan for the next stage. As the direction matures, raising a round and a possible transition to a co-founder and CEO role are discussed - within the framework of separate agreements and if goals and horizons align. The scope of responsibility can grow: from one product under full control - to several parallel streams; the level of influence and compensation is tied to the depth of product strategy across the entire scope. We expect a mature leader with full startup cycle experience; a background as an ex-engineer -> product, strong practice in UX and growth - performance, organic, content, plus project presentation and dialogue with investors, fits well. Independent initiative and full context understanding of the direction are needed.

✅ What you will do

Discovery and problem validation

• Market and competitor research via AI agents (Exa, Perplexity, Deep Research).
• User interviews and problem validation (Granola, Fireflies, Dovetail).
• Formulating hypothesis, ICP, value proposition.
• Making go/no-go decision to launch product work - jointly with Founder.

Prototype, design, code - end-to-end execution cycle

• Clickable prototype within tight deadlines from hypothesis (v0, Bolt.new, Lovable, Claude Artifacts).
• UI/UX: mobile and web interfaces, incl. pixel-perfect, without a separate full-time designer (Figma and AI plugins, Framer, Mobbin for inspiration).
• Production-ready code via vibe-coding (Cursor, Claude Code, Windsurf, Codex CLI).
• Tech stack in use: React Native / Expo (mobile), Next.js / React (web), Supabase / Neon (data), Vercel / Railway (deploy).
• Design review of your own work: iterations based on feedback.

Architecture - jointly with Founding Engineer

• Product-infra layer on the role side: choice of stack, serverless/edge, data model, LLM-pipeline, MCP integrations.
• Deep backend, security, scaling - area of Founding Engineer; joint deep-dive on complex issues.
• Joint architecture reviews before production deployment.
• Decision rule: final on product-infra - product owner; jointly - changes affecting shared inter-product infrastructure.

Marketing website and primary distribution

• Landing page as part of the delivery (Framer, Webflow, v0, Lovable).
• Copywriting, visuals, analytics from day one (PostHog / Plausible).
• Preparing pitch deck for external communication (Gamma, Tome).
• Sales enablement: demo scripts, use case materials - handover to CBO.

Agent orchestration layer (product function)

• Designing own agent pipelines, not just using ready-made scenarios.
• MCP, multi-step workflows, memory layer, function calling (LangGraph, OpenAI Agents SDK, Temporal - as needed).
• Agents for typical flows: weekly summary, demo materials, backlog analytics, competitive research, code review, feedback clustering.
• Standards for transferring agents between portfolio products.
• The share of product routine covered by agents is one of the maturity markers.

Parallel work on several directions

• Managing from one to three product streams in parallel - as the area of responsibility grows and internal gates are passed.
• Personal operating system: Cursor, Claude Projects, MCP, Linear/Notion for context switching.
• Priority on speed of decisions and delivery - default is ship.

Communication with stakeholders

• Mature, transparent communication with the client, Founder, team.
• Weekly syncs: status, blockers, dates of next deliveries.
• Brief written summaries after key decisions - high signal-to-noise.
• Early raising of risks and problems - before escalation.

💪 Must have

• 2+ products 0->1 over the past year, brought by you to production; live links.
• Vibe-coding: Cursor, Claude Code, Windsurf; at least one of v0 / Bolt.new / Lovable / Replit Agent in production.
• Strong mobile and web design awareness; interface examples.
• Full-stack: React Native / Expo, Next.js / React; Supabase / Neon; serverless / edge; deploy and monitoring.
• Product-infra: stack, data model, LLM pipeline; deep infra / security with support from Founding Engineer.
• Agents: MCP, multi-step workflows, memory, function calling; willingness to show your own "operational" stack.
• Depth in one of the domains: Hardware / KidsTech / EdTech / HealthTech / MarTech / PropTech / B2C SaaS.
• Mature communication with stakeholders.
• English B2+.

⭐ Nice to have

• Completed a full cycle in a company: from idea to round and beyond.
• Background in backend / full-stack / frontend, then PM - understanding complex production systems.
• Combo: strong engineering base plus marketing (Meta / Google, organic, content).
• Pitching and fundraising.
• Venture studio, multi-product, early-stage startups.
• Corporate background is possible if there are vivid 0->1 cases and go-to-market outside corporate frameworks.
• Deck, outbound, first sales; SQL, PostHog / Amplitude, cohorts, unit economics; public activity; hardware / on-device ML.

🛠️ Stack

• IDE and vibe-coding: Cursor, Claude Code, Windsurf, Codex CLI
• Prototypes: v0, Bolt.new, Lovable, Replit Agent, Claude Artifacts
• Mobile / web: React Native, Expo, SwiftUI (basics), Next.js, React, Tailwind, Framer Motion
• Backend / infra: Supabase, Neon, Vercel, Railway, Fly, edge, serverless
• AI: Claude / ChatGPT Projects, MCP, Deep Research, LangGraph, OpenAI Agents SDK, vector DBs (Pinecone, pgvector), generative design (Midjourney / Ideogram / Flux)
• Marketing: Meta Ads, Google Ads, content, funnels
• Design refs: Figma, Mobbin, Dribbble
• Site / GTM: Framer, Webflow, Gamma, Tome, Clay, Apollo, PostHog, Plausible
• Orchestration: Linear, Notion, Slack, Granola / Fireflies

📊 How we measure success

• Q1: movement idea -> PMF; PMF and First Revenue metrics (agreed before start).
• Speed (p50): discovery -> clickable prototype up to 12 hrs; prototype -> MVP up to 7 days; MVP -> production-ready up to 21 days.
• Throughput 0->1 per quarter: at least 2 (Core Circle), at least 3 (Venture Lead) - according to the agreed model.
• Quality: no critical failures in production demos; growth in CSAT / NPS; iterations to acceptance no more than 2.
• Agents: share of routine via agents (target thresholds per stage); transferability of agents between products.
• Trust: 360 and quarterly; transparency on risks.

👥 Team

• Founder / CEO - strategy.
• Head of Marketing/Sales - commerce and pitch.
• Head of People & Operations - OKRs and blockers.
• Founding Engineer - architecture on parity basis. In your product, you own the roadmap, priorities, UX and product-infra; for backend and infra - synchronization with Founding Engineer. We agree on goals and deadlines, then - autonomy without micromanagement.