Discovery and visibility
MID Servers, credentials, schedules, patterns, identification, reconciliation, cloud resources, and the troubleshooting needed when environments resist clean discovery.
Kaladesi / ServiceNow specialties
ServiceNow
ITOM staffing
ServiceNow
ITOM staffing.
Find ServiceNow ITOM people who can make infrastructure data trustworthy and operationally useful: architects, Discovery engineers, Service Mapping specialists, CMDB leaders, developers, and delivery leads screened by practitioners.
Full-timeContractContract-to-hire
01 — The specialty
ITOM has to survive the real environment.
Discovery schedules, service maps, event rules, and CIs can look complete while the underlying data is still unreliable. We look for people who understand the technical mechanisms and the operating discipline required to keep them useful.
Service Mapping and CSDM
Entry points, application services, dependencies, ownership, service models, and the governance that keeps maps current after the initial implementation.
Event Management and AIOps
Connector strategy, event normalization, correlation, alert noise, operational intelligence, and workflows that turn monitoring signals into action.
CMDB health and governance
Data sources, IRE behavior, duplicates, stale records, certification, ownership, health metrics, and decisions about which source should be trusted.
02 — Practitioner screening
A populated CMDB is not a trustworthy one.
ITOM ownership shows up in diagnosis and recovery: how someone found bad data, traced its source, made a technical correction, and established the controls that kept the same failure from returning.
QUESTION/01
What did Discovery get wrong?
We ask about failed credentials, duplicate CIs, incorrect classification, pattern behavior, network constraints, and how the candidate proved the resulting data was accurate.
QUESTION/02
How did the service map stay useful?
We look past the first successful map to ownership, change control, application-team participation, dependency drift, and the process used to maintain trust over time.
QUESTION/03
What happened to the alert noise?
Good Event Management work has operational consequences. We ask what was normalized, filtered, correlated, automated, and measured after the rules reached production.
03 — Roles we place
The right ITOM seat, clearly defined.
We recruit across permanent, contract, and contract-to-hire needs. The search starts with the environment, the products in scope, and what the person must make reliable.
ITOM/01
ITOM Architect
Technical direction across Discovery, Service Mapping, Event Management, CMDB, integrations, and operating model.
ITOM/02
Discovery Engineer
MID Servers, credentials, schedules, patterns, troubleshooting, cloud discovery, and data validation.
ITOM/03
Service Mapping Specialist
Application services, entry points, dependencies, traffic-based mapping, ownership, and map maintenance.
ITOM/04
CMDB / CSDM Lead
Data model, IRE, source strategy, health, governance, service modeling, and accountable ownership.
ITOM/05
ITOM Developer
Patterns, integrations, event rules, automation, extensions, and maintainable platform configuration.
ITOM/06
Delivery Lead
Scope, dependencies, infrastructure coordination, data readiness, risk, and adoption through production.
04 — Start the conversation
Tell us what the ITOM seat must make reliable.
On the first call, we’ll give you an honest view of search difficulty, candidate availability, and likely timing. If the brief is still broad, we’ll help separate the products you own from the outcomes you need.
Looking for your next ITOM role? Introduce yourself confidentially.