Manager, ServiceNow Platform Manager

We need to output HTML fragment with headings

for 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 preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not create sections with placeholder text. We need to parse the posting. Key sections: - About Vantage (company description) maybe "About the role"? Actually "About Vantage" is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. We have: Position Overview: description of role, location, reporting, etc. That could be "About the role". Essential Job Functions: list of duties (Platform Governance & Standards, Roadmap, Intake & Prioritization, Team Leadership, Delivery Readiness & Risk Management, Vendor, Metrics & Escalation Ownership). Those are responsibilities. Then there is a "Duties" section that repeats some of those but we can combine. Job Requirements: list of requirements. Additional Details: Salary Range, benefits description, etc. Travel requirements: 20% Or could increase as business needs. Physical Demands And Special Requirements: we might include under Requirements? But it's not a typical section; but we can include as part of Requirements maybe. However we should not create sections with placeholder text. Physical demands is specific content; we could include under Requirements or maybe a separate section? The allowed headings list does not include Physical Demands, but we could incorporate into Requirements or maybe not create a new heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use others? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Physical demands could go under Requirements (maybe as a bullet). Travel could go under Schedule? Actually Schedule heading could include travel expectations? But schedule usually about work schedule (remote, hybrid). Travel could be separate but not in list. Could put under Requirements as a bullet. Benefits: we have description of benefits. Pay: Salary range. Schedule: location/hybrid remote details. Qualifications vs Requirements vs Skills: There's overlap. We need to decide what to put where. The posting has "Job Requirements" which includes experience, skills, etc. Could map to Requirements. Qualifications maybe similar; but we could combine. However we should not create thin sections. Perhaps we can have Requirements (includes experience, skills, qualifications). Skills maybe separate if we have distinct skills list. The posting includes "Strong stakeholder communication skills", "Ability to manage ServiceNow with practical judgment", etc. Those are abilities/skills. Could put under Skills. Qualifications maybe education? Not present. Could omit Qualifications if no specific content. Thus sections: - About the role (Position Overview) - Responsibilities (Essential Job Functions + Duties) - Requirements (Job Requirements + Physical Demands + Travel) - Skills (maybe subset of Requirements but we can separate abilities) - Benefits (Additional Details benefits) - Pay (Salary Range) - Schedule (Location/hybrid/remote) We must not repeat job title. Must not include boilerplate like EEO, etc. We need to preserve all substantive information. Let's extract. About the role (Position Overview): "This role can be based in Denver, CO following our flexible work policy (3 days in-office, 2 days flexible). Or remote, US. The Manager, ServiceNow Platform Owner is accountable for day-to-day platform prioritization, roadmap coordination, governance, readiness, supportability, and practical business value tracking for the ServiceNow platform. Reporting to the Platform Director, this role translates platform strategy into practical priorities, coordinates intake and delivery readiness, and ensures stakeholder commitments are visible, sequenced, and supportable. The role may be consulted on adoption planning and adoption impacts but is not accountable for platform adoption. This position directly manages a ServiceNow Architect and ServiceNow Product Owner and works in close partnership with development, architecture, operations, security, SPM, PMO, finance, procurement, vendors, and business stakeholders; however, it does not directly oversee or manage the development team." We should keep that as prose

