AWS Infrastructure Project Manager
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. Let's parse the posting.
First part: "Top Skills On-premises to AWS migrations AWS modernization and infrastructure transformation initiatives Cloud-to-cloud migrations Application and infrastructure hosting strategies within AWS Hybrid cloud deployments integrating on-prem and AWS environments". That's a list of top skills. So we can have a Skills section with those items.
Then "Role Details Responsible for end-to-end management and delivery and tracking for programs of high complexity across multiple departments within a single business unit. Facilitates Agile Scrum Master and Waterfall service deliveries, leads and directs the Program efforts that are functionally aligned. Responsible for the end-to-end integration of various projects within those programs under these initiatives in order to deliver the holistic program of projects, the position specific responsibilities include: Manages Portfolio of Programs Leads and manages program efforts including regular updates, tracking, escalations and other program management related tasks. Removes impediments to the ability of the team to deliver and is keenly focused on the activities and progress of the service delivery team. Executes PMO related tasks for Program standards and governance to ensure policies and best practices are followed through the portfolio of programs. Timeline and Budget/Expenses Obtain and align resources to key project roles; establish clearly defined responsibilities and accountabilities Process improvements and change management JIRA Expertise with Microsoft products: PowerPoint, Project, Excel, OneNotes, etc. Oversight/Manage/Lead project execution, integration, and implementation Risk Management and Mitigation Planning Lead end-to-end delivery of infrastructure and cloud transformation projects, including planning, execution, monitoring, and implementation through project closure. Manage complex infrastructure initiatives involving servers, operating systems, middleware, databases, networking, and cloud environments. Drive large-scale cloud migration projects, with a strong focus on AWS public cloud environments, Including Partner with cloud engineering, architecture, security, infrastructure, application, and operations teams to coordinate successful delivery of cloud-based solutions. Manage server lifecycle initiatives, including:Server migrations (on-prem to on-prem, on-prem to cloud, and cloud-to-cloud)End-of-Life (EOL) and End-of-Support (EOS) remediationServer provisioning and deployment (Windows and Linux environments)Server decommissioning and data center exits Possess sufficient infrastructure and cloud knowledge to effectively manage project timelines, dependencies, risks, and resource planning without serving in an engineering or administrator capacity. Understand how core infrastructure components interact across cloud and on-prem environments, including servers, middleware, databases, storage, applications, and network services. Develop and maintain detailed project plans, schedules, RAID logs, executive reporting, and stakeholder communications. Ensure compliance with financial services governance, including risk management, audit requirements, security controls, change management, and regulatory standards. Facilitate technical discussions, manage dependencies, and resolve cross-functional issues among infrastructure, cloud, security, networking, and application teams. Manage project communications, including executive-level updates, stakeholder briefings, and program status reporting. Ensure operational readiness, knowledge transfer, and successful transition of delivered solutions to support and operations teams."
That's a lot of responsibilities. So we can have a Responsibilities section with bullet list.
Then "Experience Level Expert Level". That's a qualification/experience. Could be under Qualifications or Requirements. We'll treat as Qualifications.
"Job Type & Location This is a Contract position based out of Charlotte, NC." That's job type and location; we could put under About the role? Actually "About the role" is a generic heading; we could put description of role there. But we already have responsibilities. The "About the role" could include brief overview: maybe we can combine the initial description? The posting didn't have a separate "About the role" heading; but we can create one with a short paragraph summarizing role. However we must not invent content; we can use the first sentence(s) that describe role: "Responsible for end-to-end management and delivery and tracking for programs of high complexity across multiple departments within a single business unit." That's part of responsibilities. Might be okay to put under About the role a brief summary: maybe we can take the first sentence before responsibilities? Actually the text starts with "Top Skills ..." then "Role Details Responsible for end-to-end management..." So we could treat the first sentence after "Role Details" as about the role. But we already using Responsibilities for detailed list. Could still have About the role with a short paragraph: maybe "Responsible for end-to-end management and delivery and tracking for programs of high complexity across multiple departments within a single business unit. Facilitates Agile Scrum Master and Waterfall service deliveries, leads and directs the Program efforts that are functionally aligned." That's still responsibilities. But we can split: About the role: overview; Responsibilities: bullet list. It's okay to have some overlap? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Overlap is okay as long as we don't lose info. We could put overview in About the role and then responsibilities list includes more detail. That's fine.
Then "Pay And Benefits The pay range for this position is $60.00 - $70.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)". So we have Pay and Benefits sections. We'll create Pay section with the pay range. Benefits section with bullet list of benefits.
Then "Workplace Type This is a hybrid position in Charlotte,NC." That's schedule? Actually schedule could be hybrid; but we have a Schedule section only if posting states schedule details. It says hybrid position; that's workplace type, not schedule. Could treat as Schedule? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Schedule if there is schedule info. The posting says "Workplace Type This is a hybrid position in Charlotte,NC." That's not exactly schedule (like full-time, part-time, shift). Might be considered workplace type, not schedule. Since we don't have explicit schedule (like hours), we might omit Schedule section. Or we could treat hybrid as schedule? Probably better to omit Schedule because not explicit schedule details.
Then "Application Deadline This position is anticipated to close on Oct 2, 2026." That's metadata; we could fold into a short
maybe under About the role or at end. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with application deadline. Then the rest about TEKsystems is boilerplate (EEO etc.) which we should remove. Thus sections we will include: - About the role (overview paragraph) - Responsibilities (ul li list) - Qualifications (maybe Experience Level Expert Level) - Skills (ul li list of top skills) - Pay (p with pay range) - Benefits (ul li list) - Possibly Requirements? Not explicitly listed; we have qualifications and skills. Could combine Qualifications and Requirements? The instruction says use those headings if content exists. We have "Experience Level Expert Level" as qualification. Could also include "JIRA Expertise with Microsoft products: PowerPoint, Project, Excel, OneNotes, etc." as requirement. That could go under Requirements. But we already have skills list; maybe we separate: Skills = top skills list; Requirements = JIRA expertise, Microsoft products, etc. However the posting also includes "Process improvements and change management" etc. That's more responsibilities. Let's parse: Under Role Details after bullet list there is "Timeline and Budget/Expenses Obtain and align resources to key project roles; establish clearly defined responsibilities and accountabilities Process improvements and change management JIRA Expertise with Microsoft products: PowerPoint, Project, Excel, OneNotes, etc." That seems like a list of requirements/expertise. So we can put those under Requirements. Thus sections: About the role: short paragraph summarizing role (maybe first two sentences). Responsibilities: bullet list of responsibilities (the long list after "Manages Portfolio of Programs" etc.) Requirements: bullet list: JIRA Expertise with Microsoft products: PowerPoint, Project, Excel, OneNotes, etc.; Process improvements and change management; Timeline and Budget/Expenses Obtain and align resources to key project roles; establish clearly defined responsibilities and accountabilities; maybe also "Experience Level Expert Level" could go under Qualifications. Qualifications: "Expert Level" experience. Skills: bullet list of top skills (On-premises to AWS migrations, AWS modernization..., Cloud-to-cloud migrations, Application and infrastructure hosting strategies within AWS, Hybrid cloud deployments integrating on-prem and AWS environments). Pay: p with "$60.00 - $70.00/hr." Benefits: ul li list of benefits. We should also include maybe a short paragraph for Application Deadline as minor metadata. We must not include boilerplate like TEKsystems description, EEO, etc. Now produce HTML fragment: only the elements, no html/body tags. We'll wrap sections in appropriate tags: each section starts with
Heading
then content. For About the role:...
For Responsibilities:- ... each item
- ... each item
Expert Level
maybe. For Skills:- ... each item
$60.00 - $70.00/hr.
For Benefits:- ... each benefit
for Application Deadline. Make sure to preserve all substantive information: we need to include all bullet points from responsibilities, requirements, skills, benefits. Let's extract responsibilities list precisely. From text after "the position specific responsibilities include:" we have: - Manages Portfolio of Programs - Leads and manages program efforts including regular updates, tracking, escalations and other program management related tasks. - Removes impediments to the ability of the team to deliver and is keenly focused on the activities and progress of the service delivery team. - Executes PMO related tasks for Program standards and governance to ensure policies and best practices are followed through the portfolio of programs. - Timeline and Budget/Expenses Obtain and align resources to key project roles; establish clearly defined responsibilities and accountabilities - Process improvements and change management - JIRA Expertise with Microsoft products: PowerPoint, Project, Excel, OneNotes, etc. - Oversight/Manage/Lead project execution, integration, and implementation - Risk Management and Mitigation Planning - Lead end-to-end delivery of infrastructure and cloud transformation projects, including planning, execution, monitoring, and implementation through project closure. - Manage complex infrastructure initiatives involving servers, operating systems, middleware, databases, networking, and cloud environments. - Drive large-scale cloud migration projects, with a strong focus on AWS public cloud environments, - Including Partner with cloud engineering, architecture, security, infrastructure, application, and operations teams to coordinate successful delivery of cloud-based solutions. - Manage server lifecycle initiatives, including: - Server migrations (on-prem to on-prem, on-prem to cloud, and