Demo Developer & Lead — ITSM / ITOM

We need to output HTML fragment with sections: About the role (already present), Responsibilities (What You'll Do), Qualifications (What you bring + Nice to have maybe), Benefits (if present), Pay (if present), Schedule (if present). Also maybe "Company Description" but not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We should include sections only when posting has real specific content. We have: - About the role: present (the paragraph after "About the role"). - Responsibilities: "What You’ll Do" section with bullet list of duties. - Qualifications: "What you bring" and "Nice to have". Could combine into Qualifications section with bullet lists. - Benefits: The posting mentions "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." Also earlier: "FD21 For positions in this location, we offer a base pay of $137,700 - $241,000, plus equity (when applicable), variable/incentive compensation and benefits." So benefits are described. So we can include Benefits section. - Pay: The base pay range is given: "$137,700 - $241,000, plus equity (when applicable), variable/incentive compensation". So we can include Pay section. - Schedule: Not mentioned. No schedule info. So omit. - Skills: Could be part of Qualifications; but we could also have Skills section if we want. However instruction: prefer few substantive sections over many thin ones. We could combine skills into Qualifications. So we may not need separate Skills. - Requirements: Could be same as Qualifications. We'll just have Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to include the company description? Not required as heading; but we could include as a

  before sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must include company description, but we should preserve ALL substantive information. The company description is substantive. Should we include it? It's not a heading but could be a

  before sections. The instruction about headings only applies to those specific headings; we can have other content as

  . So include company description as a paragraph. Also include the "FD21 For positions in this location, we offer a base pay..." paragraph; we will extract pay info into Pay section, but we might also keep the sentence? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move the pay info into a Pay section, we still preserve it. The original sentence also mentions equity etc. We'll include that in Pay section. Similarly benefits sentence: we will put in Benefits section. We need to avoid duplication: don't repeat same info elsewhere. So we should not keep the original sentences if we moved content to sections; but we need to ensure we didn't lose any other info like "FD21 For positions in this location, we offer a base pay..." includes also "Sales positions generally offer a competitive On Target Earnings (OTE) incentive compensation structure." That's also part of compensation; we should include in Pay section maybe. Also "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." Also "Compensation is based on the geographic location in which the role is located and is subject to change based on work location." Also "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." So we need to include all that. Thus Pay section: include base pay range, equity, variable/incentive compensation, note about guideline, OTE for sales, variation factors, geographic basis. Benefits section: health plans, flexible spending accounts, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan, family leave programs. Now About the role: we have paragraph(s). We'll keep as

  . Responsibilities: "What You’ll Do" bullet list. We'll extract each bullet as

• . Need to preserve all details. Let's parse the "What You’ll Do" section: - Lead the IT demo story. Own the end-to-end ITSM and ITOM demo portfolio: keynote and event demos, spotlight and launch demos, EBC demos, and the field-ready versions derived from them. - Build it. Hands-on development of demo scenarios on ServiceNow: Now Assist / AI Agents for IT, Service Operations Workspace, ITSM Pro capabilities, Discovery and Service Mapping, Event Management and AIOps, CMDB, Cloud Cost / Cloud Management, Workflow Data Fabric touchpoints, and integrations that make the story credible. - Turn positioning into a demo. Translate release themes and PMM messaging into a demo script and click path, then build the environment, personas, and seeded data to support it. Write the talk track and the demo guide that goes with it. - Keep the environment healthy. Keep demo instances, data, and integrations stable and release-current. Own instance setup, cloning, upgrades, and the maintenance that lets a demo run reliably on a keynote stage months after it was first built. - Be the IT demo point person. Serve as the go-to expert for ITSM/ITOM demo requests across Marketing, Events, Analyst Relations, and Sales enablement. Scope requests, set expectations, and push back when a request will not produce a good demo. - Partner with Product. Work directly with PM and engineering on pre-release features; be an early adopter of new capabilities and feed real demo-build feedback into product. - Deliver on stage and on video. Collaborate with the team’s designers and video producers on UI polish, motion, and recorded demo versions. Present demos live when needed and coach presenters who will deliver them. - Raise the bar on how we build. Use AI-assisted development (Claude, Claude Code, MCP against ServiceNow instances) to compress build cycles. Contribute to the team’s shared demo frameworks, reusable components, and documentation. We'll make each bullet a
• . Ensure we keep the content exactly. Now Qualifications: "What you bring" bullet list (though not formatted as bullet but sentences separated by periods). We'll convert each distinct qualification into
• . Also "Nice to have" list. Let's extract "What you bring": - 5+ years of hands-on ServiceNow development, with deep knowledge of the ITSM and ITOM product families and how customers actually use them. - Strong scripting on the platform: Business Rules, Script Includes, Flow Designer, UI Builder / Workspaces, Service Portal, REST integrations, Transform Maps, scoped app development, and update set / instance management. - Experience building or supporting demo environments, sandboxes, or lab instances, including provisioning, cloning, and data seeding at scale. - Ability to write a story, not just build a feature: you can take a marketing message and turn it into a persona-driven narrative that a non-technical audience follows. - Strong communication with product, marketing, and executive stakeholders; comfortable presenting demos live and handling questions. - Self-directed. You run your own backlog, sequence your own work across multiple concurrent events, and flag risk early. Now "Nice to have": - Experience with Now Assist, AI Agents, or AI Control Tower demos, and with Now Assist Skill Kit or agentic workflow configuration. - ITOM depth in Discovery, Service Mapping, Event Management / AIOps, or Cloud Cost Management; familiarity with common monitoring and cloud tooling used in integrations. - Front-end skills (HTML/CSS, JavaScript, React or AngularJS) for mockups, custom widgets, and demo polish. - Practical experience with AI-assisted development workflows (Claude Code, MCP servers, structured handoffs to contractors). - ServiceNow certifications (CSA, CAD, CIS-ITSM, CIS-Discovery / Event Management) or equivalent experience. - Prior experience on a demo, solution consulting, or product marketing team. We'll combine into Qualifications section with two sub-lists? Could just have one list with all items, but we could separate into "Required" and "Nice to have" using

  ? But only

  headings allowed for sections; we could still use

  to label. Simpler: make one list with all items, but we might lose distinction. However we can keep both as separate

  paragraphs before list? The instruction: Use

  • for any list of duties/requirements/benefits. So we need to use list for requirements. Could have two lists: one for required, one for nice to have, each preceded by a

    describing. That's acceptable. Thus Qualifications section:

    Qualifications

    then

    Required:

    ...
    then

    Nice to have:

    ...
    . Now Benefits section:

    Benefits

    with items: health plans, flexible spending accounts, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan, family leave programs. Pay section:

    Pay

    Base pay range: $137,700 - $241,000, plus equity (when applicable), variable/incentive compensation. Sales positions generally offer a competitive On Target Earnings (OTE) incentive compensation structure. The base pay shown is a guideline; individual total compensation will vary based on qualifications, skill level, competencies, and work location. Compensation is based on geographic location and subject to change based on work location.

    We could also make a list but it's prose. Now About the role: we have paragraph(s). Let's capture the exact text: "About the role Our team builds the demos that show up where ServiceNow makes its biggest impression: keynotes, Knowledge, World Forums, Gartner and analyst events, executive briefings, launch videos, and the assets our field uses every day. Each product area on the team has an owner who is both the storyteller and the builder for that lens. This role owns the IT lens. You will be the lead and hands-on developer for our ITSM and ITOM demo stories: the workflows, data, personas, and instance configuration that make Technology Workflows demos land. You will work the same way our Employee and CRM demo leads do, just pointed at IT: partner with product marketing and product management on the narrative, then build it on the platform yourself, keep it current with every release, and make it reusable for the people who present it. This is a builder’s role first. You should be as comfortable in a Script Include or a Flow as you are in front of a marketing director explaining why a story beat works." We need to ensure we keep that as

    . Might need to split into sentences but it's fine as one paragraph. Now we need to output only HTML fragment. Let's construct:

    About the role

    About the role Our team builds the demos that show up where ServiceNow makes its biggest impression: keynotes, Knowledge, World Forums, Gartner and analyst events, executive briefings, launch videos, and the assets our field uses every day. Each product area on the team has an owner who is both the storyteller and the builder for that lens. This role owns the IT lens. You will be the lead