AI Product Manager

Job Description :

We're building in a market that hit $47B in 2026 and is on track to hit $107.5B by 2028 and we're not chasing that opportunity from the sidelines.

Our founding team brings marketing expertise from Kotak and Amazon paired with deep AI chops.

We were selected into Google's AI Accelerator program, and we already have paying customers like Kotak and Myntra using the product in production.

Join us early and help build the infrastructure that turns AI marketing adoption (already at 88%) into real, scaled results for customers who are already paying for it, not case studies.

Role Name : Founding Product Manager, Applied AI

Location : Mumbai - Hybrid

Reports to : CTO

WHAT THIS ROLE ACTUALLY IS :

We've built a multi-agent AI system for marketing. It works well out of the box but every client (their data, workflows, brand rules, compliance constraints, output preferences) is different. Generic doesnt ship results. Customised does.

This role is the bridge : you sit between our agent architecture and the clients reality. You understand both deeply, and you make the agents do what each specific client needs them to do.

Youre a PM who knows the spec-to-engineer handoff is where products die. So you dont hand off. You open Claude Code or Codex and ship the change yourself.

WHAT YOU'LL DO :

Day-to-day split : roughly 60% on client work, product judgment, and shaping what to ship - 40% directly in Codex and Claude Code shipping it.

• Own client outcomes end-to-end. From discovery to live deployment, you are the person responsible for whether the agents actually solve the clients problem.

• Translate ambiguity into working systems. Clients dont know what they want until they see it. You probe, prototype, demo, iterate - without waiting for an engineer to be free.

• Customise the agents yourself. Tune prompts, build new agent capabilities, configure workflows, wire up integrations. Codex and Claude Code do the heavy lifting; your product judgment does the steering.

• Diagnose creative problems sharply. When a CMO says this doesnt feel right, you can question intelligently - is it the prompt, the input brief, the brand guidelines themselves, or the clients own confusion? Most PMs nod and forward to engineering. The good ones diagnose first, then fix.

• Feed learnings back to core product. Anything that gets customised 3+ times becomes a platform feature. You decide what graduates.

• Build the playbook. As we scale from 10 to 50 to 100 clients, the customisation patterns you create become the foundation others work from.

WHAT YOU NEED :

• Real product judgment. You can hear we need a dashboard and figure out the actual problem is the marketing director doesnt trust the agents decisions yet. Youve done this before, in a role where the outcome was on you.

• Hands-on technical ability. You dont need a CS degree, but you must be able to read code, write code with AI tools, debug, and ship. If youve never opened Claude Code or Codex and built something real, this role isnt for you. Coding is part of the daily job, not an occasional adventure.

• Comfort with agents as a system. You understand how LLMs fail, why prompts drift, what context engineering means, when to use tools vs. fine-tuning, why eval harnesses matter. If MCP, tool use, and agent harness feel like jargon, this isnt the role.

• Client-facing instincts. Comfortable in a room with a CMO, an enterprise IT head, and a junior brand manager - and you can switch register for each in the same meeting.

• Creative literacy. You dont need to be a designer. You do need to be able to tell the difference between this output is technically broken and this output is technically fine but creatively wrong - and chase the right thread.

• Bias toward shipping. A working hack today beats a clean design next quarter.

YOU'LL THRIVE HERE IF :

• Youre a PM who realised the engineer handoff is where your products die.

• Youve quietly learned to ship in Claude Code or Cursor on the side because you got tired of waiting.

• You want a role where coding ability is upside, not heresy.

• You like marketing as a domain - or youre willing to fall in love with it.

YOU WON'T THRIVE HERE IF :

• You want to write strategy decks more than you want to ship features.

• You think PM doesnt code is a principle worth defending.

• You think AI is overhyped (we dont).

• You need a fully scoped backlog and weekly sprint rituals.