Software Development Engineer, RDS SQL Server

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. We need to parse the description. Let's extract sections: - About the role: The initial paragraphs describing excitement, solving challenges, etc. Could be "About the role" or maybe "Description". The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings are appropriate based on content. We have: - Description (intro) about solving challenges, RDS, etc. Could be "About the role". - "Key job responsibilities" then bullet list (Our Engineers Collaborate..., You'll Bring..., You'll Also Solve..., Design..., Build..., Research..., A day in the life...). That's responsibilities. - "About The Team" paragraph about team culture, mentorship. - "Diverse Experiences" statement encouraging apply. - "About AWS" description of AWS. - "Inclusive Team Culture", "Work/Life Balance", "Mentorship & Career Growth". These could be part of "About the team" or separate sections like "Team Culture", "Benefits"? But we have Benefits and Pay sections separate. - "Basic Qualifications" list. - "Preferred Qualifications" list. - Benefits: mention comprehensive benefits including health insurance etc. Also mention sign-on payments and RSUs. Also link to benefits page. So we have benefits content. - 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." Then "USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually". So we have pay range. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Skills: Not explicitly listed; maybe implied but not specific. We should not create Skills unless there is specific content. The posting mentions "deep analytical and engineering skills", "programming with at least one software programming language", "design or architecture", etc. That's more qualifications. Could be Skills but we have Qualifications sections. Probably we can skip Skills. - Requirements: Could be Basic Qualifications and Preferred Qualifications combined? The instruction says use headings like Requirements, Qualifications. We have Basic Qualifications and Preferred Qualifications. Could treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications (or vice versa). We need to decide. We have "Basic Qualifications" and "Preferred Qualifications". So we can map Basic Qualifications to "Requirements" heading, and Preferred Qualifications to "Qualifications" heading. Or we could have both under Qualifications. But instruction says we can use those headings. We'll produce:

About the role

with intro paragraphs.

Responsibilities

with list items from "Key job responsibilities" and "A day in the life".

Requirements

with Basic Qualifications list.

Qualifications

with Preferred Qualifications list.

Benefits

with benefits description.

Pay

with salary range and sign-on/RSU note. We should not include sections like About The Team, Diverse Experiences, About AWS, Inclusive Team Culture, Work/Life Balance, Mentorship & Career Growth unless we decide to incorporate them into About the role or maybe a separate section like "About the team". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About the team, but we could still include if we think it's substantive. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." So we might combine team/culture info into About the role or maybe a separate "About the team" section if we think it's substantive. However to keep few sections, we could incorporate team/culture into About the role. But we must preserve ALL substantive information. So we need to include the team description, diverse experiences, about AWS, inclusive culture, work/life balance, mentorship & career growth. If we omit a separate section, we must embed that info somewhere else, like in About the role or maybe a new section like "About the team". Since they gave examples but not exclusive, we could add an "About the team" heading. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should stick to those headings; but it's not strict. Safer to follow examples and not add extra headings beyond those. So we should fold team/culture info into About the role or maybe into Responsibilities? Probably About the role is appropriate to include role context, team, culture, etc. Thus About the role will contain the introductory paragraphs plus team description, diverse experiences, about AWS, inclusive culture, work/life balance, mentorship & career growth. That will be a lot but okay. We must not repeat job title. Not include Job ID. Remove boilerplate like EEO, accommodation link, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "For more information on RDS SQL Server, please visit: http://aws.amazon.com/rds/sqlserver". That's a link but maybe considered substantive? It's a reference; but it's not boilerplate; it's a link to more info. Might be considered substantive? It's a URL; but it's not essential to job description; but we could keep it as part of About the role? It's a reference for more info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that link. However it's not a heading; we can embed as a

with the URL. Also remove "10031" maybe a code? It appears after the link line: "10031". Probably a zip code? Actually it's after the link line: "http://aws.amazon.com/rds/sqlserver 10031". Might be a stray number; maybe it's a job code? Not sure. It could be a location code? It's ambiguous. Might be part of the posting but not clearly substantive. Safer to drop it if it's not clearly meaningful. It looks like maybe a placeholder. I'd drop it. Also remove "Key job responsibilities" heading; we will replace with

Responsibilities

. Also remove "About The Team", "Diverse Experiences", "About AWS", "Inclusive Team Culture", "Work/Life Balance", "Mentorship & Career Growth" headings; we will embed content. Also remove "Basic Qualifications" and "Preferred Qualifications" headings; we will replace with

Requirements

and

Qualifications

. Also remove "The base salary range for this position is listed below..." etc; we will put in Pay. Also remove "Company - Amazon Development Center U.S., Inc." maybe metadata; we can drop. Also remove "Job ID: A10452174". Drop. Also remove "USA, WA, Redmond - 143,700.00 - 194,400.00 USD annually" we will include in Pay. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." We'll embed link. Also remove "If you have a disability..." etc; that's EEO boilerplate; drop. Also remove "Amazon is an equal opportunity employer..." drop. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." drop. Also remove "For more information on RDS SQL Server, please visit: http://aws.amazon.com/rds/sqlserver" we keep as link. Now craft HTML. We need

• for any list of duties/requirements/benefits. We'll have:

  About the role

  ... paragraphs ...

  Then maybe a
  for responsibilities. But responsibilities include multiple bullet points: "Our Engineers Collaborate Across Diverse Teams, Projects, And Environments To Have a Firsthand Impact On Our Global Customer Base.", "You’ll Bring a Passion For Innovation, Data, Search, Analytics, And Distributed Systems.", "You’ll Also Solve challenging technical problems, often ones not solved before, at every layer of the stack.", "Design, implement, test, deploy and maintain innovative software solutions to transform service performance, durability, cost, and security.", "Build high-quality, highly available, always-on products.", "Research implementations that deliver the best possible experiences for customers.", Then "A day in the life" paragraph: "As You Design And Code Solutions To Help Our Team Drive Efficiencies In Software Architecture, You’ll Create Metrics, Implement Automation And Other Improvements, And Resolve The Root Cause Of Software Defects.", "You’ll Also Build high-impact solutions to deliver to our large customer base.", "Participate in design discussions, code review, and communicate with internal and external stakeholders.", "Work cross-functionally to help drive business decisions with your technical input.", "Work in a startup-like development environment, where you’re always working on the most important stuff." We can combine these into a
  • list. Now Requirements (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 We'll put as
    . Qualifications (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 We'll put as
    . Benefits: The posting says: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That is compensation but we put in Pay. Benefits section will include the health insurance etc. We'll put as
    • maybe each benefit as separate? Could be one
    • with the long description. But instruction: use
      • for any list of duties/requirements/benefits. So we can make each benefit as separate
      • . Let's parse: - 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 We could also include sign-on payments and RSUs under Pay not Benefits. We'll also include link to benefits page as maybe a

        after list. Pay: "The base salary range for this position is listed below. Your Amazon package will