ITSM and ITOM Developer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes: Must Have Technical/Functional Skills (list of ServiceNow modules). Roles & Responsibilities (list). Technical Competency (list). Behavioral competency (list). Good to have (list). Preferred to have (list). Abilities to manage conflicts (list). Generic Managerial Skills, If Any (maybe not needed). Location: Remote. Salary Range: $110,000-$160,000 a year. We need to map to sections: About the role (maybe a short paragraph summarizing). Responsibilities (list). Requirements (maybe technical skills). Qualifications (certifications). Skills (maybe technical/functional). Benefits (none given). Pay (salary range). Schedule (none). So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Possibly also Location as a paragraph. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive info. So we need to extract details: - Must Have Technical/Functional Skills: ServiceNow ITSM / ITAM / ITOM / CSM / FSM and other ServiceNow modules. - Roles & Responsibilities: Technical Competency (list items): - Experience as a Technical Lead - Experienced in ITIL Process Definition, Integration Solutions, understanding Architecture solution - Understanding customer business requirements and convert to functional requirements - Responsible for reviewing requirements for accurate estimation - Experienced in leading at least a couple of Implementation projects in ITSM / ITAM / ITOM / CSM / FSM area and one complete Implementation lifecycle for ServiceNow - Expertise ServiceNow deployments, ITSM / ITAM / ITOM / CSM / FSM migrations, consolidations, upgrades, integration with other third party tools, Orchestration, operational activities, Project Management expertise - Review, and do proactive analyze and resolve application issues as needed - Mentor and share technical knowledge/guidance to team - Very good ITIL process knowledge and ability to evaluate and bring out the correlations and impacts with respect to customer requirements and ITIL / industry standards - Must be certified with ServiceNow Systems Administrator, ServiceNow Implementation Specialist and ITIL V3 foundation - Should possess good knowledge in Agile/Scrum methodology - Behavioral competency: - Handles customer meetings and provide weekly/monthly reports for customer as well as TCS management - Good communication in orchestrating customer requirements/needs, solutions, customer responsibilities, risks, challenges and impacts - Excellent team management skills to manage the project team and members - Participate and provide feedback during planning meetings (i.e., pre-iteration, and retrospectives) - Good to have: - Experience in ServiceNow custom application design and development - Evaluate the tool stability and performance and provide recommendations - Knowledge on new servicenow modules ( HRSD, SecOps, GRC, SPM, Etc..) - Preferred to have ServiceNow Implementation Specialist certification - Abilities to manage conflicts that may arise with customers and/or TCS internal stakeholders - Generic Managerial Skills, If Any ServiceNow CSA, CAD certifications - Location: Remote - Salary Range: $110,000-$160,000 a year. We need to avoid filler like "Generic Managerial Skills, If Any". Might be considered not substantive? It says ServiceNow CSA, CAD certifications. Could be part of Qualifications. We need to decide sections: About the role: maybe a paragraph summarizing: "Technical Lead responsible for ServiceNow ITSM/ITAM/ITOM/CSM/FSM implementations, ITIL process definition, leading projects, mentoring team, etc." Responsibilities: list of duties (the technical competency items plus behavioral maybe). Could split but we can combine. Requirements: maybe technical must-have skills (ServiceNow modules, ITIL, Agile/Scrum, certifications). Qualifications: certifications (ServiceNow Systems Administrator, Implementation Specialist, ITIL V3 foundation, plus preferred Implementation Specialist, CSA, CAD). Skills: maybe technical/functional skills list (ServiceNow ITSM/ITAM/ITOM/CSM/FSM, other modules, custom app design, tool stability evaluation, new modules knowledge). Benefits: none, so omit. Pay: include salary range. Schedule: none. We must not create sections with filler like "not specified". So only include sections with real content. Thus output:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Pay

Salary Range: $110,000-$160,000 a year.

Optionally include Location as a paragraph maybe under About the role or separate? Could add a

Location: Remote

inside About the role or as its own paragraph before sections. Since location is substantive, we could add a

Location: Remote

after About the role or as its own

not under a heading. The instruction: use

for prose. So we can include a paragraph for location. We must not include any markdown fences. Just raw HTML. Let's craft content precisely, preserving all details. About the role paragraph: combine location maybe separate. Let's write:

Location: Remote

