Software Dev Engineer II, SCOT-FO, Shipment Optimization (ATROPS)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include section ONLY when posting has real specific content - never emit heading with filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless posting actually states them
9. Prefer few substantive sections over many thin ones
10. Output ONLY HTML fragment - no /, no markdown code fences
Let me analyze the job posting content:
- Description/About: "Have you ever ordered a product on Amazon..." - this is about the role/organization
- "What You'll Work On" - this is responsibilities
- "What We're Looking For" - this is requirements/qualifications
- "Basic Qualifications" - list of requirements
- "Preferred Qualifications" - list of preferred qualifications
- Pay information: "The base salary range for this position is listed below... USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
- Benefits information: "Amazon also offers comprehensive benefits including health insurance... Learn more about our benefits at..."
- Company: "Company - Amazon.com Services LLC"
- Job ID: "Job ID: A10583324" - should fold into short
or drop
I need to create sections only for content that exists. Let me map:
1. About the role / About the organization - from the first paragraph and SCOT description
2. Responsibilities - from "What You'll Work On"
3. Requirements / Qualifications - from "What We're Looking For", "Basic Qualifications", "Preferred Qualifications"
4. Pay - from salary range
5. Benefits - from benefits description
6. Maybe a small metadata paragraph for company and job ID
I should not create Schedule section as no schedule info.
Let me structure:
About the role
...
Responsibilities
- ...
Qualifications
Basic Qualifications
- ...
Preferred Qualifications
- ...
Pay
...
Benefits
...
Company: Amazon.com Services LLC | Job ID: A10583324
Wait, the rules say use for section headings. Should I use for sub-sections? The rules only mention for section headings. But "Basic Qualifications" and "Preferred Qualifications" are sub-sections under Qualifications. I could make them separate sections or use . The rules don't forbid . But to be safe, maybe make them separate sections: "Basic Qualifications" and "Preferred Qualifications". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Qualifications" as an example. So maybe I should have one "Qualifications" section with sub-lists. But the posting has distinct "Basic Qualifications" and "Preferred Qualifications". I'll make them separate sections for clarity.
Also, "What We're Looking For" is a list of skills/experience - that could be "Requirements" or "Skills". I'll include it as part of Qualifications or separate.
Let me parse the content carefully.
First paragraph: "Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot(opens in a new tab) Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door."
This is about the role/organization.
"What You'll Work On" with three bullet points:
- AI-Powered Network Automation – Build agentic AI systems...
- Route Optimization at Scale – Design and implement graph algorithms...
- Scalable Distributed Systems – Build highly available, low-latency services...
These are responsibilities.
"What We're Looking For" with bullet points:
- Strong foundations in data structures, algorithms, and system design
- Experience with or passion for: graph algorithms, optimization, AI/ML systems, or generative AI
- Ability to break down ambiguous, complex problems into elegant, shippable solutions
- Comfort operating in a fast-paced environment where you own your systems end-to-end
- Excellent communication skills and a track record of raising the engineering bar on your team
These are requirements/skills.
"Basic Qualifications" list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- Experience programming with at least one software programming language
"Preferred Qualifications" list:
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Then EEO boilerplate - 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. USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
Benefits: "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."
Company: "Company - Amazon.com Services LLC"
Job ID: "Job ID: A10583324"
Now, I need to output HTML fragment.
I'll create sections:
1. About the role
2. Responsibilities
3. Requirements (or Qualifications) - maybe combine "What We're Looking For" and "Basic Qualifications" and "Preferred Qualifications" under Qualifications with subsections.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Requirements and Qualifications as separate? The posting has "What We're Looking For" (skills/experience) and "Basic Qualifications" (formal requirements) and "Preferred Qualifications". I think "Qualifications" is appropriate heading for all.
I'll do:
About the role
...
Responsibilities
- ...
Qualifications
What we're looking for
- ...
Basic qualifications
- ...
Preferred qualifications
- ...
But the rules only mention for section headings. Using might be okay as subheadings. However, to strictly follow, maybe make each a separate ? But that would be many sections. The rules say "Prefer a few substantive sections over many thin ones." So grouping under Qualifications with subheadings is fine. I'll use for subheadings.
Alternatively, I could make "Requirements" for "What We're Looking For" and "Qualifications" for basic/preferred. But the example includes both "Requirements" and "Qualifications". I'll do:
Requirements
for "What We're Looking For"
Qualifications
for basic and preferred.
But "What We're Looking For" is more like skills/competencies. The example includes "Skills". Could be "Skills". I'll use "Requirements" for the list of what they're looking for, and "Qualifications" for formal qualifications.
Let's decide:
- About the role
- Responsibilities
- Requirements (from "What We're Looking For")
- Qualifications (Basic and Preferred)
- Pay
- Benefits
- Metadata paragraph
That seems good.
Now, write HTML.
Note: The video link "http://bit.ly/amazon-scot(opens in a new tab)" - should I include? It's part of description. I'll include as link.
Also, the salary range is specific: "USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually". Include that.
Benefits list is detailed.
Now, produce HTML.
I'll write:
About the role
Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door.
Responsibilities
- AI-Powered Network Automation – Build agentic AI systems that continuously monitor, optimize, and autonomously evolve one of the world's largest transportation networks. You'll work on systems that generate, validate, and deploy network configurations using large language models and advanced automation — moving toward a future where the network intelligently adapts itself.
- Route Optimization at Scale – Design and implement graph algorithms that find optimal routes across a massive, multi-modal transportation network — optimizing simultaneously for speed, cost, and environmental sustainability. You'll solve multi
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include section ONLY when posting has real specific content - never emit heading with filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the job posting content: - Description/About: "Have you ever ordered a product on Amazon..." - this is about the role/organization - "What You'll Work On" - this is responsibilities - "What We're Looking For" - this is requirements/qualifications - "Basic Qualifications" - list of requirements - "Preferred Qualifications" - list of preferred qualifications - Pay information: "The base salary range for this position is listed below... USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually" - Benefits information: "Amazon also offers comprehensive benefits including health insurance... Learn more about our benefits at..." - Company: "Company - Amazon.com Services LLC" - Job ID: "Job ID: A10583324" - should fold into short
or drop I need to create sections only for content that exists. Let me map: 1. About the role / About the organization - from the first paragraph and SCOT description 2. Responsibilities - from "What You'll Work On" 3. Requirements / Qualifications - from "What We're Looking For", "Basic Qualifications", "Preferred Qualifications" 4. Pay - from salary range 5. Benefits - from benefits description 6. Maybe a small metadata paragraph for company and job ID I should not create Schedule section as no schedule info. Let me structure:
About the role
...
Responsibilities
- ...
Qualifications
Basic Qualifications
- ...
Preferred Qualifications
- ...
Pay
...
Benefits
...
Company: Amazon.com Services LLC | Job ID: A10583324
Wait, the rules say use for section headings. Should I use for sub-sections? The rules only mention for section headings. But "Basic Qualifications" and "Preferred Qualifications" are sub-sections under Qualifications. I could make them separate sections or use . The rules don't forbid . But to be safe, maybe make them separate sections: "Basic Qualifications" and "Preferred Qualifications". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Qualifications" as an example. So maybe I should have one "Qualifications" section with sub-lists. But the posting has distinct "Basic Qualifications" and "Preferred Qualifications". I'll make them separate sections for clarity.
Also, "What We're Looking For" is a list of skills/experience - that could be "Requirements" or "Skills". I'll include it as part of Qualifications or separate.
Let me parse the content carefully.
First paragraph: "Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot(opens in a new tab) Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door."
This is about the role/organization.
"What You'll Work On" with three bullet points:
- AI-Powered Network Automation – Build agentic AI systems...
- Route Optimization at Scale – Design and implement graph algorithms...
- Scalable Distributed Systems – Build highly available, low-latency services...
These are responsibilities.
"What We're Looking For" with bullet points:
- Strong foundations in data structures, algorithms, and system design
- Experience with or passion for: graph algorithms, optimization, AI/ML systems, or generative AI
- Ability to break down ambiguous, complex problems into elegant, shippable solutions
- Comfort operating in a fast-paced environment where you own your systems end-to-end
- Excellent communication skills and a track record of raising the engineering bar on your team
These are requirements/skills.
"Basic Qualifications" list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- Experience programming with at least one software programming language
"Preferred Qualifications" list:
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Then EEO boilerplate - 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. USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
Benefits: "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."
Company: "Company - Amazon.com Services LLC"
Job ID: "Job ID: A10583324"
Now, I need to output HTML fragment.
I'll create sections:
1. About the role
2. Responsibilities
3. Requirements (or Qualifications) - maybe combine "What We're Looking For" and "Basic Qualifications" and "Preferred Qualifications" under Qualifications with subsections.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Requirements and Qualifications as separate? The posting has "What We're Looking For" (skills/experience) and "Basic Qualifications" (formal requirements) and "Preferred Qualifications". I think "Qualifications" is appropriate heading for all.
I'll do:
About the role
for section headings. But "Basic Qualifications" and "Preferred Qualifications" are sub-sections under Qualifications. I could make them separate sections or use . The rules don't forbid . But to be safe, maybe make them separate sections: "Basic Qualifications" and "Preferred Qualifications". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Qualifications" as an example. So maybe I should have one "Qualifications" section with sub-lists. But the posting has distinct "Basic Qualifications" and "Preferred Qualifications". I'll make them separate sections for clarity.
Also, "What We're Looking For" is a list of skills/experience - that could be "Requirements" or "Skills". I'll include it as part of Qualifications or separate.
Let me parse the content carefully.
First paragraph: "Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot(opens in a new tab) Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door."
This is about the role/organization.
"What You'll Work On" with three bullet points:
- AI-Powered Network Automation – Build agentic AI systems...
- Route Optimization at Scale – Design and implement graph algorithms...
- Scalable Distributed Systems – Build highly available, low-latency services...
These are responsibilities.
"What We're Looking For" with bullet points:
- Strong foundations in data structures, algorithms, and system design
- Experience with or passion for: graph algorithms, optimization, AI/ML systems, or generative AI
- Ability to break down ambiguous, complex problems into elegant, shippable solutions
- Comfort operating in a fast-paced environment where you own your systems end-to-end
- Excellent communication skills and a track record of raising the engineering bar on your team
These are requirements/skills.
"Basic Qualifications" list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- Experience programming with at least one software programming language
"Preferred Qualifications" list:
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Then EEO boilerplate - 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. USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
Benefits: "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."
Company: "Company - Amazon.com Services LLC"
Job ID: "Job ID: A10583324"
Now, I need to output HTML fragment.
I'll create sections:
1. About the role
2. Responsibilities
3. Requirements (or Qualifications) - maybe combine "What We're Looking For" and "Basic Qualifications" and "Preferred Qualifications" under Qualifications with subsections.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Requirements and Qualifications as separate? The posting has "What We're Looking For" (skills/experience) and "Basic Qualifications" (formal requirements) and "Preferred Qualifications". I think "Qualifications" is appropriate heading for all.
I'll do:
About the role
. The rules don't forbid . But to be safe, maybe make them separate sections: "Basic Qualifications" and "Preferred Qualifications". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Qualifications" as an example. So maybe I should have one "Qualifications" section with sub-lists. But the posting has distinct "Basic Qualifications" and "Preferred Qualifications". I'll make them separate sections for clarity.
Also, "What We're Looking For" is a list of skills/experience - that could be "Requirements" or "Skills". I'll include it as part of Qualifications or separate.
Let me parse the content carefully.
First paragraph: "Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot(opens in a new tab) Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door."
This is about the role/organization.
"What You'll Work On" with three bullet points:
- AI-Powered Network Automation – Build agentic AI systems...
- Route Optimization at Scale – Design and implement graph algorithms...
- Scalable Distributed Systems – Build highly available, low-latency services...
These are responsibilities.
"What We're Looking For" with bullet points:
- Strong foundations in data structures, algorithms, and system design
- Experience with or passion for: graph algorithms, optimization, AI/ML systems, or generative AI
- Ability to break down ambiguous, complex problems into elegant, shippable solutions
- Comfort operating in a fast-paced environment where you own your systems end-to-end
- Excellent communication skills and a track record of raising the engineering bar on your team
These are requirements/skills.
"Basic Qualifications" list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- Experience programming with at least one software programming language
"Preferred Qualifications" list:
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Then EEO boilerplate - 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. USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
Benefits: "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."
Company: "Company - Amazon.com Services LLC"
Job ID: "Job ID: A10583324"
Now, I need to output HTML fragment.
I'll create sections:
1. About the role
2. Responsibilities
3. Requirements (or Qualifications) - maybe combine "What We're Looking For" and "Basic Qualifications" and "Preferred Qualifications" under Qualifications with subsections.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Requirements and Qualifications as separate? The posting has "What We're Looking For" (skills/experience) and "Basic Qualifications" (formal requirements) and "Preferred Qualifications". I think "Qualifications" is appropriate heading for all.
I'll do:
About the role
sections: "Basic Qualifications" and "Preferred Qualifications". However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists "Qualifications" as an example. So maybe I should have one "Qualifications" section with sub-lists. But the posting has distinct "Basic Qualifications" and "Preferred Qualifications". I'll make them separate sections for clarity.
Also, "What We're Looking For" is a list of skills/experience - that could be "Requirements" or "Skills". I'll include it as part of Qualifications or separate.
Let me parse the content carefully.
First paragraph: "Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot(opens in a new tab) Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door."
This is about the role/organization.
"What You'll Work On" with three bullet points:
- AI-Powered Network Automation – Build agentic AI systems...
- Route Optimization at Scale – Design and implement graph algorithms...
- Scalable Distributed Systems – Build highly available, low-latency services...
These are responsibilities.
"What We're Looking For" with bullet points:
- Strong foundations in data structures, algorithms, and system design
- Experience with or passion for: graph algorithms, optimization, AI/ML systems, or generative AI
- Ability to break down ambiguous, complex problems into elegant, shippable solutions
- Comfort operating in a fast-paced environment where you own your systems end-to-end
- Excellent communication skills and a track record of raising the engineering bar on your team
These are requirements/skills.
"Basic Qualifications" list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- Experience programming with at least one software programming language
"Preferred Qualifications" list:
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Then EEO boilerplate - 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. USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
Benefits: "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."
Company: "Company - Amazon.com Services LLC"
Job ID: "Job ID: A10583324"
Now, I need to output HTML fragment.
I'll create sections:
1. About the role
2. Responsibilities
3. Requirements (or Qualifications) - maybe combine "What We're Looking For" and "Basic Qualifications" and "Preferred Qualifications" under Qualifications with subsections.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Requirements and Qualifications as separate? The posting has "What We're Looking For" (skills/experience) and "Basic Qualifications" (formal requirements) and "Preferred Qualifications". I think "Qualifications" is appropriate heading for all.
I'll do:
About the role
sections for clarity.
Also, "What We're Looking For" is a list of skills/experience - that could be "Requirements" or "Skills". I'll include it as part of Qualifications or separate.
Let me parse the content carefully.
First paragraph: "Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot(opens in a new tab) Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door."
This is about the role/organization.
"What You'll Work On" with three bullet points:
- AI-Powered Network Automation – Build agentic AI systems...
- Route Optimization at Scale – Design and implement graph algorithms...
- Scalable Distributed Systems – Build highly available, low-latency services...
These are responsibilities.
"What We're Looking For" with bullet points:
- Strong foundations in data structures, algorithms, and system design
- Experience with or passion for: graph algorithms, optimization, AI/ML systems, or generative AI
- Ability to break down ambiguous, complex problems into elegant, shippable solutions
- Comfort operating in a fast-paced environment where you own your systems end-to-end
- Excellent communication skills and a track record of raising the engineering bar on your team
These are requirements/skills.
"Basic Qualifications" list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- Experience programming with at least one software programming language
"Preferred Qualifications" list:
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Then EEO boilerplate - 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. USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually"
Benefits: "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."
Company: "Company - Amazon.com Services LLC"
Job ID: "Job ID: A10583324"
Now, I need to output HTML fragment.
I'll create sections:
1. About the role
2. Responsibilities
3. Requirements (or Qualifications) - maybe combine "What We're Looking For" and "Basic Qualifications" and "Preferred Qualifications" under Qualifications with subsections.
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can have Requirements and Qualifications as separate? The posting has "What We're Looking For" (skills/experience) and "Basic Qualifications" (formal requirements) and "Preferred Qualifications". I think "Qualifications" is appropriate heading for all.
I'll do:
About the role
About the role
...
Responsibilities
- ...
Qualifications
What we're looking for
- ...
Basic qualifications
- ...
Preferred qualifications
- ...
for section headings. Using might be okay as subheadings. However, to strictly follow, maybe make each a separate ? But that would be many sections. The rules say "Prefer a few substantive sections over many thin ones." So grouping under Qualifications with subheadings is fine. I'll use for subheadings.
Alternatively, I could make "Requirements" for "What We're Looking For" and "Qualifications" for basic/preferred. But the example includes both "Requirements" and "Qualifications". I'll do:
Requirements
for "What We're Looking For"
Qualifications
for basic and preferred.
But "What We're Looking For" is more like skills/competencies. The example includes "Skills". Could be "Skills". I'll use "Requirements" for the list of what they're looking for, and "Qualifications" for formal qualifications.
Let's decide:
- About the role
- Responsibilities
- Requirements (from "What We're Looking For")
- Qualifications (Basic and Preferred)
- Pay
- Benefits
- Metadata paragraph
That seems good.
Now, write HTML.
Note: The video link "http://bit.ly/amazon-scot(opens in a new tab)" - should I include? It's part of description. I'll include as link.
Also, the salary range is specific: "USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually". Include that.
Benefits list is detailed.
Now, produce HTML.
I'll write:
About the role
? But that would be many sections. The rules say "Prefer a few substantive sections over many thin ones." So grouping under Qualifications with subheadings is fine. I'll use for subheadings.
Alternatively, I could make "Requirements" for "What We're Looking For" and "Qualifications" for basic/preferred. But the example includes both "Requirements" and "Qualifications". I'll do:
Requirements
for "What We're Looking For"
Qualifications
for basic and preferred.
But "What We're Looking For" is more like skills/competencies. The example includes "Skills". Could be "Skills". I'll use "Requirements" for the list of what they're looking for, and "Qualifications" for formal qualifications.
Let's decide:
- About the role
- Responsibilities
- Requirements (from "What We're Looking For")
- Qualifications (Basic and Preferred)
- Pay
- Benefits
- Metadata paragraph
That seems good.
Now, write HTML.
Note: The video link "http://bit.ly/amazon-scot(opens in a new tab)" - should I include? It's part of description. I'll include as link.
Also, the salary range is specific: "USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually". Include that.
Benefits list is detailed.
Now, produce HTML.
I'll write:
About the role
Requirements
for "What We're Looking For"Qualifications
for basic and preferred. But "What We're Looking For" is more like skills/competencies. The example includes "Skills". Could be "Skills". I'll use "Requirements" for the list of what they're looking for, and "Qualifications" for formal qualifications. Let's decide: - About the role - Responsibilities - Requirements (from "What We're Looking For") - Qualifications (Basic and Preferred) - Pay - Benefits - Metadata paragraph That seems good. Now, write HTML. Note: The video link "http://bit.ly/amazon-scot(opens in a new tab)" - should I include? It's part of description. I'll include as link. Also, the salary range is specific: "USA, WA, Bellevue - 143,700.00 - 194,400.00 USD annually". Include that. Benefits list is detailed. Now, produce HTML. I'll write:About the role
Have you ever ordered a product on Amazon and wondered how it got to you so fast? What if you could build the AI-powered systems that make that happen — and make it faster, cheaper, and more sustainable? Watch this video to learn more about our organization, SCOT: http://bit.ly/amazon-scot Amazon's Supply Chain Optimization Technologies (SCOT) organization is responsible for the end-to-end systems that plan, optimize, and execute the movement of billions of packages across the world's most complex logistics network. We build real-time, intelligent, and fully automated systems that touch every aspect of the delivery experience — from the moment a customer clicks "Buy" to the package arriving at their door.
Responsibilities
- AI-Powered Network Automation – Build agentic AI systems that continuously monitor, optimize, and autonomously evolve one of the world's largest transportation networks. You'll work on systems that generate, validate, and deploy network configurations using large language models and advanced automation — moving toward a future where the network intelligently adapts itself.
- Route Optimization at Scale – Design and implement graph algorithms that find optimal routes across a massive, multi-modal transportation network — optimizing simultaneously for speed, cost, and environmental sustainability. You'll solve multi