Senior ML Compiler Engineer, Neuron
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Company background about AWS Machine Learning accelerators, Trainium, Neuron SDK, NKI
- Team description (Annapurna Labs)
- Role description: "As a Sr. ML Compiler Engineer on the Amazon Neuron team..."
- "Key job responsibilities" section with bullet points
- "A day in the life" section with prose
- "Basic Qualifications" with bullet points
- "Preferred Qualifications" with bullet points
- Some legal/EEO boilerplate (Los Angeles County applicants, equal opportunity employer, accommodations)
- Salary ranges for Cupertino and Seattle
- Benefits description
- Company name and Job ID at the end
I need to structure this into appropriate sections. Let me think about the sections:
1. About the role / Overview - could combine the company background and role description
2. Responsibilities - from "Key job responsibilities" and "A day in the life"
3. Requirements / Qualifications - Basic and Preferred qualifications
4. Benefits - the benefits paragraph
5. Pay - the salary ranges
6. Location - the requirement about Seattle or Cupertino
I should not include the EEO boilerplate, Los Angeles County specific text, accommodations link, etc. as they are boilerplate.
The Job ID and Company name at the end are minor metadata - I can fold into a short
or drop. I'll include a brief metadata line.
Let me structure the HTML:
About the role
...company background and role description...
Responsibilities
- ...key job responsibilities...
...day in the life...
Qualifications
Basic Qualifications
- ...
Preferred Qualifications
- ...
Location
Candidates must be located in or willing to relocate to Seattle, WA or Cupertino, CA.
Pay
Base salary ranges:
- Cupertino, CA: $193,300 - $261,500 annually
- Seattle, WA: $168,100 - $227,400 annually
Compensation includes sign-on payments and restricted stock units (RSUs). Final compensation determined by experience, qualifications, and location.
Benefits
Comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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.
Company: Annapurna Labs (U.S.) Inc. | Job ID: A10566149
Wait, the rules say use for section headings. Should I use for sub-sections? The rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention sub-headings. I could use for main sections and maybe for sub-sections, but to be safe, I'll use for main sections and perhaps or just list items for sub-sections. But the Basic and Preferred qualifications are distinct enough. I could make them separate sections: "Basic Qualifications" and "Preferred Qualifications". That might be better.
Let me restructure:
About the role
...
Responsibilities
...key responsibilities...
...day in the life...
Basic Qualifications
...
Preferred Qualifications
...
Location
...
Pay
...
...
Benefits
...
Company: Annapurna Labs (U.S.) Inc. | Job ID: A10566149
That seems clean. I'll avoid to stick to the rule.
Now, I need to preserve all substantive information. Let me extract the text carefully.
From the posting:
"AWS Machine Learning accelerators are at the forefront of AWS innovation. Trainium delivers best-in-class ML training performance with the most teraflops (TFLOPS) of compute power for ML in the cloud. This is all enabled by the AWS Neuron Software Development Kit (SDK), which includes an ML compiler, the Neuron Kernel Interface (NKI) compiler, and a runtime that natively integrates into popular ML frameworks such as PyTorch and JAX. Neuron Kernel Interface (NKI) is a bare-metal language and compiler for directly programming AWS Trainium instances. You can use NKI to develop, optimize, and run new operators directly on hardware while making full use of available compute and memory resources. Explore NKI https://awsdocs-neuron.readthedocs-hosted.com/en/latest/nki/index.html AWS Neuron is used at scale by customers such as Epic Games, Snap, Airbnb, Autodesk, Amazon Alexa, and Amazon Rekognition, along with many others across a range of segments. Amazon's Annapurna Labs is responsible for building innovative silicon and software for AWS customers. We are at the forefront of innovation, combining cloud scale with the world's most talented engineers. Our team covers multiple disciplines including silicon engineering, hardware design and verification, software, and operations. With such breadth of talent, there is opportunity to learn all the time. We operate in spaces that are very large, yet our teams remain small and agile. There is no blueprint. We're inventing. We're experimenting. When you couple that with the ability to work on so many different products and services, it makes for a unique learning culture. Learn More About Our History https://www.amazon.science/how-silicon-innovation-became-the-secret-sauce-behind-awss-success Explore The Product https://aws.amazon.com/machine-learning/neuron/ https://awsdocs-neuron.readthedocs-hosted.com/en/latest/general/nki/index.html"
I should include this but maybe not the URLs? The rule says preserve all substantive information. URLs are references, but they might be considered part of the content. I'll include them as links or just text. Since it's HTML, I could make them links, but the rule doesn't specify. I'll include them as plain text for simplicity.
"As a Sr. ML Compiler Engineer on the Amazon Neuron team, you are a thought leader supporting the ground-up development and scaling of a compiler to handle the world's largest ML workloads. Architecting and implementing customer-critical features, publishing research, and mentoring a skilled team of engineers are exciting challenges for you. You leverage your technical communications skill as a hands-on partner to Amazon ML partner teams. You want to be involved in pre-silicon design, bringing new products and features to market, and shipping high-quality code. A background in Machine Learning and AI accelerators is helpful, but not required. In order to be considered for this role, candidates must be located in or willing to relocate to Seattle or Cupertino."
Key job responsibilities:
- Design and build compiler features for the Neuron compilers. Your work may span the frontend, intermediate representations, optimization passes, and code generation for the hardware.
- Own customer-critical features end to end: scope the problem, write the design, ship production code, and provide support to customers.
- Partner with Amazon ML teams (PyTorch, JAX, and internal model teams) as a hands-on technical contact. You translate their workloads into compiler requirements and unblock them on hardware.
- Contribute to pre-silicon design. You give the hardware teams compiler and programmability feedback before a chip is built, and you bring new products and features to customers.
- Raise the technical bar by reviewing code and designs, publishing research where it makes sense, and mentoring engineers.
A day in the life:
"You start the day reviewing a teammate's code for a new compiler feature, leaving feedback before it merges. Mid-morning, you pair with a model team blocked on a kernel that hasn't reached peak performance on Trainium, and you trace the bottleneck through the compiler's passes. After lunch, you write and test the feature you scoped last week, then run your changes on hardware to confirm correctness. You close the day in a pre-silicon review, giving the hardware team programmability feedback on the next chip. The team moves quickly and you are always in the details."
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
Preferred Qualifications:
- 5+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Master's degree or Ph.D. in computer science, computer engineering, or related field
Then the boilerplate: EEO, Los Angeles County, accommodations, etc. - remove.
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. 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. USA, CA, Cupertino - 193,300.00 - 261,500.00 USD annually USA, WA, Seattle - 168,100.00 - 227,400.00 USD annually"
Company - Annapurna Labs (U.S.) Inc. Job ID: A10566149
I'll include the benefits and pay as separate sections.
Now
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Company background about AWS Machine Learning accelerators, Trainium, Neuron SDK, NKI - Team description (Annapurna Labs) - Role description: "As a Sr. ML Compiler Engineer on the Amazon Neuron team..." - "Key job responsibilities" section with bullet points - "A day in the life" section with prose - "Basic Qualifications" with bullet points - "Preferred Qualifications" with bullet points - Some legal/EEO boilerplate (Los Angeles County applicants, equal opportunity employer, accommodations) - Salary ranges for Cupertino and Seattle - Benefits description - Company name and Job ID at the end I need to structure this into appropriate sections. Let me think about the sections: 1. About the role / Overview - could combine the company background and role description 2. Responsibilities - from "Key job responsibilities" and "A day in the life" 3. Requirements / Qualifications - Basic and Preferred qualifications 4. Benefits - the benefits paragraph 5. Pay - the salary ranges 6. Location - the requirement about Seattle or Cupertino I should not include the EEO boilerplate, Los Angeles County specific text, accommodations link, etc. as they are boilerplate. The Job ID and Company name at the end are minor metadata - I can fold into a short
or drop. I'll include a brief metadata line. Let me structure the HTML:
About the role
...company background and role description...
Responsibilities
- ...key job responsibilities...
...day in the life...
Qualifications
Basic Qualifications
- ...
Preferred Qualifications
- ...
Location
Candidates must be located in or willing to relocate to Seattle, WA or Cupertino, CA.
Pay
Base salary ranges:
- Cupertino, CA: $193,300 - $261,500 annually
- Seattle, WA: $168,100 - $227,400 annually
Compensation includes sign-on payments and restricted stock units (RSUs). Final compensation determined by experience, qualifications, and location.
Benefits
Comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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.
Company: Annapurna Labs (U.S.) Inc. | Job ID: A10566149
Wait, the rules say use