Software Development Manager, Denied Party Screening, AWS Compliance & Security Assurance

The user wants me to reformat a job posting into clean semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists,

  for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold into short

  or drop 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include section ONLY when posting has real specific content - never emit heading with filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the job posting content: - Description/About the role: There's a description paragraph about the team mission, what they do, what they're looking for - Key job responsibilities: Listed as bullet points - A day in the life: Prose paragraph - About The Team: Several subsections (Diverse Experiences, Why Amazon Security?, Inclusive Team Culture, Training & Career Growth, Work/Life Balance) - these are more about company culture - Basic Qualifications: List - Preferred Qualifications: List - Pay: Base salary range given for Seattle, WA - Benefits: Listed comprehensively - Job ID: A10586904 - should fold into short

  or drop - Company: Amazon.com Services LLC I need to decide on sections. The posting has: 1. About the role / Description (prose) 2. Responsibilities (Key job responsibilities + A day in the life) 3. Requirements / Qualifications (Basic + Preferred) 4. Benefits (explicitly listed) 5. Pay (salary range given) 6. Maybe a short metadata line for Job ID and company I should not create "Schedule" section as not mentioned. I'll structure:

  About the role

  ...description...

  Responsibilities

  • ...key job responsibilities...

  ...day in the life...

  Qualifications

  Basic Qualifications

  • ...

  Preferred Qualifications

  • ...

  Benefits

  • ...

  Pay

  Base salary range: $184,900 - $250,200 annually (Seattle, WA). Package includes sign-on payments and restricted stock units (RSUs). Final compensation determined by experience, qualifications, and location.

  Job ID: A10586904 | Company: Amazon.com Services LLC

  But note: The rules say use

  for section headings. Should I use

  for subsections? The rules only mention

  for section headings. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid

  but says use

  for section headings. I think using

  for main sections and maybe

  for sub-sections is okay, but to be safe, I could make Basic and Preferred as separate

  sections? But they are subsections of Qualifications. The example includes "Requirements, Qualifications" as separate headings. I could do:

  Basic Qualifications

  ...

  Preferred Qualifications

  ...
  But the posting groups them under "Basic Qualifications" and "Preferred Qualifications". I'll treat them as separate sections. Also, the "About The Team" section is mostly company culture boilerplate. The rules say remove boilerplate. But some of it might be considered substantive? It's generic Amazon Security culture description. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This includes EEO/equal-opportunity boilerplate. The "About The Team" includes "Diverse Experiences", "Why Amazon Security?", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". These are somewhat generic but specific to Amazon Security. However, they are not specific to the role. The rules say "Preserve ALL substantive information". But also "Prefer a few substantive sections over many thin ones." I think I should include them maybe under a "Team & Culture" section? But the rules say include section ONLY when posting has real specific content for it. This content is real but generic. I'll include a brief "Team & Culture" section with a paragraph summarizing? But the rules say use
  • for lists and

    for prose. The team section has multiple subsections with prose. I could include them as a list of points? But they are not duties/requirements/benefits. The rules say "Use

    • for any list of duties/requirements/benefits". So for other lists, maybe still use
      • ? The example says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So they expect those sections. I think I'll include a "Team & Culture" section with prose paragraphs. But the rules also say "never emit a heading followed by filler/placeholder text". This is not filler, it's actual content from the posting. However, it's somewhat boilerplate. The user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The "About The Team" includes DEI, inclusive culture, etc. That might be considered EEO/equal-opportunity boilerplate. I think I should remove it. The posting also has an explicit EEO statement later: "Amazon is an equal opportunity employer...". That's definitely boilerplate to remove. Thus, I'll omit the "About The Team" section entirely, as it's generic company culture boilerplate. The description already mentions "Diverse Experiences Amazon Security values diverse experiences..." but that's in the description? Actually the description includes "About The Team Diverse Experiences Amazon Security values diverse experiences..." That's part of the posting. I'll keep the description as is, but the "About The Team" section is separate. I'll include the description paragraph that includes the team mission, but the separate "About The Team" section with subsections I'll drop. Let's parse the input text: "Description At Amazon, security is central to maintaining customer trust and delivering delightful customer experiences. Our mission is to prevent denied entities from transacting with Amazon businesses. We build automatic mechanisms to detect and prevent prohibited transactions with denied entities using a diverse set of algorithms and machine learning techniques. We screen over a billion events every day and deal with unique scaling and TPS challenges. We are still Day 1 and have an exciting road map to build Machine Learning (ML) and Generative AI (LLM) powered detection and resolution systems to help scale Amazon for years to come. We are looking for a Software Development Manager, who has the passion for working on challenging problems from the very early stages. Together with a multi-disciplinary team of engineers, ML scientists, and subject domain experts, you will help define our customer experience and protect Amazon brand. If you have an entrepreneurial spirit, know how to deliver, are technical and innovative, and looking for an opportunity to build ML/AI systems and solutions, we want to talk to you. Ideal candidate will have a strong technical background and solid people management skills to build, manage and develop a highly-talented and experienced engineering team. Strong judgment and communication skills, long term technical vision, and continuous focus on engineering and operational excellence are essential for the success in this role. Key job responsibilities Define and communicate team vision, leading with passion and empathy Shape team structure and technical strategy aligned with business objectives Develop and mentor future leaders to translate complex business needs into technical solutions Lead multiple teams in large-scale service development and deployment Make strategic decisions on software products, tools, and new development initiatives Ensure systems maintain operational excellence in production environments Partner with business stakeholders, engineering teams, and design teams A day in the life You are the owner of your team and product, diving into any problem with your engineers and stakeholders to invent scalable solutions and remove roadblocks to protect Amazon from the bad actors. You are also the mentor and champion of your team members, helping them grow in their career aspirations and technical growth. About The Team 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-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. Basic Qualifications 3+ years of engineering team management experience 7+ years of engineering experience 8+ years of leading the definition and development of multi tier web services experience Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field Knowledge of engineering practices and patterns for the full software/hardware/networks development life cycle, including coding standards, code reviews, source control management, build processes, testing, certification, and livesite operations Experience partnering with product or program management teams Preferred Qualifications Experience in communicating with users, other technical teams, and senior leadership to collect requirements, describe software product features, technical designs, and product strategy Experience in recruiting, hiring, mentoring/coaching and managing teams of Software Engineers to improve their skills, and make them more effective, product software engineers Amazon is an equal opportunity employer and does not discriminate on the basis of protected veteran status, disability, or other legally protected status. Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner. 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 S