Product Success Technical Director

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Company description: not needed? It's part of description but we can include maybe as "About the role"? Actually "Company Description" could be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly. We need to preserve all substantive information, not repeat job title, not include Job ID, etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Work Personas", "Equal Opportunity Employer", "Accommodations", "Export Control Regulations", "From Fortune." etc. We need to include sections only when posting has real specific content. Let's extract content: Company Description: It all started when engineer Fred Luddy wrote code... (the paragraph). This is about company. Could be placed under "About the role"? Actually "About the role" is more about the role, but we could treat company description as "About the role"? Might be better to have a section "About the role" containing the role description summary (the "Job Description" part). The company description could be placed under "About the role" or maybe we could create a separate "About the company" but not in allowed headings. Since only allowed headings are those listed, we should fit content into those headings. The company description could be considered part of "About the role"? Not ideal but we can include it under "About the role" as introductory paragraph. Then "Job Description" includes paragraphs: "This role is an individual contributor position..." etc. That's role description; could go under "About the role" as well. Then "Why This Role Matters": could be part of responsibilities? Might be better as its own section? Not in list but we could incorporate into "Responsibilities". However we have allowed headings: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "Who You Are": that's qualifications/requirements. Then "Your Strengths Include": list of strengths (skills). Could go under Skills. Then "What You’ll Do": responsibilities. Then "What Success Looks Like": maybe also responsibilities or outcomes; could be part of Responsibilities. Then "Qualifications": includes pay range and benefits description. Actually the section titled "Qualifications" includes pay and benefits. But we need separate sections for Pay and Benefits if they have specific content. The posting says: "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 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. Compensation is based on the geographic location in which the role is located and is subject to change based on work location." Thus we have specific pay range and benefits details. So we should create a Pay section with the pay range and maybe note about equity etc. And a Benefits section with health plans, 401(k), ESPP, matching donations, flexible time away, family leave. We should not include filler like "commensurate with experience". The pay range is specific, so we include. We also have "Additional Information" sections: Work Personas, Equal Opportunity Employer, Accommodations, Export Control Regulations, From Fortune. Those are boilerplate/legal; we should remove. Thus final HTML will have sections:

About the role

