Data Center Program Manager
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can only include sections when posting has real specific content. We have responsibilities, skills, qualifications, pay, benefits, job type/location, workplace type, maybe schedule? Not given schedule. So we should not create Schedule section.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading (not given). No Job ID.
We need to preserve all substantive info.
Let's extract content:
Description paragraph: "This role is responsible for optimizing the flow of work and the value delivered by one or more Agile teams supporting the Network AI and Agentic Transformation and is focused on serving the needs of the team to drive performance, predictability, and continuous improvement. Key responsibilities include coordinating and facilitating Agile ceremonies, managing dependencies and impediments, maintaining visibility into delivery plans and progress, and helping ensure deliverables, epics, and stories are advanced in a structured and effective manner. This role supports transformation execution by helping teams maintain healthy backlogs, improve delivery discipline, and align work to agreed priorities and outcomes."
Then "Key Responsibilities" list bullet points.
Then "Skills Data center, program management, agile, jira, automation" then "Top Skills Details Data center,program management,agile,jira,automation" (duplicate). Then "Additional Skills & Qualifications" list.
Then "Experience Level Expert Level"
Then "Job Type & Location This is a Contract position based out of Chandler, AZ."
Then "Pay And Benefits The pay range for this position is $73.00 - $80.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. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: 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)"
Then "Workplace Type This is a hybrid position in Chandler,AZ."
Then "Application Deadline This position is anticipated to close on Sep 30, 2026."
Then "About TEKsystems" paragraphs (two similar). We need to decide whether to include About TEKsystems as a section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list About the company. But we could include it as a section maybe not required. However we should preserve all substantive information. Could include as a
under a generic section? The instruction says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid other headings beyond those listed, but they gave examples. Safer to stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (description), Responsibilities (key responsibilities), Skills (skills list), Qualifications (additional skills & qualifications + experience level), Benefits (benefits list), Pay (pay range). Job Type & Location maybe could go under About the role or as separate? Not in list; but we could embed in About the role paragraph. Workplace type maybe also in About the role. Application deadline maybe also in About the role. But we need to preserve all substantive info; we can include them in paragraphs under About the role.
We must not create Schedule section because no schedule info.
We must not create Requirements section if we don't have explicit requirements separate from qualifications; but we have qualifications. Could treat "Requirements" as qualifications. But we have both "Additional Skills & Qualifications" and "Experience Level". We'll put them under Qualifications.
We need to use
- for any list of duties/requirements/benefits. So responsibilities list as ul. Skills list maybe as ul? It's a list of skills; could be ul. Benefits list as ul.
We need to avoid duplication: Skills listed twice; we should combine.
Let's craft HTML:
About the role
This role is responsible for optimizing the flow of work and the value delivered by one or more Agile teams supporting the Network AI and Agentic Transformation and is focused on serving the needs of the team to drive performance, predictability, and continuous improvement. Key responsibilities include coordinating and facilitating Agile ceremonies, managing dependencies and impediments, maintaining visibility into delivery plans and progress, and helping ensure deliverables, epics, and stories are advanced in a structured and effective manner. This role supports transformation execution by helping teams maintain healthy backlogs, improve delivery discipline, and align work to agreed priorities and outcomes. The position is a Contract role based out of Chandler, AZ, with a hybrid workplace. The anticipated closing date is September 30, 2026.
Responsibilities
- Guide and coach one or more teams on Scrum practices and help strengthen their understanding of Agile principles and delivery discipline.
- Facilitate Agile ceremonies, including sprint planning, daily stand-ups, backlog refinement, reviews, retrospectives, and other delivery routines as needed.
- Help teams maintain a healthy backlog of deliverables, epics, and stories in collaboration with workstream leads and relevant stakeholders.
- Promote structured backlog readiness by helping ensure work is sufficiently defined, sequenced, and understood before team commitment.
- Facilitate dependency management, risk management, and impediment removal to support delivery timelines and team effectiveness.
- Promote communication and collaboration within and across teams to support completion of transformation deliverables and sprint commitments.
- Provide visibility into delivery plans, team progress, blockers, and risks to stakeholders, delivery leads, and transformation leadership.
- Help the team define and reinforce working agreements, including definitions of ready and done, team norms, and execution expectations.
- Enable teams to improve performance through continuous improvement practices, retrospectives, and a focus on measurable execution outcomes.
- Track delivery, maturity, and performance metrics and review them with the team to identify improvement opportunities and execution risks.
Skills
- Data center
- Program management
- Agile
- Jira
- Automation
Qualifications
- Program Management experience – 7+ years of true PM work
- Data Center experience – network infrastructure (understand refreshes, firewall management and proxies, load balancing, routers, switches, etc)
- Cloud migration
- Jira agile / scrum
- ServiceNow (any exposure is good)
- AI automation
- DMZ familiarity (helpful)
- Financial services experience preferred (not a dealbreaker)
- Expert level experience
Pay
The pay range for this position is $73.00 - $80.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 should not include Schedule section.
Check for any boilerplate: We removed EEO, legal, etc. We kept About TEKsystems? We omitted it. Did we lose substantive info? The About TEKsystems paragraphs are generic marketing; maybe not essential but could be considered substantive. However instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About TEKsystems is not boilerplate but could be considered company description. It's not explicitly required to keep, but we might keep it as a section "About the company". However the instruction only gave examples of headings; but we could add a section "About TEKsystems" as About TEKsystems
with paragraphs. It's not prohibited. It says "include a section ONLY when the posting has real, specific content for it". The posting does have that content. So we could include it. However the examples of headings didn't list About the company, but they said e.g. About the role, Responsibilities, etc. It's not forbidden to add other headings. Safer to include it to preserve all substantive info.
Let's add About TEKsystems section after Benefits maybe.
We need to combine the two similar paragraphs into one concise paragraph without duplication.
Paragraph 1: "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, Europe and Asia. As an industry leader in Full-Stack Technology Services, Talent Services, and real-world application, we work with progressive leaders to drive change. That's the power of true partnership. TEKsystems is an Allegis Group company."
Paragraph 2: "We’re a leading provider of business and technology services. We accelerate business transformation for our customers. Our expertise in strategy, design, execution and operations unlocks business value through a range of solutions. We’re a team of 80,000 strong, working with over 6,000 customers, including 80% of the Fortune 500 across North America, Europe and Asia, who partner with us for our scale, full-stack capabilities and speed. We’re strategic thinkers, hands-on collaborators, helping customers capitalize on change and master the momentum of technology. We’re building tomorrow by delivering business outcomes and making positive impacts in our global communities. TEKsystems and TEKsystems Global Services are Allegis Group companies. Learn more at TEKsystems.com."
We can combine: mention team size, customers, Fortune 500, full-stack, Allegis Group, etc. Avoid duplication.
Let's craft:
TEKsystems is a partner in transformation, helping clients activate ideas and solutions to seize new opportunities. With a team of 80,000 serving over 6,000 clients
for prose. We must not repeat job title as heading (not given). No Job ID. We need to preserve all substantive info. Let's extract content: Description paragraph: "This role is responsible for optimizing the flow of work and the value delivered by one or more Agile teams supporting the Network AI and Agentic Transformation and is focused on serving the needs of the team to drive performance, predictability, and continuous improvement. Key responsibilities include coordinating and facilitating Agile ceremonies, managing dependencies and impediments, maintaining visibility into delivery plans and progress, and helping ensure deliverables, epics, and stories are advanced in a structured and effective manner. This role supports transformation execution by helping teams maintain healthy backlogs, improve delivery discipline, and align work to agreed priorities and outcomes." Then "Key Responsibilities" list bullet points. Then "Skills Data center, program management, agile, jira, automation" then "Top Skills Details Data center,program management,agile,jira,automation" (duplicate). Then "Additional Skills & Qualifications" list. Then "Experience Level Expert Level" Then "Job Type & Location This is a Contract position based out of Chandler, AZ." Then "Pay And Benefits The pay range for this position is $73.00 - $80.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. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: 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)" Then "Workplace Type This is a hybrid position in Chandler,AZ." Then "Application Deadline This position is anticipated to close on Sep 30, 2026." Then "About TEKsystems" paragraphs (two similar). We need to decide whether to include About TEKsystems as a section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list About the company. But we could include it as a section maybe not required. However we should preserve all substantive information. Could include as a
under a generic section? The instruction says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid other headings beyond those listed, but they gave examples. Safer to stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (description), Responsibilities (key responsibilities), Skills (skills list), Qualifications (additional skills & qualifications + experience level), Benefits (benefits list), Pay (pay range). Job Type & Location maybe could go under About the role or as separate? Not in list; but we could embed in About the role paragraph. Workplace type maybe also in About the role. Application deadline maybe also in About the role. But we need to preserve all substantive info; we can include them in paragraphs under About the role. We must not create Schedule section because no schedule info. We must not create Requirements section if we don't have explicit requirements separate from qualifications; but we have qualifications. Could treat "Requirements" as qualifications. But we have both "Additional Skills & Qualifications" and "Experience Level". We'll put them under Qualifications. We need to use
- for any list of duties/requirements/benefits. So responsibilities list as ul. Skills list maybe as ul? It's a list of skills; could be ul. Benefits list as ul.
We need to avoid duplication: Skills listed twice; we should combine.
Let's craft HTML:
About the role
This role is responsible for optimizing the flow of work and the value delivered by one or more Agile teams supporting the Network AI and Agentic Transformation and is focused on serving the needs of the team to drive performance, predictability, and continuous improvement. Key responsibilities include coordinating and facilitating Agile ceremonies, managing dependencies and impediments, maintaining visibility into delivery plans and progress, and helping ensure deliverables, epics, and stories are advanced in a structured and effective manner. This role supports transformation execution by helping teams maintain healthy backlogs, improve delivery discipline, and align work to agreed priorities and outcomes. The position is a Contract role based out of Chandler, AZ, with a hybrid workplace. The anticipated closing date is September 30, 2026.
Responsibilities
- Guide and coach one or more teams on Scrum practices and help strengthen their understanding of Agile principles and delivery discipline.
- Facilitate Agile ceremonies, including sprint planning, daily stand-ups, backlog refinement, reviews, retrospectives, and other delivery routines as needed.
- Help teams maintain a healthy backlog of deliverables, epics, and stories in collaboration with workstream leads and relevant stakeholders.
- Promote structured backlog readiness by helping ensure work is sufficiently defined, sequenced, and understood before team commitment.
- Facilitate dependency management, risk management, and impediment removal to support delivery timelines and team effectiveness.
- Promote communication and collaboration within and across teams to support completion of transformation deliverables and sprint commitments.
- Provide visibility into delivery plans, team progress, blockers, and risks to stakeholders, delivery leads, and transformation leadership.
- Help the team define and reinforce working agreements, including definitions of ready and done, team norms, and execution expectations.
- Enable teams to improve performance through continuous improvement practices, retrospectives, and a focus on measurable execution outcomes.
- Track delivery, maturity, and performance metrics and review them with the team to identify improvement opportunities and execution risks.
Skills
- Data center
- Program management
- Agile
- Jira
- Automation
Qualifications
- Program Management experience – 7+ years of true PM work
- Data Center experience – network infrastructure (understand refreshes, firewall management and proxies, load balancing, routers, switches, etc)
- Cloud migration
- Jira agile / scrum
- ServiceNow (any exposure is good)
- AI automation
- DMZ familiarity (helpful)
- Financial services experience preferred (not a dealbreaker)
- Expert level experience
Pay
The pay range for this position is $73.00 - $80.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)
About TEKsystems
with paragraphs. It's not prohibited. It says "include a section ONLY when the posting has real, specific content for it". The posting does have that content. So we could include it. However the examples of headings didn't list About the company, but they said e.g. About the role, Responsibilities, etc. It's not forbidden to add other headings. Safer to include it to preserve all substantive info. Let's add About TEKsystems section after Benefits maybe. We need to combine the two similar paragraphs into one concise paragraph without duplication. Paragraph 1: "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, Europe and Asia. As an industry leader in Full-Stack Technology Services, Talent Services, and real-world application, we work with progressive leaders to drive change. That's the power of true partnership. TEKsystems is an Allegis Group company." Paragraph 2: "We’re a leading provider of business and technology services. We accelerate business transformation for our customers. Our expertise in strategy, design, execution and operations unlocks business value through a range of solutions. We’re a team of 80,000 strong, working with over 6,000 customers, including 80% of the Fortune 500 across North America, Europe and Asia, who partner with us for our scale, full-stack capabilities and speed. We’re strategic thinkers, hands-on collaborators, helping customers capitalize on change and master the momentum of technology. We’re building tomorrow by delivering business outcomes and making positive impacts in our global communities. TEKsystems and TEKsystems Global Services are Allegis Group companies. Learn more at TEKsystems.com." We can combine: mention team size, customers, Fortune 500, full-stack, Allegis Group, etc. Avoid duplication. Let's craft:TEKsystems is a partner in transformation, helping clients activate ideas and solutions to seize new opportunities. With a team of 80,000 serving over 6,000 clients