Jobs · Engineering · Washington

Software Development Engineer I, Annapurna Labs, Early Career - 2027

Amazon · Seattle, WA · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the description. Let's extract sections: - About the role: The description includes "Description At Amazon, our tech isn't just a tool..." etc. Also "What's in it for you? An internship at Amazon means real responsibility from day one." That's maybe about role? Also "About The Team Annapurna Labs designs the custom silicon..." That's about team. We need to decide sections: Could have "About the role" (description of role), "Responsibilities" (list of duties), "Requirements" (basic qualifications), "Qualifications" (preferred qualifications), "Skills" maybe not explicit, "Benefits" (list of benefits), "Pay" (starting pay listed), "Schedule" (not present). So we include only those with content. We must not include placeholder like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract content: Description paragraph: "At Amazon, our tech isn't just a tool, it's your playground. Our engineers work on scalable systems, cloud services, and customer-facing products that operate at global scale. This is an environment where you learn by building. Whether you're creating cloud-native solutions, optimizing machine learning models, or building products that drive experiences for millions of customers around the globe, your work reaches the world, fast. You'll take ownership early, collaborate across teams and disciplines, and grow your skills as you tackle new problems. There's no single path forward here, with a chance to explore different directions and shape your journey as you go. This is where ambition meets opportunity and, where the impact of what you build helps define what comes next, for customers and for you." Then "What's in it for you? An internship at Amazon means real responsibility from day one. You'll build, test, and learn alongside people who want to see you succeed, while making an impact that reaches far beyond campus." Then "About The Team Annapurna Labs designs the custom silicon at Amazon - including Graviton (our server processors), Trainium and Inferentia (our machine learning training and inference accelerators), and the Nitro system that powers modern EC2. We own the full stack, from silicon through the software that makes it work (compilers, runtimes, drivers, and the frameworks that let customers run workloads on our hardware). As a Software Development Engineer I, you'll write the software that turns custom silicon into products used by millions. Where You Might Land Annapurna has software teams spanning the full stack, and we work to place you on a technical team aligned with your interests and strengths. Example teams and focus areas include: Compiler development for ML accelerators (Neuron SDK, MLIR, LLVM) ML runtimes and frameworks (integration with PyTorch, JAX, TensorFlow) Low-level systems software, firmware, and device drivers Performance optimization and kernel development for custom silicon Distributed training and inference infrastructure Once you join, we partner with you and our hiring managers to match you to a team where your background and interests fit best, so your project is something you're genuinely excited to work on. As an SDE I, you'll contribute to real production software, which may include: Designing, implementing, and testing software across the stack - from low-level systems code to compilers, runtimes, and tooling Writing efficient, maintainable code in languages such as C, C++, or Python Optimizing software performance on custom hardware (Graviton, Trainium, Inferentia) Debugging complex issues across the hardware-software boundary Collaborating with hardware, compiler, and systems teams to deliver features end-to-end Documenting your work and presenting results to the team" Then "Basic Qualifications Bachelor's or Master's degree program in Computer Science, Computer Engineering, or a related field, with a final graduation date of May 2027 or later Programming experience in at least one modern language such as C, C++, Java, or Python Coursework or project experience in data structures, algorithms, and software design Understanding of core computer science fundamentals: operating systems, computer architecture, or systems programming" Then "Preferred Qualifications Bachelor's or Master's degree with a focus on systems, compilers, computer architecture, or high-performance computing Experience with low-level or systems programming in C/C++ (memory management, concurrency, performance optimization) Familiarity with compilers (MLIR, LLVM, TVM), ML runtimes, operating systems internals, or distributed systems Exposure to machine learning frameworks and an understanding of how models run on hardware Prior internship, research, or open-source contribution experience in systems, compilers, or ML infrastructure" Then benefits: "Starting Day 1 of employment, Amazon offers EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits." Pay: "The starting pay for this position is listed below. Austin, TX, USA - 128,700.00 USD Annually Cupertino, CA, USA - 148,100.00 USD Annually New York, NY, USA - 141,600.00 USD Annually Seattle, WA, USA - 128,700.00 USD Annually" Schedule: Not present. We need to format sections. We need to decide which sections to include: About the role (maybe combine description and "What's in it for you?" and "About The Team"? Could be separate sections: About the role, Responsibilities, etc. Responsibilities: The list under "As an SDE I, you'll contribute to real production software, which may include:" includes bullet-like sentences. We can make a
  • list. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: Not explicit; maybe we could extract from responsibilities? But we should not invent. So skip Skills if no explicit. Benefits: list of benefits. Pay: list of locations and salaries. Schedule: none, omit. We also might include "About the team" as part of About the role or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. If we have content that matches those headings, we use them. If we have extra content like "About The Team", we could fold into About the role or Responsibilities? Probably About the role includes description of role and team. Thus:

    About the role

    At Amazon, our tech isn't just a tool, it's your playground. Our engineers work on scalable systems, cloud services, and customer-facing products that operate at global scale. This is an environment where you learn by building. Whether you're creating cloud-native solutions, optimizing machine learning models, or building products that drive experiences for millions of customers around the globe, your work reaches the world, fast. You'll take ownership early, collaborate across teams and disciplines, and grow your skills as you tackle new problems. There's no single path forward here, with a chance to explore different directions and shape your journey as you go. This is where ambition meets opportunity and, where the impact of what you build helps define what comes next, for customers and for you. What's in it for you? An internship at Amazon means real responsibility from day one. You'll build, test, and learn alongside people who want to see you succeed, while making an impact that reaches far beyond campus. Annapurna Labs designs the custom silicon at Amazon - including Graviton (our server processors), Trainium and Inferentia (our machine learning training and inference accelerators), and the Nitro system that powers modern EC2. We own the full stack, from silicon through the software that makes it work (compilers, runtimes, drivers, and the frameworks that let customers run workloads on our hardware). As a Software Development Engineer I, you'll write the software that turns custom silicon into products used by millions. Where You Might Land Annapurna has software teams spanning the full stack, and we work to place you on a technical team aligned with your interests and strengths. Example teams and focus areas include: Compiler development for ML accelerators (Neuron SDK, MLIR, LLVM) ML runtimes and frameworks (integration with PyTorch, JAX, TensorFlow) Low-level systems software, firmware, and device drivers Performance optimization and kernel development for custom silicon Distributed training and inference infrastructure Once you join, we partner with you and our hiring managers to match you to a team where your background and interests fit best, so your project is something you're genuinely excited to work on.

    But we need to keep list items for responsibilities separate. Responsibilities: list of duties: "Designing, implementing, and testing software across the stack - from low-level systems code to compilers, runtimes, and tooling Writing efficient, maintainable code in languages such as C, C++, or Python Optimizing software performance on custom hardware (Graviton, Trainium, Inferentia) Debugging complex issues across the hardware-software boundary Collaborating with hardware, compiler, and systems teams to deliver features end-to-end Documenting your work and presenting results to the team" We can split each sentence into
  • . Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Benefits: list: EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Pay: list of locations with salaries. We should not include the "Learn more about our benefits at ..." maybe keep as part of benefits paragraph? Could be a

    after list. But we need to preserve all substantive info. So include that sentence maybe as a

    after list. Similarly for pay: include the line "The starting pay for this position is listed below." then list. We must not include boilerplate like EEO, LA County, etc. Remove those. Now produce HTML fragment. Let's craft. We need to ensure no extra whitespace? It's fine. We'll output:

    About the role

    ...

    Responsibilities

    • Designing, implementing, and testing software across the stack - from low-level systems code to compilers, runtimes, and tooling
    • Writing efficient, maintainable code in languages such as C, C++, or Python
    • Optimizing software performance on custom hardware (Graviton, Trainium, Inferentia)
    • Debugging complex issues across the hardware-software boundary
    • Collaborating with hardware, compiler, and systems teams to deliver features end-to-end
    • Documenting your work and presenting results to the team

    Requirements

    • Bachelor's or Master's degree program in Computer Science, Computer Engineering, or a related field, with a final graduation date of May 2027 or later
    • Programming experience in at least one modern language such as C, C++, Java, or Python
    • Coursework or project experience in data structures, algorithms, and software design
    • Understanding of core computer science fundamentals: operating systems, computer architecture, or systems programming

    Qualifications

    • Bachelor's or Master's degree with a focus on systems, compilers, computer architecture, or high-performance computing
    • Experience with low-level or systems programming in C/C++ (memory management, concurrency, performance optimization)
    • Familiarity with compilers (MLIR, LLVM, TVM), ML runtimes, operating systems internals, or distributed systems
    • Exposure to machine learning frameworks and an understanding of how models run on hardware
    • Prior internship, research, or open-source contribution experience in systems

Similar jobs