Director of Product Management
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's an EEO line: "NinjaTech AI is an equal opportunity employer." That's boilerplate; remove.
Also "Employment Category: Full-time, Salaried." That's schedule? Could be schedule section. We'll include Schedule with that info.
Compensation Range: $180K - $200K -> Pay section.
Benefits: Not explicitly listed; maybe "Why Join Us" includes benefits? It mentions owning product, working with CEO, etc. Not explicit benefits like health, etc. Might be considered benefits? The instruction: only include Benefits section if posting actually states them. The posting does not list specific benefits like health insurance, 401k, etc. So we should not create Benefits section.
Skills: Could be derived from "What Sets You Apart" which lists attributes. That could be considered skills. We'll include Skills section with those bullet points.
Qualifications: Could be similar to Experience & Education Requirements. Might be redundant. We could combine Experience & Education Requirements as Requirements (or Qualifications). The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Skills, Pay, Schedule. That's six sections.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now extract content.
About the role: Should include Position Overview and About The Role maybe combined. Let's craft a prose paragraph summarizing: The Director of Product Management will own product portfolio end to end: narrative, launch, adoption, iteration across SuperNinja and AI Workforce; lead customer-facing launch motion for AI Workforce while steering consumer product growth; report to CEO Babak Pahlavan; first six months plan etc. We need to preserve all substantive information, not summarize away detail. That means we should keep details, not omit. But we can combine into a paragraph that includes all details? Might be lengthy but okay. Must not invent or summarize away detail. Summarizing could lose detail. Better to keep original sentences but maybe combine.
We can output multiple
under About the role heading, each containing a chunk of original text. That's allowed: use
for prose. So we can keep original paragraphs.
Similarly Responsibilities: Use
- for list of duties. The Key Challenges & Opportunities section contains bullet-like sentences each starting with a verb. We can turn each into
- .
Requirements: Experience & Education Requirements section contains bullet points? It's a paragraph with semicolons. We can split into
- items.
Skills: What Sets You Apart section contains bullet-like sentences; we can make
- .
Pay: Compensation Range.
Schedule: Employment Category.
We must not include boilerplate like "NinjaTech AI is an equal opportunity employer." Remove.
Also "Working at NinjaTech" maybe could be part of Why Join Us? But we might treat as part of About the role? It's descriptive of work environment; could be considered Benefits? Not explicit benefits. Might be considered part of Why Join Us? But we decided not to include Benefits. Could include as part of About the role? It's not about role but company. Might be considered "Why Join Us" which is like benefits/culture. Since we are not including Benefits section, we could omit that paragraph. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that paragraph, we lose substantive info about working at NinjaTech. But we could incorporate it into About the role or another section as prose. It's not a benefit per se but company description. Could be placed under About the role as additional paragraph. That would preserve info.
Similarly "Why Join Us" could be considered benefits/culture; we could treat as part of About the role or maybe a separate section "Why Join Us" but not in allowed headings. Allowed headings are limited to those list. So we must fit into those headings. Could put under About the role or maybe under Skills? Not appropriate. Better to add a paragraph under About the role describing why join us.
Thus About the role will contain multiple paragraphs: Position Overview, About The Role, What Sets You Apart? maybe not; that's Skills. Why Join Us and Working at NinjaTech can be additional prose.
Now let's extract exact text.
I'll copy relevant sections:
Position Overview:
"We are looking for a Director of Product Management to own our product portfolio end to end: narrative, launch, adoption, and iteration across SuperNinja, our direct-to-consumer agent platform, and AI Workforce, our Slack/Teams-based enterprise product. You will lead the customer-facing launch motion for AI Workforce in its first weeks while steering the consumer product's continued growth, and turn early learnings into a repeatable, scalable product motion across the company. This is a product leadership role, not an engineering role. You will report to Babak Pahlavan, CEO."
Key Challenges & Opportunities (list):
- Lead customer-facing launch motions: positioning, onboarding, rollout, and feedback capture for the users and customers of each product
- Define the product narrative for each surface: what the product is, who it is for, what workflows it supports, and why it matters
- Prioritize the highest-value, repeatable workflows and use cases instead of chasing one-off feature requests
- Translate user and customer feedback into clear priorities, requirements, and product decisions, not just relay it
- Run a daily sync with our Chief Science Officer to push launch blockers, feature gaps, and feedback into product and engineering quickly
- Define adoption and success metrics that show whether people are actually using each product and getting value
- Build onboarding and launch playbooks that take customers from discovery to rollout to adoption
- Create proof points: use cases, value statements, testimonials, expansion signals, and case-study material
- Align the CEO, Chief Science Officer, sales, and product/engineering on what users and customers need, what is being prioritized, and what must happen next
Experience & Education Requirements:
"Bachelor's degree or equivalent practical experience; an MBA or technical degree is a plus
8+ years of product management experience, including meaningful time owning a product or product area
A track record of launching a product or major product area and driving it to real adoption, in enterprise SaaS, consumer software, or both
Experience with AI/ML products, agents, or workflow automation is a strong plus
Comfort working directly with customers, users, sales, and founders in an early-stage environment
Strong written product communication: narratives, requirements, and decision documents that teams actually use"
About The Role:
"You will report to Babak Pahlavan, CEO, and own product management across the portfolio. Your first six months: Month 1 - launch, stabilize, and learn: own the customer-facing launch motion, clarify each product's narrative, support onboarding and first rollouts, set success criteria, capture feedback from first users, and run the daily launch sync to push blockers and gaps into product quickly
Month 3 - iterate, validate, and land customers: live pilots, deployments, and consumer launches, validated workflows, adoption and value metrics, shipped product improvements from feedback, and repeatable launch playbooks that help the team land each product
Month 6 - scale and systematize: the portfolio operating on clear roadmaps, repeatable adoption, proof points, enablement assets, a mature feedback and prioritization process, improved onboarding efficiency, and a recommendation on how to scale the product function and team
You will have ownership in these areas: Product narrative, use-case prioritization, and requirements across SuperNinja and AI Workforce
Customer-facing launches and post-launch iteration that turns learnings from live usage into product improvements quickly
Adoption and success metrics for each product
Onboarding and launch playbooks, from discovery through rollout to adoption
Support for sales and customer meetings as the product authority: explaining the products, shaping use cases, discussing feasibility, and building customer confidence"
What Sets You Apart:
"You have launched products from zero and lived through the messy first months
You are as credible in a customer or executive meeting as in a prioritization review
You write narratives and requirements that engineers and sales actually use
Experience with collaboration or workflow products, applied AI products, or consumer products at scale
You turn scattered feedback into a small number of sharp product decisions
You hold the line between product leadership and engineering, and customers, sales, and engineering all trust you on it"
Why Join Us:
"You will own product at a company building category-forming AI agents: one portfolio, from a consumer platform people love to the enterprise product that brings agents into where work already happens. You will work directly with the CEO and Chief Science Officer and define how both products land and grow."
Working at NinjaTech:
"You will join a small, senior team that values scientific rigor and engineering excellence, with the chance to make foundational contributions to autonomous AI agents. We work across Silicon Valley, Sydney, and Vancouver."
Employment Category: "Full-time, Salaried."
Compensation Range: "$180K - $200K"
Now we need to output HTML fragment.
Structure:
About the role
Position Overview paragraph
About The Role paragraph(s) maybe multiple
Why Join Us paragraph
Working at NinjaTech paragraph
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Pay
$180K - $200K
Schedule
Full-time, Salaried.
We must not include Benefits section.
Check that we didn't repeat any heading with empty content.
Now ensure we preserve all substantive information: Did we miss any? Let's verify.
From Position Overview we included.
From Key Challenges & Opportunities we included as responsibilities.
From Experience & Education Requirements we included as requirements.
From About The Role we included as part of About the role (we included the paragraphs). Did we include all sentences? We included the whole block as a paragraph; but we split into multiple paragraphs maybe. We'll include as one paragraph containing the whole block (including line breaks). That's fine.
From What Sets You Apart we included as skills.
From Why Join Us we included as paragraph under About the role.
From Working at NinjaTech we included as paragraph under About the role.
From Employment Category we included as Schedule.
From Compensation Range we included as Pay.
We omitted the EEO line.
We also omitted any duplicated lines (none).
Now check that we didn't include any placeholder like "commensurate with experience". Not present.
for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's an EEO line: "NinjaTech AI is an equal opportunity employer." That's boilerplate; remove. Also "Employment Category: Full-time, Salaried." That's schedule? Could be schedule section. We'll include Schedule with that info. Compensation Range: $180K - $200K -> Pay section. Benefits: Not explicitly listed; maybe "Why Join Us" includes benefits? It mentions owning product, working with CEO, etc. Not explicit benefits like health, etc. Might be considered benefits? The instruction: only include Benefits section if posting actually states them. The posting does not list specific benefits like health insurance, 401k, etc. So we should not create Benefits section. Skills: Could be derived from "What Sets You Apart" which lists attributes. That could be considered skills. We'll include Skills section with those bullet points. Qualifications: Could be similar to Experience & Education Requirements. Might be redundant. We could combine Experience & Education Requirements as Requirements (or Qualifications). The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Skills, Pay, Schedule. That's six sections. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now extract content. About the role: Should include Position Overview and About The Role maybe combined. Let's craft a prose paragraph summarizing: The Director of Product Management will own product portfolio end to end: narrative, launch, adoption, iteration across SuperNinja and AI Workforce; lead customer-facing launch motion for AI Workforce while steering consumer product growth; report to CEO Babak Pahlavan; first six months plan etc. We need to preserve all substantive information, not summarize away detail. That means we should keep details, not omit. But we can combine into a paragraph that includes all details? Might be lengthy but okay. Must not invent or summarize away detail. Summarizing could lose detail. Better to keep original sentences but maybe combine. We can output multiple
under About the role heading, each containing a chunk of original text. That's allowed: use
for prose. So we can keep original paragraphs. Similarly Responsibilities: Use
- for list of duties. The Key Challenges & Opportunities section contains bullet-like sentences each starting with a verb. We can turn each into
- . Requirements: Experience & Education Requirements section contains bullet points? It's a paragraph with semicolons. We can split into
- items. Skills: What Sets You Apart section contains bullet-like sentences; we can make
- .
Pay: Compensation Range.
Schedule: Employment Category.
We must not include boilerplate like "NinjaTech AI is an equal opportunity employer." Remove.
Also "Working at NinjaTech" maybe could be part of Why Join Us? But we might treat as part of About the role? It's descriptive of work environment; could be considered Benefits? Not explicit benefits. Might be considered part of Why Join Us? But we decided not to include Benefits. Could include as part of About the role? It's not about role but company. Might be considered "Why Join Us" which is like benefits/culture. Since we are not including Benefits section, we could omit that paragraph. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that paragraph, we lose substantive info about working at NinjaTech. But we could incorporate it into About the role or another section as prose. It's not a benefit per se but company description. Could be placed under About the role as additional paragraph. That would preserve info.
Similarly "Why Join Us" could be considered benefits/culture; we could treat as part of About the role or maybe a separate section "Why Join Us" but not in allowed headings. Allowed headings are limited to those list. So we must fit into those headings. Could put under About the role or maybe under Skills? Not appropriate. Better to add a paragraph under About the role describing why join us.
Thus About the role will contain multiple paragraphs: Position Overview, About The Role, What Sets You Apart? maybe not; that's Skills. Why Join Us and Working at NinjaTech can be additional prose.
Now let's extract exact text.
I'll copy relevant sections:
Position Overview:
"We are looking for a Director of Product Management to own our product portfolio end to end: narrative, launch, adoption, and iteration across SuperNinja, our direct-to-consumer agent platform, and AI Workforce, our Slack/Teams-based enterprise product. You will lead the customer-facing launch motion for AI Workforce in its first weeks while steering the consumer product's continued growth, and turn early learnings into a repeatable, scalable product motion across the company. This is a product leadership role, not an engineering role. You will report to Babak Pahlavan, CEO."
Key Challenges & Opportunities (list):
- Lead customer-facing launch motions: positioning, onboarding, rollout, and feedback capture for the users and customers of each product
- Define the product narrative for each surface: what the product is, who it is for, what workflows it supports, and why it matters
- Prioritize the highest-value, repeatable workflows and use cases instead of chasing one-off feature requests
- Translate user and customer feedback into clear priorities, requirements, and product decisions, not just relay it
- Run a daily sync with our Chief Science Officer to push launch blockers, feature gaps, and feedback into product and engineering quickly
- Define adoption and success metrics that show whether people are actually using each product and getting value
- Build onboarding and launch playbooks that take customers from discovery to rollout to adoption
- Create proof points: use cases, value statements, testimonials, expansion signals, and case-study material
- Align the CEO, Chief Science Officer, sales, and product/engineering on what users and customers need, what is being prioritized, and what must happen next
Experience & Education Requirements:
"Bachelor's degree or equivalent practical experience; an MBA or technical degree is a plus
8+ years of product management experience, including meaningful time owning a product or product area
A track record of launching a product or major product area and driving it to real adoption, in enterprise SaaS, consumer software, or both
Experience with AI/ML products, agents, or workflow automation is a strong plus
Comfort working directly with customers, users, sales, and founders in an early-stage environment
Strong written product communication: narratives, requirements, and decision documents that teams actually use"
About The Role:
"You will report to Babak Pahlavan, CEO, and own product management across the portfolio. Your first six months: Month 1 - launch, stabilize, and learn: own the customer-facing launch motion, clarify each product's narrative, support onboarding and first rollouts, set success criteria, capture feedback from first users, and run the daily launch sync to push blockers and gaps into product quickly
Month 3 - iterate, validate, and land customers: live pilots, deployments, and consumer launches, validated workflows, adoption and value metrics, shipped product improvements from feedback, and repeatable launch playbooks that help the team land each product
Month 6 - scale and systematize: the portfolio operating on clear roadmaps, repeatable adoption, proof points, enablement assets, a mature feedback and prioritization process, improved onboarding efficiency, and a recommendation on how to scale the product function and team
You will have ownership in these areas: Product narrative, use-case prioritization, and requirements across SuperNinja and AI Workforce
Customer-facing launches and post-launch iteration that turns learnings from live usage into product improvements quickly
Adoption and success metrics for each product
Onboarding and launch playbooks, from discovery through rollout to adoption
Support for sales and customer meetings as the product authority: explaining the products, shaping use cases, discussing feasibility, and building customer confidence"
What Sets You Apart:
"You have launched products from zero and lived through the messy first months
You are as credible in a customer or executive meeting as in a prioritization review
You write narratives and requirements that engineers and sales actually use
Experience with collaboration or workflow products, applied AI products, or consumer products at scale
You turn scattered feedback into a small number of sharp product decisions
You hold the line between product leadership and engineering, and customers, sales, and engineering all trust you on it"
Why Join Us:
"You will own product at a company building category-forming AI agents: one portfolio, from a consumer platform people love to the enterprise product that brings agents into where work already happens. You will work directly with the CEO and Chief Science Officer and define how both products land and grow."
Working at NinjaTech:
"You will join a small, senior team that values scientific rigor and engineering excellence, with the chance to make foundational contributions to autonomous AI agents. We work across Silicon Valley, Sydney, and Vancouver."
Employment Category: "Full-time, Salaried."
Compensation Range: "$180K - $200K"
Now we need to output HTML fragment.
Structure:
About the role
Position Overview paragraph
About The Role paragraph(s) maybe multiple
Why Join Us paragraph
Working at NinjaTech paragraph
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
$180K - $200K
Schedule
Full-time, Salaried.
We must not include Benefits section. Check that we didn't repeat any heading with empty content. Now ensure we preserve all substantive information: Did we miss any? Let's verify. From Position Overview we included. From Key Challenges & Opportunities we included as responsibilities. From Experience & Education Requirements we included as requirements. From About The Role we included as part of About the role (we included the paragraphs). Did we include all sentences? We included the whole block as a paragraph; but we split into multiple paragraphs maybe. We'll include as one paragraph containing the whole block (including line breaks). That's fine. From What Sets You Apart we included as skills. From Why Join Us we included as paragraph under About the role. From Working at NinjaTech we included as paragraph under About the role. From Employment Category we included as Schedule. From Compensation Range we included as Pay. We omitted the EEO line. We also omitted any duplicated lines (none). Now check that we didn't include any placeholder like "commensurate with experience". Not present.