Product Marketing Lead
Lumana · Connecticut, United States · 1 mo ago
RemoteRemoteMarketing$180k–$200k/yrFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We have:
- About the role: The description includes role description, why it matters, location, etc. So we can have About the role section with paragraphs.
- Responsibilities: list of responsibilities bullet points.
- Requirements: Must Have and Nice to Have? The posting has "Requirements" with Must Have and Nice to Have. We can treat Must Have as Requirements, maybe also include Nice to Have as part of Requirements or separate? The spec says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements (must have). Could also have Qualifications (maybe same). But we should not create thin sections. We have Must Have list; Nice to Have could be considered "Qualifications" or "Skills"? Might be better to put Nice to Have under "Qualifications" or "Skills". However we need to avoid filler. We have content for Nice to Have, so we can include a section for Qualifications (or Skills). The spec says we can use Qualifications heading. We'll put Nice to Have under Qualifications.
- Benefits: The posting has "What We Offer" with list: Competitive Pay, Equity & Upside, Tools that Work for You, Remote-First Flexibility, Product Influence, then for US-based employees: Health & Wellness, Time Off, Financial, Remote-Friendly, Parental Leave, Work Setup. Also there is Compensation range earlier. So Benefits section can include those items.
- Pay: The posting includes Compensation 180k - 200k base + Variable Compensation (U.S.A.) and later Compensation Range: $180K - $200K. So we have Pay info. We'll create Pay section.
- Schedule: Not explicitly mentioned besides location remote/hybrid. No schedule details like full-time, etc. Not given. So we should not create Schedule section.
- Skills: Not explicitly listed as separate; but we could incorporate skills in Requirements. But we could create Skills section if we have specific skills listed. The Must Have includes: strong understanding of complex technical products, exceptional storytelling, writing, presentation, messaging skills, highly analytical, strong executive presence, etc. Those could be considered Skills. However we already have Requirements covering those. To avoid duplication, we could put Skills as separate but risk duplication. The spec says prefer a few substantive sections over many thin ones. So we might combine Requirements and Skills into one Requirements section. But we need to follow headings: we can use Requirements for must have, Qualifications for nice to have, Benefits for benefits, Pay for pay. That's four sections.
We also need About the role section.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "We don’t do cookie-cutter..." etc. That's not boilerplate; it's part of encouragement. Keep.
Also includes "Our Hiring Philosophy", "Our Interview Process", "Equal Opportunity", "Interview Policy", "Recruitment Fraud". Those are boilerplate? They are not cookie/navigation/legal/EEO? They are somewhat company info but could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Equal Opportunity" line is EEO boilerplate, should be removed. "Interview Policy" and "Recruitment Fraud" maybe also considered legal/scams? Might be considered boilerplate; safer to remove them. Also "Our Hiring Philosophy" and "Our Interview Process" maybe not required but could be considered company info; not explicitly prohibited. However they are not about role; they'd be extra. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say to remove company philosophy unless it's boilerplate. It's not explicitly listed as boilerplate to remove. However it's somewhat generic; but it's still substantive about company values. I'd keep it maybe under About the role? But it's a separate block. Could include as part of About the role? Might be okay.
But to be safe, we could keep it as part of About the role section.
We need to output only HTML fragment.
Structure:
. The responsibilities list includes many items each starting with a bold heading? Actually each responsibility is a heading like "Own Market Strategy & GTM Direction" then a paragraph. We'll treat each as a list item containing the heading and description. Could split into multiple each containing the heading and its description.
We'll extract:
- Own Market Strategy & GTM Direction: Own Lumana's understanding of the market, customers, and competitive landscape. Continuously gather intelligence from customers, competitors, sales, partners, and industry trends, then translate those insights into clear strategic recommendations.Define where Lumana should focus its go-to-market efforts, adjust priorities as market conditions evolve, and ensure GTM strategy reflects real customer demand rather than assumptions.
- Own Positioning & Messaging: Develop and continuously evolve differentiated positioning and messaging that clearly communicates Lumana's value across industries, buyer personas, and customer segments.Ensure messaging remains consistent across every customer-facing touchpoint while incorporating market intelligence and customer feedback to strengthen product-market fit.
- Lead Product Launches & GTM Execution: Partner closely with Product, Engineering, Sales, Marketing, and Customer Success to bring new capabilities to market.Own launch strategy from roadmap to execution by translating product investments into compelling market narratives, launch plans, and measurable business outcomes.
- Drive Cross-Functional Alignment: Serve as the strategic connective tissue across Product, Sales, Marketing, and Customer Success.Bring teams together around GTM priorities, facilitate difficult prioritization decisions when competing initiatives arise, and ensure strategic direction is executed—not just discussed.Take ownership from initial market signal through execution, driving initiatives forward with minimal oversight.
- Enable Sales & Channel Success: Equip Sales and Channel teams with the messaging, competitive intelligence, battlecards, pitch decks, objection handling, and enablement resources needed to accelerate pipeline and improve win rates.Continuously refine enablement based on field feedback and competitive dynamics.
- Shape Content & Thought Leadership: Develop customer-facing content including website messaging, case studies, product narratives, videos, blogs, and executive thought leadership that supports the entire buyer journey.Position Lumana as an industry leader in AI-powered video intelligence through compelling storytelling grounded in customer outcomes and market trends.
- Be the Voice of the Customer: Represent the customer across the organization by synthesizing feedback, product usage data, sales insights, and market signals.Advocate for customer needs to influence messaging, GTM strategy, product prioritization, and long-term roadmap decisions.
We'll make each as with the heading bold? Not needed; just plain text.
Requirements (Must Have): list bullet points:
- 5+ years of experience in B2B SaaS Product Marketing, with a proven track record of shaping go-to-market strategy that drove measurable business outcomes—not simply executing someone else's plan.
- Experience building or scaling Product Marketing within a Series A–C startup or similarly high-growth environment where ambiguity, speed, and ownership are the norm.
- Demonstrated ability to read market signals, customer insights, competitive dynamics, and business data to make strategic decisions with incomplete information and adapt quickly as conditions evolve.
- Strong understanding of complex technical products, preferably within AI, computer vision, physical security, infrastructure, or enterprise software.
- Proven success partnering closely with Product, Sales, Marketing, Customer Success, and executive leadership to align priorities, influence roadmap direction, and execute successful go-to-market initiatives.
- Exceptional storytelling, writing, presentation, and messaging skills, with the ability to translate technical capabilities into compelling customer value.
- Highly analytical with a strong grasp of business metrics and a bias toward action—comfortable balancing long-term strategy with hands-on execution.
- Comfortable building from first principles, operating with limited structure, and taking ownership from initial market insight through execution.
- Strong executive presence with the ability to influence cross-functional teams and drive alignment through credibility rather than authority.
Qualifications (Nice to Have): list:
- Experience in AI, computer vision, video security, cybersecurity, infrastructure, or adjacent enterprise technologies.
- Experience creating or defining new product categories or repositioning innovative products within competitive or legacy markets.
- Familiarity with regulated industries such as government, education, healthcare, or other compliance-driven environments.
Benefits: from "What We Offer" and US-based employees.
List:
- Competitive Pay: Strong base salary + variable
- Equity & Upside: Own a piece of what you're building
- Tools that Work for You: We arm our team with top-tier tech and modern sales tools—so you can focus on closing, not admin
- Remote-First Flexibility: Work from where you're most effective, with teammates around the globe
- Product Influence: Your voice matters—sales feedback directly shapes our roadmap
- For U.S.-Based Employees:
- Health & Wellness: Comprehensive medical, dental, and vision coverage
- Time Off: 15 days PTO, 10 paid holidays, and sick leave
- Financial: 401(k) with
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We have:
- About the role: The description includes role description, why it matters, location, etc. So we can have About the role section with paragraphs.
- Responsibilities: list of responsibilities bullet points.
- Requirements: Must Have and Nice to Have? The posting has "Requirements" with Must Have and Nice to Have. We can treat Must Have as Requirements, maybe also include Nice to Have as part of Requirements or separate? The spec says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements (must have). Could also have Qualifications (maybe same). But we should not create thin sections. We have Must Have list; Nice to Have could be considered "Qualifications" or "Skills"? Might be better to put Nice to Have under "Qualifications" or "Skills". However we need to avoid filler. We have content for Nice to Have, so we can include a section for Qualifications (or Skills). The spec says we can use Qualifications heading. We'll put Nice to Have under Qualifications.
- Benefits: The posting has "What We Offer" with list: Competitive Pay, Equity & Upside, Tools that Work for You, Remote-First Flexibility, Product Influence, then for US-based employees: Health & Wellness, Time Off, Financial, Remote-Friendly, Parental Leave, Work Setup. Also there is Compensation range earlier. So Benefits section can include those items.
- Pay: The posting includes Compensation 180k - 200k base + Variable Compensation (U.S.A.) and later Compensation Range: $180K - $200K. So we have Pay info. We'll create Pay section.
- Schedule: Not explicitly mentioned besides location remote/hybrid. No schedule details like full-time, etc. Not given. So we should not create Schedule section.
- Skills: Not explicitly listed as separate; but we could incorporate skills in Requirements. But we could create Skills section if we have specific skills listed. The Must Have includes: strong understanding of complex technical products, exceptional storytelling, writing, presentation, messaging skills, highly analytical, strong executive presence, etc. Those could be considered Skills. However we already have Requirements covering those. To avoid duplication, we could put Skills as separate but risk duplication. The spec says prefer a few substantive sections over many thin ones. So we might combine Requirements and Skills into one Requirements section. But we need to follow headings: we can use Requirements for must have, Qualifications for nice to have, Benefits for benefits, Pay for pay. That's four sections.
We also need About the role section.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "We don’t do cookie-cutter..." etc. That's not boilerplate; it's part of encouragement. Keep.
Also includes "Our Hiring Philosophy", "Our Interview Process", "Equal Opportunity", "Interview Policy", "Recruitment Fraud". Those are boilerplate? They are not cookie/navigation/legal/EEO? They are somewhat company info but could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Equal Opportunity" line is EEO boilerplate, should be removed. "Interview Policy" and "Recruitment Fraud" maybe also considered legal/scams? Might be considered boilerplate; safer to remove them. Also "Our Hiring Philosophy" and "Our Interview Process" maybe not required but could be considered company info; not explicitly prohibited. However they are not about role; they'd be extra. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say to remove company philosophy unless it's boilerplate. It's not explicitly listed as boilerplate to remove. However it's somewhat generic; but it's still substantive about company values. I'd keep it maybe under About the role? But it's a separate block. Could include as part of About the role? Might be okay.
But to be safe, we could keep it as part of About the role section.
We need to output only HTML fragment.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
... maybe also include variable comp.
We must not include empty sections. Let's extract content. About the role: combine role description, why it matters, location. Role Description paragraph: "Lumana helps organizations turn video into action. Our AI video security platform helps customers improve safety, strengthen security, and respond faster when it matters most. Founded in 2021 and backed by leading Silicon Valley investors, we’re growing quickly. Here, you’ll think big, move fast, and own work that has a visible impact." Then "Role Description The Product Marketing Lead guides how Lumana positions, launches, and communicates its AI-first video security platform to the market. This role is responsible for ensuring prospects and customers clearly understand Lumana’s differentiated value and why we win. This is a highly global cross-functional role at the center of Product, Marketing, Sales, and Customer Success. You will translate complex technical capabilities into clear, compelling narratives that resonate with decision-makers across industries including education, government, manufacturing, hospitality, healthcare, and retail. You will act as the voice of the customer inside Lumana—owning positioning and messaging, shaping go-to-market strategy, enabling revenue teams, and driving successful product and feature launches. This role is ideal for someone who is both strategic and hands-on, energized by ambiguity, and excited to help define and build a new category through strong storytelling and disciplined GTM execution. This role currently reports to the VP of GTM Engineering." Why it Matters: paragraphs about market size, inflection point, etc. There's duplicated sentence: "Lumana is at an inflection point. We have product-market fit and real momentum. What we do next decides whether we win the category." appears twice. We should keep only once? The instruction: remove duplicated lines. So we need to deduplicate. We'll keep one instance. Location: "Location Remote - Must Live in Eastern Timezone, U.S. Hybrid - New York/New Jersey" We can combine. Thus About the role section will have maybe two paragraphs: first paragraph about company overview, second about role description, third about why it matters, fourth about location. Or we can combine into fewer paragraphs but keep substance. We'll outputfor each distinct block. Responsibilities: list bullet points from "Own Market Strategy & GTM Direction" etc. We need to capture each bullet as