Client Service Delivery Lead
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them.
Let's parse the posting.
Content:
- Opening: "Our Fortune 500 client is looking for hardworking, motivated talent to join their innovative team. Are you interested in working with them. Don't wait... apply today!" This is promotional, maybe considered boilerplate? It's not a section heading. Might be considered part of About the role? But we need to preserve substantive info. It's basically a call to apply. Might be considered application instruction? It says "apply today!" but not specific instructions. Probably we can drop as it's generic.
- Position Title: Client Service Delivery Lead (but we must not repeat job title as heading). So we can ignore.
- Location: Houston TX
- Duration: 15+ Months Contract with chances of extension
- Pay range: $80-$90/hr.(Open for c2c and w2 both)
- Job Description: then sections.
- Must-have skills: Identity & Access Management Skills
- Years of experience required for each skill? At least 10 years in IT
- Nice-to-have skills: Saviynt, OKTA, Entra, AD, CyberArk, PAM
- Role Summary: paragraph.
- Key Responsibilities: bullet list.
- Team Leadership & People Management: bullet list.
- Stakeholder & Client Management: bullet list.
- IAM Governance & Strategic Leadership: bullet list.
- Technical Leadership: bullet list.
- Required Skills & Experience: bullet list.
- Technical Skills Required: bullet list.
- Leadership Expectations: bullet list.
- Then "If this is a role that interests you and you’d like to learn more, click apply now and a recruiter will be in touch with you to discuss this great opportunity. We look forward to speaking with you!" This is application instruction, drop.
- Then About ManpowerGroup... This is company boilerplate, drop.
Thus we need to extract sections: About the role (maybe Role Summary), Responsibilities (Key Responsibilities etc), Requirements (maybe Years of experience?), Qualifications (maybe Required Skills & Experience?), Skills (Must-have and Nice-to-have?), Benefits (none), Pay (yes we have pay range), Schedule (maybe Duration? Could be considered schedule? The posting includes Duration: 15+ Months Contract with chances of extension. That's more about contract length, not schedule like full-time/part-time. The instruction says include Schedule section only if posting actually states them. Does it state schedule? Not explicitly like "Full-time", "Part-time", "Shift". Duration is not schedule. So we likely should not create Schedule section. Benefits: none mentioned. So we omit Benefits.
Pay: we have pay range: $80-$90/hr.(Open for c2c and w2 both). So we include Pay section.
Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content.
About the role: Could be Role Summary paragraph.
Responsibilities: combine all responsibility bullet points (Service Delivery & Operations Management, Team Leadership & People Management, Stakeholder & Client Management, IAM Governance & Strategic Leadership, Technical Leadership). Could be one with items.
Requirements: Could be Years of experience required (At least 10 years in IT) plus maybe Required Skills & Experience? But Required Skills & Experience is more like qualifications. The distinction between Requirements and Qualifications is fuzzy. We'll follow typical: Requirements = mandatory experience/skills; Qualifications = education/certifications? Not present. We'll put Years of experience and maybe Required Skills & Experience under Requirements? But we also have Skills section for Must-have and Nice-to-have skills. Let's think.
We have Must-have skills: Identity & Access Management Skills (vague). Nice-to-have skills: list of specific tech.
We have Required Skills & Experience: bullet list of experience leading IAM service delivery teams, managing client relationships, hands-on experience with identity lifecycle etc, experience within ITIL, analytical skills.
We have Technical Skills Required: list of specific tech (Saviynt etc) plus Preferred list.
We have Leadership Expectations: bullet list.
We could combine Required Skills & Experience and Technical Skills Required and Leadership Expectations into a Skills section? But the instruction says use for section headings like Skills. So we can have a Skills section that includes both must-have, nice-to-have, required, technical, leadership expectations. However we must not invent or summarize away detail; we need to preserve ALL substantive information. So we need to list each bullet point exactly as given, not summarizing.
Thus we could have multiple sub-sections within Skills? But we only allowed headings from the list. We could have multiple under Skills heading, each preceded by a describing category? That's okay.
Alternatively we could split into Requirements (years of experience), Qualifications (maybe Required Skills & Experience), Skills (must-have/nice-to-have/technical/leadership). But we need to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into two sections: About the role (Role Summary), Responsibilities (all responsibility bullets), and Skills/Qualifications (everything else). But we also need Pay section.
Thus we could have:
About the role
Role Summary paragraph.
Responsibilities
... all responsibility bullets ...
Skills and Qualifications
but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot use "Skills and Qualifications". We could use "Qualifications" for Required Skills & Experience and Leadership Expectations, and "Skills" for must-have/nice-to-have/technical. Or we could use "Requirements" for years of experience and maybe Required Skills & Experience, and "Skills" for the rest.
Let's decide:
- Requirements: Years of experience required (At least 10 years in IT). Could also include Required Skills & Experience? But that is more like qualifications. However we can put Required Skills & Experience under Requirements as they are required.
- Qualifications: maybe not needed if we don't have education/certifications. Could omit Qualifications section if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we have no content for Qualifications, we should omit it.
- Skills: Must-have skills, Nice-to-have skills, Technical Skills Required, Leadership Expectations.
Thus we have sections: About the role, Responsibilities, Requirements, Skills, Pay.
Check if we have any content for Benefits: none, so omit.
Schedule: we have Duration but not schedule; we could treat Duration as schedule? The instruction says include Schedule section only if posting actually states them. Does it state schedule? Not explicitly like "Full-time", "Part-time", "Shift". Duration is not schedule. So we omit Schedule.
Now we need to preserve all substantive information. Let's extract each piece.
About the role: Role Summary paragraph:
"The Onsite Identity and Access Management (IAM) Lead is responsible for the successful delivery, governance, and continuous improvement of IAM services for the client. This role serves as the primary onsite point of contact for IAM operations, driving service excellence, stakeholder engagement, team leadership, and strategic IAM initiatives. The IAM Lead is accountable for service delivery performance, resource management, quality assurance, client satisfaction, and alignment of IAM capabilities with business and security objectives."
We should keep that as a .
Responsibilities: we have multiple subheadings with bullet points. We need to combine them into a single
list? The instruction: Use - for any list of duties/requirements/benefits. So we can flatten all responsibility bullets into a single list. However we might lose the grouping headings (Service Delivery & Operations Management etc). But we could keep them as
headings inside? Not allowed because only
for section headings. We could keep subheadings as or something? Not specified. The instruction only says use for section headings, - for any list,
for prose. It doesn't forbid using other HTML like inside . But to be safe, we can keep the grouping as
before each group? That would be prose, not a list. But the instruction says use
- for any list of duties/requirements/benefits. It doesn't say we cannot have prose before lists. So we could have
Service Delivery & Operations Management
then ... but that might be considered a heading? Not exactly. Safer to just make a flat list of all duty items, preserving the text exactly as given. However we need to ensure we don't lose any nuance. The duty items are bullet points under each subheading. We can just list them all.
Let's extract each bullet:
From Service Delivery & Operations Management:
- Lead the day-to-day delivery of IAM services, ensuring alignment with contractual obligations, service level agreements (SLAs), and client expectations.
- Oversee incident, request, problem, and change management activities related to IAM services.
- Monitor, analyze, and report on service delivery metrics, KPIs, and operational performance, driving corrective actions where necessary.
- Ensure adherence to established processes, security controls, compliance requirements, and operational standards.
- Identify service improvement opportunities and lead initiatives to enhance service quality, efficiency, and user experience.
Team Leadership & People Management:
- Lead and manage the IAM delivery team, including work assignment, workload balancing, performance management, coaching, and career development.
- Establish clear priorities, objectives, and accountability across the team.
- Foster a culture of collaboration, innovation, continuous learning, and operational excellence.
- Support talent development through mentoring, knowledge sharing, and technical guidance.
Stakeholder & Client Management:
- Act as the primary onsite liaison between the client, leadership, and offshore delivery teams.
- Build strong relationships with client stakeholders and provide regular updates on service performance, risks, and strategic initiatives.
- Facilitate governance meetings, operational reviews, and executive-level discussions.
- Proactively manage escalations, risks, dependencies, and client concerns to ensure timely resolution.
IAM Governance & Strategic Leadership:
- Provide leadership and oversight for identity lifecycle management, access governance, privileged access management, authentication, and federation services.
- Drive IAM transformation initiatives and support the implementation of industry-leading security practices.
- Collaborate with security, infrastructure, application, compliance, and audit teams to strengthen the client's security posture.
- Support audit, compliance, and regulatory activities by ensuring effective IAM controls and governance processes.
Technical Leadership:
- Serve as a subject matter expert for IAM technologies and provide strategic guidance on IAM solutions and best practices.
- Review solution designs, operational processes, and platform enhancements to ensure scalability, security, and compliance.
- Support troubleshooting of complex IAM issues and provide direction for resolution across multiple technology domains.
Now Requirements: We have "Years of experience required for each skill? At least 10 years in IT". Also maybe "Must-have skills: Identity & Access Management Skills" but that's more skill. We'll treat years of experience as requirement.
Also maybe "Required Skills & Experience" could be considered requirements. But we already have Skills section for technical skills. However Required Skills & Experience includes experience leading teams, managing client relationships, hands-on experience
for section headings like Skills. So we can have a Skills section that includes both must-have, nice-to-have, required, technical, leadership expectations. However we must not invent or summarize away detail; we need to preserve ALL substantive information. So we need to list each bullet point exactly as given, not summarizing.
Thus we could have multiple sub-sections within Skills? But we only allowed headings from the list. We could have multiple under Skills heading, each preceded by a describing category? That's okay.
Alternatively we could split into Requirements (years of experience), Qualifications (maybe Required Skills & Experience), Skills (must-have/nice-to-have/technical/leadership). But we need to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into two sections: About the role (Role Summary), Responsibilities (all responsibility bullets), and Skills/Qualifications (everything else). But we also need Pay section.
Thus we could have:
About the role
Role Summary paragraph.
Responsibilities
... all responsibility bullets ...
Skills and Qualifications
but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot use "Skills and Qualifications". We could use "Qualifications" for Required Skills & Experience and Leadership Expectations, and "Skills" for must-have/nice-to-have/technical. Or we could use "Requirements" for years of experience and maybe Required Skills & Experience, and "Skills" for the rest.
Let's decide:
- Requirements: Years of experience required (At least 10 years in IT). Could also include Required Skills & Experience? But that is more like qualifications. However we can put Required Skills & Experience under Requirements as they are required.
- Qualifications: maybe not needed if we don't have education/certifications. Could omit Qualifications section if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we have no content for Qualifications, we should omit it.
- Skills: Must-have skills, Nice-to-have skills, Technical Skills Required, Leadership Expectations.
Thus we have sections: About the role, Responsibilities, Requirements, Skills, Pay.
Check if we have any content for Benefits: none, so omit.
Schedule: we have Duration but not schedule; we could treat Duration as schedule? The instruction says include Schedule section only if posting actually states them. Does it state schedule? Not explicitly like "Full-time", "Part-time", "Shift". Duration is not schedule. So we omit Schedule.
Now we need to preserve all substantive information. Let's extract each piece.
About the role: Role Summary paragraph:
"The Onsite Identity and Access Management (IAM) Lead is responsible for the successful delivery, governance, and continuous improvement of IAM services for the client. This role serves as the primary onsite point of contact for IAM operations, driving service excellence, stakeholder engagement, team leadership, and strategic IAM initiatives. The IAM Lead is accountable for service delivery performance, resource management, quality assurance, client satisfaction, and alignment of IAM capabilities with business and security objectives."
We should keep that as a .
Responsibilities: we have multiple subheadings with bullet points. We need to combine them into a single
list? The instruction: Use - for any list of duties/requirements/benefits. So we can flatten all responsibility bullets into a single list. However we might lose the grouping headings (Service Delivery & Operations Management etc). But we could keep them as
headings inside? Not allowed because only
for section headings. We could keep subheadings as or something? Not specified. The instruction only says use for section headings, - for any list,
for prose. It doesn't forbid using other HTML like inside . But to be safe, we can keep the grouping as
before each group? That would be prose, not a list. But the instruction says use
- for any list of duties/requirements/benefits. It doesn't say we cannot have prose before lists. So we could have
Service Delivery & Operations Management
then ... but that might be considered a heading? Not exactly. Safer to just make a flat list of all duty items, preserving the text exactly as given. However we need to ensure we don't lose any nuance. The duty items are bullet points under each subheading. We can just list them all.
Let's extract each bullet:
From Service Delivery & Operations Management:
- Lead the day-to-day delivery of IAM services, ensuring alignment with contractual obligations, service level agreements (SLAs), and client expectations.
- Oversee incident, request, problem, and change management activities related to IAM services.
- Monitor, analyze, and report on service delivery metrics, KPIs, and operational performance, driving corrective actions where necessary.
- Ensure adherence to established processes, security controls, compliance requirements, and operational standards.
- Identify service improvement opportunities and lead initiatives to enhance service quality, efficiency, and user experience.
Team Leadership & People Management:
- Lead and manage the IAM delivery team, including work assignment, workload balancing, performance management, coaching, and career development.
- Establish clear priorities, objectives, and accountability across the team.
- Foster a culture of collaboration, innovation, continuous learning, and operational excellence.
- Support talent development through mentoring, knowledge sharing, and technical guidance.
Stakeholder & Client Management:
- Act as the primary onsite liaison between the client, leadership, and offshore delivery teams.
- Build strong relationships with client stakeholders and provide regular updates on service performance, risks, and strategic initiatives.
- Facilitate governance meetings, operational reviews, and executive-level discussions.
- Proactively manage escalations, risks, dependencies, and client concerns to ensure timely resolution.
IAM Governance & Strategic Leadership:
- Provide leadership and oversight for identity lifecycle management, access governance, privileged access management, authentication, and federation services.
- Drive IAM transformation initiatives and support the implementation of industry-leading security practices.
- Collaborate with security, infrastructure, application, compliance, and audit teams to strengthen the client's security posture.
- Support audit, compliance, and regulatory activities by ensuring effective IAM controls and governance processes.
Technical Leadership:
- Serve as a subject matter expert for IAM technologies and provide strategic guidance on IAM solutions and best practices.
- Review solution designs, operational processes, and platform enhancements to ensure scalability, security, and compliance.
- Support troubleshooting of complex IAM issues and provide direction for resolution across multiple technology domains.
Now Requirements: We have "Years of experience required for each skill? At least 10 years in IT". Also maybe "Must-have skills: Identity & Access Management Skills" but that's more skill. We'll treat years of experience as requirement.
Also maybe "Required Skills & Experience" could be considered requirements. But we already have Skills section for technical skills. However Required Skills & Experience includes experience leading teams, managing client relationships, hands-on experience
describing category? That's okay. Alternatively we could split into Requirements (years of experience), Qualifications (maybe Required Skills & Experience), Skills (must-have/nice-to-have/technical/leadership). But we need to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into two sections: About the role (Role Summary), Responsibilities (all responsibility bullets), and Skills/Qualifications (everything else). But we also need Pay section. Thus we could have:
About the role
Role Summary paragraph.
Responsibilities
- ... all responsibility bullets ...
Skills and Qualifications
but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot use "Skills and Qualifications". We could use "Qualifications" for Required Skills & Experience and Leadership Expectations, and "Skills" for must-have/nice-to-have/technical. Or we could use "Requirements" for years of experience and maybe Required Skills & Experience, and "Skills" for the rest. Let's decide: - Requirements: Years of experience required (At least 10 years in IT). Could also include Required Skills & Experience? But that is more like qualifications. However we can put Required Skills & Experience under Requirements as they are required. - Qualifications: maybe not needed if we don't have education/certifications. Could omit Qualifications section if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we have no content for Qualifications, we should omit it. - Skills: Must-have skills, Nice-to-have skills, Technical Skills Required, Leadership Expectations. Thus we have sections: About the role, Responsibilities, Requirements, Skills, Pay. Check if we have any content for Benefits: none, so omit. Schedule: we have Duration but not schedule; we could treat Duration as schedule? The instruction says include Schedule section only if posting actually states them. Does it state schedule? Not explicitly like "Full-time", "Part-time", "Shift". Duration is not schedule. So we omit Schedule. Now we need to preserve all substantive information. Let's extract each piece. About the role: Role Summary paragraph: "The Onsite Identity and Access Management (IAM) Lead is responsible for the successful delivery, governance, and continuous improvement of IAM services for the client. This role serves as the primary onsite point of contact for IAM operations, driving service excellence, stakeholder engagement, team leadership, and strategic IAM initiatives. The IAM Lead is accountable for service delivery performance, resource management, quality assurance, client satisfaction, and alignment of IAM capabilities with business and security objectives." We should keep that as a. Responsibilities: we have multiple subheadings with bullet points. We need to combine them into a single
- list? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten all responsibility bullets into a single list. However we might lose the grouping headings (Service Delivery & Operations Management etc). But we could keep them as
headings inside? Not allowed because only
for section headings. We could keep subheadings as or something? Not specified. The instruction only says use
for section headings,
- for any list,
for prose. It doesn't forbid using other HTML like inside
. But to be safe, we can keep the grouping as
before each group? That would be prose, not a list. But the instruction says use
- for any list of duties/requirements/benefits. It doesn't say we cannot have prose before lists. So we could have
Service Delivery & Operations Management
then- ... but that might be considered a heading? Not exactly. Safer to just make a flat list of all duty items, preserving the text exactly as given. However we need to ensure we don't lose any nuance. The duty items are bullet points under each subheading. We can just list them all.
Let's extract each bullet:
From Service Delivery & Operations Management:
- Lead the day-to-day delivery of IAM services, ensuring alignment with contractual obligations, service level agreements (SLAs), and client expectations.
- Oversee incident, request, problem, and change management activities related to IAM services.
- Monitor, analyze, and report on service delivery metrics, KPIs, and operational performance, driving corrective actions where necessary.
- Ensure adherence to established processes, security controls, compliance requirements, and operational standards.
- Identify service improvement opportunities and lead initiatives to enhance service quality, efficiency, and user experience.
Team Leadership & People Management:
- Lead and manage the IAM delivery team, including work assignment, workload balancing, performance management, coaching, and career development.
- Establish clear priorities, objectives, and accountability across the team.
- Foster a culture of collaboration, innovation, continuous learning, and operational excellence.
- Support talent development through mentoring, knowledge sharing, and technical guidance.
Stakeholder & Client Management:
- Act as the primary onsite liaison between the client, leadership, and offshore delivery teams.
- Build strong relationships with client stakeholders and provide regular updates on service performance, risks, and strategic initiatives.
- Facilitate governance meetings, operational reviews, and executive-level discussions.
- Proactively manage escalations, risks, dependencies, and client concerns to ensure timely resolution.
IAM Governance & Strategic Leadership:
- Provide leadership and oversight for identity lifecycle management, access governance, privileged access management, authentication, and federation services.
- Drive IAM transformation initiatives and support the implementation of industry-leading security practices.
- Collaborate with security, infrastructure, application, compliance, and audit teams to strengthen the client's security posture.
- Support audit, compliance, and regulatory activities by ensuring effective IAM controls and governance processes.
Technical Leadership:
- Serve as a subject matter expert for IAM technologies and provide strategic guidance on IAM solutions and best practices.
- Review solution designs, operational processes, and platform enhancements to ensure scalability, security, and compliance.
- Support troubleshooting of complex IAM issues and provide direction for resolution across multiple technology domains.
Now Requirements: We have "Years of experience required for each skill? At least 10 years in IT". Also maybe "Must-have skills: Identity & Access Management Skills" but that's more skill. We'll treat years of experience as requirement.
Also maybe "Required Skills & Experience" could be considered requirements. But we already have Skills section for technical skills. However Required Skills & Experience includes experience leading teams, managing client relationships, hands-on experience
- for any list of duties/requirements/benefits. It doesn't say we cannot have prose before lists. So we could have
- for any list,