Principal Inbound Product Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting: It includes Company Description, Job Description, Key Responsibilities, Qualifications, Compensation (base pay range, equity, variable/incentive compensation, benefits), Additional Information (Work Personas, etc). We need to extract substantive content. We need sections: About the role (maybe from Job Description intro). Responsibilities (Key Responsibilities). Requirements (maybe Qualifications? Actually Qualifications is separate). Skills maybe from qualifications? But we can combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: Could be the Job Description paragraph(s) describing role: "We’re not yesterday’s IT department...". That's descriptive. We'll put that in About the role. - Responsibilities: Key Responsibilities bullet list. - Requirements: maybe the qualifications list? But Qualifications heading also present. The posting has "Qualifications" section with bullet list. So we can put Requirements maybe as "Experience and background"? But we have both Requirements and Qualifications headings. We need to decide what goes where. Typically Requirements are mandatory qualifications; Qualifications could be preferred. But we can split: Requirements: the bullet list under "To be successful in this role you have:" which includes 12+ years experience etc. Qualifications: maybe the same? Actually that list is qualifications. The posting also has "Qualifications" heading exactly. So we should put that content under Qualifications heading. Then Requirements could be maybe something else? There's no separate Requirements section besides that. Could we treat the bullet list as Requirements and not have Qualifications? But we have both headings allowed; we should only include sections with real content. If we put the same content under both, that's duplication. Better to assign: Requirements: the bullet list (experience, technical depth, etc). Qualifications: maybe we can note "None beyond those listed" but we shouldn't create filler. So we should omit Qualifications if no distinct content. However the posting explicitly has a "Qualifications" heading with bullet list. So we should treat that as Qualifications. Then Requirements maybe we can derive from earlier sentences like "As a Principal Product Manager, you will own..." but that's more responsibilities. Hmm. We could treat Requirements as the bullet list under "To be successful in this role you have:" and Qualifications as maybe the same but we could skip Qualifications to avoid duplication. But the instruction: "include a section ONLY when the posting has real, specific content for it". If we treat the bullet list as both Requirements and Qualifications, that would be duplicate content, but still specific. However duplication might be considered not ideal but not prohibited. Safer to follow the posting: there is a "Qualifications" section with bullet list. So we will output Qualifications with that list. For Requirements, maybe we can extract from the job description: "As a Principal Product Manager, you will own the Now Engage platform end to end..." etc. But those are responsibilities. There's no separate "Requirements" besides qualifications. Could we treat the bullet list as Requirements and then not have Qualifications? But the posting explicitly labels it Qualifications, so we should respect that. Thus we will have: - About the role: from Job Description paragraphs (maybe first two paragraphs before Key Responsibilities). We'll include the descriptive text about Digital Technology, role description. - Responsibilities: from Key Responsibilities bullet list. - Qualifications: from the bullet list under "To be successful in this role you have:". - Benefits: from "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." - Pay: from "For positions in this location, we offer a base pay of $199,100 - $348,400, plus equity (when applicable), variable/incentive compensation and benefits." - Schedule: Not mentioned explicitly. There's no schedule info. So we omit Schedule. - Skills: Not separate; maybe we could extract from qualifications but we already used them. Could we create Skills section from technical depth etc? But we might avoid duplication. Better to omit Skills if no distinct content. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Check if any other sections like "About the role" could be split into "About the role" and "Company Description". But we follow instruction. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include / tags. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact details. Let's extract text. 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 paragraphs: "We’re not yesterday’s IT department, we're Digital Technology. The world around us keeps changing and so do we. We’re redefining what it means to be IT with a mindset centered on transformation, experience, AI-driven automation, innovation, and growth. We’re all about delivering delightful, secure customer and employee experiences that accelerate ServiceNow’s journey to become the defining enterprise software company of the 21st century. And we love co-creating, using, and highlighting our own products to do it. Ultimately, we strive to make the world work better for our employees and customers—when you work in ServiceNow Digital Technology, you work for them. As a Principal Product Manager, you will own the Now Engage platform end to end — a ServiceNow platform serving customers, partners, and employees who support customers. Now Engage is central to how ServiceNow helps customers achieve value quickly, with a commitment to measurable time to value within the first 100 days. You will partner closely with business, engineering, product, architecture, and senior stakeholders to define the roadmap, shape AI-driven capabilities, and deliver high-impact platform experiences that accelerate adoption and improve fulfillment, support, and growth outcomes. As a Technical Product Manager, you will drive the platform, tools, and technologies that power ServiceNow's post-sale customer success experience. You will help consolidate fragmented tooling, create a real-time view of the customer, surface AI-driven insights, and build AI-native workspace and agent experiences that improve outcomes for customers, partners, employees, and the business. As the product and technology partner to Customer Success, you will operate with transparency, urgency, and strong product judgment, making clear roadmap tradeoff decisions and aligning teams around measurable business impact. You will bring business and technical acumen to the role — fluent in system design, architecture, data flows, integrations, and AI/ML concepts — enabling you to partner credibly with engineering, challenge assumptions, and write product requirements that teams can execute. This is a high-visibility, high-accountability role that requires strong stakeholder management, product sense, and the ability to ship internal and partner-facing tools from concept through launch and adoption. Success will be measured by customer time to value, customer adoption, and the quality of execution against roadmap priorities." Key Responsibilities bullet list: - Product Strategy & Roadmap: Own the Now Engage product strategy and roadmap, including AI-native workspace, SPM integration, and agent capabilities. - Execution & Delivery: Drive product requirements, prioritization, delivery, adoption, and outcome measurement across complex platform initiatives. - Executive & Stakeholder Alignment: Partner with senior leaders, business stakeholders, engineering, product, and architecture to align on priorities, tradeoffs, and impact. - Platform & Technical Depth: Apply strong technical judgment across system design, integrations, data flows, workflows, and AI-enabled capabilities. - AI Innovation: Identify practical AI opportunities that improve customer visibility, fulfiller productivity, platform intelligence, and time to value. Qualifications bullet list (starting with "To be successful in this role you have:"): each line starts with a number? Actually it's a paragraph with numbered items? Let's copy: "To be successful in this role you have: 12+ years of product management experience, including experience owning complex internal platforms, employee-facing tools, partner-facing tools, delivery/PSA tooling, or enterprise workflow products Experience shipping products or platforms used by employees, internal teams, partners, or other enterprise users, with an understanding of the business process complexity behind internal tooling Strong technical depth in system design, architecture, integrations, data flows, APIs, workflows, and AI-enabled product capabilities Fluency in AI product capabilities and experience integrating AI into enterprise workflows, with the judgment to distinguish high-value AI use cases from areas where automation may introduce risk. Stay knowledgeable of industry trends and emerging technologies to drive innovation within the product portfolio and encourage a culture of experimentation, validation, and learning within the team. Track record writing high-quality product requirements that create clarity for engineering, business stakeholders, and executive reviewers Proven track record owning a complex, cross-functional product portfolio from strategy through delivery and outcome measurement Demonstrated ability to ship integrations across systems you don't control, and to negotiate scope with their owners without escalating every time Comfort launching with deliberate manual gaps and a credible plan to close them Strong written skills, producing documents that engineering, business and executives can evaluate Judgement to operate unsupervised on scope and sequencing, and to know which decisions belong to a sponsor Strong operator mindset: comfortable holding accountability for outcomes across organizational boundaries" We need to keep each as

• . Benefits: "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." Pay: "For positions in this location, we offer a base pay of $199,100 - $348,400, 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 should keep that as prose. We must not include boilerplate like Equal Opportunity Employer, Accommodations, Export Control Regulations, etc. Now construct HTML. We'll have:

  About the role

  ... (combined company description + job description? Actually About the role should be role description; we could include company description as part of About the role? Might be okay but better to separate: About the role could be the job description paragraphs (the role). Company description maybe not needed. But we have to preserve ALL substantive information; we cannot drop company description. So we need to include it somewhere. Could be part of About the role as introductory paragraph. We'll include both company description and role description in About the role

  maybe multiple

  tags. Thus About the role: include company description paragraph(s) and then the role description paragraphs (the "We’re not yesterday’s IT department..." etc). We'll separate into multiple

  for readability. Responsibilities:

  Responsibilities

  with each bullet as
  • . Qualifications