Jobs · Consulting · New York

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

Amazon · New York, United States · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: About the role? Actually description includes description paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to preserve all substantive info, remove boilerplate. We need to parse the posting. Content: - Intro description: "At Amazon, our tech isn't just a tool, it's your playground..." etc. That's description about role. - "What's in it for you? An internship at Amazon means real responsibility from day one..." That's maybe benefits? Actually it's about internship benefits. - "About The Team Annapurna Labs designs the custom silicon..." That's about team. - "Where You Might Land Annapurna has software teams..." That's about possible teams. - "As an SDE I, you'll contribute to real production software, which may include:" then bullet list of duties. - Basic Qualifications list. - Preferred Qualifications list. - Then EEO boilerplate etc to remove. - Then Los Angeles County applicants specifics (maybe we can drop as boilerplate? It's location-specific legal text; likely considered boilerplate; we should remove. - Then "If you have a disability..." accommodation link - remove. - Then "If the country/region you’re applying in isn’t listed..." remove. - Then "The starting pay for this position is listed below." Then list of locations with salaries. - Then "Starting Day 1 of employment, Amazon offers EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Learn more about our benefits at ..." That's benefits. - Then location list with pay. - Then "Company - Annapurna Labs (U.S.) Inc. - D63 Job ID: A10558915" - minor metadata, fold into short p or drop. We need sections: About the role (maybe from intro description), Responsibilities (duties list), Requirements (basic qualifications?), Qualifications (maybe preferred?), Skills? Benefits, Pay. We need to decide which sections to include based on content. We have: - About the role: The initial description paragraph(s) about Amazon tech, internship, etc. Could be "About the role". Also "About The Team" could be part of role description. But we can combine. - Responsibilities: The list under "As an SDE I, you'll contribute to real production software, which may include:" with bullet items. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: Could be derived from qualifications? Might be redundant. Could omit if not specific. - Benefits: The paragraph about EAP, Mental Health Support, Medical Advice Line, 401(k) matching plus link. - Pay: The list of locations with salaries. - Schedule: Not mentioned; omit. We must not create sections with placeholder text. So we include only those with real content. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. Not include Job ID etc as headings; we can put minor metadata in a short

    or drop. Probably drop. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include all bullet points exactly as given. Let's extract: Intro description paragraphs: "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." Next: "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." That could be part of About the role or Benefits? It's more about internship benefits. But we have separate Benefits section later. Might treat this as part of About the role. Next: "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." Next: "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" Next: "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:" then bullet list: - 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 That's responsibilities. Next: "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" We need to format as list items. Next: "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" Next: 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." Also earlier "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." Could be part of benefits but it's more about internship experience. We could include that in About the role. Pay: list: - 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 We need to preserve exactly. Now produce HTML. Structure:

    About the role

    ... intro paragraphs ...

    Maybe combine About the role and About the Team? Could have separate sections: About the role and About the Team. But we need to avoid thin sections. Could combine into About the role includes team description. But we have "About The Team" heading in original; we could treat as a subsection but we only have h3 headings allowed. Could make a separate h3 About the Team. That's okay if we have content. We need to avoid filler. The About The Team has substantive content. Thus we could have sections: - About the role (intro + What's in it for you?) - About the Team - Responsibilities - Requirements (Basic Qualifications) - Qualifications (Preferred Qualifications) - Benefits - Pay We must not create Skills section unless we have specific skills list; we don't. Now ensure we don't repeat job title as heading. Now produce HTML. We need to escape any HTML special characters? The content includes hyphens, parentheses, etc. It's fine. We need to ensure we don't include any markdown fences. Let's craft. First section About the role: Combine intro paragraphs and "What's in it for you?" maybe as two paragraphs. Paragraph1: 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. Paragraph2: 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. Now About the Team: Paragraph: 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. Next paragraph: 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 Next paragraph: 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: (then list) But we already have responsibilities list separate. Might be redundant. Actually the responsibilities list is exactly that. So we could keep the sentence

Similar jobs