System Development Engineer, DBS Relational ADC
Amazon Web Services (AWS) · Arlington, VA · 2 wk ago
ConsultingFull-time
We need to produce semantic HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: base salary range listed: "USA, VA, Arlington - 129,200.00 - 174,800.00 USD annually". Also mentions sign-on payments and RSUs, comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave. So we have Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule.
We need sections: About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to parse content.
Let's extract:
Description paragraph: "The Amazon Web Services team is innovating new ways of building massively scalable distributed systems and delivering the next generation of cloud computing with AWS offerings like RDS and Aurora. In 2013, AWS launched 280 services, but in 2016 alone we released nearly 1000. We hold high standards for our computer systems and the services we deliver to our customers: our systems are highly secure, highly reliable, highly available, all while functioning at massive scale; our employees are smart, passionate about the cloud, driven to serve customers, and fun to work with. A successful engineer joining the team will do much more than write code and triage problems. They will work with Amazon's largest and most demanding customers to address specific needs across a full suite of services. They will dive deeply into technical issues and work diligently to improve the customer experience. The ideal candidate will... Be great fun to work with. Our company credo is "Work hard. Have fun. Make history". The right candidate will love what they do and instinctively know how to make work fun. Have strong Linux & Networking Fundamentals. The ideal candidate will have deep experience working with Linux, preferably in a large scale, distributed environment. You understand networking technology and how servers and networks inter-relate. You regularly take part in deep-dive troubleshooting and conduct technical post-mortem discussions to identify the root cause of complex issues. Love to code. Whether its building tools in Java or solving complex system problems in Python, the ideal candidate will love using technology to solve problems. You have a solid understanding of software development methodology and know how to use the right tool for the right job. Think Big. The ideal candidate will build and deploy solutions across thousands of devices. You will strive to improve and streamline processes to allow for work on a massive scale. 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."
Then "Key job responsibilities" list bullet points.
Then "A day in the life" description.
Then "About The Team" with subsections: Why AWS, AWS Infrastructure Services (AIS), Inclusive Team Culture, Work/Life Balance, Mentorship and Career Growth, Diverse Experiences.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then EEO etc.
Then salary and benefits.
We need to produce sections with content.
We need to decide what goes where.
"About the role": Could be the initial description paragraph (the overview). Could also include "A day in the life" maybe as part of responsibilities? But we have separate Responsibilities section.
"Responsibilities": Use the "Key job responsibilities" bullet list plus maybe "A day in the life" details.
"Requirements": Could be the security clearance requirement? Or maybe "Basic Qualifications" as Requirements? Usually Requirements = basic qualifications. Qualifications = preferred qualifications? But we have both sections. We'll follow typical: Requirements = Basic Qualifications. Qualifications = Preferred Qualifications.
"Skills": Could be specific skills like Linux, networking, programming languages, etc. Might be extracted from description and qualifications.
"Benefits": The benefits paragraph.
"Pay": Salary range and sign-on payments, RSUs.
We must not include filler like "commensurate with experience" etc. The security clearance requirement includes "with polygraph or commensurate clearance for each government agency". That includes "commensurate clearance". That's a phrase we might need to keep? It's part of the requirement; we cannot remove substantive info. The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That's about headings with filler text, not about content containing the word commensurate. It's okay to keep the phrase as part of content.
We must not include boilerplate like EEO, accommodation links, etc.
We must not include duplicated lines.
We need to output only HTML fragment.
Let's craft sections.
First, About the role: combine the initial description paragraph (maybe up to "Think Big." plus security clearance requirement?). Actually security clearance is a requirement, but could be part of About the role? Might be better to put in Requirements.
Let's decide:
About the role: The paragraph describing AWS team innovation, high standards, what engineer will do, etc. Up to "Think Big." maybe include the security clearance? I'd keep security clearance in Requirements.
Thus About the role: The first big paragraph (starting "The Amazon Web Services team is innovating...") up to "Think Big." plus maybe the sentence "This position requires that the candidate selected must currently possess and maintain an active TS/SCI security clearance." Actually that is a requirement. I'll move to Requirements.
Thus About the role content: The paragraph describing AWS team innovating, high standards, engineer will do much more than write code, work with customers, dive deep, ideal candidate will... etc. We'll include the bullet-like sentences about fun, Linux & networking, love to code, think big. We'll keep them as prose.
Responsibilities: Use the "Key job responsibilities" bullet list (the list after that heading). Also maybe include "A day in the life" details as prose.
Requirements: Basic Qualifications list plus security clearance requirement.
Qualifications: Preferred Qualifications list.
Skills: Could extract specific skills: Linux, networking, troubleshooting, post-mortem, coding in Java/Python, software development methodology, building tools, scaling, TS/SCI clearance, Agile/Scrum, PowerShell, Python, Ruby, Java, etc. But we might combine with Requirements/Qualifications. However we need a Skills section only if there is real specific content not already covered. Could combine skills from description and qualifications into a list.
But we must not repeat content unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info. If we put skills in Skills section, we must also keep them elsewhere? That would duplicate. Better to place the skill details in appropriate sections (Requirements, Qualifications) and not have a separate Skills section unless there is extra skill info not captured elsewhere. The description includes Linux & Networking Fundamentals, deep experience with Linux, networking technology, troubleshooting, post-mortem, love to code (Java/Python), software development methodology, think big (scale). Those are covered in Basic Qualifications (Linux, networking, storage, OS, programming language, etc.) and Preferred Qualifications (PowerShell, Python, Ruby, Java, Agile/Scrum). So we might not need a separate Skills section. However the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed.
Benefits: The paragraph about benefits.
Pay: Salary range and sign-on payments, RSUs.
We must not include Schedule.
Now we need to format.
We'll produce:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: base salary range listed: "USA, VA, Arlington - 129,200.00 - 174,800.00 USD annually". Also mentions sign-on payments and RSUs, comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave. So we have Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule.
We need sections: About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to parse content.
Let's extract:
Description paragraph: "The Amazon Web Services team is innovating new ways of building massively scalable distributed systems and delivering the next generation of cloud computing with AWS offerings like RDS and Aurora. In 2013, AWS launched 280 services, but in 2016 alone we released nearly 1000. We hold high standards for our computer systems and the services we deliver to our customers: our systems are highly secure, highly reliable, highly available, all while functioning at massive scale; our employees are smart, passionate about the cloud, driven to serve customers, and fun to work with. A successful engineer joining the team will do much more than write code and triage problems. They will work with Amazon's largest and most demanding customers to address specific needs across a full suite of services. They will dive deeply into technical issues and work diligently to improve the customer experience. The ideal candidate will... Be great fun to work with. Our company credo is "Work hard. Have fun. Make history". The right candidate will love what they do and instinctively know how to make work fun. Have strong Linux & Networking Fundamentals. The ideal candidate will have deep experience working with Linux, preferably in a large scale, distributed environment. You understand networking technology and how servers and networks inter-relate. You regularly take part in deep-dive troubleshooting and conduct technical post-mortem discussions to identify the root cause of complex issues. Love to code. Whether its building tools in Java or solving complex system problems in Python, the ideal candidate will love using technology to solve problems. You have a solid understanding of software development methodology and know how to use the right tool for the right job. Think Big. The ideal candidate will build and deploy solutions across thousands of devices. You will strive to improve and streamline processes to allow for work on a massive scale. 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."
Then "Key job responsibilities" list bullet points.
Then "A day in the life" description.
Then "About The Team" with subsections: Why AWS, AWS Infrastructure Services (AIS), Inclusive Team Culture, Work/Life Balance, Mentorship and Career Growth, Diverse Experiences.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then EEO etc.
Then salary and benefits.
We need to produce sections with content.
We need to decide what goes where.
"About the role": Could be the initial description paragraph (the overview). Could also include "A day in the life" maybe as part of responsibilities? But we have separate Responsibilities section.
"Responsibilities": Use the "Key job responsibilities" bullet list plus maybe "A day in the life" details.
"Requirements": Could be the security clearance requirement? Or maybe "Basic Qualifications" as Requirements? Usually Requirements = basic qualifications. Qualifications = preferred qualifications? But we have both sections. We'll follow typical: Requirements = Basic Qualifications. Qualifications = Preferred Qualifications.
"Skills": Could be specific skills like Linux, networking, programming languages, etc. Might be extracted from description and qualifications.
"Benefits": The benefits paragraph.
"Pay": Salary range and sign-on payments, RSUs.
We must not include filler like "commensurate with experience" etc. The security clearance requirement includes "with polygraph or commensurate clearance for each government agency". That includes "commensurate clearance". That's a phrase we might need to keep? It's part of the requirement; we cannot remove substantive info. The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That's about headings with filler text, not about content containing the word commensurate. It's okay to keep the phrase as part of content.
We must not include boilerplate like EEO, accommodation links, etc.
We must not include duplicated lines.
We need to output only HTML fragment.
Let's craft sections.
First, About the role: combine the initial description paragraph (maybe up to "Think Big." plus security clearance requirement?). Actually security clearance is a requirement, but could be part of About the role? Might be better to put in Requirements.
Let's decide:
About the role: The paragraph describing AWS team innovation, high standards, what engineer will do, etc. Up to "Think Big." maybe include the security clearance? I'd keep security clearance in Requirements.
Thus About the role: The first big paragraph (starting "The Amazon Web Services team is innovating...") up to "Think Big." plus maybe the sentence "This position requires that the candidate selected must currently possess and maintain an active TS/SCI security clearance." Actually that is a requirement. I'll move to Requirements.
Thus About the role content: The paragraph describing AWS team innovating, high standards, engineer will do much more than write code, work with customers, dive deep, ideal candidate will... etc. We'll include the bullet-like sentences about fun, Linux & networking, love to code, think big. We'll keep them as prose.
Responsibilities: Use the "Key job responsibilities" bullet list (the list after that heading). Also maybe include "A day in the life" details as prose.
Requirements: Basic Qualifications list plus security clearance requirement.
Qualifications: Preferred Qualifications list.
Skills: Could extract specific skills: Linux, networking, troubleshooting, post-mortem, coding in Java/Python, software development methodology, building tools, scaling, TS/SCI clearance, Agile/Scrum, PowerShell, Python, Ruby, Java, etc. But we might combine with Requirements/Qualifications. However we need a Skills section only if there is real specific content not already covered. Could combine skills from description and qualifications into a list.
But we must not repeat content unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info. If we put skills in Skills section, we must also keep them elsewhere? That would duplicate. Better to place the skill details in appropriate sections (Requirements, Qualifications) and not have a separate Skills section unless there is extra skill info not captured elsewhere. The description includes Linux & Networking Fundamentals, deep experience with Linux, networking technology, troubleshooting, post-mortem, love to code (Java/Python), software development methodology, think big (scale). Those are covered in Basic Qualifications (Linux, networking, storage, OS, programming language, etc.) and Preferred Qualifications (PowerShell, Python, Ruby, Java, Agile/Scrum). So we might not need a separate Skills section. However the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed.
Benefits: The paragraph about benefits.
Pay: Salary range and sign-on payments, RSUs.
We must not include Schedule.
Now we need to format.
We'll produce:
About the role
...
Responsibilities
- ... ...
under Responsibilities.
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Now we need to extract the exact sentences. Let's copy the About the role paragraph from the text: "The Amazon Web Services team is innovating new ways of building massively scalable distributed systems and delivering the next generation of cloud computing with AWS offerings like RDS and Aurora. In 2013, AWS launched 280 services, but in 2016 alone we released nearly 1000. We hold high standards for our computer systems and the services we deliver to our customers: our systems are highly secure, highly reliable, highly available, all while functioning at massive scale; our employees are smart, passionate about the cloud, driven to serve customers, and fun to work with. A successful engineer joining the team will do much more than write code and triage problems. They will work with Amazon's largest and most demanding customers to address specific needs across a full suite of services. They will dive deeply into technical issues and work diligently to improve the customer experience. The ideal candidate will... Be great fun to work with. Our company credo is "Work hard. Have fun. Make history". The right candidate will love what they do and instinctively know how to make work fun. Have strong Linux & Networking Fundamentals. The ideal candidate will have deep experience working with Linux, preferably in a large scale, distributed environment. You understand networking technology and how servers and networks inter-relate. You regularly take part in deep-dive troubleshooting and conduct technical post-mortem discussions to identify the root cause of complex issues. Love to code. Whether its building tools in Java or solving complex system problems in Python, the ideal candidate will love using technology to solve problems. You have a solid understanding of software development methodology and know how to use the right tool for the right job. Think Big. The ideal candidate will build and deploy solutions across thousands of devices. You will strive to improve and streamline processes to allow for work on a massive scale." We need to keep that as prose. Might be long but okay. Now Responsibilities: The "Key job responsibilities" bullet list: - You design, implement, and deploy software components and features. - You solve difficult problems generating positive feedback. - You have a solid understanding of design approaches (and how to best use them). - You are able to work independently and with your team to deliver software successfully. - Your work is consistently of a high quality (e.g., secure, testable, maintainable, low-defects, efficient, etc.) and incorporates best practices. - Your team trusts your work. - Your code reviews tend to be rapid and uneventful. - You provide useful code reviews for changes submitted by others. - You focus on operational excellence, constructively identifying problems and proposing solutions, taking on projects that improve your team’s software, making it better and easier to maintain. - You make improvements to your team’s development and testing processes. - You have established good working relationships with peers. - You recognize discordant views and take part in constructive dialogue to resolve them. - You are able to confidently train new team-mates about your customers, what your team’s software does, how it is constructed, tested, operates, and how it fits into the bigger picture. Also "A day in the life" paragraph: "Engineers in this role will work on automation, development, and operations to support AWS machine learning services for US government customers. They will work in an agile environment, attend daily standup, and collaborate closely with teammates. They will