Sr Staff Outbound Product Manager - Data & Analytics

We need to output HTML fragment with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. We need to parse the posting: It includes Company Description, Job Description, Business Context, What You'll Do, Qualifications, Helpful Experience, Pay info, Benefits, Additional Information (Work Personas, etc). We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Additional Information" sections like Work Personas, Equal Opportunity Employer, Accommodations, Export Control Regulations, Fortune notice, Privacy Notice, etc. Also remove "I'm interested" repeated. We need to preserve substantive info: company description, job description, business context, what you'll do, qualifications, helpful experience, pay, benefits. We need to decide sections: About the role (maybe company description + job description?), Responsibilities (What You'll Do), Requirements (Qualifications?), Skills (maybe helpful experience?), Benefits, Pay. Schedule not present, so omit. We must not create sections with filler like "commensurate with experience". Pay is present: base pay range $190,900 - $334,100 plus equity etc. So we can include Pay section. Benefits: health plans, 401(k) with match, ESPP, matching donations, flexible time away plan, family leave programs. So Benefits section. Schedule: not mentioned, omit. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we can list bullet points from "What You'll Do". For qualifications we can list bullet points from Qualifications and maybe Helpful Experience? But we need separate sections: Requirements (maybe qualifications) and Skills (maybe helpful experience). However we need to avoid thin sections. Could combine qualifications and helpful experience into Requirements? But spec says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It's okay to have multiple similar sections if content exists. We'll decide. We have Qualifications bullet list (preferred location, 10+ years experience, etc). Helpful Experience list (experience supporting data platform, etc). Could treat Qualifications as Requirements, and Helpful Experience as Skills. Or we could have Requirements = Qualifications, Skills = Helpful Experience. We'll do that. About the role: combine Company Description and Job Description? The "About the role" could be a brief summary: maybe combine company description and job description overview. We'll include company description paragraph and job description paragraph (the first paragraph after "Job Description"). Responsibilities: bullet list from "What You'll Do". Requirements: bullet list from Qualifications. Skills: bullet list from Helpful Experience. Benefits: bullet list from benefits. Pay: paragraph with pay range. We must not include headings for empty sections. We must not include markdown fences. Let's extract content. Company Description paragraph: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people." Job Description paragraph after "Job Description": "ServiceNow is seeking a highly technical, customer obsessed Sr. Staff Outbound Product Manager to join the Data & Analytics product team responsible for Workflow Data Fabric and RaptorDB. This team is building the next generation of ServiceNow’s enterprise data platform, enabling customers to connect, process, and activate data across workflows at scale. This role sits at the intersection of data architecture, platform performance, analytics, AI readiness, and customer value. You will help shape how ServiceNow customers understand, adopt, and unlock value from advanced data capabilities, translating deep technical concepts into compelling product narratives, go-to-market strategies, customer-facing content, and field enablement." Business Context paragraph(s): "Business Context Workflow Data Fabric and RaptorDB Professional are strategically important growth areas within ServiceNow’s Data & Analytics portfolio. The business is already significant, with approximately $600M in revenue and a goal to grow to $1.5B by 2029. The opportunity is not simply to sell data as a standalone product, but to build a clear wraparound strategy for how data enhances ServiceNow’s value proposition across workflows, customer outcomes, enterprise AI readiness, and strategic deal pursuits. The right leader will identify the customer problem, craft the market narrative, and help scale field enablement and growth strategies through one-to-one, one-to-few, and one-to-many motions. This person will partner closely with product, engineering, sales, solution consulting, product marketing, and customer-facing teams to ensure the market understands the value of ServiceNow’s next-generation data platform." We could incorporate Business Context into About the role or Responsibilities? Probably About the role includes company description and job description; Business Context could be part of About the role as well. But we need to avoid duplication. We'll include Business Context as part of About the role maybe after job description. But we must not create filler. We'll keep About the role as a

  containing company description + job description + business context? Might be long but okay. Alternatively, we could have About the role = company description, Responsibilities = What You'll Do, Requirements = Qualifications, Skills = Helpful Experience, Benefits = benefits, Pay = pay. Business Context could be part of About the role or Responsibilities. I'll add it to About the role after job description. Now extract bullet points for Responsibilities from "What You'll Do": - Own the outbound product strategy for Workflow Data Fabric and RaptorDB Professional, translating complex data platform capabilities into clear customer value, differentiated positioning, and compelling market narratives. - Define and refine the core messaging, use cases, personas, competitive differentiation, and customer proof points that help technical and executive audiences understand why these products matter. - Partner closely with inbound product managers, engineering, product marketing, sales, solution consulting, and customer-facing teams to shape launch strategy, field readiness, growth motions, and adoption plans. - Serve as a product evangelist in customer briefings, executive conversations, analyst sessions, webinars, conferences, and strategic deal support, adapting the message for both technical practitioners and business decision-makers. - Translate technical concepts across data strategy, databases, integration, transactional and analytical processing, distributed systems, data management, platform performance, and AI readiness into business value. - Turn field feedback, customer insights, competitive intelligence, and adoption signals into actionable recommendations that influence roadmap priorities, GTM execution, and outbound investments. - Create high-impact enablement materials including sales playbooks, demos, solution briefs, competitive guides, launch narratives, training content, and executive-ready product storytelling. - Help establish and track success metrics for outbound initiatives, including launch readiness, seller adoption, customer engagement, pipeline influence, product adoption, and market feedback. Now Requirements from Qualifications bullet list (the lines start with *Preferred candidate location is within eastern timezone* then bullet list with asterisks). Let's extract: *Preferred candidate location is within eastern timezone* (this is a note, not a requirement? It's a preference. We'll include as a bullet maybe.) - 10+ years of enterprise software product management, outbound product management, technical product marketing, or go-to-market experience, with demonstrated product leadership at Sr. Staff / IC5 level. - Enterprise software experience is required, with a strong preference for candidates who have built, positioned, sold, or taken software products to market for external enterprise customers. - Product management or outbound product experience as a builder or seller of software, not solely as an internal IT practitioner, implementation owner, or user of similar technologies. - Deep fluency across data platforms, databases, integrations/iPaaS, cloud infrastructure, analytics, AI/ML data layers, distributed systems, transactional and analytical processing, or platform architecture, with specialized in-role experience in at least one of these areas. - Strong understanding of how data strategy, integration, data management, databases, and platform capabilities support enterprise AI and workflow transformation. - Experience working directly with enterprise customers and translating technical innovation into clear business value. - Exceptional communication and storytelling skills, with the ability to simplify complexity for technical practitioners, business decision-makers, sellers, executives, and customer stakeholders. - Proven ability to influence cross-functionally across product, engineering, marketing, sales, solution consulting, customer success, and field teams. - Strong organizational skills and ability to manage multiple strategic initiatives in a fast-moving, high-growth environment. We'll keep the location preference as a bullet maybe. Now Skills from Helpful Experience: - Experience supporting data platform, database, integration/iPaaS, infrastructure, analytics, AI/ML data layer, or enterprise SaaS platform products. - Experience delivering demos or supporting technical customer conversations, EBCs, sales engagements, analyst sessions, webinars, conferences, or strategic deal pursuits. - Experience developing field enablement, launch narratives, competitive positioning, customer proof points, executive messaging, and adoption programs. - Experience with federal customers or highly regulated enterprise markets is helpful. - US citizenship or green card status is preferred to support federal market customer opportunities. Now Benefits paragraph: "We also offer health plans, including flexible spending accounts, a 401(k) Plan with company match, ESPP, matching donations, a flexible time away plan and family leave programs." We can bullet list: - Health plans (including flexible spending accounts) - 401(k) Plan with company match - ESPP - Matching donations - Flexible time away plan - Family leave programs Now Pay paragraph: "For positions in this location, we offer a base pay of $190,900 - $334,100, plus equity (when applicable), variable/incentive compensation and benefits. Sales positions generally offer a competitive On Target Earnings (OTE) incentive compensation structure. Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as qualifications, skill level, competencies, and work location." We can summarize as a paragraph. Now we need to output HTML fragment with

  headings and

  or

  • . We must not include any extra text. Let's craft:

    About the role

    Company description paragraph + job description paragraph + business context paragraph(s). We'll combine into maybe two

    elements? The rule: use

    for prose. Could have multiple

    under same heading? Probably okay. We'll put each paragraph in its own

    . Thus:

    About the role

    It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people.

    ServiceNow is seeking a highly technical, customer obsessed Sr. Staff Outbound Product Manager to join the Data & Analytics product team responsible for Workflow Data Fabric and RaptorDB. This team is building the next