Software Development Engineer, Amazon Java Runtime

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. We have description paragraphs: "Are you fascinated..." etc. That's likely "About the role" or maybe "Description". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Description (intro) maybe "About the role". - "Key job responsibilities" -> Responsibilities. - "About The Team" -> maybe "About the team" but not in list; could be part of About the role? Could be separate but not required. We could include as part of About the role or maybe "About the team" not listed; we could omit or include under About the role. - "Basic Qualifications" -> Requirements or Qualifications. They list qualifications. Could be "Requirements" or "Qualifications". We'll decide. - "Preferred Qualifications" -> maybe "Preferred Qualifications" but not in list; could be part of Qualifications. - Benefits: they mention benefits later: "Amazon also offers comprehensive benefits including health insurance...". So we have Benefits section. - Pay: they have salary range: "USA, WA, Seattle - 168,100.00 - 227,400.00 USD annually". Also mention sign-on payments and RSUs. So we have Pay. - Schedule: not mentioned. So we omit Schedule. - Skills: not explicitly listed but could be inferred from qualifications; but we should not invent. So we omit Skills if no explicit content. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them under appropriate headings. We need to remove boilerplate: EEO, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." maybe minor metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short p for Job ID maybe. We need to output only HTML fragment, no html/body tags, no markdown fences. Let's structure:

About the role

Are you fascinated by what happens beneath your code — how a compiler turns bytecode into blistering machine instructions, how a garbage collector reclaims memory without anyone noticing, how a runtime squeezes the last drop of performance out of the hardware? Maybe you've worked on garbage collection in a managed runtime like HotSpot, the .NET CLR, V8, or Chakra. Maybe you earned your expertise the hard way — tuning live services for performance and resilience under real production load. Whatever your path, the Java Runtimes Team at Amazon, owners of Amazon Corretto, would love to talk with you. Java powers the majority of services at Amazon and nearly all public-facing AWS services. When we make the runtime faster or leaner, thousands of services — and millions of customers — feel it. You will work at the intersection of compilers, garbage collection, and systems software: finding bottlenecks in real running services, developing patches to the OpenJDK compiler, runtime, and libraries, and shipping them to every Amazon developer. You'll share what you learn with the broader engineering community and contribute your improvements back to OpenJDK — where the whole world runs them too. This is deep, high-leverage systems work with an unusually direct line from your keyboard to global impact. We care about scalability, availability, and efficiency — and about going above and beyond to deliver the best possible Java experience for Amazon's internal teams, Corretto users, and the OpenJDK community.

Then Responsibilities:

Responsibilities

• Identify areas for improvement using data from real running services, and turn those findings into concrete compiler, GC, and runtime optimizations.
• Design, implement, and benchmark improvements to JIT compilation, garbage collection, and core runtime subsystems in the OpenJDK compiler, runtime, and libraries.
• Contribute your changes upstream to OpenJDK and to Amazon Corretto, working through code review and the community process.
• Tune runtime behavior for performance and efficiency across x86 and Graviton (AArch64) architectures.
• Build profiling, observability, and auto-tuning tooling so runtime expertise scales across the fleet.
• Share your findings with the engineering community and help service teams adopt runtime improvements and newer JDK versions

Then About the Team maybe we can include under About the role or separate heading "About the team". Since not in list, maybe we incorporate into About the role? But we have already used About the role for intro. Could add another heading "About the team" but not in allowed list; but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list. So we could add other headings if needed, but better to stick to those. However we have substantive content about the team; we could put it under About the role as additional paragraph. That would preserve info. Thus after responsibilities, we add a paragraph about the team under About the role? But we already closed About the role. Could we have another

About the role

