Jobs · Marketing · Texas

Sr. Director, Product Marketing

Spectrum Equity · Austin, TX · 1 mo ago
Marketing$250k–$328k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting. Key sections: - About the role: maybe summary of role and team? The posting includes "Summary Of The Role And Team". That's about the role. So we can put that under About the role. - Responsibilities: "What You Will Be Doing" list. - Requirements: "What You Bring" list (experience requirements). Could also include Qualifications? The posting includes "What You Bring" and "Nice to Have". Those could be Requirements and Qualifications? But we need to follow headings: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - Responsibilities: bullet list of duties. - Requirements: mandatory experience (12+ years etc). Could be under Requirements. - Qualifications: maybe education (Bachelor's degree) or equivalent experience. Could be under Qualifications. - Skills: maybe specific skills like AI-enabled workflows, generative AI, etc. Could be under Skills. - Benefits: "Overview Of Benefits" list. - Pay: salary range. - Schedule: not mentioned; maybe remote/hybrid flexibility? The posting mentions "Flexibility — Work where you thrive, with remote and hybrid options available across most regions". That's schedule/flexibility. So we can include Schedule section with that. We must not include headings with filler text. Ensure we have real content. We must not repeat job title as heading. No Job ID etc. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings,
  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given? We can keep the substance but not necessarily copy verbatim? Probably we should keep the content but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. Likely we should copy the bullet points as they appear. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should cut out the EEO statement, privacy notice, "Apply now", "See more open positions", etc. Also remove duplicated lines like "Varicent is committed to creating a diverse environment..." etc. We need to keep the benefits list: Health & Wellness, Time Off, Volunteer Days, Ignite Days, Financial, Retirement, Tuition Assistance, Flexibility. We need to keep the Pay: salary range. We need to keep Schedule: remote/hybrid options. We need to keep "Overview Of Benefits" as a list. We need to keep "For this role, the estimated annual base salary range is between $250,200 - $328,300 USD." plus note about bonuses etc. That's Pay. We need to keep "In addition to base salary, our compensation package may include bonuses, commissions for eligible sales roles, and a comprehensive benefits package." That's also Pay. We need to keep "The actual base salary will vary based on factors including individual qualifications and market data, as objectively assessed during the interview process." That's also Pay. We need to keep "This posting is for an existing vacancy. This hiring process utilizes artificial intelligence tools to assist in candidate screening and assessment. Our AI tools are designed to complement — not replace — human decision-making." That's maybe boilerplate? It's about hiring process; maybe we can keep? It's not explicitly listed as boilerplate to remove, but it's not substantive about role? Might be considered metadata; but we can keep as a short paragraph maybe under About the role? However instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." This is metadata about hiring process; we could fold into a short

    under About the role or maybe drop. Safer to drop? It's not required to preserve; but "Preserve ALL substantive information" - is that substantive? It's about hiring process, not role. Might be considered boilerplate? Not sure. Safer to keep as a short paragraph under About the role? But it's not about role. Might be considered generic. I'd drop it to keep focused. Also need to drop "Overview Of Benefits" heading? We'll make Benefits section with list. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now craft HTML. Structure:

    About the role

    Summary Of The Role And Team ...

    (the paragraph). We'll include the paragraph exactly as given: "As the Senior Director, Product Marketing, you will lead Varicent’s Product Marketing function and play a critical role in shaping the company’s go-to-market strategy, market positioning, category narrative, commercialization approach, and revenue growth initiatives. Reporting as a senior marketing leader, you will lead and develop a team of Product Marketing professionals responsible for translating market insights, customer needs, competitive intelligence, and product innovation into differentiated messaging, sales enablement, launch execution, and measurable business results. This role partners closely with Product, Sales, Customer Success, Revenue Operations, Alliances, Marketing, and Executive Leadership to strengthen Varicent’s market position, accelerate growth, and support the successful adoption and expansion of Varicent’s solutions." Then maybe also include the "Here’s Why You’ll Thrive At Varicent" bullet points? That's more about culture; could be part of About the role? Might be considered "About the role" or separate? Not specified headings. Could include under About the role as a paragraph? But it's a list of bullet points: "Innovate with Purpose: Build impactful solutions for customers worldwide.Join Excellence: Work in a diverse, collaborative, and innovative team.Shape the Future: Lead in redefining revenue optimization.Grow Together: Unlock your potential in a supportive environment." That's basically a list. Could be under About the role as
      . But we need to decide. Better to keep it as part of About the role as a
        list. Thus About the role section will have two parts: a paragraph summary and a list of why you'll thrive. Now Responsibilities:

        Responsibilities

          with each bullet from "What You Will Be Doing". Need to preserve each bullet exactly. Let's extract bullets: - Lead and develop the Product Marketing organization, establishing priorities, operating rhythms, team goals, and performance measures aligned to business objectives - Define and evolve product positioning, messaging frameworks, buyer personas, value propositions, and market narratives across Varicent’s solution portfolio - Partner with Product leadership to influence roadmap priorities, commercialization strategies, packaging decisions, and market readiness activities - Lead product launches and go-to-market initiatives, ensuring alignment across Product, Sales, Customer Success, Demand Generation, Enablement, and Partner organizations - Drive sales enablement programs, competitive intelligence initiatives, and value-based messaging that improve seller effectiveness and customer engagement - Lead market, customer, analyst, and competitive research efforts to identify growth opportunities, market trends, and differentiation strategies - Champion the strategic use of AI-enabled workflows and modern marketing technologies to improve research, content creation, enablement, and operational effectiveness - Provide strategic market insights and recommendations to executive leadership regarding category evolution, competitive dynamics, growth opportunities, and go-to-market performance Now Requirements:

          Requirements

            with mandatory experience bullets from "What You Bring". Those are: - 12+ years of experience in B2B technology organizations, with significant experience in enterprise SaaS, Revenue Operations, Sales Performance Management, sales technology, HR technology, financial planning technology, or related enterprise software markets - 7+ years of Product Marketing experience, including ownership of positioning, messaging, go-to-market strategy, commercialization, or product launches - 3+ years of experience leading and developing Product Marketing teams, including managing senior individual contributors, people leaders, or Product Marketing managers - Demonstrated success influencing go-to-market strategy and driving measurable business outcomes such as pipeline growth, revenue impact, customer adoption, retention, expansion, or market differentiation - Experience partnering with Product, Sales, Marketing, Customer Success, and Executive teams on commercialization and growth initiatives - Ability to transform market insights, customer challenges, and product capabilities into compelling business narratives and positioning strategies - Experience leveraging generative AI technologies and AI-enabled workflows to improve marketing effectiveness, scalability, and insight generation - Bachelor's degree in Marketing, Business, Communications, Computer Science, Engineering, or a related field, or equivalent experience Now Qualifications: maybe we separate education? But we already included Bachelor's degree in Requirements. Could move education to Qualifications. However we have to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." Could combine Requirements and Qualifications? But we need to follow headings; we can still have both if they have content. Let's decide: Requirements: experience requirements. Qualifications: education and maybe nice-to-have? Actually "Nice to Have" could be Qualifications or Skills. Let's assign: - Qualifications: Bachelor's degree (or equivalent) maybe also MBA or advanced business degree as nice to have? But that's nice to have. We'll put education under Qualifications. - Skills: maybe list of specific skills like AI-enabled workflows, generative AI, value-based selling, platform selling, account-based marketing, enterprise sales motions, engaging industry analysts, strategic partners, customer communities, industry associations, partner ecosystems, marketplaces, integrations, adjacent enterprise technology platforms. Also maybe "value-based selling, platform selling, account-based marketing, and enterprise sales motions". Also "Experience with value-based selling, platform selling, account-based marketing, and enterprise sales motions". Also "Experience engaging industry analysts, strategic partners, customer communities, or industry associations". Also "Experience working with partner ecosystems, marketplaces, integrations, or adjacent enterprise technology platforms". Also "MBA or advanced business degree" could be under Qualifications as nice to have but we can put under Qualifications as optional? But we should not invent filler; we can include it as a bullet under Qualifications if present. It's present under Nice to Have. Thus we need to parse Nice to Have list: - Experience within Sales Performance Management, Revenue Operations, Incentive Compensation, Sales Planning, Financial Planning, or related enterprise software categories - Experience with value-based selling, platform selling, account-based marketing, and enterprise sales motions - Experience engaging industry analysts, strategic partners, customer communities, or industry associations - MBA or advanced business degree - Experience working with partner ecosystems, marketplaces, integrations, or adjacent enterprise technology platforms We could treat these as Skills or Qualifications. Since they are "Nice to Have", they are not strict requirements but still substantive. We could put them under Skills. Thus:

            Skills

              with those bullets. Now Benefits:

              Benefits

                with each benefit line. Extract benefits: - Health & Wellness — Comprehensive medical, dental, and vision coverage tailored to your local needs - Time Off — PTO and public holidays to rest, recharge, and do what matters most - Volunteer Days — Dedicated time to give back and support the communities that matter to you - Ignite Days — Dedicated learning days to support continuous growth, skill development, and professional learning - Financial — Compensation that reflects your market and your value - Retirement — Retirement plans designed to help you build long-term financial security - Tuition Assistance — Invest in your growth with support for continuing education and professional development - Flexibility — Work where you thrive, with remote and hybrid options available across most regions Now Pay

Similar jobs