Product Success Technical Director

We need to output HTML fragment with sections: About the role? Actually we need headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. We must not repeat job title. We need to extract content. From posting: Company Description (maybe "About the role"? Actually "Company Description" could be considered "About the role"? The instruction: use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we map sections accordingly. We have: - Company Description: description of ServiceNow. Could be "About the role"? Actually "About the role" is about the role, not company. But we have no explicit "About the role". However we have "Job Description" which includes role context. Could treat that as "About the role". But we need to decide. Better: Use "About the role" for the initial description of the role (the paragraph after Job Description? Actually there is "Job Description" heading then paragraphs describing role. So we can put that under "About the role". Or we could treat "Job Description" as "About the role". We'll do that. Then we have "Why This Role Matters" maybe part of responsibilities? Could be part of responsibilities. We have "Who You Are" maybe qualifications. We have "Your Strengths Include" maybe skills. We have "What You’ll Do" responsibilities. We have "What Success Looks Like" maybe outcomes, could be part of responsibilities or separate but not required. We have "Qualifications" section with bullet list (numbered). That's qualifications. We have "Preferred Qualifications" maybe also qualifications. We have "For positions in this location, we offer a base pay of $199,100 - $348,400, plus equity..." that's Pay. We have 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." That's Benefits. We have schedule? Not mentioned. No schedule. We have "Work Personas" etc but that's extra info maybe not needed; we can drop as boilerplate? It's not cookie/navigation/legal/EEO etc but it's about work flexibility. Might be considered relevant but not in headings list. Could be omitted as not required. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from sections we keep. We must not include boilerplate like EEO, equal opportunity, accommodations, export control, privacy notice, etc. Remove those. We must not repeat job title. We must not put Job ID/requisition numbers as headings (none present). We must output only HTML fragment. Let's extract content: Company Description: "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." That's substantive. Job Description / About the role: The paragraphs after "Job Description" heading: "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." Then "Why This Role Matters": paragraphs: "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." We could combine these under "About the role" or maybe separate "Why This Role Matters" as part of responsibilities. But we only have allowed headings; we could put all under "About the role". That's fine. Next "Who You Are": "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." Then "Your Strengths Include": bullet list (but not formatted as bullet in text). It's a sentence with colon then list separated by commas? Actually: "Your Strengths Include 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" We can turn each into

under a

under a heading "Skills". Or we could treat as Skills section. Next "What You’ll Do": responsibilities bullet-ish paragraphs: - "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." We can format as
• each. Next "What Success Looks Like": paragraphs: - "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." We could treat as maybe "Responsibilities" or separate but we don't have a heading for success metrics. Could include under "Responsibilities" as additional bullet points. But we already have responsibilities; we could add these as part of responsibilities or maybe under a separate heading like "Impact". Not in allowed list. Safer to include under "Responsibilities" as additional bullets. Next "Qualifications": numbered list: 1. 15+ years in technical leadership spanning enterprise architecture, complex solution delivery, and/or customer-facing escalation resolution. 2. Deep, hands-on expertise architecting and troubleshooting production AI/agentic systems: LLM integration, RAG, multi-agent orchestration, prompt and guardrail design, and reliability/evaluation. 3. Demonstrated success owning and resolving high-severity, executive-visible customer escalations. 4. Strong executive presence, with the ability to rebuild customer trust and lead a room during a crisis. 5. Proven ability to influence without authority across Product, Engineering, field, and customer executive stakeholders. 6. A track record of turning complex engagements into reusable frameworks, playbooks, or reference architectures. Then "Preferred Qualifications": bullet-ish sentences: - Deep ServiceNow platform expertise (Now Assist, AI Agents, Virtual Agent, Now Assist Skill Kit, AI Control Tower) or comparable enterprise SaaS depth. - Experience standing up or scaling an escalation, go-live, or technical SWAT function. - Familiarity with agentic governance, observability, and evaluation frameworks. - Multi-region or global delivery experience. We could combine qualifications and preferred qualifications under "Qualifications" heading, maybe separate subheadings? But only allowed headings list includes Qualifications. We could include both required and preferred under same heading, maybe separate paragraphs. Next 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 need to keep that. 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." We should keep that. Schedule: none. We must not include boilerplate like "Additional Information Work Personas", "Equal Opportunity Employer", "Accommodations", "Export Control Regulations", "From Fortune...", "Privacy Notice", etc. Now produce HTML. Structure:

  About the role

  Company description paragraph(s) + job description paragraphs + why this role matters + who you are? Actually "Who You Are" could be part of Qualifications? But we have separate Qualifications heading. Better to put "Who You Are" under About the role? It's more about personal attributes; could be part of Qualifications. But we already have Qualifications heading for required qualifications. "Who You Are" is descriptive of ideal candidate, could be part of Qualifications. However we have separate "Your Strengths Include" which is skills. We need to decide mapping. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: Company description + role