CMDB Administrator/ Service Delivery Analyst

Job Title: Service Delivery Analyst/ CMDB Administrator
Location-Type: Remote working CST
Start Date Is: ASAP
Duration: 6 month contract to hire

Job Description:
The CMDB Administrator/ Service Delivery Analyst is responsible for managing and maintaining the ServiceNow CMDB to ensure accurate, reliable configuration data and support ITSM processes.

Day-to-Day Responsibilities:

• Manage and maintain CMDB including HAM, SAM, and Certificate Management
• Ensure data accuracy, integrity, and governance within ServiceNow
• Support ITSM processes: Incident, Problem, Change, and Asset Management
• Perform data analysis to support business and technical solutions
• Lead process improvements and root cause analysis initiatives
• Collaborate with internal stakeholders and third-party vendors
• Monitor SLAs and KPIs to ensure service performance
• Support service integration across multiple providers (SIAM model)
• Assist with IT operational budgeting and resource planning
• Deliver presentations and reporting to senior leadership

Requirements:

• Must-Haves:
  • Experience administering CMDB within ServiceNow
  • Strong knowledge of ITSM processes (Incident, Change, Problem, Asset Management)
  • Experience with HAM and SAM modules
  • Data analysis and process improvement experience
  • Ability to manage multiple vendors and service providers
  • Strong communication and stakeholder management skills
• Nice-to-Haves:
  • Experience with SIAM frameworks
  • Exposure to governance, compliance, or InfoSec processes
  • Experience supporting enterprise IT environments
  • Background in financial or regulated industries

1. CMDB Design & Ownership

Purpose: Validate end to end ownership, not just tool familiarity.

1.    "Can you walk me through a CMDB that you personally designed, implemented, or formally took ownership of? What problems were you solving, and what outcomes improved?”

2.    "What CI classes did you decide were in scope, and how did you determine required vs. optional attributes?”

3.    "How did you decide which data should be authoritative from discovery versus manual entry?”

Strong signal: Talks about tradeoffs, governance decisions, and business impact—not just configuration.

________________________________________

2. ServiceNow CMDB & Discovery Depth

Purpose: Ensure hands on capability with your core platform.

4.    "Which parts of ServiceNow CMDB and Discovery have you directly configured or built yourself?”

5.    "How do you validate that Discovery data is reliable and complete? What metrics do you use?”

6.    "Describe how you've handled discovery gaps, false positives, or duplicate CIs.”

Red flag: Only describes what Discovery does, not how they validated or corrected it.

________________________________________

3. CMDB Health, Certification & Governance

Purpose: Test ability to enforce standards and accountability.

7.    "Have you managed a CMDB certification or attestation process? How did you drive completion and handle non compliance?”

8.    "How do you hold CI owners or custodians accountable for data quality?”

9.    "Give an example of when you had to escalate a CMDB issue to leadership. What was the outcome?”

Strong signal: Comfortable with escalation and governance—not overly apologetic.

________________________________________

4. CI Lifecycle & Decommissioning Discipline

Purpose: Prevent CMDB sprawl and tech debt.

10.    "How do you ensure CIs are properly retired or decommissioned when systems are shut down?”

11.    "What controls do you put in place to prevent zombie or orphaned CIs?”

12.    "How does Change Management interact with CMDB in your model?”

Strong signal: Mentions lifecycle status controls, Change integration, and audits.

________________________________________

5. Application Mapping & Relationships

Purpose: Validate usefulness beyond inventory.

13.    "Describe your experience with application mapping. How deep do you go, and how do you keep relationships accurate over time?”

14.    "How have you used CI relationships to improve Incident, Problem, or Change outcomes?”

Strong signal: Can connect CMDB quality to real operational improvements.

________________________________________

6. Integration with HAM, SAM, and Monitoring

Purpose: Align CMDB with financial, security, and operational controls.

15.    "How should CMDB integrate with Hardware Asset Management and Software Asset Management?”

16.    "What is the CMDB's role in monitoring, alerting, or root cause analysis?”

17.    "Have you supported audits (financial, security, or compliance) using CMDB data? What was required?”

Strong signal: Understands CMDB as a control plane, not a reporting tool.

________________________________________

7. Metrics, Reporting & Continuous Improvement

Purpose: Ensure outcome orientation.

18.    "What CMDB health metrics do you regularly report on, and to whom?”

19.    "How do you identify where CMDB quality is degrading and proactively address it?”

20.    "What improvements would you look to make in the first 90 days if you joined a struggling CMDB environment?”

Strong signal: Clear diagnostic approach and prioritization.

________________________________________

8. Communication & Cross Functional Influence

Purpose: Test soft skills critical for success.

21.    "How do you explain CMDB value to teams that see it as overhead?”

22.    "Describe a time you had to push back on engineering, operations, or a vendor due to CMDB standards.”

Strong signal: Calm, direct, and confident—not defensive.

________________________________________

Optional Close Out Question (Highly Recommended)

23.    "In your opinion, why do most CMDB implementations fail—and how do you prevent