Security Engineer, AWS Proactive Security
About the role
...
Responsibilities
- ... ...
Requirements
maybe for Basic Qualifications? Or Requirements vs Qualifications: Usually Requirements = basic qualifications, Qualifications = preferred. We'll follow.Requirements
- ... basic qualifications
Qualifications
- ... preferred qualifications
Skills
maybe combine scripting languages? Could be separate but we have skills in qualifications. Could create Skills section summarizing technical skills: scripting languages, web protocols, penetration testing, etc. But we already have them in Requirements/Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have both basic and preferred, so we can have Requirements and Qualifications sections. Skills: Could be derived from both but maybe we can omit if thin. However we have explicit skill mentions: scripting with Python, Perl, Bash or PowerShell; knowledge of system security vulnerabilities; experience with AWS services; coding/scripting in languages; using BurpSuite, Metasploit, IDA Pro. Could be a Skills section. But we already have them in Requirements/Qualifications. To avoid thin sections, maybe we omit Skills and put those details in Requirements/Qualifications. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's a list of possible headings, not mandatory to use all. So we can omit Skills if we think it's thin. But we have skill details; we could put them under Requirements and Qualifications. That's fine.
Benefits: we have description.
Pay: we have salary range and sign-on payments, RSUs.
Schedule: we have flexible work hours and arrangements from Work/Life Balance.
We must not include boilerplate like "Amazon is an equal opportunity employer..." etc.
We must not include duplicated lines.
We need to ensure we preserve all substantive info: includes the intro paragraph, responsibilities, day in the life (maybe part of About the role), About The Team subsections (maybe we can incorporate into About the role or maybe we can omit as it's more culture but still substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the About The Team content as well. Where to put? Could be part of About the role or maybe a separate section like "About the Team". But allowed headings list does not include About the Team. However we could incorporate that content into About the role section as additional paragraphs. That would preserve it.
Thus About the role will contain the initial description, plus the day in the life, plus About The Team subsections (Diverse Experiences, Why Amazon Security?, Inclusive Team Culture, Training & Career Growth, Work/Life Balance). We'll need to paraphrase? No, we must preserve all substantive information, not invent or summarize away detail. We can keep the original sentences; we can just include them as paragraphs.
We must not repeat headings like "A day in the life" as a heading; we can just include as paragraph.
We must not include duplicated lines: there is duplicate "A day in the life" heading; we will only include the content once.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove the EEO statement, accommodation link, etc.
We must not include Job ID.
Now craft HTML.
We'll need to escape any HTML special characters? The text includes punctuation but fine.
We'll produce:
About the role
Are you interested in security and supporting penetration testing at a global scale? Do you strive to achieve a deep understanding of systems and apply a hacker mindset to determine how they can be broken? As a pre-launch Security Engineer, you are part of a testing team that evaluates AWS services and features to help builders maintain a high security bar. When builders have implemented fixes to security issues, you review their proposed corrections to determine efficacy before final release. You work closely with testers to understand their approaches and methodologies so you can quickly reproduce them in a variety of customer environments. You recognize the value of automation and are comfortable with scripting languages to develop tools that improve the speed and quality of your team's verification work. Our team is responsible for the manual assessment of all products, services and software released by AWS. To accomplish this, we support and write a variety of automated tooling (e.g. fuzzers, scanners, analyzers, etc.) to verify security fixes related to penetration testing. We specialize in digging deep to find security issues that static analysis tools can’t, and write the tooling to help with these goals whenever possible. The AWS surface area is large and diverse, and we use results found in manual analysis to help improve our enterprise-wide automation to proactively spot and fix potential security issues to protect customers.
As a Security Engineer supporting verifications for pre-launch testing, you have the opportunity to review and dive deep into builder-proposed fixes. You'll access development environments for upcoming AWS services and features to dive deep into their code to learn how security issues were discovered and how the builders intend to address them. You perform static code analysis and dynamic reproduction of issues to make the final decision on whether the builder's proposed fix is sufficient to allow their code release.
Diverse Experiences: Amazon Security values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying.
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.
Inclusive Team Culture: In Amazon Security, it’s in our nature to learn and be curious. Ongoing DEI events and learning experiences inspire us to continue learning and to embrace our uniqueness. Addressing the toughest security challenges requires that we seek out and celebrate a diversity of ideas, perspectives, and voices.
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