Software Dev Engineer II, Technical Content Experience (TCX) Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, application instructions, etc. We need to parse the description. Key parts: Description paragraph: "Do you want to own the latest technology, solve new problems, and have the ability to see the impact of your successes? Amazon is growing, and we need SDEs who move fast, are capable of breaking down and solving complex problems, and have a strong will to get things done. SDEs at Amazon work on real world problems on a global scale, own their systems end to end and influence the direction of our technology that impacts hundreds of millions customers around the world. In this role, you will own solutions from design and execution through deployment and support, using the best of available tools, including Lambda, DynamoDB, and AI/ML services. You will be responsible for delivering high quality code and optimizing existing systems. You should be invested in helping our customers, understanding that it is important to build practical solutions that are scalable and easy to maintain. Most importantly, you should be comfortable working in a fast-paced environment where delivery of new products and features is very rapid. The right candidate will possess proven software engineering skills, with experience creating and launching large distributed systems with the help of a team. You are expected to be versatile, able to thrive in a dynamic, entrepreneurial environment and eager to mentor junior engineers. You are comfortable managing competing priorities. Maturity and impeccable judgment are essential. You are data-driven and analytical. You can clearly & effectively communicate with the team on work and technical design (written as well as verbally)." That's about the role. Then "Key job responsibilities" list: - Design and own technical software AI-powered components that are scalable, performant and easy to maintain. - Provide guidance on technology choices. - Drive adoption of engineering best practices. - Hands on coding. - Work backwards from customer needs to design technical solutions. - Solve ambiguous problems - Invent and simplify existing systems - Technical mentoring of team members Then "A day in the life" paragraph: "You will provide mentorship and technical direction to the team, perform design and code reviews, write exemplary code with unit and integration tests, contribute to technical roadmap discussions, perform on call activities (performance enhancements, bug fixes, correction of errors), refactor and deprecate systems, communicate with Product, senior leadership and other stakeholders. Work backwards from the customer on large and ambiguous problems. Invent and Simplify designs, breakdown large problems into smaller ones and incrementally deliver highest quality code along with the team." Then "About The Team" paragraph: "TCX Engineering builds customer-facing experiences to deliver technical documentation for AWS. We innovate, research, experiment and collaborate with product managers to understand our customers’ needs. We partner with software developers to learn the inner workings of AWS services so that we can influence design and the customer experience. We are a catalyst in the successful adoption and implementation of AWS services." Then "Basic Qualifications" bullet 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 - 3+ years of programming with at least one software programming language experience Then "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 - Experience with Machine Learning and Large Language Model fundamentals, including architecture, training/inference lifecycles, and optimization of model execution Then benefits and pay: - "Amazon is an equal opportunity employer..." (boilerplate, remove) - "If you have a disability..." (remove) - "If the country/region you’re applying in isn’t listed..." (remove) - "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." - Then location and salary: "USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually" - Company: "Amazon Development Center U.S., Inc." - Job ID: "A10543901" (drop) We need sections: About the role (maybe from description), Responsibilities (key job responsibilities + A day in the life?), Requirements (Basic Qualifications?), Qualifications (Preferred Qualifications?), Skills (maybe combine?), Benefits, Pay, Schedule. We need to decide what to put where. The instruction: Use

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 (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We need to 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. Thus we need to include Benefits, Pay, Schedule only if present. Benefits: yes, they list health insurance etc. Pay: yes, they give salary range. Schedule: not mentioned. So we should not include Schedule section. We need to decide what goes into each section. About the role: likely the initial description paragraph(s) that describe role overview. Could combine description and "About The Team"? The "About The Team" is separate but could be part of About the role or maybe separate. But we have limited headings; we could put About the role includes the initial description and maybe the team description. Or we could treat About The Team as part of About the role. Responsibilities: list from "Key job responsibilities" and "A day in the life". Could combine. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe we could extract skills from responsibilities? But we might not need a Skills section if no explicit skills list. However we could include skills like "Lambda, DynamoDB, AI/ML services", "design patterns", etc. But the instruction says prefer a few substantive sections over many thin ones. If we don't have explicit skills list, we could omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we need to include "Skills"? Not required. Now we need to format. We'll output HTML fragment like:

  About the role

  ... prose ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  USA, WA, Seattle - $143,700.00 - $194,400.00 USD annually

  We need to ensure we preserve all substantive information. Let's extract prose for About the role: combine the initial description paragraph and maybe the "About The Team" paragraph. Initial description: "Do you want to own the latest technology, solve new problems, and have the ability to see the impact of your successes? Amazon is growing, and we need SDEs who move fast, are capable of breaking down and solving complex problems, and have a strong will to get things done. SDEs at Amazon work on real world problems on a global scale, own their systems end to end and influence the direction of our technology that impacts hundreds of millions customers around the world. In this role, you will own solutions from design and execution through deployment and support, using the best of available tools, including Lambda, DynamoDB, and AI/ML services. You will be responsible for delivering high quality code and optimizing existing systems. You should be invested in helping our customers, understanding that it is important to build practical solutions that are scalable and easy to maintain. Most importantly, you should be comfortable working in a fast-paced environment where delivery of new products and features is very rapid. The right candidate will possess proven software engineering skills, with experience creating and launching large distributed systems with the help of a team. You are expected to be versatile, able to thrive in a dynamic, entrepreneurial environment and eager to mentor junior engineers. You are comfortable managing competing priorities. Maturity and impeccable judgment are essential. You are data-driven and analytical. You can clearly & effectively communicate with the team on work and technical design (written as well as verbally)." Then About The Team: "TCX Engineering builds customer-facing experiences to deliver technical documentation for AWS. We innovate, research, experiment and collaborate with product managers to understand our customers’ needs. We partner with software developers to learn the inner workings of AWS services so that we can influence design and the customer experience. We are a catalyst in the successful adoption and implementation of AWS services." We can combine them into a single paragraph or two paragraphs. Use

  for prose. Could be two

  elements under About the role. Now Responsibilities: list items from Key job responsibilities and A day in the life. Key job responsibilities list: - Design and own technical software AI-powered components that are scalable, performant and easy to maintain. - Provide guidance on technology choices. - Drive adoption of engineering best practices. - Hands on coding. - Work backwards from customer needs to design technical solutions. - Solve ambiguous problems - Invent and simplify existing systems - Technical mentoring of team members A day in the life paragraph includes many items: "You will provide mentorship and technical direction to the team, perform design and code reviews, write exemplary code with unit and integration tests, contribute to technical roadmap discussions, perform on call activities (performance enhancements, bug fixes, correction of errors), refactor and deprecate systems, communicate with Product, senior leadership and other stakeholders. Work backwards from the customer on large and ambiguous problems. Invent and Simplify designs, breakdown large problems into smaller ones and incrementally deliver highest quality code along with the team." We need to avoid duplication. Some items overlap: mentorship, work backwards, invent and simplify, etc. We should combine unique items. Let's list unique responsibilities: - Design and own technical software AI-powered components that are scalable, performant and easy to maintain. - Provide guidance on technology choices. - Drive adoption of engineering best practices. - Hands on coding. - Work backwards from customer needs to design technical solutions. - Solve ambiguous problems. - Invent and simplify existing systems. - Technical mentoring of team members. - Provide mentorship and technical direction to the team (similar to technical mentoring; maybe combine). - Perform design and code reviews. - Write exemplary code with unit and integration tests. - Contribute to technical roadmap discussions. - Perform on-call activities (performance enhancements, bug fixes, correction of errors). - Refactor and de