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 that have real specific content. Need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Remove application instructions. Also remove duplicated lines. Need to include Pay and Benefits if present. The posting includes salary ranges for multiple locations, and benefits description. So we can have a Pay section with salary ranges. Benefits section with description of benefits. Also maybe a Schedule? Not mentioned. So omit Schedule. We need sections: About the role (maybe from description intro). Responsibilities (Key job responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills maybe not separate; could combine with Requirements? But we can include Skills if there is explicit skill list. There's mention of programming languages etc. Could put under Skills. But we can also put under Requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which to include based on content. We have: About the role: The introductory paragraphs about helping implement innovative cloud computing solutions, etc. That's about the role. Responsibilities: "Key job responsibilities" bullet list. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe list of technical skills: programming languages, DevOps, Agile, etc. Could extract from responsibilities and qualifications. But we might combine into Requirements and Qualifications. Safer to include Skills if we can extract specific skill statements: "Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby", "Experience in automating, deploying, and supporting large-scale infrastructure", "Experience working in an Agile environment using the Scrum methodology", "understands the Agile mindset and DevOps philosophies". We'll put those under Skills. Benefits: description of benefits. Pay: salary ranges. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive info: include location list? The salary ranges are per location; we should keep them. Also mention that position requires TS/SCI clearance with polygraph etc. That's a requirement; include in Requirements or maybe a separate section? Could be under Requirements (Basic Qualifications includes "Current, active US Government Security Clearance of Top Secret with SCI eligibility or above"). Also mention that after start must obtain and maintain TS/SCI with polygraph or commensurate clearance for each government agency. That's also a requirement. We need to remove boilerplate: EEO statement, accommodation link, etc. Also remove "Application deadline: Applications will be accepted on an ongoing basis". That's maybe minor metadata; we can fold into a short p or drop. Probably drop. Also remove "Company - Amazon Development Center U.S., Inc." maybe minor metadata; could drop or include in a p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short p with location and company? But location is relevant to pay. We'll keep location within Pay section. We must not invent or summarize away detail. Keep all specifics. Let's craft HTML. Structure:

About the role

... paragraphs ...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

... benefits description ...

Pay

... salary ranges per location ...

We need to ensure we don't include filler like "commensurate with experience". The posting includes "commensurate clearance for each government agency". That's specific, not filler. Keep. Now extract content. About the role: The first few paragraphs up to "Key job responsibilities". Let's capture: "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. 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." That's about the role. Responsibilities: After "Key job responsibilities" there is a paragraph: "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." Then there is "About The Team" etc. That's more about team/culture, not responsibilities. Might be considered part of About the role? But we already have About the role. Could treat "About The Team" as part of About the role or maybe separate but not required. We'll keep responsibilities as the bullet list? Actually there are no bullet list; it's prose. We'll put that as

under Responsibilities. But we also have "About The Team" sections: Why AWS, AWS Infrastructure Services (AIS), Inclusive Team Culture, Work/Life Balance, Mentorship and Career Growth, Diverse Experiences. Those are more about team/culture; could be considered part of About the role or maybe we could create a section "About the team". However instruction only lists certain headings; we could add About the role only. But we could also include "About the team" under About the role? Might be okay to include as part of About the role prose. But we need to preserve all substantive info; we can include them as

under About the role after the initial paragraphs. That would keep all info. Thus About the role will contain multiple paragraphs: the initial motivational paragraphs, then the "About The Team" subsections. We need to avoid duplication: there is repeated lines like "Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform." etc. We'll keep. Now Responsibilities: we have the paragraph after Key job responsibilities and before About The Team. Also the "A day in the life" paragraph. We'll combine. Now Requirements: Basic Qualifications list: - 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 Also mention after start must obtain and maintain TS/SCI with polygraph or commensurate clearance for each government agency. That's also a requirement; we can add as a bullet. Now Qualifications: Preferred Qualifications: - Experience in automating, deploying, and supporting large-scale infrastructure - Experience working in an Agile environment using the Scrum methodology Also maybe "Amazon is an equal opportunity employer" etc is boilerplate; remove. Skills: we can extract skill statements: understanding Agile mindset and DevOps philosophies, integration, decompose and reinvent systems, depth in Development, Operations, Networking, Systems Engineering, programming languages, automation, Agile/Scrum, large-scale infrastructure, etc. But to avoid duplication, we could just list the specific skill mentions not already covered in Requirements/Qualifications. However instruction says we can include Skills section if there is real specific content. We'll include a list of skills: "Integration expertise", "Agile mindset and DevOps philosophies", "Systems engineering (networking, storage, OS)", "Programming in C++, C#, Java, Python, Golang, PowerShell, Ruby", "Designing/architecting for reliability and scaling", "Automating, deploying, supporting large-scale infrastructure", "Agile/Scrum methodology", "TS/SCI clearance with polygraph". But some overlap with Requirements/Qualifications. Might be okay but could be considered redundant. Perhaps better to omit Skills section and rely on Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could skip Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: The paragraph after "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." We need to keep that. Also maybe the line about sign-on payments and RSUs is part of compensation, not benefits. Could be in Pay section. But we can keep in Benefits? The instruction: Benefits section for benefits. Sign-on payments and RSUs are compensation; maybe better in Pay. But we have Pay section for salary ranges. We could include sign-on payments and RSUs in Pay as well. However the Benefits paragraph includes health insurance etc. We'll keep Benefits as that paragraph minus the sign-on payments and RSUs? Actually the sentence: "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 ..." So we could split: Pay includes base salary range and sign-on payments/RSUs. Benefits includes health insurance etc. We'll do that. Thus Pay section: include base salary ranges per location, plus note about sign-on payments and RSUs. Now we need to format Pay: list each location with range. Could be a

with each location. Now we must not include boilerplate like "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; maybe we can keep as part of Benefits paragraph? It's not boilerplate? It