ngram is building agentic AI video creation for the enterprise. We turn docs, URLs, and rough screen recordings into polished, on-brand videos.

We have a domain we believe in (enterprise video, AI-native), a working product across three input types, and early customer signal across multiple use cases. The next thing we're committing to is a wedge — one ICP and one workflow we'll win first. That's what this hire is for.

We're hiring our first PM in Hyderabad.

What's working, and what we're choosing next

What's working:

• Enterprise video budgets exist and are growing. Synthesia, HeyGen, and Loom have proven the demand from three different angles.
• Our technical stack works. Doc-to-video, URL-to-video, and screen-recording-to-video pipelines are all live and shipping output that customers like.
• We believe "agentic" is the unlock — meaning the system makes decisions about format, structure, and edits autonomously, instead of asking a human to direct each step.

What we're choosing next:

• Which of sales, marketing, L&D, customer education, or internal comms is our beachhead. We have live conversations across all five. We're choosing deliberately, not by default — which is why this hire matters.
• Which of our three input types is the highest-leverage one to lean into. Possibly all three. More likely one — and helping us pick is part of this role.

The first PM's job is to help us answer these questions, then execute against the answers. If you want a defined roadmap to ship against, this isn't the role. If you want to help define what ngram is, it is.

Why this role exists

We need someone who can deeply map the market — what the relevant players are building, how they're positioning, and where the customer pull is strongest — and translate that into a wedge ngram can win. Then turn that wedge into a roadmap engineering can execute against.

This is a critical first PM hire. You'll have a lot of ownership and a lot of freedom. We need someone who thinks like a founder: high-agency, fast-moving, market-aware, AI-native.

What you'll actually do

Months 0–3: Find the wedge.

• Map the competitive and customer landscape rigorously. Not as a slide deck — as a working thesis we revise weekly.
• Sit with every active customer conversation. Identify which use case has the strongest pull, which buyer has budget, and which workflow we're uniquely good at.
• Help Anish and Devadutta make the call: which ICP, which workflow, which competitor we're displacing. Then commit to it on paper so the team can execute behind it.

Months 3–6: Execute against it.

• Translate the chosen wedge into a roadmap engineering can ship against.
• Vibe-code prototypes, push small features to prod, and unblock engineering on UI/UX decisions.
• Make sure the marketing site, the product, and the customer story tell the same story — because the wedge becomes the story.

Throughout: sit close to customers, sales, and engineering. Translate signal into shipped product.

What success looks like

Six months in:

• We've picked our wedge and we can defend it. One ICP, one workflow, one competitor we're beating. Written down. Visible to the team.
• The product, marketing, and customer narrative agree — because there's a real bet to point them at.
• One enterprise use case has genuine pull. Not five hypotheses. One real customer pattern that compounds.
• Engineering moves faster because of you, not in spite of you. Specs, prototypes, demos — whatever unlocks the team. Small things ship straight to prod from your hands.
• The roadmap reflects the market and our wedge — not the backlog, and not what competitors shipped last week.

What we're looking for

• Senior PM with a wedge-finding instinct. You've helped a company pick its first ICP before, or you've done it as a founder. You know that picking is harder than building.
• AI-native. Cursor, Claude, v0, Lovable, Figma Make — daily, as part of how you work.
• Hands-on. You can prototype, vibe-code, and demo your own ideas end-to-end.
• Market-aware without being derivative. You can map a landscape, see where the pull actually is, and form a contrarian view when the evidence supports it.
• Design sense. You know when a UI is right and when it's off. You care about polish, not just function.
• Strong opinions, loosely held — emphasis on both halves. You bring sharp takes. You also revise them when the evidence changes.

What we're not looking for

• PMs who want a defined roadmap to execute against. We don't have one yet — finding it is the job.
• PMs who define their work as "alignment" and "stakeholder management."
• Spec-writers who haven't shipped anything in a year.
• People who need a six-week discovery phase to form an initial opinion. Two weeks is fine. Six is a tell.

Logistics

• Location: Hyderabad. Minimum 3 days in-office; expect more when shipping is heavy, which is often.
• Comp: Competitive cash + meaningful ESOPs. We'll share specifics — round, valuation, options pool, vesting, strike — on the first call. Bring questions.
• Reports to: Anish (CEO).

Interview process

• Application form — read carefully. The Q11 take is real signal.
• Conversation with Anish (CEO). We'll discuss the wedge question directly. Come with a point of view.
• Conversation with Devadutta (CTO).
• Final round with the engineering team.

It's thorough on purpose. You'll be our first PM, and you'll help shape what ngram becomes.

How to apply

Spend time at ngram.com first. Then fill out the form:

We'll get back to everyone who completes it.