. Responsibilities: combine Essential Job Functions and Duties (avoid duplication). Let's list distinct responsibilities: From Essential Job Functions: - Platform Governance & Standards: * Define practical standards for ServiceNow intake, prioritization, roadmap management, architecture review, release readiness, documentation, supportability, adoption input, and value tracking. * Run ServiceNow governance routines and keep decisions, tradeoffs, risks, dependencies, and escalations visible and traceable for the Platform Director and stakeholders. * Continue maturing ServiceNow governance so it can act as a reusable standard for other enterprise platforms. * Ensure ServiceNow functional boards are operational, decision-oriented, and supported by companion product owners who represent functional priorities. * Reduce shadow work, unclear ownership, duplicate configuration, unmanaged customization, and unapproved commitments through clear ServiceNow guardrails. - Roadmap, Intake & Prioritization: * Maintain the ServiceNow roadmap, informed by business priorities, platform strategy, technical considerations, dependencies, risks, releases, and decisions. * Ensure work enters through approved intake and is ready enough to sequence responsibly. * Own ServiceNow platform content and communications channels, including the SharePoint site/web page, release notes, and bi-weekly platform updates; stakeholder and program updates remain PMO-owned. * Manage ServiceNow platform prioritization and coordinate funding assumptions, delivery capacity inputs, architecture decisions, and risk tradeoffs with the Platform Director and partner teams. - Team Leadership: * Lead, coach, and develop the ServiceNow Architect and ServiceNow Product Owner, ensuring clear ownership for technical direction, product priorities, roadmap execution, stakeholder engagement, and platform outcomes. * Set expectations for ServiceNow ownership, technical decision discipline, product management, communication, stakeholder management, governance participation, and measurable outcomes. * Support hiring, role clarity, performance feedback, development planning, workload balance, and succession planning. * Build an accountable ServiceNow team culture that balances speed, quality, platform health, business value, and sustainable operations. - Delivery Readiness & Risk Management: * Coordinate with development to ensure ServiceNow delivery commitments align to approved decisions, capacity inputs, architecture readiness, release timing, and support readiness. * Set minimum readiness expectations for testing, documentation, support handoff, rollback planning, post-release ownership, and adoption-related inputs needed by business or change owners. * Escalate risks affecting ServiceNow platform health, stakeholder commitments, budget, staffing, compliance, or enterprise outcomes. * Serve as a consulted partner on ServiceNow platform health, technical debt, integration sprawl, customization risk, support complexity, data quality, and value realization where development or execution ownership sits with other teams. - Vendor, Metrics & Escalation Ownership: * Own large program statements of work with vendors, ensuring scope, deliverables, assumptions, dependencies, handoffs, and acceptance criteria are documented and aligned to ServiceNow platform priorities. * Use metrics, usage insights, incident trends, backlog health, vendor performance inputs, and stakeholder feedback to inform prioritization recommendations, SOW adjustments, and resourcing discussions. * Set day-to-day ServiceNow governance expectations, require decision traceability, return work that is not ready, manage platform prioritization within agreed guardrails, own large program vendor SOWs, and escalate priorities, risks, funding needs, staffing needs, or exceptions to the Platform Director. From Duties (some overlap): - Partner with the Platform Director to translate ServiceNow strategy into an actionable platform roadmap. - Coordinate intake, prioritization, governance, and readiness routines across ServiceNow stakeholders. - Maintain clear visibility into platform commitments, tradeoffs, risks, dependencies, and decisions. - Partner with architecture, development, security, operations, finance, procurement, PMO, and business stakeholders to sequence work responsibly. - Ensure ServiceNow communications, release notes, bi-weekly platform updates, and platform content are clear, current, and aligned to approved decisions. - Lead the ServiceNow Architect and ServiceNow Product Owner through clear expectations, coaching, prioritization discipline, and role clarity. - Support ServiceNow functional boards and companion product owners in representing business priorities and decision needs. - Guide vendor SOW development and alignment to platform priorities, delivery assumptions, dependencies, and acceptance criteria. - Monitor platform health indicators, backlog health, incident trends, stakeholder feedback, and adoption-related inputs to inform prioritization recommendations. - Escalate risks, issues, resourcing needs, funding implications, or exceptions that impact ServiceNow platform outcomes. Many of these duplicate earlier points. We'll combine unique items, but we must preserve all substantive info; we can include duplicates but better to avoid redundancy. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicates are still substantive; but we could keep them as they appear; but we might risk being considered summarizing away? If we remove duplicates, we might lose some info (though it's same). Safer to keep them as they appear, but we can combine similar bullet points to avoid repetition while still preserving meaning. The instruction says do not summarize away detail; summarizing could be considered losing detail. But merging duplicate statements that are identical in meaning might be okay? It's ambiguous. Safer to keep them as separate bullet points even if similar. However that could be lengthy but okay. We'll produce a

• list for responsibilities. We'll include all bullet points from Essential Job Functions and Duties, maybe deduplicate obvious identical sentences. Let's list them: Essential Job Functions bullets: 1. Define practical standards for ServiceNow intake, prioritization, roadmap management, architecture review, release readiness, documentation, supportability, adoption input, and value tracking. 2. Run ServiceNow governance routines and keep decisions, tradeoffs, risks, dependencies, and escalations visible and traceable for the Platform Director and stakeholders. 3. Continue maturing ServiceNow governance so it can act as a reusable standard for other enterprise platforms. 4. Ensure ServiceNow functional boards are operational, decision-oriented, and supported by companion product owners who represent functional priorities. 5. Reduce shadow work, unclear ownership, duplicate configuration, unmanaged customization, and unapproved commitments through clear ServiceNow guardrails. 6. Maintain the ServiceNow roadmap, informed by business priorities, platform strategy, technical considerations, dependencies, risks, releases, and decisions. 7. Ensure work enters through approved intake and is ready enough to sequence responsibly. 8. Own ServiceNow platform content and communications channels, including the SharePoint site/web page, release notes, and bi-weekly platform updates; stakeholder and program updates remain PMO-owned. 9. Manage ServiceNow platform prioritization and coordinate funding assumptions, delivery capacity inputs, architecture decisions, and risk tradeoffs with the Platform Director and partner teams. 10. Lead, coach, and develop the ServiceNow Architect and ServiceNow Product Owner, ensuring clear ownership for technical direction, product priorities, roadmap execution, stakeholder engagement, and platform outcomes. 11. Set expectations for ServiceNow ownership, technical decision discipline, product management, communication, stakeholder management, governance participation, and measurable outcomes. 12. Support hiring, role clarity, performance feedback, development planning, workload balance, and succession planning. 13. Build an accountable ServiceNow team culture that balances speed, quality, platform health, business value, and sustainable operations. 14. Coordinate with development to ensure ServiceNow delivery commitments align to approved decisions, capacity inputs, architecture readiness, release timing, and support readiness. 15. Set minimum readiness expectations for testing, documentation, support handoff,