Jobs · Quality Assurance · California

Security Engineer, Leo Security

Amazon · San Francisco, CA · 1 mo ago
Quality AssuranceFull-time
We need to output HTML fragment with sections: Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Description: Amazon Leo initiative, security team. We can treat as "About the role" maybe. - Export Control Requirement: US citizen or national. - Key job responsibilities: bullet list. - A day in the life: includes Role description, etc. - About The Team: includes Why Amazon Security? Training & Career Growth. - Basic Qualifications: list. - Preferred Qualifications: list. - Benefits: mention comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs. - Pay: base salary range listed: USA, CA, San Francisco - $166,600.00 - $212,800.00 USD annually. - Schedule: not mentioned. - Job ID etc to be omitted. We need to preserve all substantive info, not invent. We need to avoid boilerplate: EEO, equal opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal. We need to output only HTML fragment. We need to decide sections. Potential sections: - About the role (description of role, mission, export control requirement maybe). Could include description paragraph. - Responsibilities (key job responsibilities list). - Qualifications (maybe combine Basic and Preferred? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use headings for those specific labels if content exists. We have Basic Qualifications and Preferred Qualifications. Could map Basic Qualifications to "Requirements" and Preferred Qualifications to "Qualifications" or "Skills". However we need to follow instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include based on content. We have content for: - About the role: description paragraph (Amazon Leo initiative, security team purpose, export control requirement). Also maybe "A day in the life" could be part of About the role. - Responsibilities: key job responsibilities list. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe not separate; we could omit if no specific skills list beyond qualifications. - Benefits: benefits description. - Pay: salary range. - Schedule: none -> omit. We must not create sections with filler like "not specified". So omit Schedule. We need to preserve all substantive info: include export control requirement, responsibilities list, day in the life description, about the team, training & career growth, basic qualifications, preferred qualifications, benefits, pay. We need to avoid repeating job title as heading (not needed). Do not include Job ID. We need to output only HTML fragment. Let's craft. Structure:

About the role

Amazon Leo is an initiative to launch a constellation of Low Earth Orbit satellites that will provide low-latency, high-speed broadband network connectivity to unserved and underserved communities around the world. We are a specialized security team that sits inside a global satellite communications business. Our job is to make sure security lessons become permanent: when a security event happens, we find the root cause, close the immediate gap, and build the mechanism that keeps it closed. We watch across the whole environment, spot the trends others are too busy to chase, and turn them into initiatives that measurably reduce risk. We work shoulder to shoulder with the builder teams designing, launching, and operating the product, and we partner closely with incident response, detection, and enterprise security functions. Over the coming years our focus is shifting further upstream: getting ahead of incidents through proactive posture improvement, hunting for gaps before they are exploited, and investing in automation so security scales with the business rather than against it. If you want your work to protect customers of a system being built at a scale few companies attempt, you will find that purpose here.

Export Control Requirement: Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national.

Maybe also include "A day in the life" paragraph inside About the role? Could add another

describing role. We have "A day in the life Role In this highly dynamic role, you will decide where your time investments deliver the most security value, balancing proactive posture-improvement work against reactive support when security events arise. Teams across the business will reach out for guidance on a wide variety of security problems, and you can anticipate questions like: ..." plus rest. We could incorporate that as part of About the role. Let's add a paragraph after export control. Now Responsibilities:

Responsibilities

  • Analyze the security events observed across Amazon Leo, separating each one into the immediate fixes it demands and the longer-term, systemic trends it reveals across the organization.
  • Prioritize this work by the severity and business impact of the threat to Leo, concentrating your effort on the most serious security issues and making sound risk-based trade-offs to deliver against them on time.
  • Drive immediate fixes to closure by identifying the right team or individual to own each task, and by creating the mechanisms needed to ensure security outcomes are prioritized and tracked to completion across teams with competing priorities.
  • Lead time-boxed Find and Fix missions to investigate and clarify emerging security trends, turning early and ambiguous signals into a validated understanding of the underlying problem.
  • Own security initiatives end-to-end that resolve the root cause of systemic trends, favoring centralized, secure-by-default controls that measurably and durably reduce risk across the organization.
Now Requirements (Basic Qualifications):

Requirements

  • Bachelor's degree in a STEM field (Science, Technology, Engineering, Mathematics), or 4+ years of IT Security experience
  • 1+ years of cloud based solution (AWS or equivalent), system, network and operating system experience
  • Experience driving security programs across large diverse organizations
  • 3+ years of any combination of the following: application security frameworks, identity and access controls, incident response, mobile security, cloud computing and security, AI security, threat intelligence, and penetration testing experience
  • 1+ years experience using AI to automate security
Now Qualifications (Preferred Qualifications):

Qualifications

  • Experience working in identifying security issues and risks, and developing mitigation plans
  • Experience in threat hunting, detection engineering, or product/application security, including moving from a security hypothesis to a validated detection, control, or remediation within a time-boxed engagement
  • Experience owning security remediation initiatives end-to-end, including scoping the problem, driving cross-team execution without direct authority, and measuring the resulting outcome
Now Benefits:

Benefits

  • 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
  • Parental leave
  • Sign-on payments and restricted stock units (RSUs)
Now Pay:

Pay

Base salary range: $166,600.00 - $212,800.00 USD annually (USA, CA, San Francisco)

We should not include Schedule. Check for any duplicated content: we included export control requirement, about the role, day in the life not explicitly but we could add a paragraph about day in the life. Let's incorporate that. Add a paragraph after export control: "A day in the life: In this highly dynamic role, you will decide where your time investments deliver the most security value, balancing proactive posture-improvement work against reactive support when security events arise. Teams across the business will reach out for guidance on a wide variety of security problems, and you can anticipate questions like: 'What's the right way to handle authentication tokens in service-to-service communications?' 'We're planning a confidential new product launch and need to define its security requirements.' 'We just had a security event and need to run a root cause analysis to identify and correct what produced it.' When you're not responding to builder teams, you will evaluate overall security posture across the organization to surface architectural defects, hunt for gaps before they become incidents, and propose new security initiatives that correct systemic problems. Through this blend of consultation, investigation, and long-term mechanism building, you will help maintain a high bar for customer security." We also have About The Team section: Why Amazon Security? Training & Career Growth. Could we include that as part of About the role? Might be better to add another section "About the team". But we only have predefined headings list; we could add "About the team" but not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add extra headings like About the team. We can incorporate that content into About the role or maybe into Responsibilities? Probably About the role is appropriate to include team description. Thus we can add a paragraph about Why Amazon Security? Training & Career Growth inside About the role. Let's craft About the role paragraph(s): First paragraph: description of Amazon Leo and team purpose. Second paragraph: Export Control Requirement. Third paragraph: A day in the life (as above). Fourth paragraph: About The Team: Why Amazon Security? Training & Career Growth. We need to preserve all substantive info: includes "Why Amazon Security? At Amazon, security is central to maintaining customer trust and delivering delightful customer experiences. Our organization is responsible for creating and maintaining a high bar for security across all of Amazon’s products and services. We offer talented security professionals the chance to accelerate their careers with opportunities to build experience in a wide variety of areas including cloud, devices, retail, entertainment, healthcare, operations, and physical stores. Training & Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, training, and other career-advancing resources here to help you develop into a better-rounded professional." We'll include that as a paragraph. Now ensure we didn't include any boilerplate like EEO, equal opportunity, Los Angeles County, San Francisco Fair Chance, disability accommodation, etc. Remove those. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (that's a link; maybe we can keep but it's not substantive? It's a reference; but it's not required. Might be considered boilerplate? It's a link to benefits; we already described benefits. Could keep but it's not necessary. Safer to omit. Also remove "USA, CA, San Francisco - 166,600.00 - 212,800.00 USD annually" we already have in Pay. Also remove "Company - Amazon.com Services LLC Job ID: A10552745". Remove. Now ensure we didn't miss any substantive info: The "Basic Qualifications" includes "This position requires U.S. citizenship in order to access AWS GovCloud". That's a note about citizenship. We already have export control requirement; but this is additional nuance: requires US citizenship to

Similar jobs