ServiceNow CMDB / ITOM Functional Consultant
maybe under "About the role"? The instructions: 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. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we need to map content to these headings if possible. If content doesn't fit any, we could maybe not create a heading? But we need to preserve all substantive information. Could embed eligibility statement in a
under "About the role" or maybe a generic
without heading? The instruction says use
for section headings (e.g. About the role, ...). It doesn't forbid having
without heading. So we can output a
for eligibility statement, then sections for Responsibilities, Requirements, Benefits, etc. Let's parse the posting: - "Employment Eligibility Statement Due to specific project and client requirements, this position is open to U.S. Citizens and U.S. Lawful Permanent Residents (Green Card holders). Sponsorship is not available at this time. Danta Technologies evaluates all candidates in compliance with the Immigration and Nationality Act (INA) and EEOC guidelines. All hiring decisions are made without regard to race, color, religion, sex, gender identity, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic." - "Note This position is based in Austin, Texas / San Jose, California, and requires 3 days per week working from the office and 2days remote per week. Only candidates who are currently located within Texas and California will be considered. ! Applications from candidates residing outside the USA will not be accepted." - "Job Description The client is looking for a senior ServiceNow CMDB/ITOM Functional Consultant who can bridge ITSM/CMDB business processes and the technical ServiceNow team. We are looking for a Senior ServiceNow CMDB / ITOM Functional Consultant with strong experience in CMDB, Discovery, Service Mapping, CSDM, IRE, and ITOM solutioning." - "Key Requirements" list bullet points (numbered). Those are requirements. - Then "Preferred ITIL v3 Foundation / Intermediate certification ServiceNow Administration experience ServiceNow Discovery / ITOM certifications CMDB / ITOM Architecture experience" - Then "Notes:- All qualified applicants will receive consideration for employment without regard to race, color, religion, religious creed, sex, national origin, ancestry, age, physical or mental disability, medical condition, genetic information, military and veteran status, marital status, pregnancy, gender, gender expression, gender identity, sexual orientation, or any other characteristic protected by local law, regulation, or ordinance." - Then "Benefits: Danta offers a compensation package to all W2 employees that are competitive in the industry. It consists of competitive pay, the option to elect healthcare insurance (Dental, Medical, Vision), Major holidays and Paid sick leave as per state law. The rate/ Salary range is dependent on numerous factors including Qualification, Experience and Location." Thus we have: - About the role: could be the Job Description paragraph. - Responsibilities: maybe not explicit; but we have "bridge ITSM/CMDB business processes and the technical ServiceNow team" and "lead functional discussions and translate requirements into functional specifications, test cases, and solutions". Could be responsibilities. - Requirements: the list under "Key Requirements" plus maybe the preferred qualifications. - Qualifications: maybe overlapping with Requirements; but we can combine. - Skills: maybe not separate. - Benefits: we have benefits paragraph. - Pay: not specific; only says rate/salary range dependent on factors; no explicit numbers. According to instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated, so we can include Benefits. Pay: not specific numbers, just says dependent; that is vague; we should not create Pay section because it's not specific. Schedule: we have note about 3 days office, 2 remote; that is schedule info. So we can include Schedule section. Thus sections: About the role (Job Description), Responsibilities (maybe from description), Requirements (Key Requirements + preferred), Benefits, Schedule. We must not repeat job title as heading. Use
for each section heading.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract details:
Eligibility statement: U.S. Citizens and LPR only, no sponsorship, compliance with INA and EEOC, hiring decisions without regard to protected characteristics.
Location note: based in Austin, Texas / San Jose, California; requires 3 days per week office, 2 days remote; only candidates located within Texas and California considered; applications from candidates residing outside USA not accepted.
Job Description: client looking for senior ServiceNow CMDB/ITOM Functional Consultant who can bridge ITSM/CMDB business processes and technical ServiceNow team. Looking for Senior ServiceNow CMDB/ITOM Functional Consultant with strong experience in CMDB, Discovery, Service Mapping, CSDM, IRE, and ITOM solutioning.
Key Requirements (numbered list):
1. 10+ years of experience with CMDB / Discovery / Service Mapping / ITOM
2. 5+ years of hands-on ServiceNow Discovery experience
3. Strong understanding of ServiceNow CMDB and ITOM
4. Strong experience with CSDM (Common Service Data Model)
5. Strong knowledge of IRE (Identification & Reconciliation Engine)
6. Experience with CMDB Health Dashboards and data quality
7. Experience analyzing CI data from Discovery, procurement, and other sources
8. Strong understanding of Asset Management / ITAM lifecycle
9. Experience maintaining data integrity between CMDB and AMDB
10. Experience with Configuration Management, Asset Management, and Change Management
11. Ability to lead functional discussions and translate requirements into functional specifications, test cases, and solutions
12. Experience working closely with ServiceNow Technical Architects and development teams
13. Strong understanding of Service Mapping and ITOM processes
Preferred:
- ITIL v3 Foundation / Intermediate certification
- ServiceNow Administration experience
- ServiceNow Discovery / ITOM certifications
- CMDB / ITOM Architecture experience
Notes (EEO statement): All qualified applicants will receive consideration for employment without regard to race, color, religion, religious creed, sex, national origin, ancestry, age, physical or mental disability, medical condition, genetic information, military and veteran status, marital status, pregnancy, gender, gender expression, gender identity, sexual orientation, or any other characteristic protected by local law, regulation, or ordinance.
Benefits: Danta offers a compensation package to all W2 employees that are competitive in the industry. It consists of competitive pay, the option to elect healthcare insurance (Dental, Medical, Vision), Major holidays and Paid sick leave as per state law. The rate/ Salary range is dependent on numerous factors including Qualification, Experience and Location.
We need to avoid boilerplate like EEO etc? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is considered boilerplate? It says remove EEO/equal-opportunity boilerplate. So we should remove the EEO statements (both the earlier one and the later Notes). However we must preserve ALL substantive information; but EEO is considered boilerplate to remove. So we can drop those paragraphs.
Similarly, the eligibility statement about US Citizens and LPR is not EEO; it's a specific requirement, we keep.
Location note: we keep.
Job Description: keep.
Key Requirements: keep.
Preferred: keep.
Benefits: keep.
Schedule: we have note about 3 days office, 2 remote; we can put under Schedule.
We also need to maybe include About the role: maybe combine Job Description and eligibility? But we have separate sections.
Let's structure:
About the role
... job description paragraph ...
Responsibilities
... ability to lead functional discussions ... experience working closely with ServiceNow Technical Architects ...
maybe also bridging ITSM/CMDB business processes. But we need to ensure we don't lose any detail. Let's list all substantive bits we need to keep: - Eligibility: U.S. Citizens and LPR only, no sponsorship, compliance with INA and EEOC guidelines (but EEOC guideline mention maybe borderline; but it's part of eligibility; we can keep as it's not boilerplate? It mentions compliance with INA and EEOC guidelines; that's not boilerplate per se but could be considered legal. However it's part of eligibility statement; we can keep. - Location: based in Austin, Texas / San Jose, California; requires 3 days per week office, 2 days remote; only candidates located within Texas and California considered; applications from candidates residing outside USA not accepted. - Job Description: client looking for senior ServiceNow CMDB/ITOM Functional Consultant who can bridge ITSM/CMDB business processes and the technical ServiceNow team. We are looking for a Senior ServiceNow CMDB / ITOM Functional Consultant with strong experience in CMDB, Discovery, Service Mapping, CSDM, IRE, and ITOM solutioning. - Key Requirements list (13 items). - Preferred qualifications list (4 items). - Benefits: compensation package competitive; includes competitive pay, option to elect healthcare insurance (Dental, Medical, Vision), Major holidays and Paid sick leave as per state law; rate/salary range dependent on qualification, experience, location. - Schedule: 3 days office, 2 remote (already in location note). Could be separate. We should avoid duplication: location note includes schedule; we could put schedule in its own section and location in About the role or a separate. But we must not duplicate. We can keep location info in a
under About the role or a separate
without heading. But we need to preserve all info; we can include location details in About the role paragraph. Let's craft About the role paragraph: combine job description and location and eligibility? Might be too long but okay. Better: About the role: job description paragraph. Then a separate
for eligibility and location? But we need headings only for sections we define. We can have multiple
elements without headings. Thus output:
About the role
The client is looking for a senior ServiceNow CMDB/ITOM Functional Consultant who can bridge ITSM/CMDB business processes and the technical ServiceNow team. We are looking for a Senior ServiceNow CMDB / ITOM Functional Consultant with strong experience in CMDB, Discovery, Service Mapping, CSDM, IRE, and ITOM solutioning.
Responsibilities
Ability to lead functional discussions and translate requirements into functional specifications, test cases, and solutions. Experience working closely with ServiceNow Technical Architects and development teams.
Requirements
- 10+ years of experience with CMDB / Discovery / Service Mapping / ITOM
- 5+ years of hands-on ServiceNow Discovery experience
- Strong understanding of ServiceNow CMDB and ITOM
- Strong experience with CSDM (Common Service Data Model)
- Strong knowledge of IRE (Identification & Reconciliation Engine)
- Experience with CMDB Health Dashboards and data quality
- Experience analyzing CI data from Discovery, procurement, and other sources
- Strong understanding of Asset Management / ITAM lifecycle
- Experience maintaining