Senior Staff Strategic Operations

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate. We need to parse the job description. Company description: not needed? It's part of posting but we can include maybe as part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections. Let's parse the posting: - Company Description: not needed? It's not a required heading; we could include as part of About the role? But we have "About the team" etc. The job description includes "About the team: Office of Business Strategy manages the portfolio, strategy and operations for the Cloud Engineering & Support (CES) organization. The CES organization is accountable for delivering autonomous infrastructure with speed and efficiency—while providing the enterprise-grade services our customers rely on." Then "What You Get To Do In This Role" includes bullet-like sentences. Then "Qualifications Preferred Qualifications:" then list. Then "Basic Qualifications" with experience/education. Then "For positions in this location, we offer a base pay of $171,900 - $300,800, plus equity (when applicable), variable/incentive compensation and benefits." Then "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." Then "Compensation is based on the geographic location in which the role is located and is subject to change based on work location." Then "Additional Information Work Personas ..." (maybe schedule? Not exactly schedule but work persona: flexible, remote, or required in office). That could be schedule info. We need to decide sections. We have content for: - About the role: could include "About the team" and maybe "What You Get To Do In This Role". Actually "About the role" could be a summary of responsibilities. But we also have a separate "Responsibilities" section. We have responsibilities described in "What You Get To Do In This Role". That's a list of duties. We have qualifications: Preferred Qualifications and Basic Qualifications. We have skills: maybe included in qualifications but we could separate. We have Benefits: health plans etc. We have Pay: base pay range. We have Schedule: Work Personas (flexible, remote, or required in office). That's schedule info. Thus we can create sections: About the role (maybe short description), Responsibilities, Qualifications (maybe combine Preferred and Basic?), Benefits, Pay, Schedule. But we need to avoid thin sections. Could combine Qualifications and Skills? But we have separate headings allowed: Qualifications, Skills. We could put qualifications under Qualifications, and maybe skills under Skills (like communication, facilitation, etc). However the qualifications already list many skills. Might be redundant. Better to follow typical structure: About the role (short paragraph), Responsibilities (ul), Qualifications (ul), Benefits (ul), Pay (p), Schedule (p). Skills maybe not needed if covered. But we must include only sections with real specific content. Let's see if we have enough for each. About the role: we have "About the team" description. That's specific. Could be used as About the role. Responsibilities: we have bullet list from "What You Get To Do In This Role". That's specific. Qualifications: we have Preferred Qualifications and Basic Qualifications. That's specific. Benefits: we have health plans etc. That's specific. Pay: we have base pay range. That's specific. Schedule: we have Work Personas description. That's specific. Thus we can include all six sections. We must not include fluff like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we don't repeat. We need to format as HTML fragment: use

  for each section heading. Then content: for lists use

  • . For prose use

    . We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract details precisely. About the role: The posting has "Company Description" and "About the team". The "Company Description" is a narrative about ServiceNow. Might be considered part of About the role? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put About the role heading and include both company description and about the team? But we must not repeat job title. The company description is substantive. Let's include it. Thus About the role content: combine Company Description paragraph and About the team paragraph. 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." About the team: "Office of Business Strategy manages the portfolio, strategy and operations for the Cloud Engineering & Support (CES) organization. The CES organization is accountable for delivering autonomous infrastructure with speed and efficiency—while providing the enterprise-grade services our customers rely on." We can combine into a single

    or two

    s. Probably one

    with both sentences separated by space. Now Responsibilities: The "What You Get To Do In This Role" paragraph includes multiple sentences, each describing a duty. We need to turn each into

    . Let's parse: - Organize complex, ambiguous problems into prioritized milestones, deliverables, dependencies, and success criteria — designing programs to deliver specific strategic outcomes and drive relentless accountability against them - Develop and implement scalable processes, templates, and training to ensure program delivery and process adoption; oversee change management efforts, guiding teams through organizational transitions and improvements - Establish governance frameworks and lead executive-level meetings and cross-functional events; serve as the go-to source of leadership, transparency, and visibility — clearly communicating objectives, status, risks, and results while ensuring surgical execution and handoffs across workstreams Also earlier sentences: "In this role, you will drive the organization’s most critical cross-functional priorities and strategic programs— operating at the intersection of strategy and execution and setting the standard for how high-impact programs are designed, governed, and run at scale.This person is effective at building relationships, collaborating, and influencing others; they must also be highly experienced working with senior executives across various geographies and functions." We need to decide if those are responsibilities too. They are part of role description. Could be included as responsibilities as well. Let's include them as separate list items. Thus responsibilities list items: 1. Drive the organization’s most critical cross-functional priorities and strategic programs— operating at the intersection of strategy and execution and setting the standard for how high-impact programs are designed, governed, and run at scale. 2. Effective at building relationships, collaborating, and influencing others; must also be highly experienced working with senior executives across various geographies and functions. 3. Organize complex, ambiguous problems into prioritized milestones, deliverables, dependencies, and success criteria — designing programs to deliver specific strategic outcomes and drive relentless accountability against them. 4. Develop and implement scalable processes, templates, and training to ensure program delivery and process adoption; oversee change management efforts, guiding teams through organizational transitions and improvements. 5. Establish governance frameworks and lead executive-level meetings and cross-functional events; serve as the go-to source of leadership, transparency, and visibility — clearly communicating objectives, status, risks, and results while ensuring surgical execution and handoffs across workstreams. Check for duplication: The second item is a bit like a skill but it's a responsibility attribute. We'll keep. Now Qualifications: We have Preferred Qualifications and Basic Qualifications. Preferred Qualifications bullet list (each sentence seems a separate bullet). Let's extract: - Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry. - Proven project/program management experience involving many cross-functional teams - Solid organizational skills with high regard for quality - Strong collaboration and relationship-building skills – able to work well with many different types of personalities in various functions. - Masterful in the art of bringing people together - Excellent communication skills - Ability to communicate, document, and present complex technical issues in a concise and efficient manner for a variety of audiences - Experienced and confident in creating slides and presenting to executives - Must possess effective listening skills and comfortable asking powerful questions - Passion for working with people in technical environments - Proven leadership skills to influence and motivate without authority. True servant leader - Proven facilitation skills to lead/drive a variety of program events - Excellent negotiation and conflict management skills Basic Qualifications: "12 years of project/program management experience in mid/large size companies, ideally in a software engineering/product development organization with a Bachelor's degree; or 8 years and a Master's degree; or a PhD with 5 years experience; or equivalent experience." We need to include that as a qualification. Thus Qualifications section could combine both Preferred and Basic as a list. Or we could split into Requirements and Qualifications? The instruction includes Requirements heading as possible. But we have qualifications. We could treat Requirements as Basic Qualifications and Qualifications as Preferred? But we have both headings allowed: Requirements, Qualifications, Skills. To avoid thin sections, we could combine all into Qualifications. But we need to follow instruction: Use headings as examples; not required to use all. So we can just have Qualifications heading and include all qualification items (both basic and preferred). That's fine. Thus Qualifications list items: - 12 years of project/program management experience in mid/large size companies, ideally in a software engineering/product development organization with a Bachelor's degree; or 8 years and a Master's degree; or a PhD with 5 years experience; or equivalent experience. - Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry. - Proven project/program management experience involving many cross-functional teams - Solid organizational skills with high regard for quality - Strong collaboration and relationship-building skills – able to work well with many different types of personalities in various functions. - Master