Systems Development Engineer, ADC2S

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to include sections only when there is real specific content. Let's extract content. The posting: - Description: Application deadline: Applications will be accepted on an ongoing basis (maybe minor metadata, can be folded into short p or drop). Probably we can include as a short paragraph. - Intro paragraphs: "Would you like to help implement innovative cloud computing solutions..." etc. That's prose. - "We are seeking a talented engineer skilled in the art of integration ..." etc. - "This position requires that the candidate selected must currently possess and maintain an active TS/SCI security clearance. The position further requires that, after start, the selected candidate obtain and maintain an active TS/SCI security clearance with polygraph or commensurate clearance for each government agency for which they perform AWS work." - "Key job responsibilities" then bullet list? Actually after that they have paragraphs: "You'll be part of a world-class team..." etc. Then "A day in the life" etc. Then sections: About The Team, Why AWS, AWS Infrastructure Services (AIS), Inclusive Team Culture, Work/Life Balance, Mentorship and Career Growth, Diverse Experiences. - Then Basic Qualifications list. - Preferred Qualifications list. - Then EEO statement etc (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 ... 401(k) matching, paid time off, and parental leave. Learn more about our benefits at ..." - Then location salary ranges: list of locations with same range. - Then Company - Amazon Development Center U.S., Inc. Job ID: ... (drop). We need to decide sections. Potential sections: - About the role (intro description). Could be a

summarizing role? The posting has introductory paragraphs describing role. Could put under

About the role

with paragraphs. - Responsibilities: The "Key job responsibilities" and following paragraphs about day in the life etc. Could be under Responsibilities. - Requirements: Could include security clearance requirement? Or maybe Qualifications. - Qualifications: Basic Qualifications and Preferred Qualifications. - Skills: maybe not separate; could combine with Qualifications. - Benefits: The paragraph about benefits (health insurance, 401k, PTO, parental leave). Also mention sign-on payments and RSUs. - Pay: The base salary range info. - Schedule: Not mentioned; no schedule info, so omit. We must not create sections with placeholder text. So if we include Pay, we need actual salary ranges. We have them. Benefits: we have specific benefits listed. We need to avoid duplication. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

Application deadline: Applications will be accepted on an ongoing basis.

About the role

Would you like to help implement innovative cloud computing solutions and solve the world's most complex technical problems? Do you have a deep passion and desire to engineer and operate the world's largest cloud computing infrastructure to provide a better world for future generations? Amazon Web Services is seeking a top industry technical expert to grow our team dedicated to expanding our Compute services to government customers. We are seeking a talented engineer skilled in the art of integration who understands the Agile mindset and DevOps philosophies, yet is not constrained by how “things are usually done" and is willing to decompose and reinvent systems, processes, and tools. We're looking for a technical expert for one of the largest compute services on the planet; if you possess that rare mix of depth in Development, Operations, Networking, and Systems Engineering then we are waiting for your application.

Responsibilities

You'll be part of a world-class team in a fast-paced environment that has the entrepreneurial feel of a start-up. This is an opportunity to operate and engineer systems on a massive scale, and to gain top-notch experience in cloud computing. You'll be surrounded by people who are smart, passionate about cloud computing, and believe that world class service is critical to customer success. You will design and build the operational scalability that sustains the platform's insane growth. You will be able to measure your success by its visible impact on the efficiency and effectiveness of government services for our nation.

A day in the life: Amazon has a fast-paced environment where we “Work Hard, Have Fun, Make History.” On a “typical” day engineers might deep dive to root cause a customer issue, investigate why a metric is trending the wrong way, consult with the top engineers at Amazon, or discuss radical new approaches to automate operational issues.

Requirements

This position requires that the candidate selected must currently possess and maintain an active TS/SCI security clearance. The position further requires that, after start, the selected candidate obtain and maintain an active TS/SCI security clearance with polygraph or commensurate clearance for each government agency for which they perform AWS work.

Qualifications

Basic Qualifications

• Bachelor's degree, or CSSLP (Certified Secure Software Lifecycle Professional)
• 2+ years of non-internship professional software development experience
• 1+ years of designing or architecting (design patterns, reliability and scaling) of new and existing systems experience
• 4+ years of administrative experience in networking, storage systems, operating systems and hands-on systems engineering experience
• Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
• Current, active US Government Security Clearance of Top Secret with SCI eligibility or above

Preferred Qualifications

• Experience in automating, deploying, and supporting large-scale infrastructure
• Experience working in an Agile environment using the Scrum methodology

We could also include a Skills section but maybe not needed; we have qualifications. But the instruction says use headings for sections like Skills, Benefits, Pay, Schedule. We have Benefits and Pay. We need to include Benefits section if there is real specific content. Yes.

Benefits

Amazon 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. Additionally, the package includes sign-on payments and restricted stock units (RSUs).

Pay section:

Pay

The base salary range for this position is:

• USA, CO, Denver: $129,200.00 - $174,800.00 USD annually
• USA, MD, Annapolis Junction: $129,200.00 - $174,800.00 USD annually
• USA, VA, Arlington: $129,200.00 - $174,800.00 USD annually
• USA, VA, Herndon: $129,200.00 - $174,800.00 USD annually
• USA, WA, Bellevue: $129,200.00 - $174,800.00 USD annually
• USA, WA, Seattle: $129,200.00 - $174,800.00 USD annually

We could also mention that final compensation based on experience, qualifications, location. We should not include Schedule as no info. We need to ensure we didn't include boilerplate like EEO, accommodation, etc. We removed. Check for duplicated lines: we didn't repeat. We need to ensure we didn't include Job ID or company name? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We dropped Job ID. Company name maybe not needed; we can drop as minor metadata. The posting includes "Company - Amazon Development Center U.S., Inc." Could be considered minor metadata; we can drop. We kept location salary ranges. We need to ensure we didn't include any "Learn more about our benefits at ..." link; we could drop as it's a reference; but we could keep as part of benefits? Might be considered boilerplate? It's a link; maybe we can drop. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not exactly those; but it's a reference. Safer to drop. We kept benefits description. Now ensure we used

for section headings only. We used

for subheadings inside Qualifications; is that allowed? The instruction only says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but to be safe we could avoid

and instead use

with bold? But we need to preserve structure. Could we instead make Basic Qualifications and Preferred Qualifications as

sections? But then we would have many sections; they said prefer a few substantive sections over many thin ones. So maybe keep Qualifications as one section with two subsections using

or . Using

is okay as it's not a section heading per the list; but it's still a heading. Might be acceptable. However to be safe, we could use

Basic Qualifications:

then

. Similarly for Preferred. Let's do that. Thus:

Qualifications

Basic Qualifications:

...

Preferred Qualifications:

...
Now ensure we didn't miss any substantive info: The "About The Team" sections like Why AWS, AWS Infrastructure Services, Inclusive Team Culture, Work/Life Balance, Mentorship and Career Growth, Diverse Experiences. Those are substantive but could be considered part of "About the role" or maybe we could include a section "About the Team". The instruction says include a section ONLY when the posting has real, specific content for it. We have that content. Could we create a section "About the Team"? Not in the list of allowed headings but we could still use

for any section heading; the list is examples, not exclusive. So we could add

About the Team

and include those paragraphs. However they said prefer a few substantive sections over many thin ones. Adding another section may increase count. But we already have many sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six. Adding About the Team would be seven. Might be okay but they said prefer few over many. However the content about team is substantial; maybe we can incorporate into About the role or Responsibilities? The "About The Team