Product Manager - AI-Native Development, Czech Republic

Hello, we are Meiro! 🚀

Welcome to Meiro – where data meets human connection! Founded in Singapore, we’ve expanded into a global family throughout Southeast Asia, Australia, New Zealand, Europe, and the Middle East. Our mission is to help businesses leverage customer data securely and seamlessly.

In today’s AI world, we focus on helping brands forge genuine connections with their customers through personalized experiences, while prioritizing data security and privacy.

Our diverse team of over 50 professionals spans the globe, from our Singapore headquarters to tech hubs in Brno and Prague. Over the past five years, we’ve partnered with top clients, including leading banks, retail chains, e-commerce platforms, and innovative travel companies.

Our devs use AI tools that let them implement features in hours instead of weeks. This broke traditional PM rhythms.

Weekly planning? Too slow - three features are built before we meet. Daily standups? Devs need decisions in minutes, not tomorrow. Sprint reviews? We're validating continuously, not bi-weekly.

We're inventing what PM looks like at AI speed. You'll help us discover it.

💡 What We Know

Response time is minutes. When a dev needs clarity, they need it now. In Slack, jumping on a 5-min call if needed. Not "let's schedule a meeting."
Decisions live in Linear, coordination in Slack. Product decisions get documented in Linear where the work lives. Slack is for quick coordination.
Async-first, calls when ambiguity is expensive. Default to async (Slack threads, Linear comments). But when something has multiple valid interpretations, we pull people into a 5-minute call rather than let everyone build different solutions.

Example: Token storage/refresh spec was clear on intent, unclear on implementation approach. Three valid options. We pulled 3 devs + product into a 5-min call, aligned on Postgres-backed approach, documented in Linear. Saved days of divergent work.

Feature-level planning, irregular cadence. No story points or sprints. We plan at feature granularity. Some take 2 days, some take 3 weeks. The variance is real.

🤔 What We're Still Figuring Out

The exact daily rhythm and coordination patterns.
How to articulate intent that's clear enough for AI execution.
When to involve more people versus let someone run.
What success metrics actually matter.

You'll help us figure this out.

☀️ What you'll actually do

Rapid clarification: Devs ping you. You answer immediately or recognize "this needs a quick call." You iterate toward clarity as building reveals gaps. Sometimes pairing with devs in Claude/Cursor. Document decisions in Linear.
Continuous validation: Verify implementations solve the actual problem - daily, not bi-weekly. Catch specs that were clear but incomplete, implementations that match the spec but miss intent.
Coordination judgment: Recognize when work needs one person running versus multiple people aligning. When to resolve async versus pull people into a quick call.
Variance management: Distinguish "taking longer because we're learning" from "stuck and need to change approach." Make real-time priority calls.

🎯 What you need

Must have:

Comfortable operating at minutes response time
Can articulate intent clearly enough for productive iteration
Recognize when ambiguity is expensive versus fine to let someone run
Async-first but comfortable jumping on quick calls
Okay with variance (some work converges fast, some explores for weeks)

Strong plus:

Used AI code generation tools (Claude, Cursor, Copilot, etc.)
Technical enough to read code and understand APIs
Experience where building reveals requirements (not everything knowable upfront)

🔴 Why this might not work for you

Love long-term roadmapping and predictable sprint cadences? This will frustrate you. The work is continuous iteration with varying timelines. If you need quarterly plans and velocity metrics to feel productive, this isn't it.

🟢 Why this might be perfect for you

You love rapid iteration - multiple refinements per day. You're good at pattern matching when to coordinate versus let someone run. You want to validate at machine speed. And you're comfortable with honest uncertainty: we're inventing this together.

🚀 What's in store for you?

Team of ~20 engineers shipping with AI tools
Response time: minutes
Location: Remote-first, ideally near Prague/ Brno timezone
Reporting to our CEO Pavel cooperating closely with duo Jirka & Jirka
Be part of a global startup. The opportunity to become a key player in our team, shaping internal projects for companies in APAC and EMEA;
Although we mostly work remotely, we love getting together from time to time - for team on-sites, team lunches, or just to catch up outside of work;
Education budget for personal development.
Good financial compensation based on your skills and experience.