Systems Development Engineer I
for sections 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. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Key info:
- Description: Application deadline: ongoing basis (maybe not needed). Not a section.
- Opening paragraphs: talk about designing cloud solutions, etc. Could be "About the role" or maybe "Overview". We'll treat as "About the role".
- Responsibilities: "Key job responsibilities" section: bullet list? It says: 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.
Also earlier: "A day in the life" maybe not needed but could be part of responsibilities? Could be separate but we can include as part of responsibilities.
But we need to use - for any list of duties/requirements/benefits. The responsibilities are prose, not a list. Could embed as
. However we might break into bullet list? The instruction: Use
- for any list of duties/requirements/benefits. If not a list, use
. So we will keep as
.
- Requirements: Basic Qualifications list: Associate's degree or above, or CND or GSEC; Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby; 1+ years of working in a Linux/Unix environment; Experience with automating and simplifying team development, test, and operations processes; Current, active US Government Security Clearance of TS/SCI with Polygraph.
These are bullet-like but not explicitly list. Could format as
- .
- Preferred Qualifications: list of items: 3+ years programming..., 3+ years cloud computing technologies, 3+ years Linux/Unix systems, 3+ years multithreaded, distributed development, Working knowledge of TCP/IP networking..., Working knowledge of configuration management systems...
These also can be list.
- Skills: maybe combine qualifications? But we have separate sections for Requirements and Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
We have Basic Qualifications (maybe Requirements) and Preferred Qualifications (maybe Qualifications). Skills could be extracted from qualifications? But we could also put technical skills under Skills. However we must not invent sections lacking content. We have content for Requirements (basic qualifications) and Qualifications (preferred). Skills maybe not explicitly separate; we could omit Skills section if no explicit skills list beyond qualifications. But we have some skill-like items: programming languages, Linux/Unix, automation, security clearance, TCP/IP, config management. Those could go under Skills. However we already have them in qualifications. To avoid duplication, we could treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as empty -> omit.
Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. So we have benefits content.
Pay: The posting includes salary ranges for multiple locations: "USA, CO, Denver - 99,100.00 - 160,000.00 USD annually" etc. So we have pay info.
Schedule: Not mentioned. No schedule info (like full-time, part-time). So omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must not repeat job title. Not include Job ID etc.
We must remove boilerplate: EEO, accommodation link, etc. Also remove "Application deadline: Applications will be accepted on an ongoing basis" maybe not needed but could be part of About the role? It's metadata; we could drop as per instruction: fold minor metadata into a short
or drop it. Probably drop.
We need to include all substantive info: The paragraphs about AWS, mission, etc. Should be included in About the role.
Let's extract About the role content: The initial paragraphs up to "Key job responsibilities". Let's capture:
"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 "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." This is a requirement (security clearance). Could be part of Requirements.
Then "Key job responsibilities 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 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." This could be part of Responsibilities or separate but we can include in Responsibilities as prose.
Then "Why AWS ..." etc. That's more about company; could be part of About the role or separate but we can include in About the role.
Then "Inclusive Team Culture", "Work/Life Balance", "Mentorship and Career Growth", "Diverse Experiences". These are company culture; could be part of About the role or maybe separate but we can include in About the role as they are substantive.
We must not include boilerplate like EEO etc.
Now Benefits: we have paragraph about benefits.
Pay: we have multiple location salary lines.
We need to output HTML fragment only.
Let's craft:
About the role
... (all about role paragraphs)
Responsibilities
... (key job responsibilities + day in the life)
Requirements
- Associate's degree or above, or CND (Certified Network Defender) or GSEC (GIAC Security Essentials)
- Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
- 1+ years of working in a Linux/Unix environment
- Experience with automating and simplifying team development, test, and operations processes
- Current, active US Government Security Clearance of TS/SCI with Polygraph
Qualifications
- 3+ years of programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
- 3+ years of cloud computing technologies experience
- 3+ years of Linux/Unix systems experience
- 3+ years of multithreaded, distributed development experience
- Working knowledge of TCP/IP networking and core web technologies, such as DNS, HTTP, TLS/SSL certificates, and session and cookie handling
- Working knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems
Benefits
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. The package includes sign-on payments and restricted stock units (RSUs).
Pay
USA, CO, Denver - 99,100.00 - 160,000.00 USD annually
USA, MD, Annapolis Junction - 99,100.00 - 160,000.00 USD annually
USA, VA, Arlington - 99,100.00 - 160,000.00 USD annually
USA, VA, Herndon - 99,100.00 - 160,000.00 USD annually
USA, WA, Bellevue - 99,100.00 - 160,000.00 USD annually
USA, WA, Seattle - 99,100.00 - 160,000.00 USD annually
We need to ensure we didn't include any boilerplate like EEO, accommodation, etc. Also we
. However we might break into bullet list? The instruction: Use
- for any list of duties/requirements/benefits. If not a list, use
. So we will keep as
. - Requirements: Basic Qualifications list: Associate's degree or above, or CND or GSEC; Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby; 1+ years of working in a Linux/Unix environment; Experience with automating and simplifying team development, test, and operations processes; Current, active US Government Security Clearance of TS/SCI with Polygraph. These are bullet-like but not explicitly list. Could format as
- .
- Preferred Qualifications: list of items: 3+ years programming..., 3+ years cloud computing technologies, 3+ years Linux/Unix systems, 3+ years multithreaded, distributed development, Working knowledge of TCP/IP networking..., Working knowledge of configuration management systems...
These also can be list.
- Skills: maybe combine qualifications? But we have separate sections for Requirements and Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
We have Basic Qualifications (maybe Requirements) and Preferred Qualifications (maybe Qualifications). Skills could be extracted from qualifications? But we could also put technical skills under Skills. However we must not invent sections lacking content. We have content for Requirements (basic qualifications) and Qualifications (preferred). Skills maybe not explicitly separate; we could omit Skills section if no explicit skills list beyond qualifications. But we have some skill-like items: programming languages, Linux/Unix, automation, security clearance, TCP/IP, config management. Those could go under Skills. However we already have them in qualifications. To avoid duplication, we could treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as empty -> omit.
Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. So we have benefits content.
Pay: The posting includes salary ranges for multiple locations: "USA, CO, Denver - 99,100.00 - 160,000.00 USD annually" etc. So we have pay info.
Schedule: Not mentioned. No schedule info (like full-time, part-time). So omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must not repeat job title. Not include Job ID etc.
We must remove boilerplate: EEO, accommodation link, etc. Also remove "Application deadline: Applications will be accepted on an ongoing basis" maybe not needed but could be part of About the role? It's metadata; we could drop as per instruction: fold minor metadata into a short
or drop it. Probably drop. We need to include all substantive info: The paragraphs about AWS, mission, etc. Should be included in About the role. Let's extract About the role content: The initial paragraphs up to "Key job responsibilities". Let's capture: "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 "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." This is a requirement (security clearance). Could be part of Requirements. Then "Key job responsibilities 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 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." This could be part of Responsibilities or separate but we can include in Responsibilities as prose. Then "Why AWS ..." etc. That's more about company; could be part of About the role or separate but we can include in About the role. Then "Inclusive Team Culture", "Work/Life Balance", "Mentorship and Career Growth", "Diverse Experiences". These are company culture; could be part of About the role or maybe separate but we can include in About the role as they are substantive. We must not include boilerplate like EEO etc. Now Benefits: we have paragraph about benefits. Pay: we have multiple location salary lines. We need to output HTML fragment only. Let's craft:
About the role
... (all about role paragraphs)
Responsibilities
... (key job responsibilities + day in the life)
Requirements
- Associate's degree or above, or CND (Certified Network Defender) or GSEC (GIAC Security Essentials)
- Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
- 1+ years of working in a Linux/Unix environment
- Experience with automating and simplifying team development, test, and operations processes
- Current, active US Government Security Clearance of TS/SCI with Polygraph
Qualifications
- 3+ years of programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
- 3+ years of cloud computing technologies experience
- 3+ years of Linux/Unix systems experience
- 3+ years of multithreaded, distributed development experience
- Working knowledge of TCP/IP networking and core web technologies, such as DNS, HTTP, TLS/SSL certificates, and session and cookie handling
- Working knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems
Benefits
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. The package includes sign-on payments and restricted stock units (RSUs).
Pay
USA, CO, Denver - 99,100.00 - 160,000.00 USD annually
We need to ensure we didn't include any boilerplate like EEO, accommodation, etc. Also we
USA, MD, Annapolis Junction - 99,100.00 - 160,000.00 USD annually
USA, VA, Arlington - 99,100.00 - 160,000.00 USD annually
USA, VA, Herndon - 99,100.00 - 160,000.00 USD annually
USA, WA, Bellevue - 99,100.00 - 160,000.00 USD annually
USA, WA, Seattle - 99,100.00 - 160,000.00 USD annually
- .
- Preferred Qualifications: list of items: 3+ years programming..., 3+ years cloud computing technologies, 3+ years Linux/Unix systems, 3+ years multithreaded, distributed development, Working knowledge of TCP/IP networking..., Working knowledge of configuration management systems...
These also can be list.
- Skills: maybe combine qualifications? But we have separate sections for Requirements and Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
We have Basic Qualifications (maybe Requirements) and Preferred Qualifications (maybe Qualifications). Skills could be extracted from qualifications? But we could also put technical skills under Skills. However we must not invent sections lacking content. We have content for Requirements (basic qualifications) and Qualifications (preferred). Skills maybe not explicitly separate; we could omit Skills section if no explicit skills list beyond qualifications. But we have some skill-like items: programming languages, Linux/Unix, automation, security clearance, TCP/IP, config management. Those could go under Skills. However we already have them in qualifications. To avoid duplication, we could treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as empty -> omit.
Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. So we have benefits content.
Pay: The posting includes salary ranges for multiple locations: "USA, CO, Denver - 99,100.00 - 160,000.00 USD annually" etc. So we have pay info.
Schedule: Not mentioned. No schedule info (like full-time, part-time). So omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must not repeat job title. Not include Job ID etc.
We must remove boilerplate: EEO, accommodation link, etc. Also remove "Application deadline: Applications will be accepted on an ongoing basis" maybe not needed but could be part of About the role? It's metadata; we could drop as per instruction: fold minor metadata into a short