Senior Applied Scientist, AWS Healthcare AI

We need to produce HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have description: "At AWS Healthcare AI, we're revolutionizing..." that's about the role. Then "Key job responsibilities" list. Then "About The Team" repeated (but that's about team, not required). Then "BASIC QUALIFICATIONS" and "PREFERRED QUALIFICATIONS". Then benefits and pay info: "The base salary range for this position is listed below... Amazon also offers comprehensive benefits including ...". Also location salary ranges: USA, CA, Sunnyvale - 192,200.00 - 260,000.00 USD annually; USA, WA, Seattle - 167,100.00 - 226,100.00 USD annually. So we have Pay info. Benefits info present. Schedule not mentioned. So we should not include Schedule section. Also we should not repeat job title heading. Use

for each section heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, scam warning, etc. Also remove duplicated lines like "About The Team" repeated. Also remove navigation etc. We need to include sections: About the role (maybe from first paragraph), Responsibilities, Qualifications (maybe combine BASIC and PREFERRED?), Skills (maybe list programming languages etc?), Benefits, Pay. We need to decide what goes where. The posting includes "Key job responsibilities" bullet list? It is prose: "To be successful in this mission, we are seeking an experienced Applied Scientist to lead pioneering research and development of new, highly confidential AI applications that re-imagine experiences for end-customers (e.g., consumers, patients), frontline workers (e.g., customer service agents, clinicians), and back-office staff (e.g., claims processing, medical coding). As a leading subject matter expert in NLU, deep learning, knowledge representation, foundation models, and reinforcement learning, you will guide a team of scientists to invent novel, generative AI-powered experiences. This role involves defining research directions, developing new ML techniques, conducting rigorous experiments, and ensuring research translates to impactful products. You will be a hands-on technical innovator who is passionate about building scalable scientific solutions. You will set the standard for excellence, invent scalable, scientifically sound solutions across teams, define evaluation methods, and lead complex reviews. This role wields significant influence across AWS, Amazon, and the global research community." We can treat that as responsibilities. Could also split into bullet list? It's prose; we can keep as

  . But rule: Use

  • for any list of duties/requirements/benefits. This is not a list but prose; we can keep as

    . About the role: The initial description "At AWS Healthcare AI, we're revolutionizing healthcare delivery through AI solutions that serve millions globally..." That's about the role/team. We'll put that in About the role section. Qualifications: BASIC QUALIFICATIONS and PREFERRED QUALIFICATIONS. We can combine into a Qualifications section with two sublists? But rule: Use

    • for any list of duties/requirements/benefits. So we can make a
      for BASIC QUALIFICATIONS items and another for PREFERRED QUALIFICATIONS items. Or we could have two headings? But we only allowed headings for sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have a Qualifications section with two
      lists, maybe with a

      indicating BASIC and PREFERRED. But we need to preserve all info. Could do:

      Qualifications

      Basic Qualifications:

      • PhD, or Master's degree and 6+ years of applied research experience
      • 3+ years of building machine learning models for business application experience
      • Experience programming in Java, C++, Python or related language
      • Experience with neural deep learning methods and machine learning
      • 8+ years of building large-scale machine learning and AI solutions at Internet scale experience

      Preferred Qualifications:

      • Experience with modeling tools such as R, scikit-learn, Spark MLLib, MxNet, Tensorflow, numpy, scipy etc.
      • Experience in building speech recognition, machine translation and natural language processing systems (e.g., commercial speech products or government speech projects)
      • Experience with large scale machine learning systems such as profiling and debugging and understanding of system performance and scalability
      • Master's degree, or a PhD or equivalent research experience and experience in patents or publications at top-tier peer-reviewed conferences or journals
      • Strong publication record in top-tier journals and conferences.
      But note duplicate "Strong publication record in top-tier journals and conferences." appears twice in original; we should preserve but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If it's duplicated in source, we might keep it once? It's ambiguous. Safer to keep as appears, but we could keep both entries; but that would be duplicating same line. Might be considered unnecessary but not invented. I'd keep one to avoid redundancy but it's summarizing away detail (removing duplicate). Might be okay? The instruction says do NOT invent or summarize away detail. Removing a duplicate could be considered summarizing away detail (though it's redundant). Safer to keep both? But that would be weird. I'd keep one but note it's duplicate; maybe better to keep both to preserve detail. I'll include two identical entries. Skills: The posting includes experience programming in Java, C++, Python or related language; experience with neural deep learning methods; experience with modeling tools etc. Could be placed under Skills section. But we already have qualifications covering those. Could create a Skills section for technical skills: programming languages, ML methods, tools. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one Qualifications section. But we need to follow headings list: we can use Qualifications for both basic and preferred. Skills maybe not needed if covered. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we can omit if no specific content. Since we have skill details, we could put them under Skills. But we already have them in qualifications. To avoid duplication, maybe we put programming languages etc under Skills, and keep qualifications for degrees/experience. Let's parse: Basic qualifications include degree, years, programming language experience, deep learning methods, large-scale ML experience. Preferred qualifications include modeling tools, speech/NLP systems, large scale ML systems, patents/publications, strong publication record. Thus we could separate: Qualifications (degrees, years of experience) and Skills (programming languages, ML methods, tools). But the basic qualifications already include programming language and deep learning methods. Might be okay to have overlap. Given the instruction to prefer few substantive sections, I'd combine into Qualifications section with two lists: Basic and Preferred. That covers all. Then we don't need a separate Skills section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now Benefits: The posting includes: "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." We should preserve that as a
      list? It's a sentence with parentheses. Could break into list items: health insurance (list subitems), 401(k) matching, paid time off, parental leave. But we must not invent detail; we can keep as

      with the sentence. However rule: Use

      • for any list of duties/requirements/benefits. This is a list of benefits, so we should use
        • . We need to extract each benefit item. The sentence includes health insurance with many subcomponents; we could treat health insurance as one item with its details in parentheses. Then 401(k) matching, paid time off, parental leave. Also link to learn more. We could keep link as part of

          after list. Thus:

          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

          Learn more about our benefits at https://amazon.jobs/en/benefits

          But we must not add extra info like link? The original includes "Learn more about our benefits at https://amazon.jobs/en/benefits." So we should keep that. Using is okay; it's still HTML. It's not adding info. Pay: The posting includes base salary ranges for two locations. Also mentions sign-on payments and RSUs. So we need to capture that. We can do:

          Pay

          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.

          • USA, CA, Sunnyvale - $192,200.00 - $260,000.00 USD annually
          • USA, WA, Seattle - $167,100.00 - $226,100.00 USD annually
          We need to preserve the exact numbers; include dollar signs? Original: "USA, CA, Sunnyvale - 192,200.00 - 260,000.00 USD annually". We can keep as is, maybe add $ for clarity but that would be adding detail not present. Better to keep exactly as original: "192,200.00 - 260,000.00 USD annually". So:
        • USA, CA, Sunnyvale - 192,200.00 - 260,000.00 USD annually
        • USA, WA, Seattle - 167,100.00 - 226,100.00 USD annually
        Now About the role: We'll take the first paragraph(s) before "Key job responsibilities". The description includes two paragraphs: "At AWS Healthcare AI, we're revolutionizing healthcare delivery through AI solutions that serve millions globally. As a pioneer in healthcare technology, we're building next-generation services that combine Amazon's world-class AI infrastructure with deep healthcare expertise. Our mission is to accelerate our healthcare businesses by delivering intuitive and differentiated technology solutions that solve enduring business challenges. The AWS Healthcare AI organization includes services such as HealthScribe, Comprehend Medical, HealthLake, and more." Then later there is a repeated "About The Team" paragraph identical to that. We'll include only once. Thus:

        About the role