Sr. Technical Infrastructure Program Manager, Data Center Planning & Delivery
Amazon Web Services (AWS) · Seattle, WA · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Intro paragraph about AWS Infrastructure Services: description of team, role location, etc. This could be "About the role" maybe.
- Then responsibilities: "Key job responsibilities We are seeking a Sr. Technical Infrastructure Program Manager who to own and deliver on end-to-end builds. Working with stakeholder teams to map dependencies, create and drive schedules, as well as think big to solve some of our biggest challenges! We're looking for a highly organized, attention to detail, problem solver with the ability to dive deep into critical path items. This is a high judgement role to deliver capacity to our end customers."
- About The Team section with bullet points: *Why AWS*, *Diverse Experiences*, *Work/Life Balance*, *Inclusive Team Culture*, *Mentorship and Career Growth*. Those are subheadings? The instruction: use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Intro paragraph about AWS Infrastructure Services: description of team, role location, etc. This could be "About the role" maybe.
- Then responsibilities: "Key job responsibilities We are seeking a Sr. Technical Infrastructure Program Manager who to own and deliver on end-to-end builds. Working with stakeholder teams to map dependencies, create and drive schedules, as well as think big to solve some of our biggest challenges! We're looking for a highly organized, attention to detail, problem solver with the ability to dive deep into critical path items. This is a high judgement role to deliver capacity to our end customers."
- About The Team section with bullet points: *Why AWS*, *Diverse Experiences*, *Work/Life Balance*, *Inclusive Team Culture*, *Mentorship and Career Growth*. Those are subheadings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create subheadings for those bullet points; they could be part of "About the role" or maybe "About The Team" could be part of "About the role". But we need to decide.
- Basic Qualifications list: multiple bullet-like lines: "5+ years of program management or technical project management experience", "Bachelor's degree or equivalent, or 5+ years of project/program management experience", "5+ years of building and leading large teams and working in matrixed operating structures experience", "5+ years of MS Project, MS Office, and MS Sharepoint experience". Those are qualifications.
- Preferred Qualifications: "Master's degree or above in engineering, management, or technology, or 3+ years of directly managing and responsible for multiple large projects experience", "4+ years of data center design, construction, operations, or facility maintenance experience", "Experience managing multiple projects, prioritizing, planning, and managing time". Those could be qualifications or skills.
- Benefits: description of benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs.
- Pay: salary ranges listed for three locations: USA, PA, FAIRLESS HILLS - 148,700.00 - 201,200.00 USD annually; similarly for VA Herndon and WA Seattle. So we have Pay info.
- Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section.
- Skills: maybe we can include technical skills: MS Office, MS Project, MS SharePoint, Tableau, KanBan, Playbook, SQL, systems integration. Those could be Skills.
- Requirements: maybe combine Basic Qualifications and Preferred Qualifications? The instruction: sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have:
- About the role: introductory paragraph describing AWS Infrastructure Services, role location, overview.
- Responsibilities: the "Key job responsibilities" paragraph.
- Requirements: maybe the Basic Qualifications (mandatory). Could be "Requirements".
- Qualifications: maybe Preferred Qualifications.
- Skills: technical skills list (MS Office, etc.) plus maybe "ability to influence without authority", "critical thinking", etc. But those are more like competencies; could be Skills.
- Benefits: benefits paragraph.
- Pay: salary ranges.
- Schedule: none, so omit.
We must not repeat job title as heading. Also not include Job ID etc.
We must remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Data Services, Inc." maybe not needed? It's metadata but not a heading; could be folded into short p or dropped. Probably drop.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the description, but we can format them into lists.
We need to ensure we don't lose any info: e.g., location list (Herndon, VA; Seattle, WA; Fairless Hills, PA). That's part of About the role maybe.
Also mention "oversee data center build projects". Also mention "lead cross-functional and technical teams from conceptual design feasibility through scope and schedule creation, budget management, completed design, implementation, commissioning, and data center deployment." That's part of responsibilities maybe.
Also mention "use your judgment, critical thinking skills, ability to influence without authority, analytical talent, technical aptitude, and leadership to collaborate with a diverse set of stakeholders, eliminate non-value-add activities, design solutions, remove blockers, and find creative ways to accelerate project delivery."
Also mention "The successful candidate will be a strong communicator (both written and verbal), not be hindered by ambiguity or competing priorities, and be capable of understanding mechanical/electrical engineering concepts."
Also mention "They will be able to apply a variety of project management tools, methodologies and techniques for all phases of the project lifecycle and exhibit demonstrated experience in core project management disciplines including scope, schedule, budget, resources, quality and risk management, reporting and metric development/tracking."
Also mention "Other requirements include experience with MS Office, MS Project and MS SharePoint. Experience with Tableau, KanBan, Playbook, SQL and systems integration a plus."
Also mention "Key job responsibilities We are seeking a Sr. Technical Infrastructure Program Manager who to own and deliver on end-to-end builds. Working with stakeholder teams to map dependencies, create and drive schedules, as well as think big to solve some of our biggest challenges! We're looking for a highly organized, attention to detail, problem solver with the ability to dive deep into critical path items. This is a high judgement role to deliver capacity to our end customers."
Also mention "About The Team *Why AWS* ..." etc. Those are basically culture/benefits but we already have Benefits section. However those are more about culture, not benefits. Could be part of About the role or maybe a separate section like "About the team". But we only allowed specific headings; we could incorporate that content into About the role or maybe Benefits? But Benefits is for compensation/benefits. The culture points are not benefits; they'd be more like "About the team". Since we don't have a heading for that, we could include them under About the role as a paragraph.
We must not create sections with filler text. So we need to ensure each heading we include has substantive content.
Thus plan:
About the role
About the role
... (intro paragraph plus location plus team description plus culture points)
Responsibilities
- ... each responsibility as list items
Requirements
- ... basic qualifications
Qualifications
- ... preferred qualifications
Skills
- ... technical skills and competencies
Benefits
- ... benefits
Pay
- ... salary ranges per location