Software Development Engineer, AWS Transform Migrations
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to extract substantive content.
Let's parse the posting:
Description: "AWS Transform is building the next generation of Agentic AI services that autonomously migrate the world's largest enterprises to the cloud. With approximately 7/8 of all enterprise workloads still running on-premises, we are at the center of one of AWS's most significant growth opportunities. We are looking for a Software Development Engineer who is excited to build at the frontier of AI — an engineer who wants to design and ship the autonomous agents that reason about complex infrastructure, make intelligent decisions, and execute large-scale migrations with minimal human intervention. This is a rare opportunity to do hands-on engineering on an AI-native platform as it takes shape."
That's prose.
Key job responsibilities: bullet list (we need to extract each bullet). Let's list:
- Design, build, and own major components of our Agentic AI migration platform, where autonomous agents discover, plan, and execute data center migrations.
- Implement multi-agent capabilities that leverage foundation models, chain-of-thought reasoning, and tool-use patterns to solve concrete migration challenges.
- Contribute to AI-powered network transformation features, using generative models to analyze, replicate, and optimize enterprise network topologies.
- Collaborate closely with engineers and product partners within your team, contributing to design reviews and helping maintain architectural coherence across our agent frameworks.
- Improve the autonomy and accuracy of agentic orchestration for migration of servers, storage, networks, and applications through iterative development, testing, and measurement.
- Raise the bar on engineering quality through code reviews, operational excellence, and AI-native development practices; mentor junior engineers and interns, and contribute to a culture of rapid experimentation, spec-driven engineering, and high-velocity releases on Brownfield projects.
About The Team: includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more generic company info; we need to decide if they count as substantive content for sections. The instruction says remove boilerplate, duplicated lines, and application instructions. The "About The Team" sections are generic AWS culture statements; they might be considered boilerplate. However they are part of the posting but not specific to the role. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About The Team" might be considered boilerplate but not explicitly listed. However they are generic AWS marketing. Likely we should drop them as they are not specific to the role. The instruction: "Prefer a few substantive sections over many thin ones." So we might keep only About the role (description), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. Skills maybe not present; we could omit Skills section if no specific skills listed. There's mention of programming language experience, design/architecture, etc. Those are qualifications. Could treat them under Requirements and Qualifications.
Basic Qualifications:
- 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
- Experience programming with at least one software programming language
Preferred Qualifications:
- 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
Also there is EEO statement etc which we drop.
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."
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, MA, Boston - 143,700.00 - 194,400.00 USD annually"
Thus we have pay range.
Schedule: not present.
Thus output HTML with sections:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
We should not include Schedule.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the description text exactly as given? We can keep it as prose. Should we keep the exact sentences? Likely yes.
We need to ensure we don't include boilerplate like "Amazon is an equal opportunity employer..." etc. Also drop "About The Team" sections.
Also drop "If you have a disability..." etc.
Also drop "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe we can keep as part of benefits? It's a link; but we might keep it as part of benefits prose. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that sentence as part of benefits.
Similarly for pay: include the sentence about sign-on payments and RSUs, final compensation determination, and the range.
We need to format as HTML fragment only.
Let's craft.
About the role: combine the description paragraph(s). There's only one paragraph.
Responsibilities: list each bullet as - .
Requirements: basic qualifications list.
Qualifications: preferred qualifications list.
Benefits: list each benefit item? The benefits sentence includes a parenthetical list. Could break into
- 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
- parental leave
- Learn more about our benefits at https://amazon.jobs/en/benefits.
But we need to preserve all detail; we could keep as a single with the sentence. However instruction says use
- for any list of duties/requirements/benefits. Benefits is a list, so we should use
- . The sentence includes multiple items separated by commas; we could split them into separate
- for each distinct benefit. However the parenthetical list is part of health insurance; splitting might lose nuance. Safer to keep as one
- for health insurance with its details, then separate
- for 401(k) matching, paid time off, parental leave, and the learn more link.
Pay: we can put in
because it's not a list; but could also be
- . The instruction says use
- for any list of duties/requirements/benefits. Pay is not a list; we can use
.
Now ensure we don't include any filler like "commensurate with experience". Not present.
Now produce HTML.
Let's write:
About the role
AWS Transform is building the next generation of Agentic AI services that autonomously migrate the world's largest enterprises to the cloud. With approximately 7/8 of all enterprise workloads still running on-premises, we are at the center of one of AWS's most significant growth opportunities. We are looking for a Software Development Engineer who is excited to build at the frontier of AI — an engineer who wants to design and ship the autonomous agents that reason about complex infrastructure, make intelligent decisions, and execute large-scale migrations with minimal human intervention. This is a rare opportunity to do hands-on engineering on an AI-native platform as it takes shape.
Responsibilities
- Design, build, and own major components of our Agentic AI migration platform, where autonomous agents discover, plan, and execute data center migrations.
- Implement multi-agent capabilities that leverage foundation models, chain-of-thought reasoning, and tool-use patterns to solve concrete migration challenges.
- Contribute to AI-powered network transformation features, using generative models to analyze, replicate, and optimize enterprise network topologies.
- Collaborate closely with engineers and product partners within your team, contributing to design reviews and helping maintain architectural coherence across our agent frameworks.
- Improve the autonomy and accuracy of agentic orchestration for migration of servers, storage, networks, and applications through iterative development, testing, and measurement.
- Raise the bar on engineering quality through code reviews, operational excellence, and AI-native development practices; mentor junior engineers and interns, and contribute to a culture of rapid experimentation, spec-driven engineering, and high-velocity releases on Brownfield projects.
Requirements
- 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
- Experience programming with at least one software programming language
Qualifications
- 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
Benefits
- 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
- parental leave
- Learn more about our benefits at https://amazon.jobs/en/benefits
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to extract substantive content. Let's parse the posting: Description: "AWS Transform is building the next generation of Agentic AI services that autonomously migrate the world's largest enterprises to the cloud. With approximately 7/8 of all enterprise workloads still running on-premises, we are at the center of one of AWS's most significant growth opportunities. We are looking for a Software Development Engineer who is excited to build at the frontier of AI — an engineer who wants to design and ship the autonomous agents that reason about complex infrastructure, make intelligent decisions, and execute large-scale migrations with minimal human intervention. This is a rare opportunity to do hands-on engineering on an AI-native platform as it takes shape." That's prose. Key job responsibilities: bullet list (we need to extract each bullet). Let's list: - Design, build, and own major components of our Agentic AI migration platform, where autonomous agents discover, plan, and execute data center migrations. - Implement multi-agent capabilities that leverage foundation models, chain-of-thought reasoning, and tool-use patterns to solve concrete migration challenges. - Contribute to AI-powered network transformation features, using generative models to analyze, replicate, and optimize enterprise network topologies. - Collaborate closely with engineers and product partners within your team, contributing to design reviews and helping maintain architectural coherence across our agent frameworks. - Improve the autonomy and accuracy of agentic orchestration for migration of servers, storage, networks, and applications through iterative development, testing, and measurement. - Raise the bar on engineering quality through code reviews, operational excellence, and AI-native development practices; mentor junior engineers and interns, and contribute to a culture of rapid experimentation, spec-driven engineering, and high-velocity releases on Brownfield projects. About The Team: includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more generic company info; we need to decide if they count as substantive content for sections. The instruction says remove boilerplate, duplicated lines, and application instructions. The "About The Team" sections are generic AWS culture statements; they might be considered boilerplate. However they are part of the posting but not specific to the role. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About The Team" might be considered boilerplate but not explicitly listed. However they are generic AWS marketing. Likely we should drop them as they are not specific to the role. The instruction: "Prefer a few substantive sections over many thin ones." So we might keep only About the role (description), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. Skills maybe not present; we could omit Skills section if no specific skills listed. There's mention of programming language experience, design/architecture, etc. Those are qualifications. Could treat them under Requirements and Qualifications. Basic Qualifications: - 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 - Experience programming with at least one software programming language Preferred Qualifications: - 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 Also there is EEO statement etc which we drop. 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." 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, MA, Boston - 143,700.00 - 194,400.00 USD annually" Thus we have pay range. Schedule: not present. Thus output HTML with sections:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
We should not include Schedule. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the description text exactly as given? We can keep it as prose. Should we keep the exact sentences? Likely yes. We need to ensure we don't include boilerplate like "Amazon is an equal opportunity employer..." etc. Also drop "About The Team" sections. Also drop "If you have a disability..." etc. Also drop "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe we can keep as part of benefits? It's a link; but we might keep it as part of benefits prose. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that sentence as part of benefits. Similarly for pay: include the sentence about sign-on payments and RSUs, final compensation determination, and the range. We need to format as HTML fragment only. Let's craft. About the role: combine the description paragraph(s). There's only one paragraph. Responsibilities: list each bullet as- 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
- parental leave
- Learn more about our benefits at https://amazon.jobs/en/benefits.
with the sentence. However instruction says use
- for any list of duties/requirements/benefits. Benefits is a list, so we should use
- . The sentence includes multiple items separated by commas; we could split them into separate
- for each distinct benefit. However the parenthetical list is part of health insurance; splitting might lose nuance. Safer to keep as one
- for health insurance with its details, then separate
- for 401(k) matching, paid time off, parental leave, and the learn more link.
Pay: we can put in
because it's not a list; but could also be
- . The instruction says use
- for any list of duties/requirements/benefits. Pay is not a list; we can use
. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's write:
About the role
AWS Transform is building the next generation of Agentic AI services that autonomously migrate the world's largest enterprises to the cloud. With approximately 7/8 of all enterprise workloads still running on-premises, we are at the center of one of AWS's most significant growth opportunities. We are looking for a Software Development Engineer who is excited to build at the frontier of AI — an engineer who wants to design and ship the autonomous agents that reason about complex infrastructure, make intelligent decisions, and execute large-scale migrations with minimal human intervention. This is a rare opportunity to do hands-on engineering on an AI-native platform as it takes shape.
Responsibilities
- Design, build, and own major components of our Agentic AI migration platform, where autonomous agents discover, plan, and execute data center migrations.
- Implement multi-agent capabilities that leverage foundation models, chain-of-thought reasoning, and tool-use patterns to solve concrete migration challenges.
- Contribute to AI-powered network transformation features, using generative models to analyze, replicate, and optimize enterprise network topologies.
- Collaborate closely with engineers and product partners within your team, contributing to design reviews and helping maintain architectural coherence across our agent frameworks.
- Improve the autonomy and accuracy of agentic orchestration for migration of servers, storage, networks, and applications through iterative development, testing, and measurement.
- Raise the bar on engineering quality through code reviews, operational excellence, and AI-native development practices; mentor junior engineers and interns, and contribute to a culture of rapid experimentation, spec-driven engineering, and high-velocity releases on Brownfield projects.
Requirements
- 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
- Experience programming with at least one software programming language
Qualifications
- 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
Benefits
- 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
- parental leave
- Learn more about our benefits at https://amazon.jobs/en/benefits
- for any list of duties/requirements/benefits. Pay is not a list; we can use
- . The instruction says use