Senior Software Development Engineer, AWS Compliance & Security Assurance
About the role
withcontaining that paragraph. - Then "Key job responsibilities As an AWS Senior SDE, you’ll design and build services and applications with a team of engineers. To succeed in this role, you believe in high standards for code quality, code reviews, testing, and operational excellence. You support your peers to deliver results in a space that operates much like a start-up, with the autonomy to build the right solution from Day One. You will collaborate with other engineers on technical direction and strategy with a career growth opportunity that AWS can offer." That's responsibilities. We'll put
Responsibilities
with- items? The paragraph contains multiple sentences; we could split into bullet points. But we need to preserve all substantive info; we can convert each sentence to a
- . Or we can keep as
. The rule: Use
- for any list of duties/requirements/benefits. This is duties; we can make list.
- Then "About The Team Diverse Experiences Amazon Security values diverse experiences...." This is about team; could be part of About the role or separate? There's no explicit heading for About the Team but we could treat as part of About the role or maybe a separate section like "About the Team". However allowed headings list does not include About the Team; only the given set. So we should incorporate that content into About the role or maybe Responsibilities? Probably About the role.
- Then sections: Why Amazon Security?, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. Those are benefits/culture. Could go under Benefits section? Benefits usually refers to compensation/benefits like health insurance etc. But we have a Benefits section later with actual benefits. The culture parts could be considered Benefits? The instruction: include a section ONLY when posting has real, specific content for it. We have Benefits section later with health insurance etc. So we should put those culture parts maybe under Benefits? But they are not typical benefits like health insurance; they are more about culture. Could we create a Benefits section and include those bullet points? The rule: Benefits section only if posting actually states them. It does state benefits: health insurance etc. So we will have Benefits section with those specifics. The culture parts could be placed under About the role or maybe omitted? But we must preserve ALL substantive information; cannot drop. So we need to include them somewhere. Could create a section "Benefits" and include both culture and tangible benefits? Might be okay. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine culture and tangible benefits into Benefits section.
- Then "Basic Qualifications" list: 5+ years of non-internship professional software development experience etc. That's Requirements/Qualifications. We'll have Requirements section (maybe combine Basic and Preferred). We'll list each bullet.
- Then "Preferred Qualifications" list.
- Then "Amazon is an equal opportunity employer..." that's EEO boilerplate; we must remove.
- Then accommodation link etc; remove.
- Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." 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."
That's Pay and Benefits. We'll create Pay section with salary range and sign-on payments/RSUs. Benefits section with health insurance etc.
- Then "USA, WA, Seattle - 168,100.00 - 227,400.00 USD annually" that's location and pay; we already captured pay.
- Then "Company - Amazon Web Services, Inc. Job ID: A10455253" metadata; drop.
Now we need to decide sections:
- About the role: include intro paragraph + About The Team etc? Could also include Why Amazon Security? etc. But maybe better to keep About the role as the initial description (GTPC Tech...). Then Responsibilities as separate. Then Requirements/Qualifications combined? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications as separate possible headings. We could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or combine. We'll follow typical: Requirements = basic qualifications, Qualifications = preferred qualifications.
- Skills: maybe we can extract from responsibilities: experience with AWS CDK, Typescript, etc. Those are under Preferred Qualifications. Could also be under Skills. But we already have Qualifications for preferred. Could also create Skills section for specific technologies: AWS CDK, Typescript. But we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and put those under Qualifications.
- Schedule: not mentioned; omit.
- Pay: include salary range and sign-on payments/RSUs.
- Benefits: include health insurance etc and also culture points? Might be too much but okay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment.
We'll structure:
About the role
GTPC Tech is an AWS Security team developing services used by internal compliance teams to enable the international flow of AWS’s hardware, software, services, and technology. Through (i) self-service management of data, automation, and analytics, and (ii) integrations with supply chain systems, our solutions help AWS keep pace with rapidly expanding compliance obligations driven by regional expansion, evolving regulations, new hardware development, and shifting compliance responsibilities. We're looking for a Senior Software Development Engineer (SDE) who will provide key technical leadership on the team responsible for GTPC Tech's foundational services, which house compliance data (e.g., part classifications, requirements, evidence of compliance) and integrations with upstream and downstream systems. In this role, you will lead the design and development of capabilities that build upon these services to enable our customers to rapidly scale their capacity, through automation (both rule-based and AI-driven), streamlined user workflows, and innovative solutions that simplify and standardize bespoke business processes.
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-rounded professional.
Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why flexible work hours and arrangements are part of our culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve.
But that's many paragraphs; maybe we could combine into fewer sections. However we must preserve all substantive info; we can keep them asunder About the role. Now Responsibilities:
Responsibilities
- Design and build services and applications with a team of engineers.
- Believe in high standards for code quality, code reviews, testing, and operational excellence.
- Support peers to deliver results in a startup‑like environment with autonomy to build the right solution from day one.
- Collaborate with other engineers on technical direction and strategy.
- Benefit from career growth opportunities that AWS can offer.
Requirements
- 5+ years of non‑internship professional software development experience
- 5+ years of programming with at least one software programming language
- 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems
- Experience as a mentor, tech lead or leading an engineering team
Qualifications
- 5+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations
- Bachelor's degree in computer science or equivalent
- Experience with AWS CDK and services
- Experience programming with TypeScript
Benefits
- Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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
Pay
Base salary range: $168,100.00 – $227,400.00 USD annually (Seattle, WA). Package includes sign‑on payments and restricted stock units (RSUs). Final compensation determined by experience, qualifications, and location.
We could also include the link to benefits but that's boilerplate; maybe we can include as a link? The instruction: remove duplicated lines, application instructions. The link to learn more about benefits might be considered boilerplate; but it's a reference to benefits page. Might be okay to keep? It's not essential; but we could keep as a <
- for any list of duties/requirements/benefits. This is duties; we can make list.
- Then "About The Team Diverse Experiences Amazon Security values diverse experiences...." This is about team; could be part of About the role or separate? There's no explicit heading for About the Team but we could treat as part of About the role or maybe a separate section like "About the Team". However allowed headings list does not include About the Team; only the given set. So we should incorporate that content into About the role or maybe Responsibilities? Probably About the role.
- Then sections: Why Amazon Security?, Inclusive Team Culture, Training & Career Growth, Work/Life Balance. Those are benefits/culture. Could go under Benefits section? Benefits usually refers to compensation/benefits like health insurance etc. But we have a Benefits section later with actual benefits. The culture parts could be considered Benefits? The instruction: include a section ONLY when posting has real, specific content for it. We have Benefits section later with health insurance etc. So we should put those culture parts maybe under Benefits? But they are not typical benefits like health insurance; they are more about culture. Could we create a Benefits section and include those bullet points? The rule: Benefits section only if posting actually states them. It does state benefits: health insurance etc. So we will have Benefits section with those specifics. The culture parts could be placed under About the role or maybe omitted? But we must preserve ALL substantive information; cannot drop. So we need to include them somewhere. Could create a section "Benefits" and include both culture and tangible benefits? Might be okay. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine culture and tangible benefits into Benefits section.
- Then "Basic Qualifications" list: 5+ years of non-internship professional software development experience etc. That's Requirements/Qualifications. We'll have Requirements section (maybe combine Basic and Preferred). We'll list each bullet.
- Then "Preferred Qualifications" list.
- Then "Amazon is an equal opportunity employer..." that's EEO boilerplate; we must remove.
- Then accommodation link etc; remove.
- Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." 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."
That's Pay and Benefits. We'll create Pay section with salary range and sign-on payments/RSUs. Benefits section with health insurance etc.
- Then "USA, WA, Seattle - 168,100.00 - 227,400.00 USD annually" that's location and pay; we already captured pay.
- Then "Company - Amazon Web Services, Inc. Job ID: A10455253" metadata; drop.
Now we need to decide sections:
- About the role: include intro paragraph + About The Team etc? Could also include Why Amazon Security? etc. But maybe better to keep About the role as the initial description (GTPC Tech...). Then Responsibilities as separate. Then Requirements/Qualifications combined? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications as separate possible headings. We could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or combine. We'll follow typical: Requirements = basic qualifications, Qualifications = preferred qualifications.
- Skills: maybe we can extract from responsibilities: experience with AWS CDK, Typescript, etc. Those are under Preferred Qualifications. Could also be under Skills. But we already have Qualifications for preferred. Could also create Skills section for specific technologies: AWS CDK, Typescript. But we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and put those under Qualifications.
- Schedule: not mentioned; omit.
- Pay: include salary range and sign-on payments/RSUs.
- Benefits: include health insurance etc and also culture points? Might be too much but okay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment.
We'll structure: