Desired Competencies (Technical/Behavioral Competency)

1. Minimum 7+ years of hands-on ServiceNow developer experience with strong implementation exposure in ITOM modules, especially Event Management and Discovery.
2. Overall 10+ years of IT experience with senior-level capability to design, develop, configure, customize, and troubleshoot ServiceNow ITOM solutions.
3. Strong experience in ServiceNow Discovery, including MID Server setup, credentials, schedules, patterns, classifiers, probes/sensors, and end-to-end troubleshooting of discovery failures.
4. Strong implementation experience in ServiceNow Event Management, including event rules, alert correlation, alert noise reduction, monitoring tool integrations, and automated incident creation.
5. Mandatory ServiceNow certifications required: Certified System Administrator (CSA) and relevant ITOM certification such as CIS-Discovery and/or CIS-Event Management.

Role descriptions / Expectations from the Role 1. Design, develop, configure, and enhance ServiceNow ITOM solutions with primary focus on Discovery and Event Management for enterprise infrastructure operations.

2. Implement and troubleshoot Discovery components including MID Server, credentials, schedules, patterns/classifiers, probes/sensors, and CMDB population.

3. Configure Event Management capabilities including event ingestion, alert correlation, rule tuning, noise reduction, and integration with enterprise monitoring tools.

4. Develop ServiceNow scripts, flows, integrations, business rules, script includes, and automation workflows following platform best practices.

5. Act as a senior developer by supporting technical design, code review, production troubleshooting, upgrade impact analysis, and stakeholder coordination.

Technical Questions & Answers :

1. Explain ServiceNow Discovery end-to-end. How would you troubleshoot a failed Discovery? Answer: Discovery uses MID Server to communicate with infrastructure using configured credentials, schedules, probes/sensors or patterns, and then updates the CMDB through identification and reconciliation rules. Troubleshooting should start with MID Server status, credential validation, network/firewall reachability, Discovery logs, ECC queue errors, pattern/probe failures, and CMDB identification errors. A senior developer should also verify whether the right CI class, relationship, and reconciliation rules are being applied.

2. How do you configure Event Management and reduce alert noise in ServiceNow? Answer: Event Management receives events from monitoring tools and converts them into alerts based on event rules, thresholds, filters, and mappings.

Noise reduction can be achieved through event deduplication, alert correlation rules, maintenance windows, proper CI binding,



suppression rules, and routing logic. The candidate should explain how alerts are correlated to CIs/services and how critical alerts can trigger incidents automatically while avoiding duplicate incidents.

3. What is the role of CMDB, IRE, and reconciliation in ITOM implementation? Answer: CMDB stores configuration items and relationships discovered from infrastructure and integrated tools.

The Identification and Reconciliation Engine helps identify existing CIs, prevent duplicates, and decide which data source can update specific attributes. In ITOM, proper CI classification, identifiers, reconciliation rules, relationship mapping, and CMDB health checks are critical to ensure accurate Discovery, Event Management correlation, impact analysis, and operational reporting.

4. Scripting scenario: Write logic to create an incident for a critical alert only if no active incident already exists for the same CI and alert signature. Answer: The logic should check the alert record, validate severity/priority, identify the CI and alert signature, query the incident table for an active incident with the same CI and correlation/signature reference, and create a new incident only when no active match exists.

This can be implemented through an Event Management rule, Flow Designer action, Script Include, or Business Rule depending on design standards. The script should use GlideRecord efficiently, include null checks, avoid duplicate creation, and log failures for supportability.

5. What ServiceNow scripting skills are mandatory for this role? Answer: The candidate must have strong hands-on JavaScript and ServiceNow scripting experience, including Business Rules, Script Includes, Client Scripts, UI Policies, UI Actions, Scheduled Jobs, GlideRecord, GlideAggregate, GlideAjax, Flow Designer scripting, REST/SOAP integrations, and error handling.

For a senior developer, the answer should also include scripting best practices such as avoiding inefficient queries, using encoded queries carefully, validating access/security, maintaining reusable Script Includes, and ensuring code is upgrade-safe and performance-conscious.

6. Write a ServiceNow server-side script to identify all open Priority 1 incidents that are older than two hours and do not have an assigned user. Explain the script line by line.

Answer:



The candidate should write a server-side GlideRecord script using the incident table, filter active/open Priority 1 incidents, check incidents created more than two hours ago, and ensure assigned_to is empty. The script should demonstrate proper use of addQuery, addNullQuery, gs.hoursAgoStart or equivalent date logic, query execution, and while loop processing. A strong answer should also explain performance considerations, index usage, avoiding unnecessary updates, and how this script could be adapted into a Scheduled Job or Script Include.

7. Write a Script Include to check whether an active incident already exists for the same Configuration Item and alert signature before creating a new incident. Answer: The candidate should create a reusable server-side Script Include that accepts CI sys_id and alert signature as inputs, queries the incident table for active matching records, and returns true or false.

The script should include input validation, GlideRecord query optimization, null checks, and explicit return values so it can be reused from Business Rules, Flow Designer actions, or Event Management rules.

8. Write a ServiceNow script to call an external monitoring tool REST API, parse the response, and create events in ServiceNow Event Management. Answer: The candidate should use RESTMessageV2 or an equivalent configured REST message, handle authentication through secure configuration, parse the JSON response, validate mandatory fields, and insert records into the event table or trigger the appropriate Event Management ingestion path.

A strong answer should include response code handling, try-catch blocks, logging, timeout/error handling, and protection against duplicate or malformed events.

9. Write a script to validate newly discovered CIs and prevent duplicate CI creation by checking key attributes before insertion/update. Answer: The candidate should explain that in a real ITOM implementation, duplicate prevention should primarily rely on Identification and Reconciliation Engine rules, identifiers, reconciliation definitions, and CMDB governance.

From a scripting perspective, the candidate can write validation logic to check key attributes such as serial number, name, IP address, and class before creating or updating a CI. A strong answer should mention that direct CMDB manipulation must be carefully controlled and aligned with IRE best practices.

Expected Senior-Level Explanation: The candidate should highlight that scripting is secondary to IRE-based identification. The preferred approach is to configure proper CI identifiers, use Discovery/IRE APIs where applicable, maintain CMDB health rules, and avoid uncontrolled custom inserts that bypass governance.

📌 Senior ServiceNow ITOM Developer (Bengaluru)
🏢 Nustar Technologies
📍 Bengaluru