Sr Embedded Software Engineer, Annapurna ML Software

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the description. Key parts: - Description paragraph about Annapurna Labs. - "Key job responsibilities" list: bullet points? It shows lines: Define technical strategy and lead architecture for Annapurna Labs' machine learning platform, driving decisions that impact multiple product lines Collaborate with EC2 teams and manufacturing partners to ensure seamless system integration Own end-to-end qualification frameworks and processes, mentoring engineers on implementation best practices Drive end-to-end qualification processes for new software implementations Craft high-performance solutions using C/C++ running on Linux - "A day in the life" paragraph: description. - "About The Team" paragraph. - "Basic Qualifications" list: multiple bullet points each with "5+ years of ..." etc. - "Preferred Qualifications": Bachelor's degree in computer science or equivalent - Then EEO etc to remove. - Then Los Angeles County applicants paragraph: includes job duties etc. This is likely location-specific legal text; we should remove as boilerplate? It's not EEO but it's location-specific legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal boilerplate (Los Angeles County). Should remove. - Then "Our inclusive culture empowers..." paragraph: likely also boilerplate (EEO style). Remove. - Then accommodation paragraph: remove. - Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. - Then "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." This contains Pay and Benefits info. We need to include Pay and Benefits sections if posting actually states them. It does state salary ranges for two locations: USA, CA, Cupertino - 193,300.00 - 261,500.00 USD annually; USA, TX, Austin - 168,100.00 - 227,400.00 USD annually. Also mentions sign-on payments and RSUs, benefits list. So we should include Pay section with those salary ranges. Benefits section with the list. Schedule: not mentioned, so omit. Skills: maybe we can infer from responsibilities but not explicit list. Better not to create Skills unless explicit. The posting does not have a separate Skills section. So we may omit Skills. Qualifications: we have Basic Qualifications and Preferred Qualifications. Could combine into Requirements/Qualifications. The instruction: use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have responsibilities, qualifications (basic and preferred). Could have a section "Requirements" for basic qualifications, and maybe "Preferred Qualifications" as a subsection? But we only allowed headings from list; we could use "Qualifications" for both basic and preferred, maybe separate with

or

. Or we could have "Requirements" for basic and "Preferred Qualifications" not in list; but we could still include as a

under Qualifications. Safer: Use "Requirements" for basic qualifications, and "Preferred Qualifications" maybe as a

under Qualifications? But heading must be from list; we could still have a

Qualifications

and inside include both basic and preferred as lists. Responsibilities: we have "Key job responsibilities" and "A day in the life" and "About The Team". Could combine into Responsibilities section. About the role: we have initial description paragraph. Could be "About the role". Thus sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (maybe preferred?), Benefits, Pay. But we need to avoid thin sections. Perhaps combine Basic and Preferred into one Qualifications section with two sublists: Basic Qualifications and Preferred Qualifications. We must not repeat job title as heading. We must not include Job ID. We must output only HTML fragment. Let's craft:

About the role

Annapurna Labs designs silicon and software that accelerates innovation. Customers choose us to create cloud solutions that solve challenges that were unimaginable a short time ago- even yesterday. Our custom chips, accelerators, and software stacks enable us to take on technical challenges that have never been seen before, and deliver results that help our customers change the world. In Annapurna Labs we are at the forefront of hardware/software co-design not just in Amazon Web Services (AWS) but across the industry. Our Annapurna MLA Software team is looking for candidates interested in diving deep into the different hardware technologies that power our Machine Learning servers and develop the software and firmware to drive, support and sustain these technologies as they evolve though concept and manufacturing, and finally take their place in our rapidly expanding fleet of bleeding edge Machine Learning products our customers demand.

Responsibilities

• Define technical strategy and lead architecture for Annapurna Labs' machine learning platform, driving decisions that impact multiple product lines
• Collaborate with EC2 teams and manufacturing partners to ensure seamless system integration
• Own end-to-end qualification frameworks and processes, mentoring engineers on implementation best practices
• Drive end-to-end qualification processes for new software implementations
• Craft high-performance solutions using C/C++ running on Linux
• Architect and develop the software and firmware that drives NeuronSwitches- the high-performance interconnect fabric for Trainium chips.
• Work closely with EC2, Annapurna Labs teams and manufacturing teams to bring up new hardware, debug board-level issues and optimize data paths.
• Write device drivers, build ML infrastructure, implement switch fabric control logic and develop the tooling needed for testing, qualification, and production deployment.
• Perform hands-on systems work- from initial hardware bring-up through manufacturing scale-up.
We could also include About The Team paragraph as part of responsibilities or as separate? Might be okay to add as a

under Responsibilities. Add a

about team: "The Annapurna ML Software team builds the software and firmware that powers NeuronSwitches- AWS' next-generation switching infrastructure forming the high-performance interconnect fabric for Trainium 3 chips. We focus on mission-mode control of sensors, board-level hardware, and the critical data paths that enable chip-to-chip communication at scale. Our work spans device drivers, switched fabric and everything in between- from debug and testing through qualification and manufacturing. We work at the hardware-software boundary where silicon meets systems. While ML engineers optimize models and algorithms, we ensure the underlying infrastructure can move data at the speeds those workloads demand." We can add that as a

after the list. Now Qualifications section:

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
• 5+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
• Experience as a mentor, tech lead or leading an engineering team

Preferred Qualifications

• Bachelor's degree in computer science or equivalent
But we used

which is not allowed? The instruction only says use

for section headings. It didn't forbid other headings, but to be safe we could avoid

and just use

or . However using

might be okay but better to stick to

only for sections; we can use

Basic Qualifications

then list. Thus:

Qualifications

Basic Qualifications

...

Preferred Qualifications

...

Now Benefits section: We have benefits list: 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. Also sign-on payments and RSUs mentioned under Pay? Actually sign-on payments and RSUs are part of compensation, could be in Pay. We'll create Benefits section with that list. Pay section: include salary ranges for two locations and mention sign-on payments and RSUs. Thus:

Pay

Base salary range:

• USA, CA, Cupertino: $193,300.00 - $261,500.00 USD annually
• USA, TX, Austin: $168,100.00 - $227,400.00 USD annually

Compensation package includes sign-on payments and restricted stock units (RSUs); final compensation based on experience, qualifications, and location.

Benefits:

Benefits

• 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
• Parental leave

We should not include Schedule. Now ensure we removed all boilerplate: removed EEO, LA County legal, inclusive culture, accommodation, etc. Check if any other legal bits: "Los Angeles County applicants: Job duties for this position include: work safely and cooperatively..." we removed. Now ensure we preserved all substantive info: The description, responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, pay, benefits. We might have missed the line "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Already in Pay. Check if any other info: "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; we could keep as part of Benefits but it's a reference; we could include as a

with link. But it's not essential; but we might keep as it's part of benefits info. However it's a link; we can include as

Learn more about our benefits at amazon.jobs/en/benefits

. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that link. It's not boilerplate; it's a reference