Security Area Manager, Global Security Operations Center
Amazon · Goodyear, AZ · 3 wk ago
ManufacturingFull-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. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, accommodations, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Mission description: maybe part of About the role? The description begins: "Description The mission of Worldwide Operations Security (WWOS) is to support Amazon’s Worldwide Operations, as well as affiliate and retail businesses, by creating and maintaining a work environment that is both prepared and secure through global security centers of excellence staffed by subject matter experts in people and asset protection. We accomplish this by creating policy and implementation guidelines; training leadership and staff; using technology to eliminate subjectivity, complexity, and variation; identifying, preparing for, and mitigating risk; and auditing our practices to ensure compliance. The Security Area Manager is a leadership position overseeing 24/7 global operations at Amazon’s Global Security Operations Center (GSOC), supporting Amazon’s Worldwide Operations. The Security Area Manager is responsible for ensuring performance Service Level Agreements (SLAs) are met, customer responses are appropriate according to policies and procedures, and the continuous development and motivation of a high-performing team. The role manages incident response and crisis management with significant impact on life safety, operations, and brand reputation. The successful candidate must have a proven record of effective leadership capability and demonstrate above-average judgment while operating under pressure. They must possess the ability to operate autonomously, use discretion when dealing with sensitive and critical information, and apply sound business principles and data analysis to identify barriers and initiate actions to resolve."
That's about the role.
Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph.
Then "About The Team" paragraph.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then benefits and salary info: "Amazon is an equal opportunity employer..." (EEO) we need to remove. Then "If you have a disability..." remove. Then "If the country/region you’re applying in isn’t listed..." remove. Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location: "USA, AZ, Goodyear - 83,200.00 - 145,500.00 USD annually Company - Amazon.com Services LLC Job ID: A10554357"
We need to include Pay section if salary range is given. Yes we have salary range: 83,200 - 145,500 USD annually. So Pay section.
Benefits: we have description of benefits. So Benefits section.
Schedule: maybe mention shift work: "This leadership role requires the employee to work on a shift, including nights and weekends, based on the needs of the GSOC." So we have schedule info.
Skills: maybe not explicit separate list; but we could combine qualifications and skills? The instruction: Use headings for sections like Skills if there is content. We have qualifications (basic and preferred). Could treat them as Requirements and Qualifications? The headings list includes Requirements, Qualifications, Skills. We need to decide what to put where. Usually Requirements = basic qualifications, Qualifications = preferred qualifications, Skills maybe from responsibilities? But we can also put skills under Qualifications. However we must not create empty sections. We need to include sections only if there is real specific content.
We have basic qualifications: Bachelor's degree or equivalent, 5+ years work in relevant industries such as law, customer service, investigations, risk, compliance or project management experience, 5+ years of customer service experience, Experience with all Microsoft Office applications.
Preferred qualifications: 3+ years of high-volume, high-intensity environment such as a security operations center, event security, call center, or crisis management/emergency response center experience, Experience with process improvements (Lean Six Sigma and/or Kaizen), Experience working cross-functionally across several teams both technical and non-technical, Experience in workplace violence, emergency response, crisis management, and business continuity practices, Experience using data and metrics to back up assumptions, evaluate outcomes, and make data-driven decisions.
We could map Basic Qualifications to "Requirements" heading, Preferred Qualifications to "Qualifications" heading. Skills maybe not needed; we could omit Skills section if no explicit skills list. But we could extract skills from responsibilities: leadership, discretion, business principles, data analysis, incident management, process improvement, mentoring, etc. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings list includes both; we could still include both if they have content. That's fine.
We also need About the role section (maybe from mission description). Responsibilities section (from Key job responsibilities and A day in the life). About The Team could be part of About the role or separate? Could be its own section maybe "About the Team". But headings list does not include About the Team; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fold About The Team content into About the role or Responsibilities? Probably About the role includes mission and team description. We'll incorporate About The Team into About the role.
We must not repeat job title as heading. So we will not have a heading for Security Area Manager.
We need to output only HTML fragment, no or . Use
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. Must not include Job ID etc. Remove boilerplate like EEO, accommodations, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Mission description: maybe part of About the role? The description begins: "Description The mission of Worldwide Operations Security (WWOS) is to support Amazon’s Worldwide Operations, as well as affiliate and retail businesses, by creating and maintaining a work environment that is both prepared and secure through global security centers of excellence staffed by subject matter experts in people and asset protection. We accomplish this by creating policy and implementation guidelines; training leadership and staff; using technology to eliminate subjectivity, complexity, and variation; identifying, preparing for, and mitigating risk; and auditing our practices to ensure compliance. The Security Area Manager is a leadership position overseeing 24/7 global operations at Amazon’s Global Security Operations Center (GSOC), supporting Amazon’s Worldwide Operations. The Security Area Manager is responsible for ensuring performance Service Level Agreements (SLAs) are met, customer responses are appropriate according to policies and procedures, and the continuous development and motivation of a high-performing team. The role manages incident response and crisis management with significant impact on life safety, operations, and brand reputation. The successful candidate must have a proven record of effective leadership capability and demonstrate above-average judgment while operating under pressure. They must possess the ability to operate autonomously, use discretion when dealing with sensitive and critical information, and apply sound business principles and data analysis to identify barriers and initiate actions to resolve."
That's about the role.
Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph.
Then "About The Team" paragraph.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then benefits and salary info: "Amazon is an equal opportunity employer..." (EEO) we need to remove. Then "If you have a disability..." remove. Then "If the country/region you’re applying in isn’t listed..." remove. Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location: "USA, AZ, Goodyear - 83,200.00 - 145,500.00 USD annually Company - Amazon.com Services LLC Job ID: A10554357"
We need to include Pay section if salary range is given. Yes we have salary range: 83,200 - 145,500 USD annually. So Pay section.
Benefits: we have description of benefits. So Benefits section.
Schedule: maybe mention shift work: "This leadership role requires the employee to work on a shift, including nights and weekends, based on the needs of the GSOC." So we have schedule info.
Skills: maybe not explicit separate list; but we could combine qualifications and skills? The instruction: Use headings for sections like Skills if there is content. We have qualifications (basic and preferred). Could treat them as Requirements and Qualifications? The headings list includes Requirements, Qualifications, Skills. We need to decide what to put where. Usually Requirements = basic qualifications, Qualifications = preferred qualifications, Skills maybe from responsibilities? But we can also put skills under Qualifications. However we must not create empty sections. We need to include sections only if there is real specific content.
We have basic qualifications: Bachelor's degree or equivalent, 5+ years work in relevant industries such as law, customer service, investigations, risk, compliance or project management experience, 5+ years of customer service experience, Experience with all Microsoft Office applications.
Preferred qualifications: 3+ years of high-volume, high-intensity environment such as a security operations center, event security, call center, or crisis management/emergency response center experience, Experience with process improvements (Lean Six Sigma and/or Kaizen), Experience working cross-functionally across several teams both technical and non-technical, Experience in workplace violence, emergency response, crisis management, and business continuity practices, Experience using data and metrics to back up assumptions, evaluate outcomes, and make data-driven decisions.
We could map Basic Qualifications to "Requirements" heading, Preferred Qualifications to "Qualifications" heading. Skills maybe not needed; we could omit Skills section if no explicit skills list. But we could extract skills from responsibilities: leadership, discretion, business principles, data analysis, incident management, process improvement, mentoring, etc. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings list includes both; we could still include both if they have content. That's fine.
We also need About the role section (maybe from mission description). Responsibilities section (from Key job responsibilities and A day in the life). About The Team could be part of About the role or separate? Could be its own section maybe "About the Team". But headings list does not include About the Team; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fold About The Team content into About the role or Responsibilities? Probably About the role includes mission and team description. We'll incorporate About The Team into About the role.
We must not repeat job title as heading. So we will not have a heading for Security Area Manager.
We need to output only HTML fragment, no or . Use for section headings. Use - for lists. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the description, but we can format them.
We must remove boilerplate: EEO, accommodations, recruiting partner note, etc. Also remove "Learn more about our benefits at https://..." maybe we can keep the benefits description but drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is maybe considered navigation? It's a link to learn more; could be considered application instruction? It's not exactly application instruction but it's a link. Safer to remove the link line, but keep the benefits description. The sentence: "Learn more about our benefits at https://amazon.jobs/en/benefits." That's likely considered navigation/link; we should remove it. Keep the preceding benefits description.
Also remove "Company - Amazon.com Services LLC" maybe considered metadata; we can drop it. Keep location and salary.
We need to include location? Not in headings; maybe we can include location in a short
under About the role or maybe under Pay? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location is minor metadata; we can fold into a short
maybe under About the role or at end. We'll include a
with location: "Location: Goodyear, AZ, USA". Or we can incorporate into Pay section? Probably better to have a short
after Pay? But we need to decide.
We also need to include the salary range in Pay section.
Now let's draft sections:
About the role
... mission description ...
... About The Team content ...
But we need to avoid duplication. Let's extract mission description paragraph: "The mission of Worldwide Operations Security (WWOS) is to support Amazon’s Worldwide Operations, as well as affiliate and retail businesses, by creating and maintaining a work environment that is both prepared and secure through global security centers of excellence staffed by subject matter experts in people and asset protection. We accomplish this by creating policy and implementation guidelines; training leadership and staff; using technology to eliminate subjectivity, complexity, and variation; identifying, preparing for, and mitigating risk; and auditing our practices to ensure compliance."
Then: "The Security Area Manager is a leadership position overseeing 24/7 global operations at Amazon’s Global Security Operations Center (GSOC), supporting Amazon’s Worldwide Operations. The Security Area Manager is responsible for ensuring performance Service Level Agreements (SLAs) are met, customer responses are appropriate according to policies and procedures, and the continuous development and motivation of a high-performing team. The role manages incident response and crisis management with significant impact on life safety, operations, and brand reputation. The successful candidate must have a proven record of effective leadership capability and demonstrate above-average judgment while operating under pressure. They must possess the ability to operate autonomously, use discretion when dealing with sensitive and critical information, and apply sound business principles and data analysis to identify barriers and initiate actions to resolve."
Then About The Team: "The Global Security Operations Center (GSOC) supports the WWOS mission by providing 24/7/365 services to Amazon's Worldwide Operations. The GSOC provides support and timely notification to global partners regarding critical incidents that have impacted, or have the potential to impact, Life-Safety, Operations, and/or the Amazon Brand. We are Amazon's central location for critical incident management supporting worldwide operations, as well as affiliate and retail businesses. The GSOC operates across multiple global sites with coverage in 14+ languages, managing a team of Security Operations Managers, Security Area Managers, and Crisis Specialists. We are looking for an agile, adaptive, and detail-oriented leader to oversee a diverse, multi-disciplined team."
We can combine these into About the role.
Now Responsibilities: from "Key job responsibilities" bullet list and "A day in the life" paragraph.
Key job responsibilities bullet list:
- Lead and maintain command authority over assigned shift personnel, ensuring uninterrupted 24/7 operational readiness.
- Maintain situational awareness of global events affecting Amazon’s associates, assets, operations, and reputation.
- Demonstrate mastery of GSOC Policies, Standards, Procedures, and Guides; execute established compliance processes in alignment with WWOS requirements.
- Oversee incident lifecycles (Assess/Triage, Notify/Activate, Manage/Respond), ensuring adherence to standardized procedures, proper documentation within technology platforms, and timely incident closure.
- Serve as the Incident Owner (IO) during critical events; conduct Incident Triage Calls, develop Incident Mitigation Plans, make escalation decisions, and direct stakeholder communication.
- Manage process controls to ensure compliance across the assigned shift; identify, assess, and mitigate risks to the operation that are above tolerance levels.
- Lead, develop, and motivate a team of GSOC Specialists to achieve service level agreements (SLAs) and key performance indicators (KPIs).
- Manage, mentor, and coach direct reports; foster individual and team development through performance goals, continuous improvement, and wellness initiatives.
- Optimize cross-team processes to improve team efficacy and delivery; drive process improvements that enhance operational readiness and crisis response capabilities.
A day in the life paragraph: "A Security Area Manager is responsible for developing and motivating a high-performing team of GSOC Specialists. Daily, a SAM operates autonomously, using discretion when dealing with sensitive and critical information, and applying sound business principles to identify barriers and initiate actions to resolve. The SAM leads people during shift operations, triages incoming security alerts and emergency notifications, coordinates crisis response across internal and external stakeholders, and ensures all incidents are documented and tracked through resolution using established protocols and the Event Management Tool (EMT). This leadership role requires the employee to work on a shift, including nights and weekends, based on the needs of the GSOC."
We can incorporate the shift work note
- for lists. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the description, but we can format them. We must remove boilerplate: EEO, accommodations, recruiting partner note, etc. Also remove "Learn more about our benefits at https://..." maybe we can keep the benefits description but drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is maybe considered navigation? It's a link to learn more; could be considered application instruction? It's not exactly application instruction but it's a link. Safer to remove the link line, but keep the benefits description. The sentence: "Learn more about our benefits at https://amazon.jobs/en/benefits." That's likely considered navigation/link; we should remove it. Keep the preceding benefits description. Also remove "Company - Amazon.com Services LLC" maybe considered metadata; we can drop it. Keep location and salary. We need to include location? Not in headings; maybe we can include location in a short
under About the role or maybe under Pay? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location is minor metadata; we can fold into a short
maybe under About the role or at end. We'll include a
with location: "Location: Goodyear, AZ, USA". Or we can incorporate into Pay section? Probably better to have a short
after Pay? But we need to decide. We also need to include the salary range in Pay section. Now let's draft sections:
About the role
... mission description ...
... About The Team content ...
But we need to avoid duplication. Let's extract mission description paragraph: "The mission of Worldwide Operations Security (WWOS) is to support Amazon’s Worldwide Operations, as well as affiliate and retail businesses, by creating and maintaining a work environment that is both prepared and secure through global security centers of excellence staffed by subject matter experts in people and asset protection. We accomplish this by creating policy and implementation guidelines; training leadership and staff; using technology to eliminate subjectivity, complexity, and variation; identifying, preparing for, and mitigating risk; and auditing our practices to ensure compliance." Then: "The Security Area Manager is a leadership position overseeing 24/7 global operations at Amazon’s Global Security Operations Center (GSOC), supporting Amazon’s Worldwide Operations. The Security Area Manager is responsible for ensuring performance Service Level Agreements (SLAs) are met, customer responses are appropriate according to policies and procedures, and the continuous development and motivation of a high-performing team. The role manages incident response and crisis management with significant impact on life safety, operations, and brand reputation. The successful candidate must have a proven record of effective leadership capability and demonstrate above-average judgment while operating under pressure. They must possess the ability to operate autonomously, use discretion when dealing with sensitive and critical information, and apply sound business principles and data analysis to identify barriers and initiate actions to resolve." Then About The Team: "The Global Security Operations Center (GSOC) supports the WWOS mission by providing 24/7/365 services to Amazon's Worldwide Operations. The GSOC provides support and timely notification to global partners regarding critical incidents that have impacted, or have the potential to impact, Life-Safety, Operations, and/or the Amazon Brand. We are Amazon's central location for critical incident management supporting worldwide operations, as well as affiliate and retail businesses. The GSOC operates across multiple global sites with coverage in 14+ languages, managing a team of Security Operations Managers, Security Area Managers, and Crisis Specialists. We are looking for an agile, adaptive, and detail-oriented leader to oversee a diverse, multi-disciplined team." We can combine these into About the role. Now Responsibilities: from "Key job responsibilities" bullet list and "A day in the life" paragraph. Key job responsibilities bullet list: - Lead and maintain command authority over assigned shift personnel, ensuring uninterrupted 24/7 operational readiness. - Maintain situational awareness of global events affecting Amazon’s associates, assets, operations, and reputation. - Demonstrate mastery of GSOC Policies, Standards, Procedures, and Guides; execute established compliance processes in alignment with WWOS requirements. - Oversee incident lifecycles (Assess/Triage, Notify/Activate, Manage/Respond), ensuring adherence to standardized procedures, proper documentation within technology platforms, and timely incident closure. - Serve as the Incident Owner (IO) during critical events; conduct Incident Triage Calls, develop Incident Mitigation Plans, make escalation decisions, and direct stakeholder communication. - Manage process controls to ensure compliance across the assigned shift; identify, assess, and mitigate risks to the operation that are above tolerance levels. - Lead, develop, and motivate a team of GSOC Specialists to achieve service level agreements (SLAs) and key performance indicators (KPIs). - Manage, mentor, and coach direct reports; foster individual and team development through performance goals, continuous improvement, and wellness initiatives. - Optimize cross-team processes to improve team efficacy and delivery; drive process improvements that enhance operational readiness and crisis response capabilities. A day in the life paragraph: "A Security Area Manager is responsible for developing and motivating a high-performing team of GSOC Specialists. Daily, a SAM operates autonomously, using discretion when dealing with sensitive and critical information, and applying sound business principles to identify barriers and initiate actions to resolve. The SAM leads people during shift operations, triages incoming security alerts and emergency notifications, coordinates crisis response across internal and external stakeholders, and ensures all incidents are documented and tracked through resolution using established protocols and the Event Management Tool (EMT). This leadership role requires the employee to work on a shift, including nights and weekends, based on the needs of the GSOC." We can incorporate the shift work note