Systems Development Engineer I

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, description: "Application deadline: Applications will be accepted on an ongoing basis" - that's metadata, can be short

maybe. Then a lot of prose about role, responsibilities, etc. We need to extract sections: - About the role: maybe the introductory paragraphs describing the role. - Responsibilities: "Key job responsibilities" bullet list. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe combine? But we can include Skills as part of qualifications? The instruction says use headings for sections like Skills if present. We have skills mentioned in responsibilities and qualifications. Could create a Skills section summarizing required skills? But we must not invent or summarize away detail; we must preserve all substantive info. So we can't create a Skills section that just repeats info; we could list skills under Requirements or Qualifications. Better to follow the posting: they have Basic Qualifications and Preferred Qualifications. So we can have Requirements (Basic Qualifications) and Qualifications (Preferred Qualifications). Also maybe a Skills section not needed. - Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave." Also mentions sign-on payments and RSUs. So we have benefits content. - Pay: The posting includes salary ranges for multiple locations: "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 lists ranges for several locations. So we have Pay info. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Also maybe a section "About the team" or "Work/Life Balance" etc. But we only use headings from list; we could include other headings if they match? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should only use those headings; we shouldn't add other headings like "Work/Life Balance". So we should only include those sections if content exists. Thus we need to produce:

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

Then maybe an

About the role

with prose summarizing the role description (but we must not invent or summarize away detail; we can keep the prose as is, but we need to avoid repeating the job title as heading. We can include the descriptive paragraphs that talk about the role, mission, etc. We need to preserve ALL substantive information; we cannot omit details. So we need to include all the prose that is not part of responsibilities, qualifications, benefits, pay, etc. That's a lot. We could wrap it in

tags. We must not repeat the job title as a heading. The job title is not given explicitly in the snippet; maybe it's implied but we don't have it. So fine. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement and accommodation link, also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instructions/boilerplate; we should remove. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe keep benefits content but not the link? The instruction: remove boilerplate, but benefits content is substantive; we can keep the description of benefits but maybe drop the link. It's okay to keep the link? It's not boilerplate? It's a link to benefits page; could be considered boilerplate but it's a reference. Safer to remove the link but keep the description. Also remove "Company - Amazon Development Center U.S., Inc. Job ID: A10563988" maybe minor metadata; fold into short

or drop it. We can drop it. Now structure:

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

About the role

[all the introductory prose about role, mission, etc.]

Responsibilities

• ... (list from "Key job responsibilities")
...

Requirements

• ... (Basic Qualifications)
...

Qualifications

• ... (Preferred Qualifications)
...

Benefits

[benefits description]

Pay

[salary ranges]

We must not include Schedule. Now we need to extract the exact prose. Let's copy the relevant sections. First, after the initial paragraph about application deadline, there is a block: "Would you like to design, develop, and 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 build a better world for future generations? This is an exciting opportunity to use the latest cloud computing technologies to help US government agencies implement innovative cloud computing solutions and solve technical problems. AWS established a specialized group of service teams responsible for the work we are doing with the US Intelligence Community. We are building some of the largest and most complex distributed systems in the world, and we need adaptable people to help us implement and operate them, and expand capabilities with the speed of relevance. You'd work with some of the best and brightest engineers in the industry, while also developing your skills and furthering your career within one of the most innovative and progressive technology companies anywhere. Amazon Web Services is seeking top industry technical experts to grow our team dedicated to expanding our Elastic Compute Cloud (EC2) 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 practitioner for one of the largest compute services on the planet; if you possess that rare mix of skills in Operations, Networking, and Systems Engineering, then we are waiting for your application. We are looking for smart, enthusiastic, and creative engineers with a solid background in solving hard problems that span the software development, systems engineering, and systems security disciplines. As a member of this team, you will be charged with identifying ways to improve the lives of our customers through improvements to tools, processes, and documentation. You will be a member of a team of highly motivated and talented systems developers and systems engineers improving the use of tools in both isolated AWS regions and in the AWS GovCloud regions." That seems like About the role. Then after that: "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 could be part of Requirements (Basic Qualifications) but it's also a requirement. However Basic Qualifications list includes "Current, active US Government Security Clearance of TS/SCI with Polygraph". So we can incorporate that into Requirements. Then "Key job responsibilities" heading appears. Then bullet list: "As a member of this team, you will be charged with identifying ways to improve the lives of our customers through improvements to tools, processes, and documentation, while working alongside talented systems developers and systems engineers across isolated AWS regions and the AWS GovCloud regions. You will also be learning site reliability engineering fundamentals: recognizing toil, the manual, repetitive work that produces no lasting improvement, contributing code and automation that removes it, and coming to understand your systems' normal performance envelope well enough to tune alarms that catch real problems." Then "A day in the life" heading repeated twice? Actually appears: "A day in the life 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." That seems like additional description but not responsibilities per se; could be part of About the role or maybe we could treat as part of About the role. But we already have About the role; we could include this as part of About the role as well. Then "Why AWS" etc. That's more about company; could be part of About the role or maybe we could ignore as boilerplate? It's substantive about AWS but not directly role. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep it. But where to put? Could be part of About the role as well, or we could create a separate section like "About AWS" but not in allowed headings. Since only allowed headings are those list, we should incorporate into About the role or maybe we could omit? The instruction says "Prefer a few substantive sections over many thin ones." So we can merge all descriptive prose into About the role. Thus About the role will include all paragraphs before Responsibilities, plus the "A day in the life", "Why AWS", "AWS Infrastructure Services", "Inclusive Team Culture", "Work/Life Balance", "Mentorship and Career Growth", "Diverse Experiences". All that is substantive about role/company. Then after that we have "Basic Qualifications" list. Then "Preferred Qualifications" list. Then EEO statement etc to remove. Then benefits paragraph: "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." Then salary ranges list. Then "Learn more about our benefits at https://amazon.jobs/en/benefits." (remove link maybe keep sentence? It's boilerplate; better to remove.) Then location list. Then company and job ID (drop). Thus we need to output HTML. We must ensure we don't include any heading with empty content. Now craft the HTML. We'll start with

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

Then

About the role

and a

containing all the descriptive prose. We need to be careful to not include duplicated lines. The text includes some repeated sentences like "As a member of this team, you will be charged with identifying ways to improve the lives of our customers through improvements to tools, processes, and documentation." appears both in the introductory paragraph and in responsibilities. We should keep both occurrences as they are in original; but we might be duplicating content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines are okay to keep? It says remove duplicated lines. Actually earlier: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. That means if the same sentence appears multiple times, we should keep only one instance. So we need to deduplicate. Thus we need to identify duplicated lines and keep only one. Duplicated line: "As a member of this team, you will