> Markdown version of [/jobs/ext/4826075-software-development-engineer-iii-amazon-java-runtime](https://www.wearedevelopers.com/jobs/ext/4826075-software-development-engineer-iii-amazon-java-runtime). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Development Engineer III, Amazon Java Runtime - **Company:** Amazon.com, Inc. - **Location:** Seattle, WA, United States - **Contract:** Permanent contract - **Skills:** Java (Programming Language), X86 Architecture, Code Review, Java Development Kit, Java Virtual Machine (JVM), Software Engineering - **Published:** November 21, 2026 - **Apply:** https://www.careerbuilder.com/job-details/software-development-engineer-iii-amazon-java-runtime-seattle-wa--f49142ff-e067-4694-9883-3dfe8f44a96c ## About the Role Software Development, Java, Software Engineering, Java, Memory Hardware, Machine Tool, Vehicle Fleets, Ecosystems, x86 Processors, Prototyping ## Description The Java Runtimes Team (JRT) owns and advances the Java runtime that powers a large share of Amazon"s production services. We work at the intersection of language runtimes, compilers, and hardware - tuning the JVM and its ecosystem so that thousands of services run faster, use less memory, and scale more efficiently across x86 and Graviton (AArch64) fleets. We contribute directly to OpenJDK and our Corretto JDK, and we build the tooling that turns deep runtime expertise into automated, fleet-wide performance gains., 1. Analyze production JVM workloads to identify compiler, GC, and runtime bottlenecks, and translate findings into concrete optimizations. 2. Design, implement, and benchmark improvements to JIT compilation, garbage collection, and core runtime subsystems. 3. Contribute changes upstream to OpenJDK and to Amazon Corretto, working through code review and community processes. 4. Tune runtime behavior for performance and efficiency across x86 and Graviton (AArch64) architectures. 5. Build and improve profiling, observability, and auto-tuning tooling so runtime expertise scales across the fleet rather than through manual, per-service consultation. 6. Validate performance and reliability of changes against real workloads before broad rollout. 7. Partner with service teams to drive adoption of runtime improvements and newer JDK versions.