Senior Segment Product Marketing Manager (Public Sector)

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes "Who We Are" (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to decide which sections to include based on content. We have content: Who We Are (company overview) - could be "About the role"? Actually "About the role" is more about the role description. The posting includes "Who You Are" (role description). There's "What You'll Do" (responsibilities). "How You'll Make An Impact" (maybe also responsibilities). "What You'll Bring To This Role" (requirements/qualifications/skills). Then "Why Job Seekers Choose Geotab" (benefits). Also "How We Work" (schedule? flexible hybrid). Also mention remote across US, flexible hybrid model, occasional travel up to 20% maybe schedule? Not exactly pay. No explicit pay or schedule details besides flexible hybrid and occasional travel. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: they list benefits under "Why Job Seekers Choose Geotab": Flex working arrangements, Home office reimbursement program, Baby bonus & parental leave top up program, Online learning and networking opportunities, Electric vehicle purchase incentive program, Competitive medical and dental benefits, Retirement savings program. That's specific benefits. So we can include Benefits section. Schedule: they mention flexible hybrid model, remote across US, occasional travel up to 20% may be required. That's schedule info. So we can include Schedule section. Pay: not mentioned. So omit Pay. Qualifications: they have "What You'll Bring To This Role" includes experience, education, etc. That's qualifications/requirements/skills. We could split into Requirements and Qualifications and Skills but we can combine maybe into Requirements (or Qualifications). The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role (maybe a brief summary), Responsibilities, Requirements, Benefits, Schedule. Or we could combine About the role with Responsibilities? But we need headings from list. Let's decide: - About the role: could be a short paragraph summarizing the role (maybe from "Who You Are" and "We are seeking a Senior Segment Product Marketing Manager (Public Sector)"). - Responsibilities: from "What You'll Do" and "How You'll Make An Impact". Combine. - Requirements: from "What You'll Bring To This Role" (experience, education, skills). Could also include "Objective-focused..." etc. - Benefits: from "Why Job Seekers Choose Geotab". - Schedule: from "How We Work" and remote/hybrid and occasional travel. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details, not just high-level. But we can keep them as list items or paragraphs. We need to use

• for any list of duties/requirements/benefits. So for responsibilities, requirements, benefits we should use lists. We need to use

  for prose. We must not repeat the job title as a heading. So no heading like "Senior Segment Product Marketing Manager (Public Sector)". Use About the role heading maybe. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's extract content. First, About the role: Could be a paragraph describing the role: "We are seeking a Senior Segment Product Marketing Manager (Public Sector) who will be a senior individual contributor within Geotab’s Segment Product Marketing team. This role owns the end-to-end marketing strategy and execution for Geotab’s assigned segments, with minimal oversight and deep subject matter expertise. Recognized as Geotab’s internal authority on segment go-to-market, this role sits at the intersection of strategy, market intelligence, and cross-functional execution." That's from Who You Are section. Responsibilities: combine What You'll Do and How You'll Make An Impact. Let's list duties: - Own the end-to-end strategy and execution for Geotab's Public Sector segments — Public Works, Public Safety, People Transportation, and Public Administration — spanning research, messaging, content, and sales enablement, and be able to demonstrate the pipeline results generated. - Understand government buying cycles, multi-stakeholder procurement processes, cooperative purchasing vehicles, and compliance considerations such as FedRAMP, CJIS, and FERPA that shape public sector purchasing decisions. - Be a strong cross-functional partner to both Sales and Product, and know how to tailor a message to government, education, and municipal buyers without losing the brand. - Instrumental in shaping and executing comprehensive marketing strategies that align with Geotab's public sector revenue objectives. - Impactful relationships across Marketing, Sales, and the partner ecosystem to propel Geotab's market presence within Public Works, Public Safety, People Transportation, and Public Administration. - Collaborate closely with demand generation, content, events, product marketing, and sales teams to ensure marketing plans are seamlessly integrated with public sector goals. - Through effective communication, market intelligence, and strategic execution, maximize the impact of marketing efforts — creating a unified approach that supports Geotab's public sector revenue objectives. - Lead the development of comprehensive marketing strategies for all assigned segments; mobilize cross-functional teams to ensure alignment with overall segment business goals. - Develop a marketing strategy for the assigned segments that targets ideal customer profiles (ICPs), priority market tiers, and buyer personas to drive new customer acquisition, existing account expansion, and retention. - Define, own, and maintain segment ICP definitions and buyer persona maps — including target buyer profiles, pain points, motivations, objections, and trust signals, updating them as markets evolve and win/loss data shifts. - Conduct segment-specific research — including buyer interviews, surveys, win/loss analysis, and industry data synthesis — and translate insights into tailored marketing programs, messaging updates, and sales tools. - Develop vertical-specific content and enablement assets, including messaging & positioning, brochures, videos, industry guides, segment specific web pages, assist with case studies, solution playbooks, and pitch decks. - Support strategic segment-focused projects such as market mapping and quarterly initiatives, while proactively identifying the next 1-, 3-, and 5-year opportunity to propose back to the business. - Articulate Geotab's unique value proposition across assigned segments and align strategies with key purchase drivers, integrating them into segment playbooks and strategy briefs. - Partner with Product Marketing to support product launches, providing segment tiering input, translating product messaging into segment-specific value propositions, proof points, and objection handling, and developing segment-specific launch materials for sales and the field. - Partner with sales and business development to create and execute segment and account specific growth strategies that drive brand awareness, market position, and demand. - Serve as a thought leader, subject matter expert, and lead marketing advocate for Geotab's assigned segments, including representing Geotab at industry events and with key associations. - Create a robust relationship development and engagement strategy for chosen associations to enhance Geotab's visibility, influence, and networking presence in the industry. That's a lot; we can keep as list items. Requirements: from What You'll Bring To This Role: - Minimum 8+ years of proven experience in a marketing strategy role, with preference for B2B SaaS or technology organizations. - 3+ years of experience in vertical or segment-specific B2B marketing, with demonstrated familiarity with industry-specific buyer dynamics, relevant compliance considerations, and complex procurement processes. - Bachelor’s degree in Marketing, Communications, Business, or a related field, or an equivalent combination of education and relevant work experience. An MBA is an asset. - Experience in telematics, fleet management, or connected vehicle technology is advantageous. - Objective-focused, strategic, and outcomes-based mindset; able to operate independently and manage priorities, stakeholders, and deliverables without day-to-day direction. - Proven ability to conduct and synthesize segment research — buyer interviews, competitive intelligence, win/loss data — and translate findings into actionable strategy. - Excellent storyteller and analytical thinker who can back ideas with customer and market insights; comfortable building reports, interpreting performance data, and using data to inform decisions. - Demonstrated experience writing compelling value propositions and operationalizing them through messaging frameworks, marketing collateral, sales materials, and thought leadership content. - Outstanding cross-functional collaboration and communication skills, with a proven track record of cultivating strong relationships with sales teams. - Excellent project management, time management, and problem-solving skills with strong attention to detail. - Occasional travel of up to 20% may be required. We could also include "If you got this far, we hope you're feeling excited about this role! Even if you don't feel you meet every single requirement, we still encourage you to apply." That's more encouragement, maybe not needed but could be prose. Benefits: from Why Job Seekers Choose Geotab: - Flex working arrangements - Home office reimbursement program - Baby bonus & parental leave top up program - Online learning and networking opportunities - Electric vehicle purchase incentive program - Competitive medical and dental benefits - Retirement savings program Also note: "The above are offered to full-time permanent employees only". Could include as note. Schedule: from How We Work and remote/hybrid: - Flexible hybrid working model; systems, functions, programs and policies support both in-person and virtual work. - Welcomed and encouraged to come into offices as often as you like. - When working from home, required to have reliable internet connection with at least 50mb DL/10mb UL. - Virtual work supported with cloud-based applications, collaboration tools and asynchronous working. - Encourage work-life balance; online social events, chat rooms and gatherings. - Remote candidates across the United States; employees local to a Geotab office follow flexible hybrid model. - Occasional travel of up to 20% may be required (already in requirements but could be schedule). We'll keep travel in schedule maybe. We must not duplicate content; but travel appears both in requirements and schedule. We could keep it only once, maybe under Schedule as it's about work arrangement. But requirements also mention occasional travel. To avoid duplication, we could mention travel only under Schedule. However the requirement list includes it; but we could keep it there and not duplicate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we omit travel from requirements, we lose that detail. So better to keep it in requirements and not repeat in schedule. Or we could keep it in both but that's duplication; we should avoid duplicated lines. So we need to decide where to place it. Since it's about work arrangement, schedule seems appropriate. But it's also a requirement. I'd put it under Schedule and not repeat in Requirements. However the requirement list includes many other items; we can keep travel under Schedule and not duplicate. That would mean we omit travel from Requirements list. Is that summarizing away detail? We are removing a line but it's still present elsewhere. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we keep the detail somewhere else, it's preserved. So it's okay. Thus we will not include travel in Requirements list. Now we need to format. We'll start with

  About the role

  then a

  with the paragraph. Then

  Responsibilities

  then
  • each duty. Then

    Requirements

    then
    • each requirement (excluding travel). Then

      Benefits

      then
      • each benefit. Then

        Schedule

        then
        • each schedule item. We must ensure we don't