again? That would be duplicate heading; maybe better to rename to "About the team" but it's not in list but allowed as example? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. So we can use other headings as needed. However they also say "Prefer a few substantive sections over many thin ones." So maybe we should incorporate team info into About the role section. Thus we can extend About the role paragraph to include team info after the initial description. Let's merge. About the role paragraph: combine intro and team info. Team info: "In 2018 the team migrated Amazon's default JDK to OpenJDK, building rigorous security and quality mechanisms around it so that security and custom patches land internally the moment they are ready. We took that expertise and launched Amazon Corretto, Amazon's no-cost, production-ready distribution of OpenJDK — bringing our enhancements to customers and the OpenJDK community at large. Today we push the runtime forward across x86 and Graviton (AArch64) fleets, and we increasingly encode deep runtime expertise into tooling so that fleet-wide performance gains scale far beyond one-to-one consultation." We'll add that after the initial description. Now Requirements/Qualifications: We have Basic Qualifications and Preferred Qualifications. We could make a section "Requirements" for Basic Qualifications, and maybe another "Preferred Qualifications" but not in list; but we could incorporate preferred into Requirements or Qualifications. Since they said "Qualifications" as a possible heading, we could put all qualifications under

Qualifications

and separate basic and preferred as subpoints maybe using

with
• and maybe mark preferred? But we must preserve all detail; we can list basic qualifications as items, then preferred qualifications as items under a subheading? Could add a

  Preferred Qualifications

  inside but not allowed? Might be okay but better to keep simple: have

  Qualifications

  then two

  paragraphs: one for Basic Qualifications, one for Preferred Qualifications. That preserves detail. Thus:

  Qualifications

  Basic Qualifications

  • 5+ years of non-internship professional software development experience
  • 5+ years of programming with at least one software programming language experience
  • 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience
  • Experience as a mentor, tech lead or leading an engineering team
  • Direct contributions to OpenJDK, the HotSpot JVM, or another production managed runtime (e.g. .NET CLR, V8, or Chakra).
  • Compiler backend or optimization experience — instruction selection, register allocation, code generation, escape analysis, inlining, or intrinsics.
  • Familiarity with JVM internals such as bytecode, class loading, JIT deoptimization, tiered compilation, or the JVMCI / Graal interfaces.

  Preferred Qualifications

  • A track record of upstream open-source contributions, published performance work, or conference talks.
  • A master's or PhD in Computer Science or a related field with a focus on compilers, runtimes, or systems.
  • Experience mentoring engineers or leading technical initiatives across teams
  But we used which is okay; but we might just use plain text. The instruction didn't forbid formatting tags. It's okay. 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
  We also have mention of sign-on payments and restricted stock units (RSUs) under Pay maybe. Pay:

  Pay

  The base salary range for this position is $168,100.00 - $227,400.00 USD annually (Seattle, WA). 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.

  We could also mention that Amazon also offers comprehensive benefits (already covered). So Pay section includes salary and RSUs. We should also include minor metadata like Job ID and Company maybe as a short p at end. We need to remove boilerplate: EEO, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." maybe we can include as short p: "Company: Amazon Web Services, Inc." but it's minor metadata; we can fold into a short p. Job ID: A10559744. We can add at end:

  Job ID: A10559744

  Now ensure we didn't repeat job title as heading. We didn't. Check for any duplicated lines: we have not. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now output only HTML fragment. Let's craft final HTML. We need to ensure proper nesting. We'll output:

  About the role

  Are you fascinated by what happens beneath your code — how a compiler turns bytecode into blistering machine instructions, how a garbage collector reclaims memory without anyone noticing, how a runtime squeezes the last drop of performance out of the hardware? Maybe you've worked on garbage collection in a managed runtime like HotSpot, the .NET CLR, V8, or Chakra. Maybe you earned your expertise the hard way — tuning live services for performance and resilience under real production load. Whatever your path, the Java Runtimes Team at Amazon, owners of Amazon Corretto, would love to talk with you. Java powers the majority of services at Amazon and nearly all public-facing AWS services. When we make the runtime faster or leaner, thousands of services — and millions of customers — feel it