containing company description + job description + why this role matters? Might be too much but okay. Better to split: About the role (company description + brief role summary), Responsibilities (What You’ll Do + Why This Role Matters + What Success Looks Like), Requirements (maybe not needed separate if we have Qualifications), Qualifications (Who You Are + Your Strengths Include?), Skills (Your Strengths Include), Pay, Benefits. But we must not create thin sections. Let's decide: - About the role: company description + role overview (first paragraph of Job Description: "This role is an individual contributor position..." plus maybe the "Team AI Adoption Engineering..." paragraph). That seems substantive. - Responsibilities: "Why This Role Matters", "What You’ll Do", "What Success Looks Like". Combine into a list of duties. - Requirements: maybe not needed if we have Qualifications and Skills. But we could have Qualifications section for "Who You Are" (experience, fluency). Skills section for "Your Strengths Include". Pay and Benefits separate. We need to avoid duplication. Let's extract content precisely. 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(s): "This role is an individual contributor position. Team AI Adoption Engineering is the delivery engine that turns ServiceNow's AI investments into live, referenceable customer outcomes. We are the front line for resolving the most complex agentic AI escalations across our install base. This is where agentic AI meets production reality—stabilizing at-risk go-lives, hardening deployments, and turning hard-won field learnings into reusable patterns that scale." "Why This Role Matters" paragraph(s): "Enterprises are moving agentic AI from compelling demos into production, and the hardest problems surface exactly at go-live: reliability, orchestration, grounding, and governance. When a strategic customer's agentic deployment is at risk, someone has to own that moment—diagnose root cause, make the right architectural call under pressure, restore executive confidence, and get the customer to green. As Product Success Technical Director – AI Adoption Engineering, you are the senior technical authority for agentic escalations and the architecture consulting that prevents them. You sit at the intersection of our most demanding customer situations, our platform's agentic capabilities, and the field patterns that determine whether AI adoption sticks. This role is built for a senior, customer-credible technical leader who can hold the room in a crisis, make sound architecture decisions in real time, elevate the team's technical bar, and remain hands-on enough to debug agentic systems in production." "Who You Are" paragraph(s): "You are a seasoned technical architect and escalation leader who stays calm under fire. You build trust with customer executives quickly, cut to root cause fast, and turn ambiguous, high-pressure situations into stabilized outcomes and reusable assets. You are deeply fluent in both the ServiceNow platform and modern agentic AI, and you elevate the people around you through expertise and execution rather than authority." "Your Strengths Include" bullet list (actually sentences separated by line breaks): - Root-cause diagnosis and resolution of complex, production agentic AI systems - Designing resilient agentic architectures (LLM integration, RAG, multi-agent orchestration, guardrails, and governance) - Executive communication and trust-rebuilding during high-stakes escalations - Codifying escalation playbooks, reference architectures, and diagnostic tooling that scale beyond any one person - Coaching and elevating technical teams - You embody ServiceNow values: Wow our Customers Win as a Team Stay Hungry and Humble Create Belonging "What You’ll Do" bullet list: - Own the Hardest Agentic Escalations Front and resolve the most complex, highest-visibility agentic AI escalations across the install base, owning path-to-green for at-risk and RED go-lives. - Lead cross-functional resolution efforts, aligning account teams, Product, and Engineering under a single technical plan. - Serve as the calm, credible technical voice with customer executives when confidence in an AI deployment is on the line. - Provide Consulting-Grade Technical Architecture Design and validate agentic solution architectures spanning Now Assist, AI Agents, Virtual Agent, multi-agent orchestration, RAG and knowledge grounding, integrations, and guardrails/governance via AI Control Tower. - Advise customers and field teams on the best-practice patterns that de-risk agentic adoption before problems reach production. - Set the architectural direction for how we deliver reliable, governable agentic AI at enterprise scale. - Elevate Team Technical Excellence Set the technical bar for the team's escalation and architecture work, and mentor engineers toward that bar. - Codify reusable escalation playbooks, reference architectures, and diagnostic tooling so hard-won solutions become repeatable capability, not tribal knowledge. - Raise team standards for reliability, reuse, and executive-grade communication. - Close the Loop to Product Act as a strategic conduit between field escalations and Product/Engineering. Convert escalation patterns and architecture gaps into structured, prioritized input that hardens agentic capabilities before they become the next escalation. - Partner with Product and Engineering to stress-test emerging capabilities and shape roadmap where reliability and governance are decisive for adoption. "What Success Looks Like" bullet list: - Customer Impact: Strategic customer engagements result in measurable outcomes, referenceable wins, and reusable assets. - Team Growth: AI Futures team members demonstrate improved storytelling, customer fluency, demo quality, and execution consistency. - Reusable Value: Demos, frameworks, and patterns influenced by this role see broad adoption across field teams, SCs, and customer pilots. - Product Influence: Customer-driven insights lead to platform improvements, roadmap shifts, or feature hardening prior to GA. - Trusted Technical Advisor: Customers, field teams, PM, and Engineering view you as a credible and dependable leader who bridges invention and adoption. "Qualifications" paragraph (the pay/benefits): "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 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. Compensation is based on the geographic location in which the role is located and is subject to change based on work location." We need to separate Pay and Benefits. Pay: base pay range $199,100 - $348,400, plus equity (when applicable), variable/incentive compensation. Also note OTE for sales positions but not relevant? It's still compensation detail. We'll include. Benefits: health plans including flexible spending accounts, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan, family leave programs. We should not include the sentence about compensation based on geographic location etc? That's still part of compensation but maybe we can include in Pay section as note. Now we need to output HTML fragment only, no extra text. We'll structure:

About the role

Company description paragraph + role overview paragraphs (maybe combine).

Responsibilities