ITOM Solution Architect

We need to output HTML fragment with sections for headings present: About the role? Not present. The posting includes Company Description, Job Description, What You'll Do, Why join us, Qualifications, Additional Information (but we need to filter out boilerplate). We need to include sections only when posting has real specific content. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if applicable, but we can also use other headings? Probably we should map content to those standard headings where appropriate. The posting includes: Company Description (maybe not needed as heading? Could be "About the role"? Actually company description is about the company, not role. Could be omitted? The instruction: "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." It doesn't forbid other headings besides those examples, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where relevant. So we need to decide which sections map. We have content: - Company Description: could be considered "About the role"? Not exactly. Maybe we can treat as "About the role" (though it's about company). But we could also omit company description if not needed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep company description. We could put it under a heading like "About the role" or maybe "About the company". But they only gave examples; not strict list. I'd include a heading "About the role" with company description. - Job Description: could be "Responsibilities"? Actually Job Description includes overview of role. Could be under "Responsibilities". But we also have a separate "What You'll Do" which is responsibilities. So maybe we combine. Better: Use headings: "About the role" (company description + job overview), "Responsibilities" (What You'll Do), "Qualifications" (Required and Preferred), maybe "Skills" (certifications?), "Benefits" (none explicit), "Pay" (none), "Schedule" (none). We should not create sections for Pay/Benefits/Schedule unless posting actually states them. It does not mention pay, benefits, schedule. So we omit those. We also have "Why join us" which could be part of "About the role" or separate "Benefits"? Not exactly benefits. Could be under "About the role" as well. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list we need
  . For qualifications list we need
  . For skills maybe. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the "Additional Information" sections like Work Personas, Equal Opportunity Employer, Accommodations, Export Control Regulations, From Fortune copyright, etc. Also remove "Additional Information" heading if it's just boilerplate. We need to preserve all substantive information: company description, job description, what you'll do, why join us, qualifications (required and preferred), certifications required/preferred. We need to format as HTML fragment only. Let's extract content. 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: "ServiceNow is moving from a workflow platform with AI features to an AI platform where agents do the work. That shift depends entirely on whether the operational data underneath it can be trusted, which is the problem this role owns. The ITOM Solution Architect designs and leads technical delivery of ServiceNow ITOM solutions across CMDB and service data foundations, Discovery, Service Mapping, ITOM Health, event intelligence, and service observability, and increasingly designs the agentic layer built on top of them. The role moves fluidly between deep technical design and executive advisory, with the judgement to give customers evidence-based assessments of their operational maturity rather than aspirational ones." What You'll Do: multiple paragraphs each starting with a bold heading? Actually they have headings like "Architect the data foundation", "Own ITOM architecture: ...", "Design and data foundations AI-ready and trustworthy", etc. We need to capture all bullet points? It's not bullet list but paragraphs with headings. We can treat each as a responsibility item. We'll put them in
  • each. Let's list responsibilities: - Architect the data foundation - Own ITOM architecture: Discovery, Service Graph Connectors, Agent Client Collector, CMDB/CSDM design, IRE and reconciliation, and Service Mapping strategy - Design and data foundations AI-ready and trustworthy - Design sustainable data population architecture, including MID Server and collection topologies that hold up under real enterprise network and security constraints - Design the event intelligence and observability layer - Architect ITOM Health and Service Observability with SLO-based Service Reliability Management as one signal-to-service model - Integrate existing monitoring estates (for example, Dynatrace, Datadog, SolarWinds, Splunk) - Define operational success: noise reduction, alert-to-CI coverage, MTTR, and service health accuracy - Design and govern the agentic layer - Design where ServiceNow Otto and AI agents fit operationally, including alert triage alert triage, detecting and correcting CMDB issues, and autonomous SLO creation - Build custom agentic workflows in AI Agent Studio where out-of-box coverage stops - Build guardrails before automation, especially in regulated environments - Advise and lead - Give honest current-state assessments, including telling customers when they are not ready for the use case they came in asking for - Translate architecture into business outcomes for CIOs and infrastructure leaders: risk, cost, and toil avoided - Flag integration, data-quality, and scalability risk before it hits delivery - Keep architecture consistent with engagement managers, technical consultants, and platform architects - Support pre-sales scoping with realistic effort and sequencing - Contribute reusable IP to the practice and mentor consultants toward architect capability - Advise on release cadence and upgrade sequencing as part of architecture, not an afterthought Why join us: bullet points? Actually it's a paragraph with three bullet-like sentences: - Shape the architecture of multi-million-dollar transformation programs from the first design conversation - Work on the problem that determines whether autonomous IT actually works: trustworthy operational data - Join a practice that invests in architect development and values honest delivery over optimistic scoping We'll put those in
    . Qualifications: Required and Preferred. Required list: - Substantial ServiceNow ITOM delivery experience at architect or lead level on large, multi-workstream programs - Demonstrated depth in CMDB architecture, CSDM alignment, IRE and reconciliation design, and Discovery pattern design - Working command of ITOM Visibility and ITOM Health, including enterprise-scale Event Management design - Practical experience applying AI to operational work, and the judgement to know where it helps and where it does not - Infrastructure and cloud fluency: hybrid and multi-cloud architecture, containers and Kubernetes, and the network and security constraints that affect discovery and monitoring - Integration fluency: REST, MID Server architecture, credential and certificate handling, and event and telemetry ingestion patterns - Executive presence, with the ability to hold a design position under challenge and explain it without jargon - A collaborative, one-team posture across sales, solution consulting, and delivery Preferred: - Experience designing agentic solutions in AI Agent Studio - Experience governing AI through AI Control Tower, including scope, autonomy, escalation, and value measurement - Adjacent ITAM (HAM/SAM) or SecOps experience, given shared CMDB dependencies - Scripting fluency sufficient to review and debug pattern, transform, and event-rule logic Certifications: Required: CIS-Data Foundations, CIS-Discovery, CIS-Service Mapping, and CIS-Event Management, held or obtained within an agreed window Preferred: CSA; ArchX, CTA, or CMA for architect-track candidates; and current experience with Now Assist, ServiceNow Otto, and AI Agents We could put certifications under Qualifications or a separate "Skills" section. Since they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Qualifications for required+preferred experience, and Skills for certifications. Or we could include certifications under Qualifications as well. But better to follow examples: Qualifications for experience, Skills for certifications. Thus sections:

    About the role

    (company description + job description maybe combined). We'll put two

    elements.

    Responsibilities

    with
    • each responsibility (maybe nested? but we can just list top-level items; sub-items could be separate
    • as well). We'll flatten.

      Qualifications

      with
      • for required and preferred? Could separate required and preferred with headings inside? But we cannot add extra headings besides

        . Could use

        to label required/preferred then

        . That's okay.

        Skills

        for certifications. We must not include Pay/Benefits/Schedule. Now produce HTML. Let's craft. We need to ensure no extra whitespace? It's fine. We'll output:

        About the role

        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.

        ServiceNow is moving from a workflow platform with AI features to an AI platform where agents do the work. That shift depends entirely on whether the operational data underneath it can be trusted, which is the problem this role owns. The ITOM Solution Architect designs and leads technical delivery of ServiceNow ITOM solutions across CMDB and service data foundations, Discovery, Service Mapping, ITOM Health, event intelligence, and service observability, and increasingly designs the agentic layer built on top of them. The role moves fluidly between deep technical design and executive advisory, with the judgement to give customers evidence-based assessments of their operational maturity rather than aspirational ones.

        Responsibilities

        • Architect the data foundation
        • Own ITOM architecture: Discovery, Service Graph