Product Owner (AI) Corp Messanger

Vibe Product Owner

🏢 Company overview

Unimatch Lab is an AI-driven venture studio and fund based in Silicon Valley. We build a horizontal portfolio of AI products: hardware and smart devices, kid-tech, personalized AI assistants around health and productivity, proprietary AI media, and other verticals.

In parallel we run R&D on local and distributed data centers and distributed computing, and on foundational layers: memory layer, RAM/VRAM, orchestration, and AI software for infrastructure and compute.

How we choose what to build: we ship products we use and care about first - in daily life and at work. The primary driver is impact, not commercial upside alone: quality of life, financial wellbeing, health, productivity, safety, freedom from routine - products that help people stay calm and clear-headed. Commercial results matter, but they are not the only frame for early decisions.

Our goal is a top-50 AI company by combined asset valuation by 2032. We work on OKRs: speed, transparency, ownership, measurable outcomes. Culture is corporate entrepreneurship inside the team and traction in numbers, not process for its own sake.

The studio acts as strategic partner and investor: capital, network, technology, capabilities, PR/GR. The format is closer to partnership with clear agreements than classic employment.

🎯 Position summary

The Product Owner in Venture Tribe leads a product direction in the studio portfolio: sets meaning, priorities, and metrics, and owns outcomes from hypothesis through launch.

You are the integration point between discovery, product, and engineering delivery: from idea validation and PoC through production, first revenue, and channel scale. Product, UX, and delivery pace are your calls; the founder sets frame and gates; the Founding Engineer owns deep engineering. Discovery, PoC, unit economics, interface, and release coordination sit with you.

We validate hypotheses quickly in separate domain areas. At the start one strong stream matters; more parallel directions can follow as the work matures. PoC cadence target: up to 14-21 days from idea to a testable prototype with economics modeled. Early UX is on you without a separate designer. After hypothesis confirmation you pair with a Founding Engineer and take the product to production.

After release the focus shifts to demand, revenue, sustainable unit economics, and channels - with transparent metrics and a plan for the next stage. As a direction matures, funding rounds and a possible path to co-founder or CEO are discussed under separate agreements.

✅ Key responsibilities

• Run discovery: market, ICP, value proposition, competitive context, customer interviews
• Model unit economics before major build: monetization model, key assumptions, viability metrics
• Make go/no-go on launch with the founder based on evidence, not intuition
• Build proof-of-concept and clickable prototypes on tight timelines: interface, scenarios, basic analytics - yourself, without a separate designer
• Deliver UI/UX at production-demo level: mobile and web, iterations from feedback to acceptable quality
• Use vibe-coding for solo execution where backend is not required
• Take a confirmed hypothesis to production with a Founding Engineer: stack, data model, deploy, stable release
• Own the product-infra layer: serverless/edge, data model, LLM pipeline; deep backend, security, and scaling stay with engineering
• Align product and engineering delivery: APIs, integrations, release plan, readiness criteria
• Launch initial distribution in collabaratiom with Head of Marketing: landing, copy, demo, pitch materials
• After release, drive the direction toward confirmed demand: first revenue, unit economics, channel scale
• Hand off to CBO with ready commercial artifacts when the product is ready
• Design agent pipelines for the product function: research, reporting, backlog, competitive intel
• Set standards portable across portfolio products
• Run one stream at the start and grow throughput to several parallel directions; keep transparent status, blockers, and next ship dates

💪 Required qualifications

• 5+ years in product: led directions or products end to end with accountability for outcomes, metrics, and economics
• Corporate workplace domain experience: shipped or led B2B products in team messaging, internal communications, corporate systems, or workplace collaboration - with concrete cases for interview review
• Full 0->1 cycle in production: discovery, PoC, launch, first users, demand validation, and unit economics - with concrete cases for interview review
• Product ownership in a tight format: priorities, metrics, readiness criteria, engineering delivery coordination - your accountability
• Strong hands-on UX: you build prototypes and interfaces yourself; interface quality is part of your craft
• Unit economics and data literacy: hypothesis economics, metrics, cohorts, SQL; decisions grounded in numbers
• Vibe-coding in practice: PoC and working prototypes where backend is not required; Cursor, Claude Code, or equivalents
• Growth experience with measurable outcomes: performance, organic, or content - influence on acquisition, activation, or revenue
• Packaging and stakeholder defense: pitch deck, narrative, answers on economics, metrics, and roadmap - at investor-dialogue level
• Mature communication: transparent status, initiative, dialogue with founder, engineers, and external stakeholders
• English B2+

⭐ Preferred qualifications

• ex-engineer to product path: you understand technical trade-offs and work with engineers in shared language
• Experience running several products in parallel without quality or decision-speed drop

🛠️ Technology stack

• IDE and vibe-coding: Cursor, Claude Code, Windsurf, Codex CLI
• Prototypes: v0, Bolt.new, Lovable, Replit Agent, Claude Artifacts
• AI: Claude, 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

📊 Success metrics

• Cycle time: discovery -> clickable prototype <= 72 hours; prototype -> MVP <= 7 days; MVP -> production-ready <= 21 days (p50)
• Portfolio: 1 stream at start -> 2 -> 3 parallel directions as capacity grows
• Ship velocity: 0->1 products shipped per quarter
• UI/UX quality: no critical issues on production-demo
• Customer satisfaction: NPS on launched products, quarter-over-quarter growth
• Iterations to acceptance: <= 2
• Agent layer: share of product routine closed by agents; portability of agents across products
• Stakeholder trust: issues raised proactively, not through escalation

👥 Team structure

Founder / CEO - strategy.

Head of Marketing/Sales - commercial motion and pitch.

Head of People and Operations - OKRs and blockers.

Founding Engineer - architecture on product partnerships.

In your product you own roadmap, priorities, UX, and product-infra; backend and core infra sync with the Founding Engineer. Goals and timelines are agreed upfront; then autonomy without micromanagement.