Founding Product Director, NDot AI
for each section heading. We need to include sections only when there is real content. The posting includes: About NewsBreak (company description), About NDot AI (maybe a description), About The Role (role description), What You'll Do (responsibilities), What We're Looking For (requirements/qualifications), Nice to have (maybe skills?), Benefits, Pay (salary range). Also maybe "Why Join" could be a section? Not listed as required heading but could be considered Benefits? Actually "Why Join" is a section describing motivations; could be considered part of Benefits or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About The Role" could be "About the role". "What You'll Do" -> Responsibilities. "What We're Looking For" -> Requirements (maybe also Qualifications). "Nice to have" -> Skills? Could be Skills. "Benefits" -> Benefits. Pay -> Pay. "Why Join" maybe not needed; could be omitted or folded into Benefits? Probably omit as not a required heading; but we could include as a separate section? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid extra headings beyond the list, but suggests using those headings. Safer to stick to those headings. So we will produce sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like cookie/navigation/legal/EEO etc. There's a CPRA Privacy Notice at end; that's boilerplate legal; should be removed. Also "For more information, visit www.newsbreak.com/about" maybe not needed; could be removed as navigation? It's not boilerplate but maybe considered a link; but it's not substantive about the job; we can drop.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to parse content.
Let's extract:
About NewsBreak: description of company. Could be placed under "About the role"? Actually "About the role" is separate; but we have company description maybe not needed? The instruction says use heading for section headings like About the role, Responsibilities, etc. There's no heading for company overview; but we could include it as a paragraph before sections? The instruction says output ONLY the HTML fragment; we can include a
with company description if we want, but not under a heading. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other content outside headings. So we can include a brief intro paragraph about NewsBreak and NDot AI maybe as a
before sections. But we must preserve ALL substantive information; so we need to include company description and NDot AI description. We'll put them as
elements before the first heading.
Now "About The Role": we need to put under
About the role
and then prose.
Then "What You'll Do": responsibilities list. We'll make Responsibilities
then - each bullet.
Then "What We're Looking For": requirements. We'll make
Requirements
then - each bullet.
Then "Nice to have": skills. We'll make
Skills
then - each bullet.
Then "Benefits": list. We'll make
Benefits
then - each bullet.
Then Pay: we have salary range. We'll make
Pay
then with the range.
We must not include "Why Join" section; we can incorporate its content maybe into Benefits? But it's separate motivational content; we could drop it as not required heading; but we need to preserve ALL substantive information. If we drop it, we lose info. However instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include all possible headings; we can include other headings not listed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed. But to be safe, we could include a heading "Why Join" as Why Join
with its content. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings; it's just examples. So we could add Why Join. But they also said "Prefer a few substantive sections over many thin ones." Why Join is a thin section maybe; but it's substantive. Could be merged into Benefits? Not really. Might be okay to include as its own section.
But the instruction also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add Why Join.
Let's include Why Join as a section.
Now we need to strip boilerplate: CPRA Privacy Notice, "For more information, visit www.newsbreak.com/about", maybe also "At NewsBreak, we design our overall rewards package to attract top talents..." that's part of Benefits? Actually that's prose about benefits; we can keep as part of Benefits paragraph.
Also "Depending on the position, the role may also be eligible for discretionary bonus and options. Your recruiter can share more details during the hiring process." That's about Pay; we can include in Pay paragraph.
Now let's craft.
First, intro paragraphs: About NewsBreak and About NDot AI.
We have:
"About NewsBreak Founded in 2015, NewsBreak is the Content Intelligence platform shaping the future content economy. With over 40 million monthly active users, our flagship platform delivers highly personalized local news and information powered by advanced AI, recommendation systems, and adtech. Recognized by Fast Company as #32 on the Top Workplaces for Innovators, we're proud to be Great Place to Work® certified and home to a dynamic team of technologists, product innovators, and business leaders who are passionate about solving meaningful challenges at scale. Together, we reached unicorn status in 2021, and we remain committed to continuing this high-growth trajectory with the right team to fulfill our mission: building the infrastructure layer for content intelligence. If you’re inspired to dream big, innovate fast, and make a difference, we’d love to hear from you!"
Then "About NDot AI Build the owned-audience growth infrastructure for the future of media."
That's a short sentence.
We'll combine them maybe as two paragraphs.
Now sections.
About the role: The paragraph after "About The Role": "We're looking for a 0→1 product leader to own the NDot product roadmap and the publisher experience end to end. This is a highly customer-facing role: you'll spend real time in publisher meetings, work side-by-side with engineers on product and technical tradeoffs, and make the call on which customer requests should become reusable platform capabilities versus one-off custom work. You'll be building reusable platform capabilities that can ultimately serve publishers and adjacent digital content businesses (e.g., short dramas), while sequencing that expansion deliberately rather than chasing every vertical at once."
We'll put that as
under About the role.
Responsibilities: bullet list from "What You'll Do". Let's extract each bullet:
- Run structured discovery with publishers to build a clear, evidence-based view of their priority needs, and translate that into a focused product roadmap.
- Ship visible improvements to the publisher portal and publisher experience (reporting, insights, and beyond).
- Define the minimum product and integration required for lighthouse customers, and establish clear success metrics for each.
- Work directly with engineering on architecture, APIs, data, and integrations — you'll need enough technical depth to be a real thought partner, not just a requirements-writer.
- Build a repeatable loop from customer feedback → prioritization → launch → measurement, and use it to productize the most valuable recurring needs across onboarding, analytics, engagement/growth, and integrations.
- Design the platform so proven capabilities can extend to adjacent verticals without fragmenting the roadmap.
We'll put each as
- .
Requirements: from "What We're Looking For". Bullets:
- Must have Strong customer discovery, product strategy, and prioritization skills, with real analytics chops and technical fluency across APIs, data, and integrations.
- Strong customer empathy and judgment; a structured thinker with a bias for action who's comfortable with ambiguity and can separate scalable product needs from bespoke requests.
- Senior-level PM experience, including having built a 0→1 B2B/platform product and worked directly with customers and small engineering teams.
We'll put as
- .
Skills: from "Nice to have". Bullets:
- Experience with recommendation/personalization, growth, monetization, or AI products.
- Strong commercial instinct and executive presence.
- Background in publisher/media tech, adtech, or consumer-growth, or experience productizing internal technology for external customers.
We'll put as
- .
Benefits: list from "Benefits We offer a competitive benefits package:" then bullets:
- Health, dental, and vision care for you and your family (100% coverage for employee)
- Top-tier 401(K) plan with company matching
- Paid time off and paid holidays
- FSA, HSA and commuter benefits programs
- Team activity budget
Also there is prose after: "The US base salary range for this full-time position is listed below. Pay may vary based on a number of factors including job-related skills, level, experience, geographic location and relevant education or training. At NewsBreak, we design our overall rewards package to attract top talents. Depending on the position, the role may also be eligible for discretionary bonus and options. Your recruiter can share more details during the hiring process."
We'll keep that prose maybe as a
under Benefits? Actually it's about benefits and pay; but we have separate Pay section. We'll put the benefits list under Benefits heading, and then after the list we can include a
with the prose about rewards package, discretionary bonus, etc. That seems appropriate.
Pay: heading Pay, then
with salary range: "Annual Base Pay Range $235,000 - $345,000 USD". Also maybe include note about variability etc. But we already put variability prose under Benefits; maybe we should move that to Pay? Actually the prose about Pay may vary based on factors etc. is more about Pay. The sentence "At NewsBreak, we design our overall rewards package to attract top talents." is generic. The sentence about discretionary bonus and options also about Pay. So we could put that under Pay. Let's restructure:
Under Benefits heading: just the list of benefits.
Under Pay heading:
with: "The US base salary range for this full-time position is listed below. Pay may vary based on a number of factors including job-related skills, level, experience, geographic location and relevant education or training. Annual Base Pay Range $235,000 - $345,000 USD
- for any list of duties/requirements/benefits, and
for prose. We need to parse content. Let's extract: About NewsBreak: description of company. Could be placed under "About the role"? Actually "About the role" is separate; but we have company description maybe not needed? The instruction says use heading for section headings like About the role, Responsibilities, etc. There's no heading for company overview; but we could include it as a paragraph before sections? The instruction says output ONLY the HTML fragment; we can include a
with company description if we want, but not under a heading. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other content outside headings. So we can include a brief intro paragraph about NewsBreak and NDot AI maybe as a
before sections. But we must preserve ALL substantive information; so we need to include company description and NDot AI description. We'll put them as
elements before the first heading. Now "About The Role": we need to put under
About the role
and then prose. Then "What You'll Do": responsibilities list. We'll makeResponsibilities
then- each bullet.
Then "What We're Looking For": requirements. We'll make
Requirements
then- each bullet.
Then "Nice to have": skills. We'll make
Skills
then- each bullet.
Then "Benefits": list. We'll make
Benefits
then- each bullet.
Then Pay: we have salary range. We'll make
Pay
thenwith the range. We must not include "Why Join" section; we can incorporate its content maybe into Benefits? But it's separate motivational content; we could drop it as not required heading; but we need to preserve ALL substantive information. If we drop it, we lose info. However instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include all possible headings; we can include other headings not listed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed. But to be safe, we could include a heading "Why Join" as
Why Join
with its content. However the instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings; it's just examples. So we could add Why Join. But they also said "Prefer a few substantive sections over many thin ones." Why Join is a thin section maybe; but it's substantive. Could be merged into Benefits? Not really. Might be okay to include as its own section. But the instruction also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add Why Join. Let's include Why Join as a section. Now we need to strip boilerplate: CPRA Privacy Notice, "For more information, visit www.newsbreak.com/about", maybe also "At NewsBreak, we design our overall rewards package to attract top talents..." that's part of Benefits? Actually that's prose about benefits; we can keep as part of Benefits paragraph. Also "Depending on the position, the role may also be eligible for discretionary bonus and options. Your recruiter can share more details during the hiring process." That's about Pay; we can include in Pay paragraph. Now let's craft. First, intro paragraphs: About NewsBreak and About NDot AI. We have: "About NewsBreak Founded in 2015, NewsBreak is the Content Intelligence platform shaping the future content economy. With over 40 million monthly active users, our flagship platform delivers highly personalized local news and information powered by advanced AI, recommendation systems, and adtech. Recognized by Fast Company as #32 on the Top Workplaces for Innovators, we're proud to be Great Place to Work® certified and home to a dynamic team of technologists, product innovators, and business leaders who are passionate about solving meaningful challenges at scale. Together, we reached unicorn status in 2021, and we remain committed to continuing this high-growth trajectory with the right team to fulfill our mission: building the infrastructure layer for content intelligence. If you’re inspired to dream big, innovate fast, and make a difference, we’d love to hear from you!" Then "About NDot AI Build the owned-audience growth infrastructure for the future of media." That's a short sentence. We'll combine them maybe as two paragraphs. Now sections. About the role: The paragraph after "About The Role": "We're looking for a 0→1 product leader to own the NDot product roadmap and the publisher experience end to end. This is a highly customer-facing role: you'll spend real time in publisher meetings, work side-by-side with engineers on product and technical tradeoffs, and make the call on which customer requests should become reusable platform capabilities versus one-off custom work. You'll be building reusable platform capabilities that can ultimately serve publishers and adjacent digital content businesses (e.g., short dramas), while sequencing that expansion deliberately rather than chasing every vertical at once." We'll put that as
under About the role. Responsibilities: bullet list from "What You'll Do". Let's extract each bullet: - Run structured discovery with publishers to build a clear, evidence-based view of their priority needs, and translate that into a focused product roadmap. - Ship visible improvements to the publisher portal and publisher experience (reporting, insights, and beyond). - Define the minimum product and integration required for lighthouse customers, and establish clear success metrics for each. - Work directly with engineering on architecture, APIs, data, and integrations — you'll need enough technical depth to be a real thought partner, not just a requirements-writer. - Build a repeatable loop from customer feedback → prioritization → launch → measurement, and use it to productize the most valuable recurring needs across onboarding, analytics, engagement/growth, and integrations. - Design the platform so proven capabilities can extend to adjacent verticals without fragmenting the roadmap. We'll put each as
- . Requirements: from "What We're Looking For". Bullets: - Must have Strong customer discovery, product strategy, and prioritization skills, with real analytics chops and technical fluency across APIs, data, and integrations. - Strong customer empathy and judgment; a structured thinker with a bias for action who's comfortable with ambiguity and can separate scalable product needs from bespoke requests. - Senior-level PM experience, including having built a 0→1 B2B/platform product and worked directly with customers and small engineering teams. We'll put as
- . Skills: from "Nice to have". Bullets: - Experience with recommendation/personalization, growth, monetization, or AI products. - Strong commercial instinct and executive presence. - Background in publisher/media tech, adtech, or consumer-growth, or experience productizing internal technology for external customers. We'll put as
- .
Benefits: list from "Benefits We offer a competitive benefits package:" then bullets:
- Health, dental, and vision care for you and your family (100% coverage for employee)
- Top-tier 401(K) plan with company matching
- Paid time off and paid holidays
- FSA, HSA and commuter benefits programs
- Team activity budget
Also there is prose after: "The US base salary range for this full-time position is listed below. Pay may vary based on a number of factors including job-related skills, level, experience, geographic location and relevant education or training. At NewsBreak, we design our overall rewards package to attract top talents. Depending on the position, the role may also be eligible for discretionary bonus and options. Your recruiter can share more details during the hiring process."
We'll keep that prose maybe as a
under Benefits? Actually it's about benefits and pay; but we have separate Pay section. We'll put the benefits list under Benefits heading, and then after the list we can include a
with the prose about rewards package, discretionary bonus, etc. That seems appropriate. Pay: heading Pay, then
with salary range: "Annual Base Pay Range $235,000 - $345,000 USD". Also maybe include note about variability etc. But we already put variability prose under Benefits; maybe we should move that to Pay? Actually the prose about Pay may vary based on factors etc. is more about Pay. The sentence "At NewsBreak, we design our overall rewards package to attract top talents." is generic. The sentence about discretionary bonus and options also about Pay. So we could put that under Pay. Let's restructure: Under Benefits heading: just the list of benefits. Under Pay heading:
with: "The US base salary range for this full-time position is listed below. Pay may vary based on a number of factors including job-related skills, level, experience, geographic location and relevant education or training. Annual Base Pay Range $235,000 - $345,000 USD
- each bullet.
Then Pay: we have salary range. We'll make
- each bullet.
Then "Benefits": list. We'll make
- each bullet.
Then "Nice to have": skills. We'll make
- each bullet.
Then "What We're Looking For": requirements. We'll make