ServiceNow CMDB Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes compensation: $170,000 – $220,000. So Pay section can be included. Benefits are listed: Competitive compensation and performance-based incentives, 401(k) with company match, three weeks paid annual leave, comprehensive medical/dental/vision, life insurance and disability, transit/commuting benefits, professional development and paid training, remote work details. So Benefits section can be included. Schedule? Not explicitly given; remote-first, occasional onsite in DC. Could be considered Schedule? Not explicit schedule like hours. Might not include Schedule if not explicit. The posting mentions "Availability for occasional onsite work in Washington, DC." That's more location/travel. Not schedule. So we may omit Schedule. We need sections: About the role (maybe a summary), Responsibilities (What You'll Own), Requirements/Qualifications/Skills (What You Bring). Could combine Requirements and Qualifications? The instruction: use headings for those categories if content exists. We'll create sections: About the role (intro paragraph), Responsibilities (What You'll Own), Requirements (What You Bring). Could also have Skills separate but we can embed within Requirements. Better to follow instruction: Use headings for those categories if content exists. We'll be present. We'll have About the role, Responsibilities, Requirements, Benefits, Pay. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove duplicated lines like "Ready to apply? Send us your résumé." etc. Also remove navigation, cookie, legal. We need to preserve all substantive information. So we need to include details: remote-first, occasional onsite in DC, clearance TS, etc. Also mention compensation range. Benefits list. Responsibilities bullet list. Requirements bullet list. We must not invent or summarize away detail. Keep specifics. Let's extract content. About the role: The intro paragraphs: "OWN THE CMDB. ACTUALLY OWN IT...." plus description of role. We'll summarize but must preserve all substantive information; we can't omit details. However we can rephrase but must keep all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details; we must keep them. But we can rephrase? It says do not summarize away detail. Summarizing may lose detail. Safer to keep the original sentences but maybe we can keep them as is within
. We can copy the paragraphs but ensure no boilerplate. We need to avoid duplication. The posting has repeated "Ready to apply? Send us your résumé." We'll include only once maybe not at all because it's application instruction, which we should remove. So we drop that. We also need to drop duplicated lines like "WHY ENGINEERS TAKE THIS ROLE" etc? Those are headings within the posting but we are re-structuring; we can incorporate content under appropriate sections. Let's extract sections: About the role: The initial description: "OWN THE CMDB. ACTUALLY OWN IT. Every organization complains its CMDB is wrong. Almost none of them fund somebody to fix it. The data drifts, Discovery half-works, nobody trusts the dependency map, and the person nominally responsible has four other jobs. This is the other situation. Improvix Technologies is hiring a ServiceNow CMDB Engineer for a federal program where configuration management is a funded, staffed, named responsibility — yours. You'll run Discovery and Service Mapping, wire the CMDB to the asset and inventory systems that should be feeding it, and build the data quality that everything downstream depends on. Incident, Change, asset management, and the service views leadership actually looks at all rest on this data being right. When it is, nobody notices. You'll know." Also "WHY ENGINEERS TAKE THIS ROLE" bullet points: "A CMDB with a real owner... Remote-first, with a TS... A Top Secret clearance, sponsored... Scarce, durable expertise... A team above and beside you." We can incorporate those as part of About the role or separate? Probably About the role includes overview and why. Responsibilities: "What You'll Own" with subheadings: Discovery & Service Mapping, CMDB Data Architecture & Health, Asset Management Integration, Integrations & Data Feeds, Collaboration & Documentation. We'll turn each bullet into list items under Responsibilities. Requirements: "What You Bring" includes: 3+ years hands-on ServiceNow experience, including 2+ years working directly on CMDB, Discovery, or configuration management. Practical experience configuring and troubleshooting ServiceNow Discovery — MID Servers, credentials, schedules, and patterns. Working knowledge of CMDB structure: CI classes, relationships, identification and reconciliation rules, and data normalization. Experience building or maintaining integrations that feed the CMDB (IntegrationHub, Service Graph Connectors, or REST/SOAP). Scripting ability in ServiceNow — JavaScript, Glide APIs, business rules, script includes, and transform maps. Solid understanding of enterprise infrastructure: servers, networking, virtualization, and cloud resources — enough to know what Discovery is looking at and why it failed. Clear written and verbal communication, including the ability to explain data quality problems to people who don't work in the platform. U.S. citizenship and an active Top Secret clearance, or an active Secret clearance with willingness to be sponsored for TS. Availability for occasional onsite work in Washington, DC. Bonus points: list of certifications, experience aligning CMDB to CSDM, hands-on hardware or software asset management, license reconciliation, ITOM Health, cloud discovery experience, background supporting federal/defense programs in cleared environment, familiarity with ITIL/ITSM. We could include Bonus as part of Requirements or separate Skills? The instruction: Use headings for sections like Skills. We could create a Skills section for bonus points. But we need to avoid thin sections. Maybe combine Requirements and Skills into one Requirements section that includes both required and bonus? But we must not invent or summarize away detail; we can keep bonus as part of Requirements but label as "Preferred Qualifications" maybe not needed. However we have headings: Requirements, Qualifications, Skills. We could split: Requirements (mandatory), Qualifications (maybe same), Skills (bonus). But we need to avoid filler. Let's think: The posting has "What You Bring" (mandatory) and "BONUS POINTS" (preferred). So we can have Requirements (mandatory) and Skills (bonus). Qualifications maybe not needed. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not include Schedule. Now we need to format lists with
- . For prose, use
. We must not include any markdown code fences. Let's craft HTML. Start with maybe not needed; just output fragment. We'll do:
About the role
OWN THE CMDB. ACTUALLY OWN IT. Every organization complains its CMDB is wrong. Almost none of them fund somebody to fix it. The data drifts, Discovery half-works, nobody trusts the dependency map, and the person nominally responsible has four other jobs. This is the other situation. Improvix Technologies is hiring a ServiceNow CMDB Engineer for a federal program where configuration management is a funded, staffed, named responsibility — yours. You'll run Discovery and Service Mapping, wire the CMDB to the asset and inventory systems that should be feeding it, and build the data quality that everything downstream depends on. Incident, Change, asset management, and the service views leadership actually looks at all rest on this data being right. When it is, nobody notices. You'll know.
Why engineers take this role: a CMDB with a real owner — this isn’t twenty percent of somebody’s job. Discovery, Service Mapping, data health, and the integrations feeding it are the role. Remote‑first, with a Top Secret clearance. If you hold a Secret clearance today, we’ll sponsor and support the TS upgrade. Scarce, durable expertise in Discovery, Service Mapping, and CMDB data architecture are specialties every ServiceNow program needs and few engineers have. You’ll work alongside ServiceNow architects, developers, and business analysts on these programs, giving you people to design with rather than a queue to work alone.
That captures the why engineers take this role content. Now Responsibilities:Responsibilities
- Discovery & Service Mapping: Configure, run, and tune ServiceNow Discovery — MID Servers, discovery schedules, credentials, probes, sensors, and patterns. Build and maintain application service maps so the relationships between CIs reflect how services actually run. Troubleshoot discovery gaps and failures, and expand coverage across on‑premises and cloud infrastructure.
- CMDB Data Architecture & Health: Maintain CI class structure, relationships, and attributes so the CMDB stays coherent as it grows. Configure identification and reconciliation rules (IRE), normalization, and de‑duplication to keep records clean at the source. Build and monitor CMDB health dashboards — completeness, correctness, and compliance — and drive the remediation they surface.
- Asset Management Integration: Integrate hardware and software asset management (HAM/SAM) with the CMDB so assets and CIs stay reconciled. Support lifecycle tracking from procurement through disposal, and software license reconciliation against discovered install data.
- Integrations & Data Feeds: Design and maintain integrations that populate the CMDB from external sources using IntegrationHub, Service Graph Connectors, and REST/SOAP web services. Work with cloud and on‑premises inventory systems to keep authoritative data flowing in without creating duplicates. Script the transforms, business rules, and scheduled jobs that keep those feeds reliable.
- Collaboration & Documentation: Partner with architects, developers, and federal stakeholders to make sure CMDB design supports what the program needs downstream. Document class models, discovery configurations, integration designs, and data governance decisions. Provide occasional onsite support in Washington, DC for planning sessions, network‑restricted work, and stakeholder engagement.
Requirements
- 3+ years of hands‑on ServiceNow experience, including 2+ years working directly on CMDB, Discovery, or configuration management.
- Practical experience configuring and troubleshooting ServiceNow Discovery — MID Servers, credentials, schedules, and patterns.
- Working knowledge of CMDB structure: CI classes, relationships, identification and reconciliation rules, and data normalization.
- Experience building or maintaining integrations that feed the CMDB (IntegrationHub, Service Graph Connectors, or REST/SOAP).
- Scripting ability in ServiceNow — JavaScript, Glide APIs, business rules, script includes, and transform maps.
- Solid understanding of enterprise infrastructure: servers, networking, virtualization, and cloud resources — enough to know what Discovery is looking at and why it failed.
- Clear written and verbal communication, including the ability to explain data quality problems to people who don't work in the platform.
- U.S. citizenship and an active Top Secret clearance, or an active Secret clearance with willingness to be sponsored for a TS upgrade.
- Availability for occasional onsite work in Washington, DC.
Skills
- ServiceNow certifications — CSA, CIS–Discovery, CIS–Service Mapping, CIS–Hardware or Software Asset Management, or CAD.
- Experience aligning a CMDB to the Common Service Data Model (CSDM).
- Hands‑on hardware or software asset management, including license reconciliation.
- Experience with ITOM Health — Event Management or Service Operations Workspace.
- Cloud discovery experience across AWS, Azure, or similar.
- Background supporting federal or defense programs