Then About the role: "Technical Lead responsible for ServiceNow ITSM, ITAM, ITOM, CSM, and FSM modules, ITIL process definition, integration solutions, architecture understanding, converting customer business requirements to functional requirements, reviewing requirements for estimation, leading implementation projects, overseeing deployments, migrations, consolidations, upgrades, third‑party tool integration, orchestration, operational activities, project management, issue analysis and resolution, mentoring team, and ensuring alignment with ITIL and industry standards." That's a lot but we need to preserve all substantive info; we can paraphrase but must not invent or summarize away detail. Paraphrasing is okay as long as we keep meaning. We'll try to keep details. Responsibilities list: each bullet from technical competency and behavioral. Let's list: - Experience as a Technical Lead - Experienced in ITIL Process Definition, Integration Solutions, understanding Architecture solution - Understanding customer business requirements and convert to functional requirements - Responsible for reviewing requirements for accurate estimation - Experienced in leading at least a couple of Implementation projects in ITSM / ITAM / ITOM / CSM / FSM area and one complete Implementation lifecycle for ServiceNow - Expertise ServiceNow deployments, ITSM / ITAM / ITOM / CSM / FSM migrations, consolidations, upgrades, integration with other third party tools, Orchestration, operational activities, Project Management expertise - Review, and do proactive analyze and resolve application issues as needed - Mentor and share technical knowledge/guidance to team - Very good ITIL process knowledge and ability to evaluate and bring out the correlations and impacts with respect to customer requirements and ITIL / industry standards - Handles customer meetings and provide weekly/monthly reports for customer as well as TCS management - Good communication in orchestrating customer requirements/needs, solutions, customer responsibilities, risks, challenges and impacts - Excellent team management skills to manage the project team and members - Participate and provide feedback during planning meetings (i.e., pre-iteration, and retrospectives) - Abilities to manage conflicts that may arise with customers and/or TCS internal stakeholders That covers all. Requirements: Must-have technical/functional skills and baseline qualifications. - ServiceNow ITSM / ITAM / ITOM / CSM / FSM and other ServiceNow modules - ITIL process knowledge - Agile/Scrum methodology knowledge - ServiceNow Systems Administrator certification - ServiceNow Implementation Specialist certification - ITIL V3 foundation certification Qualifications: maybe additional certifications preferred. - Preferred ServiceNow Implementation Specialist certification (though already required? Actually required includes Implementation Specialist; preferred says same; but we can note) - ServiceNow CSA certification - ServiceNow CAD certification But we need to avoid duplication. We'll list qualifications as certifications beyond required: CSA, CAD. Skills: maybe technical/functional skills list: ServiceNow custom application design and development, evaluating tool stability and performance, knowledge on new ServiceNow modules (HRSD, SecOps, GRC, SPM, etc.), ability to mentor, etc. But many overlap. We could combine Skills with Requirements but we need separate sections if content distinct. Let's define: Skills: - ServiceNow custom application design and development - Evaluate the tool stability and performance and provide recommendations - Knowledge on new ServiceNow modules (HRSD, SecOps, GRC, SPM, etc.) - Mentor and share technical knowledge/guidance to team (though also responsibility) - Good communication, team management (maybe duplicate) But to avoid duplication, we could keep Skills as the technical/functional skills list from "Must Have Technical/Functional Skills" plus "Good to have" and "Preferred". However we already put Must Have in Requirements. So Skills could be the "Good to have" and "Preferred" items. Thus Skills: - Experience in ServiceNow custom application design and development - Evaluate the tool stability and performance and provide recommendations - Knowledge on new ServiceNow modules (HRSD, SecOps, GRC, SPM, etc.) - Preferred ServiceNow Implementation Specialist certification (though duplicate) - ServiceNow CSA, CAD certifications (maybe) But we need to avoid duplication; maybe better to have Skills as the technical/functional skills (Must Have) and keep Requirements as experience, certifications, methodology. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine into fewer sections: About the role, Responsibilities, Requirements/Qualifications/Skills combined into one "Requirements" section that includes all must-have, qualifications, skills. But we need to use headings only when there is real content. We could have just About the role, Responsibilities, Requirements (which includes all). Pay separate. Let's see: The posting has distinct categories: Must Have Technical/Functional Skills, Roles & Responsibilities, Technical Competency, Behavioral competency, Good to have, Preferred to have, Abilities to manage conflicts, Generic Managerial Skills, Location, Salary. We could map: - About the role: short summary (maybe include location as paragraph before) - Responsibilities: combine Technical Competency + Behavioral competency + Abilities to manage conflicts + Generic Managerial Skills? Actually generic managerial skills maybe part of responsibilities. - Requirements: Must Have Technical/Functional Skills + Certifications + ITIL + Agile/Scrum + Good to have + Preferred to have (these are qualifications/skills) - Pay: salary range. That seems reasonable. Thus sections: About the role, Responsibilities, Requirements, Pay. We'll include location paragraph before About the role or inside. Let's craft:

Location: Remote

About the role

Technical Lead responsible for ServiceNow ITSM, ITAM, ITOM, CSM, and FSM modules, ITIL process definition, integration solutions, architecture understanding, converting customer business requirements to functional requirements, reviewing requirements for estimation, leading implementation projects, overseeing deployments, migrations, consolidations, upgrades, third‑party tool integration, orchestration, operational activities, project management, issue analysis and resolution, mentoring team, and ensuring alignment with ITIL and industry standards.

Responsibilities

• Experience as a Technical Lead
• Experienced in ITIL Process Definition, Integration Solutions,