ITSM Lead
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose
. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key parts:
- Top Skills' Details: bullet list? Actually "Top Skills' Details 8+ years of ITSM consulting or process leadership experience supporting ServiceNow or IT Service Management initiatives Deep understanding of ITSM processes, including Incident, Problem, Change, Service Catalog, and Knowledge Experience leading enterprise ITSM migration, consolidation, or integration initiatives, including process workshops, workflow alignment, migration planning, and stakeholder decision-making"
- Description: paragraph.
- Key Responsibilities: bullet list.
- Additional Skills & Qualifications: bullet list.
- Job Type & Location: "This is a Contract position based out of Waukegan, IL."
- Pay And Benefits: includes pay range $75.00 - $75.00/hr (so same). Benefits list.
- Workplace Type: "This is a fully onsite position in Waukegan,IL."
- Application Deadline: "This position is anticipated to close on Oct 2, 2026."
- About TEKsystems: paragraphs.
- About TEKsystems And TEKsystems Global Services: paragraphs.
- EEO statements, etc: remove.
- San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of AI: remove (these are legal boilerplate).
We need to decide sections.
We have:
- About the role: could be description paragraph.
- Responsibilities: Key Responsibilities.
- Requirements / Qualifications: Additional Skills & Qualifications (maybe also Top Skills' Details). Could combine.
- Skills: maybe Top Skills' Details.
- Benefits: Pay And Benefits includes pay and benefits.
- Schedule: maybe Workplace Type (fully onsite) could be schedule? Actually schedule is about hours, but we have workplace type. Could treat as Schedule? But we only create Schedule section if posting actually states schedule (like hours, shift). Not present. So we may not include Schedule.
- Pay: we have Pay And Benefits includes pay range. So we can have Pay section (maybe combined with Benefits). The rule: Prefer few substantive sections over many thin ones. So we could combine Pay and Benefits into one section titled "Pay and Benefits". However headings list includes Pay and Benefits separate. But we can choose to include only if we have content. Since we have both pay and benefits, we could make a single section "Pay and Benefits" using
Pay and Benefits
. That's acceptable? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict that we must use exactly those headings; we can use those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings if we create those sections. But we can also combine? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits into one section, but then heading would not match the examples exactly. Might be okay but safer to follow examples: we could have separate Pay and Benefits sections, each with content. Pay: we have pay range. Benefits: we have list. That's two sections, each substantive. That's fine.
Schedule: we have workplace type (fully onsite). That's not schedule but could be considered Schedule? The instruction says Schedule section only if posting actually states them. The posting does state "Workplace Type This is a fully onsite position in Waukegan,IL." That's about location/workplace type, not schedule (hours). Could we treat as Schedule? Probably not. Better to omit Schedule section.
We also have About TEKsystems etc. That's company description; could be "About the role"? Actually About the role is description of the role. The company description is not about the role but about the employer. Could be omitted? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not boilerplate; it's substantive info about the employer. Should we keep? Likely yes, as it's part of posting. Could be placed under "About the role" or maybe a separate section "About the company". But heading list does not include About the company. However we could put it under "About the role" as part of description? Might be okay to include as a paragraph under About the role. But the instruction says "About the role" heading for section headings (e.g. About the role...). So we can use About the role for role description, not company. But we could still include company description under About the role? Might be mixing.
Better to follow: we have Description paragraph (the role description). That's suitable for About the role. Then we have company description paragraphs; we could put them under a separate heading like "About TEKsystems". But not in list. However we could still use About TEKsystems
as it's a heading; the instruction didn't forbid other headings, just gave examples. It said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections, but not strictly limited. Safer to stick to those headings. So we could incorporate company description into About the role or maybe under Responsibilities? Not appropriate.
Maybe we can treat company description as part of "About the role" as additional context. It's not harmful.
Thus sections:
- About the role: combine the Description paragraph and maybe the company description? But we can keep description only; company description could be omitted? Might be considered boilerplate? It's not legal boilerplate; it's marketing. Might be okay to keep.
But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description paragraphs. If we omit them, we lose substantive info. So we need to include them somewhere.
We could create a section "About the company" using About the company
. Not in examples but acceptable. The instruction didn't forbid other headings; just gave examples. So we can do that.
Thus sections:
About the role
Description paragraph.
Responsibilities
- ... each responsibility.
Requirements
maybe combine Top Skills' Details and Additional Skills & Qualifications? But we have separate headings Requirements and Qualifications. Could split: Requirements = Top Skills' Details (experience, understanding, leading migration). Qualifications = Additional Skills & Qualifications (years, experience, facilitation, etc). Or we could combine into Requirements. But we have both headings available; we can use both.
Thus:
Requirements
- 8+ years of ITSM consulting or process leadership experience supporting ServiceNow or IT Service Management initiatives
- Deep understanding of ITSM processes, including Incident, Problem, Change, Service Catalog, and Knowledge
- Experience leading enterprise ITSM migration, consolidation, or integration initiatives, including process workshops, workflow alignment, migration planning, and stakeholder decision-making
Qualifications
- 8+ years of ITSM consulting, process analysis, or service management experience
- Demonstrated experience leading ServiceNow-enabled ITSM migration or consolidation workstreams
- Strong workshop facilitation, stakeholder management, process analysis, and decision-management skills
- Experience guiding analysts and coordinating process-workstream activities
- Ability to work onsite in Waukegan, Illinois
Skills
maybe we could put Top Skills' Details again? But we already used them. Could omit Skills section to avoid duplication. The instruction: prefer few substantive sections over many thin ones. So we could skip Skills if we already covered in Requirements/Qualifications.
Pay
The pay range for this position is $75.00 - $75.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
We might also include Workplace Type (fully onsite) maybe under a section "Workplace Type" but not in list. Could add as a paragraph under About the role or under Responsibilities? Probably better to add a short paragraph under About the role: "This is a fully onsite position in Waukegan, IL." Or we could create a section "Schedule" but it's not schedule. However we could treat as "Workplace Type" but not in examples. Safer to include as a paragraph under About the role.
Also include Application Deadline? That's not in list; could be omitted? It's substantive info about timing. Could be included under About the role as a note. But we might consider it as metadata; not required to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. Where to put? Could be a paragraph under About the role or maybe under a separate section "Important Dates". Not in list. Could add a paragraph under About the role: "This position is anticipated to close on Oct 2, 2026."
Thus About the role paragraph will contain description + workplace type + deadline.
Now we need to remove boilerplate: remove EEO statements, legal, etc. Also remove duplicated lines: there are duplicated About TEKsystems sections (two similar paragraphs). We need to keep only one copy? The instruction: remove duplicated lines. So we should deduplicate. There are two "About TEKsystems" sections with similar content; we should keep one version (maybe combine). We'll keep one concise paragraph summarizing? But we must preserve all substantive information; we cannot summarize away detail. However duplicated lines are identical or near identical; we can keep one copy. The two paragraphs are slightly different but similar. Let's examine:
First About TEKsystems paragraph:
"We're partners in transformation. We help clients activate ideas and solutions to take advantage of a new world of opportunity. We are a team of 80,000 strong, working with over 6,000 clients, including 80% of the Fortune 500, across North America,
for prose
. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key parts: - Top Skills' Details: bullet list? Actually "Top Skills' Details 8+ years of ITSM consulting or process leadership experience supporting ServiceNow or IT Service Management initiatives Deep understanding of ITSM processes, including Incident, Problem, Change, Service Catalog, and Knowledge Experience leading enterprise ITSM migration, consolidation, or integration initiatives, including process workshops, workflow alignment, migration planning, and stakeholder decision-making" - Description: paragraph. - Key Responsibilities: bullet list. - Additional Skills & Qualifications: bullet list. - Job Type & Location: "This is a Contract position based out of Waukegan, IL." - Pay And Benefits: includes pay range $75.00 - $75.00/hr (so same). Benefits list. - Workplace Type: "This is a fully onsite position in Waukegan,IL." - Application Deadline: "This position is anticipated to close on Oct 2, 2026." - About TEKsystems: paragraphs. - About TEKsystems And TEKsystems Global Services: paragraphs. - EEO statements, etc: remove. - San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of AI: remove (these are legal boilerplate). We need to decide sections. We have: - About the role: could be description paragraph. - Responsibilities: Key Responsibilities. - Requirements / Qualifications: Additional Skills & Qualifications (maybe also Top Skills' Details). Could combine. - Skills: maybe Top Skills' Details. - Benefits: Pay And Benefits includes pay and benefits. - Schedule: maybe Workplace Type (fully onsite) could be schedule? Actually schedule is about hours, but we have workplace type. Could treat as Schedule? But we only create Schedule section if posting actually states schedule (like hours, shift). Not present. So we may not include Schedule. - Pay: we have Pay And Benefits includes pay range. So we can have Pay section (maybe combined with Benefits). The rule: Prefer few substantive sections over many thin ones. So we could combine Pay and Benefits into one section titled "Pay and Benefits". However headings list includes Pay and Benefits separate. But we can choose to include only if we have content. Since we have both pay and benefits, we could make a single section "Pay and Benefits" using
Pay and Benefits
. That's acceptable? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict that we must use exactly those headings; we can use those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings if we create those sections. But we can also combine? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits into one section, but then heading would not match the examples exactly. Might be okay but safer to follow examples: we could have separate Pay and Benefits sections, each with content. Pay: we have pay range. Benefits: we have list. That's two sections, each substantive. That's fine.
Schedule: we have workplace type (fully onsite). That's not schedule but could be considered Schedule? The instruction says Schedule section only if posting actually states them. The posting does state "Workplace Type This is a fully onsite position in Waukegan,IL." That's about location/workplace type, not schedule (hours). Could we treat as Schedule? Probably not. Better to omit Schedule section.
We also have About TEKsystems etc. That's company description; could be "About the role"? Actually About the role is description of the role. The company description is not about the role but about the employer. Could be omitted? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not boilerplate; it's substantive info about the employer. Should we keep? Likely yes, as it's part of posting. Could be placed under "About the role" or maybe a separate section "About the company". But heading list does not include About the company. However we could put it under "About the role" as part of description? Might be okay to include as a paragraph under About the role. But the instruction says "About the role" heading for section headings (e.g. About the role...). So we can use About the role for role description, not company. But we could still include company description under About the role? Might be mixing.
Better to follow: we have Description paragraph (the role description). That's suitable for About the role. Then we have company description paragraphs; we could put them under a separate heading like "About TEKsystems". But not in list. However we could still use About TEKsystems
as it's a heading; the instruction didn't forbid other headings, just gave examples. It said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections, but not strictly limited. Safer to stick to those headings. So we could incorporate company description into About the role or maybe under Responsibilities? Not appropriate.
Maybe we can treat company description as part of "About the role" as additional context. It's not harmful.
Thus sections:
- About the role: combine the Description paragraph and maybe the company description? But we can keep description only; company description could be omitted? Might be considered boilerplate? It's not legal boilerplate; it's marketing. Might be okay to keep.
But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description paragraphs. If we omit them, we lose substantive info. So we need to include them somewhere.
We could create a section "About the company" using About the company
. Not in examples but acceptable. The instruction didn't forbid other headings; just gave examples. So we can do that.
Thus sections:
About the role
About TEKsystems
as it's a heading; the instruction didn't forbid other headings, just gave examples. It said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections, but not strictly limited. Safer to stick to those headings. So we could incorporate company description into About the role or maybe under Responsibilities? Not appropriate.
Maybe we can treat company description as part of "About the role" as additional context. It's not harmful.
Thus sections:
- About the role: combine the Description paragraph and maybe the company description? But we can keep description only; company description could be omitted? Might be considered boilerplate? It's not legal boilerplate; it's marketing. Might be okay to keep.
But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description paragraphs. If we omit them, we lose substantive info. So we need to include them somewhere.
We could create a section "About the company" using About the company
. Not in examples but acceptable. The instruction didn't forbid other headings; just gave examples. So we can do that.
Thus sections:
About the role
Description paragraph.
Responsibilities
- ... each responsibility.
Requirements
maybe combine Top Skills' Details and Additional Skills & Qualifications? But we have separate headings Requirements and Qualifications. Could split: Requirements = Top Skills' Details (experience, understanding, leading migration). Qualifications = Additional Skills & Qualifications (years, experience, facilitation, etc). Or we could combine into Requirements. But we have both headings available; we can use both. Thus:Requirements
- 8+ years of ITSM consulting or process leadership experience supporting ServiceNow or IT Service Management initiatives
- Deep understanding of ITSM processes, including Incident, Problem, Change, Service Catalog, and Knowledge
- Experience leading enterprise ITSM migration, consolidation, or integration initiatives, including process workshops, workflow alignment, migration planning, and stakeholder decision-making
Qualifications
- 8+ years of ITSM consulting, process analysis, or service management experience
- Demonstrated experience leading ServiceNow-enabled ITSM migration or consolidation workstreams
- Strong workshop facilitation, stakeholder management, process analysis, and decision-management skills
- Experience guiding analysts and coordinating process-workstream activities
- Ability to work onsite in Waukegan, Illinois
Skills
maybe we could put Top Skills' Details again? But we already used them. Could omit Skills section to avoid duplication. The instruction: prefer few substantive sections over many thin ones. So we could skip Skills if we already covered in Requirements/Qualifications.Pay
The pay range for this position is $75.00 - $75.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)