Program Integration Manager, Defense, Global Defense Program Management Office
Amazon Web Services (AWS) · Arlington, VA · 1 mo ago
AdvertisingFull-time
We need to output HTML fragment with sections: About the role? The description includes description paragraphs. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, accommodation, etc. Must preserve all substantive info.
We need to parse the posting.
Key parts:
- Description paragraph: "Do you want to help deliver cloud technology to the Department of War (DoW)? ..." This is about the role. Could be "About the role" section.
- Key job responsibilities: list of responsibilities bullet points.
- A day in the life: narrative description; could be part of responsibilities or separate? Could be "Responsibilities" maybe includes both. But we have a separate "A day in the life" which is more narrative; could be placed under "About the role" or separate "Day in the Life". However headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create custom headings like "A day in the life". So we need to fit content into allowed headings. Probably put narrative under "About the role" or "Responsibilities". Since "A day in the life" describes typical activities, could be part of Responsibilities.
- About The Team: could be "About the role" or maybe "About the team" not allowed; could go under "About the role".
- Basic Qualifications: that's Requirements/Qualifications. We have both Requirements and Qualifications headings allowed. We need to decide what to put where. Usually "Requirements" for basic qualifications, "Preferred Qualifications" for preferred. So we can put Basic Qualifications under "Requirements" (or "Qualifications") and Preferred Qualifications under "Qualifications". But we have both headings; we need to avoid duplication. Could put Basic Qualifications under "Requirements" and Preferred Qualifications under "Qualifications". Or vice versa. Let's decide: Requirements = basic qualifications; Qualifications = preferred qualifications.
- Skills: not explicitly listed; we could infer from responsibilities but better not to create unless explicit. The posting does not have a separate Skills section. So we should not create Skills section.
- Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave." Also mentions sign-on payments and RSUs. That's benefits. So we can include Benefits section.
- Pay: The posting includes base salary range: "USA, VA, Arlington - 147,900.00 - 200,100.00 USD annually". Also mentions sign-on payments and RSUs. So we can include Pay section.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines.
We need to preserve all substantive information. Let's extract.
Description paragraph:
"Do you want to help deliver cloud technology to the Department of War (DoW)? The DoW is scaling AI and modernizing its capabilities to get advanced technology into the hands of warfighters — and AWS is at the center of that effort. As a Program Integration Manager on the AWS Defense Program Management Office, you will be the connective tissue of a multi-billion dollar cloud computing contract, serving as the primary integration point between engineering, cybersecurity, vendor management, contract operations, and government stakeholders. You will drive program reviews, manage vendor and third-party marketplace governance, and maintain the security and compliance posture of deliverables. Your work directly impacts how DoW customers receive, adopt, and operate AWS cloud services. This is also a role where you will sharpen your program management skills on a large, complex program where taking initiative and excelling in ambiguity are rewarded. This position requires that the candidate selected be a US Citizen and obtain and maintain an active TS/SCI security clearance."
We need to keep that.
Key job responsibilities bullet list:
- Serve as the primary integration point between engineering, cybersecurity, and the program management office — lead cross-functional syncs and technical exchange meetings, track action items to closure, and provide program context and escalation support to senior leadership.
- Manage stakeholder relationships across internal teams and serve as the primary customer-facing integration lead, triaging government requests, supporting contract modifications, and coordinating deliverables with government agencies.
- Own the end-to-end vendor onboarding lifecycle — addendum negotiations, compliance verification, and approvals — and maintain the third-party product catalog for listing accuracy and vendor readiness.
- Own program security deliverables and vulnerability notifications; track cloud authorizations, accessibility compliance, and contract-driven security documentation in coordination with security, legal, and government reviewers.
- Develop and maintain program schedules and agile tracking boards, identify and mitigate risks, produce monthly and quarterly business reviews and executive briefing materials, and maintain program dashboards for vendor and customer visibility.
A day in the life paragraph: we can incorporate into responsibilities or about the role. Let's maybe add a paragraph under About the role after description: "A day in the life: ..." but we need to keep as prose.
About The Team paragraph:
"Our team sits at the intersection of Department of War mission needs and AWS cloud technology, managing a multi-billion dollar cloud computing contract that directly supports DoW operations. As the DoW accelerates its modernization and AI adoption, our work is more critical than ever. We partner closely with engineering, cybersecurity, legal, and government counterparts to deliver compliant, reliable cloud services at scale. We operate in a collaborative environment where clear communication and disciplined execution matter. If you are excited about contributing to a program with real national impact alongside inclusive, motivated teammates, we would love to hear from you."
Basic Qualifications list (each line starts with bullet? Actually they are sentences separated by spaces). Let's list:
- 5+ years of in program management, workforce strategy development, or metrics-driven decision making experience
- Experience managing programs across cross functional teams, building processes and coordinating release schedules
- 5+ years of developing, negotiating and executing business agreements experience
- 5+ years of professional or military experience
- Experience leading complex, multi-year initiatives that may be cross-functional and/or span business and technology
- Experience developing strategies that influence leadership decisions at the organizational level
- Experience presenting to both technical and non-technical executive audiences
- Bachelor's degree
Preferred Qualifications:
- Master's degree in business, data science, public administration, finance, engineering, human resources, or related field, or PMP certificate
- Experience interpreting data and making business recommendations
- Experience identifying, negotiating, and executing complex legal agreements
- Experience interpreting data and making business recommendations across leadership and cross-functional teams (duplicate line? appears twice)
- 8+ years of experience working in DoD, Intelligence Community, or defense industry programs
Note there is duplicate line "Experience interpreting data and making business recommendations". We should keep only one instance? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines are considered duplicated lines; we should remove duplicated lines. So we need to deduplicate.
Also there is line "Experience interpreting data and making business recommendations across leadership and cross-functional teams". That's slightly different; keep both? The first is generic, second adds "across leadership and cross-functional teams". They are not identical; keep both.
Now Benefits: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation but could be benefits. We'll include sign-on payments and RSUs under Benefits or Pay? Usually sign-on and RSUs are part of compensation. But we have Pay section for base salary range. We can include sign-on payments and RSUs under Benefits as they are part of total compensation. Or we could include them under Pay. The instruction: include Pay section only if posting actually states them. It states base salary range. It also mentions sign-on payments and RSUs. Could be part of Pay. But we can put them under Benefits as they are benefits. However typical classification: sign-on bonus and RSUs are part of compensation. Since we have Pay section for base salary, we could add note about sign-on payments and RSUs there. But we must not invent. We can include them in Pay section as additional compensation details. Let's decide: Pay section includes base salary range and mention of sign-on payments and RSUs.
Benefits section includes health insurance etc, 401(k) matching, paid time off, parental leave.
Schedule: not present, omit.
Now we need to output HTML fragment with
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, accommodation, etc. Must preserve all substantive info.
We need to parse the posting.
Key parts:
- Description paragraph: "Do you want to help deliver cloud technology to the Department of War (DoW)? ..." This is about the role. Could be "About the role" section.
- Key job responsibilities: list of responsibilities bullet points.
- A day in the life: narrative description; could be part of responsibilities or separate? Could be "Responsibilities" maybe includes both. But we have a separate "A day in the life" which is more narrative; could be placed under "About the role" or separate "Day in the Life". However headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create custom headings like "A day in the life". So we need to fit content into allowed headings. Probably put narrative under "About the role" or "Responsibilities". Since "A day in the life" describes typical activities, could be part of Responsibilities.
- About The Team: could be "About the role" or maybe "About the team" not allowed; could go under "About the role".
- Basic Qualifications: that's Requirements/Qualifications. We have both Requirements and Qualifications headings allowed. We need to decide what to put where. Usually "Requirements" for basic qualifications, "Preferred Qualifications" for preferred. So we can put Basic Qualifications under "Requirements" (or "Qualifications") and Preferred Qualifications under "Qualifications". But we have both headings; we need to avoid duplication. Could put Basic Qualifications under "Requirements" and Preferred Qualifications under "Qualifications". Or vice versa. Let's decide: Requirements = basic qualifications; Qualifications = preferred qualifications.
- Skills: not explicitly listed; we could infer from responsibilities but better not to create unless explicit. The posting does not have a separate Skills section. So we should not create Skills section.
- Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave." Also mentions sign-on payments and RSUs. That's benefits. So we can include Benefits section.
- Pay: The posting includes base salary range: "USA, VA, Arlington - 147,900.00 - 200,100.00 USD annually". Also mentions sign-on payments and RSUs. So we can include Pay section.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines.
We need to preserve all substantive information. Let's extract.
Description paragraph:
"Do you want to help deliver cloud technology to the Department of War (DoW)? The DoW is scaling AI and modernizing its capabilities to get advanced technology into the hands of warfighters — and AWS is at the center of that effort. As a Program Integration Manager on the AWS Defense Program Management Office, you will be the connective tissue of a multi-billion dollar cloud computing contract, serving as the primary integration point between engineering, cybersecurity, vendor management, contract operations, and government stakeholders. You will drive program reviews, manage vendor and third-party marketplace governance, and maintain the security and compliance posture of deliverables. Your work directly impacts how DoW customers receive, adopt, and operate AWS cloud services. This is also a role where you will sharpen your program management skills on a large, complex program where taking initiative and excelling in ambiguity are rewarded. This position requires that the candidate selected be a US Citizen and obtain and maintain an active TS/SCI security clearance."
We need to keep that.
Key job responsibilities bullet list:
- Serve as the primary integration point between engineering, cybersecurity, and the program management office — lead cross-functional syncs and technical exchange meetings, track action items to closure, and provide program context and escalation support to senior leadership.
- Manage stakeholder relationships across internal teams and serve as the primary customer-facing integration lead, triaging government requests, supporting contract modifications, and coordinating deliverables with government agencies.
- Own the end-to-end vendor onboarding lifecycle — addendum negotiations, compliance verification, and approvals — and maintain the third-party product catalog for listing accuracy and vendor readiness.
- Own program security deliverables and vulnerability notifications; track cloud authorizations, accessibility compliance, and contract-driven security documentation in coordination with security, legal, and government reviewers.
- Develop and maintain program schedules and agile tracking boards, identify and mitigate risks, produce monthly and quarterly business reviews and executive briefing materials, and maintain program dashboards for vendor and customer visibility.
A day in the life paragraph: we can incorporate into responsibilities or about the role. Let's maybe add a paragraph under About the role after description: "A day in the life: ..." but we need to keep as prose.
About The Team paragraph:
"Our team sits at the intersection of Department of War mission needs and AWS cloud technology, managing a multi-billion dollar cloud computing contract that directly supports DoW operations. As the DoW accelerates its modernization and AI adoption, our work is more critical than ever. We partner closely with engineering, cybersecurity, legal, and government counterparts to deliver compliant, reliable cloud services at scale. We operate in a collaborative environment where clear communication and disciplined execution matter. If you are excited about contributing to a program with real national impact alongside inclusive, motivated teammates, we would love to hear from you."
Basic Qualifications list (each line starts with bullet? Actually they are sentences separated by spaces). Let's list:
- 5+ years of in program management, workforce strategy development, or metrics-driven decision making experience
- Experience managing programs across cross functional teams, building processes and coordinating release schedules
- 5+ years of developing, negotiating and executing business agreements experience
- 5+ years of professional or military experience
- Experience leading complex, multi-year initiatives that may be cross-functional and/or span business and technology
- Experience developing strategies that influence leadership decisions at the organizational level
- Experience presenting to both technical and non-technical executive audiences
- Bachelor's degree
Preferred Qualifications:
- Master's degree in business, data science, public administration, finance, engineering, human resources, or related field, or PMP certificate
- Experience interpreting data and making business recommendations
- Experience identifying, negotiating, and executing complex legal agreements
- Experience interpreting data and making business recommendations across leadership and cross-functional teams (duplicate line? appears twice)
- 8+ years of experience working in DoD, Intelligence Community, or defense industry programs
Note there is duplicate line "Experience interpreting data and making business recommendations". We should keep only one instance? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines are considered duplicated lines; we should remove duplicated lines. So we need to deduplicate.
Also there is line "Experience interpreting data and making business recommendations across leadership and cross-functional teams". That's slightly different; keep both? The first is generic, second adds "across leadership and cross-functional teams". They are not identical; keep both.
Now Benefits: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation but could be benefits. We'll include sign-on payments and RSUs under Benefits or Pay? Usually sign-on and RSUs are part of compensation. But we have Pay section for base salary range. We can include sign-on payments and RSUs under Benefits as they are part of total compensation. Or we could include them under Pay. The instruction: include Pay section only if posting actually states them. It states base salary range. It also mentions sign-on payments and RSUs. Could be part of Pay. But we can put them under Benefits as they are benefits. However typical classification: sign-on bonus and RSUs are part of compensation. Since we have Pay section for base salary, we could add note about sign-on payments and RSUs there. But we must not invent. We can include them in Pay section as additional compensation details. Let's decide: Pay section includes base salary range and mention of sign-on payments and RSUs.
Benefits section includes health insurance etc, 401(k) matching, paid time off, parental leave.
Schedule: not present, omit.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include any extra text outside HTML.
Structure:
About the role
... description paragraph ...
A day in the life ...
About The Team ...
But we have multiple paragraphs; we could combine into one with line breaks? Better separate
for each distinct block.
Then
Responsibilities
- ... each responsibility ...
Then Requirements
- ... basic qualifications ...
Then Qualifications
- ... preferred qualifications ...
Then Benefits
- ... benefits ...
Then Pay
... base salary range and sign-on payments/RSUs ...
We must ensure no empty sections.
Check for any duplicated content: we removed duplicate line.
Now let's craft the text.
About the role paragraph: combine the initial description (first paragraph). We'll keep as is.
A day in the life paragraph: copy the paragraph exactly.
About The Team paragraph: copy.
Now Responsibilities: list each bullet as given.
Check each bullet for any extra punctuation.
Bullet 1: "Serve as the primary integration point between engineering, cybersecurity, and the program management office — lead cross-functional syncs and technical exchange meetings, track action items to closure, and provide program context and escalation support to senior leadership."
Bullet 2: "Manage stakeholder relationships across internal teams and serve as the primary customer-facing integration lead, triaging government requests, supporting contract modifications, and coordinating deliverables with government agencies."
Bullet 3: "Own the end-to-end vendor onboarding lifecycle — addendum negotiations, compliance verification, and approvals — and maintain the third-party product catalog for listing accuracy and vendor readiness."
Bullet 4: "Own program security deliverables and vulnerability notifications; track cloud authorizations, accessibility compliance, and contract-driven security documentation in coordination with security, legal, and government reviewers."
Bullet 5: "Develop and maintain program schedules and agile tracking boards, identify and mitigate risks, produce monthly and quarterly business reviews and executive briefing materials, and maintain program dashboards for vendor and customer visibility."
Now Requirements (basic qualifications):
List each:
- "5+ years of in program management, workforce strategy development, or metrics-driven decision making experience"
- "Experience managing programs across cross functional teams, building processes and coordinating release schedules"
- "5+ years of developing, negotiating and executing business agreements experience"
- "5+ years of professional or military experience"
- "Experience leading complex, multi-year initiatives that may be cross-functional and/or span business and technology"
- "Experience developing strategies that influence leadership decisions at the organizational level"
- "Experience presenting to both technical and non-technical executive audiences"
- "Bachelor's degree"
Check grammar: first bullet says "5+ years of in program management..." maybe a typo but we keep as is.
Now Qualifications (preferred):
List each,
- for lists,
for prose. We must not include any extra text outside HTML. Structure:
About the role
... description paragraph ...
A day in the life ...
About The Team ...
But we have multiple paragraphs; we could combine into onewith line breaks? Better separate
for each distinct block. Then
Responsibilities
- ... each responsibility ...
Requirements
- ... basic qualifications ...
Qualifications
- ... preferred qualifications ...
Benefits
- ... benefits ...
Pay
... base salary range and sign-on payments/RSUs ...
We must ensure no empty sections. Check for any duplicated content: we removed duplicate line. Now let's craft the text. About the role paragraph: combine the initial description (first paragraph). We'll keep as is. A day in the life paragraph: copy the paragraph exactly. About The Team paragraph: copy. Now Responsibilities: list each bullet as given. Check each bullet for any extra punctuation. Bullet 1: "Serve as the primary integration point between engineering, cybersecurity, and the program management office — lead cross-functional syncs and technical exchange meetings, track action items to closure, and provide program context and escalation support to senior leadership." Bullet 2: "Manage stakeholder relationships across internal teams and serve as the primary customer-facing integration lead, triaging government requests, supporting contract modifications, and coordinating deliverables with government agencies." Bullet 3: "Own the end-to-end vendor onboarding lifecycle — addendum negotiations, compliance verification, and approvals — and maintain the third-party product catalog for listing accuracy and vendor readiness." Bullet 4: "Own program security deliverables and vulnerability notifications; track cloud authorizations, accessibility compliance, and contract-driven security documentation in coordination with security, legal, and government reviewers." Bullet 5: "Develop and maintain program schedules and agile tracking boards, identify and mitigate risks, produce monthly and quarterly business reviews and executive briefing materials, and maintain program dashboards for vendor and customer visibility." Now Requirements (basic qualifications): List each: - "5+ years of in program management, workforce strategy development, or metrics-driven decision making experience" - "Experience managing programs across cross functional teams, building processes and coordinating release schedules" - "5+ years of developing, negotiating and executing business agreements experience" - "5+ years of professional or military experience" - "Experience leading complex, multi-year initiatives that may be cross-functional and/or span business and technology" - "Experience developing strategies that influence leadership decisions at the organizational level" - "Experience presenting to both technical and non-technical executive audiences" - "Bachelor's degree" Check grammar: first bullet says "5+ years of in program management..." maybe a typo but we keep as is. Now Qualifications (preferred): List each,