Sr. DevOps Engineer (AWS)
Jobgether · United States · 3 wk ago
RemoteRemoteEngineering$123k–$145k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading only if content exists. No job title heading. No Job ID etc. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Keep substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The first paragraph(s) describing role: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Sr. DevOps Engineer (AWS) based in United States. This role is responsible for helping manage, mature, and optimize a large-scale AWS platform while advancing modern DevOps practices across the organization. You will work closely with AWS teams and internal technology stakeholders to increase the value, reliability, security, and scalability of cloud infrastructure. The position combines hands-on cloud engineering, automation, infrastructure modernization, and technical problem-solving. You will help integrate complex infrastructure builds with application deployment processes and support major technology initiatives. The role also provides opportunities to research emerging technologies, incorporate AI/ML capabilities, and improve operational efficiency. As a senior technical contributor, you will mentor others and help champion lean, agile, and systems-thinking practices."
We can keep that as About the role.
- Responsibilities: The "Accountabilities" list bullet points. Those are responsibilities.
List them:
- Manage and continuously mature AWS environments, applying strong DevOps practices to improve platform reliability, scalability, security, and operational efficiency.
- Champion DevOps and lean-agile disciplines across major initiatives, including practices such as Test Driven Development, improved workflow, flow optimization, and systems thinking.
- Improve the integration of complex infrastructure builds with application deployment processes across major projects and systems.
- Troubleshoot complex technical problems involving information systems and provide insight, guidance, and technical expertise to other specialists.
- Analyze, design, evaluate, and improve large-scale automation scripts, infrastructure systems, and operational tooling.
- Research and assess emerging technologies that can improve efficiency, effectiveness, scalability, and platform capabilities.
- Develop and maintain automation that reduces manual work across infrastructure, deployment, and operational processes.
- Support the migration of complex workloads to AWS and help ensure successful operation of cloud-based workloads following migration.
- Design, build, and operate Kubernetes and AWS serverless workloads as part of modern cloud architectures.
- Integrate AI/ML capabilities into AWS platform engineering, including foundational services that improve operational efficiency, delivery workflows, and platform reliability.
- Provide coaching, technical expertise, and guidance to colleagues and other professionals, and oversee work when appropriate.
- Maintain a strong commitment to child protection and incorporate applicable safeguarding considerations into technology decisions, activities, and processes.
We can put these under Responsibilities.
- Requirements: The "Requirements" list bullet points.
List:
- Extensive experience operating and optimizing AWS production environments at scale.
- Deep understanding of the AWS Cloud Operations lifecycle, including security, governance, compliance, and disaster recovery models.
- Hands-on experience implementing and operating AWS Landing Zone Accelerator (LZA), including multi-account architecture, governance, security controls, and automation patterns.
- Experience designing and operating service-to-service communication using AWS Application Networking / AWS Lattice, including secure connectivity, traffic routing, service mesh patterns, cross-account communication, and hybrid networking.
- Experience integrating AI/ML capabilities into AWS platform engineering and designing and maintaining foundational services that support AI-enabled operations.
- Strong automation expertise, including Infrastructure as Code, deployment pipelines, operational scripting, and other approaches that eliminate repetitive manual work.
- Demonstrated experience migrating complex workloads onto AWS.
- Ability to design, build, and operate workloads using Kubernetes and AWS serverless architectures.
- Strong Python development skills for operational tooling, automation scripts, AWS Lambda functions, and related cloud engineering tasks.
- Strong troubleshooting, analytical, and systems-thinking skills, with the ability to diagnose complex technical issues and develop scalable solutions.
- Ability to research emerging technologies and assess their potential value within a cloud platform environment.
- Strong communication, collaboration, mentoring, and technical leadership capabilities.
- Ability to work effectively in a lean-agile environment and help others adopt modern DevOps practices.
- Commitment to a Christian faith-based mission and willingness to support an organizational environment centered on Christian values and spiritual practices.
We can put under Requirements.
- Qualifications: Not separate; maybe combine with Requirements? The instruction says use headings for Qualifications if content exists. There's no separate qualifications block; we could skip Qualifications.
- Skills: Could be extracted from requirements but we already have them. Might not need separate Skills section if we already have Requirements covering skills. But we could create Skills section for specific skills like Python, Kubernetes, AWS, etc. However we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine skills into Requirements or maybe have a Skills section for technical skills like Python, Kubernetes, AWS, IaC, etc. But we already have them in Requirements. Might be okay to have only Requirements and Benefits and Pay.
- Benefits: The "Benefits" list bullet points.
List:
- Remote work within the United States.
- Full-time position.
- Expected salary range of $123,240–$144,797.60, with geographic differentials potentially available in certain high-cost U.S. locations.
- Generous paid time off.
- 10% employer contribution to a 403(b) retirement fund in addition to salary.
- Comprehensive healthcare coverage.
- Free short-term professional counseling.
- Opportunities for spiritual growth through chapel services, prayer groups, and department devotionals.
- Opportunity to contribute technical expertise to a mission-driven organization focused on supporting children and communities.
Note: Salary is also in Benefits but we also need a Pay section if posting actually states them. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states salary range in Benefits bullet. Should we create a Pay section separate? The instruction says we can have Pay section if posting actually states them. It does state salary range. So we could create a Pay section with that salary info. However the Benefits bullet includes salary; we could move salary to Pay section and keep other benefits in Benefits. That seems appropriate.
- Schedule: Not explicitly stated besides full-time. Could be considered schedule: Full-time position. Could create Schedule section with "Full-time". But we need to check if posting actually states schedule. It says "Full-time position." That's schedule info. So we can create Schedule section with "Full-time". However we also have Benefits bullet "Full-time position." Might be redundant. Better to put schedule in Schedule section and keep other benefits in Benefits.
Thus sections:
- About the role (h3)
- Responsibilities (h3) with ul li
- Requirements (h3) with ul li
- Benefits (h3) with ul li (excluding salary and full-time)
- Pay (h3) with p (salary range)
- Schedule (h3) with p (Full-time)
We should not include sections with placeholder text. All have content.
We must not repeat job title as heading. Not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
for each heading only if content exists. No job title heading. No Job ID etc. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Keep substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The first paragraph(s) describing role: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Sr. DevOps Engineer (AWS) based in United States. This role is responsible for helping manage, mature, and optimize a large-scale AWS platform while advancing modern DevOps practices across the organization. You will work closely with AWS teams and internal technology stakeholders to increase the value, reliability, security, and scalability of cloud infrastructure. The position combines hands-on cloud engineering, automation, infrastructure modernization, and technical problem-solving. You will help integrate complex infrastructure builds with application deployment processes and support major technology initiatives. The role also provides opportunities to research emerging technologies, incorporate AI/ML capabilities, and improve operational efficiency. As a senior technical contributor, you will mentor others and help champion lean, agile, and systems-thinking practices."
We can keep that as About the role.
- Responsibilities: The "Accountabilities" list bullet points. Those are responsibilities.
List them:
- Manage and continuously mature AWS environments, applying strong DevOps practices to improve platform reliability, scalability, security, and operational efficiency.
- Champion DevOps and lean-agile disciplines across major initiatives, including practices such as Test Driven Development, improved workflow, flow optimization, and systems thinking.
- Improve the integration of complex infrastructure builds with application deployment processes across major projects and systems.
- Troubleshoot complex technical problems involving information systems and provide insight, guidance, and technical expertise to other specialists.
- Analyze, design, evaluate, and improve large-scale automation scripts, infrastructure systems, and operational tooling.
- Research and assess emerging technologies that can improve efficiency, effectiveness, scalability, and platform capabilities.
- Develop and maintain automation that reduces manual work across infrastructure, deployment, and operational processes.
- Support the migration of complex workloads to AWS and help ensure successful operation of cloud-based workloads following migration.
- Design, build, and operate Kubernetes and AWS serverless workloads as part of modern cloud architectures.
- Integrate AI/ML capabilities into AWS platform engineering, including foundational services that improve operational efficiency, delivery workflows, and platform reliability.
- Provide coaching, technical expertise, and guidance to colleagues and other professionals, and oversee work when appropriate.
- Maintain a strong commitment to child protection and incorporate applicable safeguarding considerations into technology decisions, activities, and processes.
We can put these under Responsibilities.
- Requirements: The "Requirements" list bullet points.
List:
- Extensive experience operating and optimizing AWS production environments at scale.
- Deep understanding of the AWS Cloud Operations lifecycle, including security, governance, compliance, and disaster recovery models.
- Hands-on experience implementing and operating AWS Landing Zone Accelerator (LZA), including multi-account architecture, governance, security controls, and automation patterns.
- Experience designing and operating service-to-service communication using AWS Application Networking / AWS Lattice, including secure connectivity, traffic routing, service mesh patterns, cross-account communication, and hybrid networking.
- Experience integrating AI/ML capabilities into AWS platform engineering and designing and maintaining foundational services that support AI-enabled operations.
- Strong automation expertise, including Infrastructure as Code, deployment pipelines, operational scripting, and other approaches that eliminate repetitive manual work.
- Demonstrated experience migrating complex workloads onto AWS.
- Ability to design, build, and operate workloads using Kubernetes and AWS serverless architectures.
- Strong Python development skills for operational tooling, automation scripts, AWS Lambda functions, and related cloud engineering tasks.
- Strong troubleshooting, analytical, and systems-thinking skills, with the ability to diagnose complex technical issues and develop scalable solutions.
- Ability to research emerging technologies and assess their potential value within a cloud platform environment.
- Strong communication, collaboration, mentoring, and technical leadership capabilities.
- Ability to work effectively in a lean-agile environment and help others adopt modern DevOps practices.
- Commitment to a Christian faith-based mission and willingness to support an organizational environment centered on Christian values and spiritual practices.
We can put under Requirements.
- Qualifications: Not separate; maybe combine with Requirements? The instruction says use headings for Qualifications if content exists. There's no separate qualifications block; we could skip Qualifications.
- Skills: Could be extracted from requirements but we already have them. Might not need separate Skills section if we already have Requirements covering skills. But we could create Skills section for specific skills like Python, Kubernetes, AWS, etc. However we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine skills into Requirements or maybe have a Skills section for technical skills like Python, Kubernetes, AWS, IaC, etc. But we already have them in Requirements. Might be okay to have only Requirements and Benefits and Pay.
- Benefits: The "Benefits" list bullet points.
List:
- Remote work within the United States.
- Full-time position.
- Expected salary range of $123,240–$144,797.60, with geographic differentials potentially available in certain high-cost U.S. locations.
- Generous paid time off.
- 10% employer contribution to a 403(b) retirement fund in addition to salary.
- Comprehensive healthcare coverage.
- Free short-term professional counseling.
- Opportunities for spiritual growth through chapel services, prayer groups, and department devotionals.
- Opportunity to contribute technical expertise to a mission-driven organization focused on supporting children and communities.
Note: Salary is also in Benefits but we also need a Pay section if posting actually states them. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states salary range in Benefits bullet. Should we create a Pay section separate? The instruction says we can have Pay section if posting actually states them. It does state salary range. So we could create a Pay section with that salary info. However the Benefits bullet includes salary; we could move salary to Pay section and keep other benefits in Benefits. That seems appropriate.
- Schedule: Not explicitly stated besides full-time. Could be considered schedule: Full-time position. Could create Schedule section with "Full-time". But we need to check if posting actually states schedule. It says "Full-time position." That's schedule info. So we can create Schedule section with "Full-time". However we also have Benefits bullet "Full-time position." Might be redundant. Better to put schedule in Schedule section and keep other benefits in Benefits.
Thus sections:
- About the role (h3)
- Responsibilities (h3) with ul li
- Requirements (h3) with ul li
- Benefits (h3) with ul li (excluding salary and full-time)
- Pay (h3) with p (salary range)
- Schedule (h3) with p (Full-time)
We should not include sections with placeholder text. All have content.
We must not repeat job title as heading. Not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Sr. DevOps Engineer (AWS) based in United States. This role is responsible for helping manage, mature, and optimize a large-scale AWS platform while advancing modern DevOps practices across the organization. You will work closely with AWS teams and internal technology stakeholders to increase the value, reliability, security, and scalability of cloud infrastructure. The position combines hands-on cloud engineering, automation, infrastructure modernization, and technical problem-solving. You will help integrate complex infrastructure builds with application deployment processes and support major technology initiatives. The role also provides opportunities to research emerging technologies, incorporate AI/ML capabilities, and improve operational efficiency. As a senior technical contributor, you will mentor others and help champion lean, agile, and systems-thinking practices.
Responsibilities
- Manage and continuously mature AWS environments, applying strong DevOps practices to improve platform reliability, scalability, security, and operational efficiency.
- Champion DevOps and lean-agile disciplines across major initiatives, including practices such as Test Driven Development, improved workflow, flow optimization, and systems thinking.
- Improve the integration of complex infrastructure builds with application deployment processes across major projects and systems.
- Troubleshoot complex technical problems involving information systems and provide insight, guidance, and technical expertise to other specialists.
- Analyze, design, evaluate, and improve large-scale automation scripts, infrastructure systems, and operational tooling.
- Research and assess emerging technologies that can improve efficiency, effectiveness, scalability, and platform capabilities.
- Develop and maintain automation that reduces manual work across infrastructure, deployment, and operational processes.
- Support the migration of complex workloads to AWS and help ensure successful operation of cloud-based workloads following migration.
- Design, build, and operate Kubernetes and AWS serverless workloads as part of modern cloud architectures.
- Integrate AI/ML capabilities into AWS platform engineering, including foundational services that improve operational efficiency, delivery workflows, and platform reliability.
- Provide coaching, technical expertise, and guidance to colleagues and other professionals, and oversee work when appropriate.
- Maintain a strong commitment to child protection and incorporate applicable safeguarding considerations into technology decisions, activities, and processes.
Requirements
- Extensive experience operating and optimizing AWS production environments at scale.
- Deep understanding of the AWS Cloud Operations lifecycle, including security, governance, compliance, and disaster recovery models.
- Hands-on experience implementing and operating AWS Landing Zone Accelerator (LZA), including multi-account architecture, governance, security controls, and automation patterns.
- Experience designing and operating service-to-service communication using AWS Application Networking / AWS Lattice, including secure connectivity, traffic routing, service mesh patterns, cross-account communication, and hybrid networking.
- Experience integrating AI/ML capabilities into AWS platform engineering and designing and maintaining foundational services that support AI-enabled operations.
- Strong automation expertise, including Infrastructure as Code, deployment pipelines, operational scripting, and other approaches that eliminate repetitive manual work.
- Demonstrated experience migrating complex workloads onto AWS.
- Ability to design, build, and operate workloads using Kubernetes and AWS serverless architectures.
- Strong Python development skills for operational tooling, automation scripts, AWS Lambda functions, and related cloud engineering tasks.
- Strong troubleshooting, analytical, and systems-thinking skills, with the ability to diagnose complex technical issues and develop scalable solutions.
- Ability to research emerging technologies and assess their potential value within a cloud platform environment.
- Strong communication, collaboration, mentoring, and technical leadership capabilities.
- Ability to work effectively in a lean-agile environment and help others adopt modern DevOps practices.
- Commitment to a Christian faith-based mission and willingness to support an organizational environment centered on Christian values and spiritual practices.
Benefits
- Remote work within the United States.
- Generous paid time off.
- 10% employer contribution to a 403(b) retirement fund in addition to salary.
- Comprehensive healthcare coverage.
- Free short-term professional counseling.
- Opportunities for spiritual growth through chapel services, prayer groups, and department devotionals.
- Opportunity to contribute technical expertise to a mission-driven organization focused on supporting children and communities.