Enterprise - DevOps Engineer - AWS, Kubernetes, Linux

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to parse the job posting. Let's extract content: Company description: "Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers." That's about the company; could be "About the role"? Actually "About the role" is more about the position. But we can treat that as "About the role" maybe. However they said do NOT repeat the job title as a heading. Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's list sections: - About the role: Could include description of role: "We are seeking a highly motivated and experienced DevOps Engineer to join our fast-paced development team. The ideal candidate will have strong working knowledge in Kubernetes and Container Orchestration, Configuration Management, CI/CD, Automation, AWS, Linux systems administration, Scripting in Bash and Programming in Python, and a background in Big Data solutions. The DevOps Engineer will be responsible for implementing infrastructure, automating deployment processes, and ensuring the monitoring, reliability and scalability of our services. Work is performed in a hybrid environment (on average 1-2 days a week) with a great team." That's about the role. - Responsibilities: The bullet list after "Support development and deployment..." etc. Those are duties/responsibilities. - Requirements: Could include clearance, experience, education, etc. Also required skills? Might be separate. - Qualifications: Could be education/experience combos. - Skills: Required skills list. - Benefits: Benefits section. - Pay: Salary range. - Schedule: Hybrid environment mention. We need to avoid boilerplate like EEO, referral, etc. We must preserve all substantive info, not invent. We must not include placeholders like "commensurate with experience". Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment. Let's craft sections:

About the role

... (company description + role description)

But maybe we split company description into About the company? Not required. We'll include in About the role. Better: About the role includes the description of the role and company context. Let's write:

Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers. We are seeking a highly motivated and experienced DevOps Engineer to join our fast-paced development team. The ideal candidate will have strong working knowledge in Kubernetes and Container Orchestration, Configuration Management, CI/CD, Automation, AWS, Linux systems administration, Scripting in Bash and Programming in Python, and a background in Big Data solutions. The DevOps Engineer will be responsible for implementing infrastructure, automating deployment processes, and ensuring the monitoring, reliability and scalability of our services. Work is performed in a hybrid environment (on average 1-2 days a week) with a great team.

That covers a lot. Now Responsibilities: list of duties. We have bullet list: - Support development and deployment of cloud infrastructure in AWS, especially EKS - Support development and deployment of non-cloud (Edge) infrastructure of on-premise and portable equipment - Automate deployment processes and ensure reliability and scalability of services - Manage and maintain Kubernetes containers and cloud infrastructure on AWS - Collaborate with development teams to integrate their applications into the infrastructure - Monitor and troubleshoot production systems and resolve issues as necessary - Continuously improve processes and tools to ensure high availability and performance - Stay current with new technologies and industry trends, continuously exploring new ways to improve our infrastructure - Other duties as assigned We'll put in

• ...

. Now Requirements: Could include clearance, citizenship, experience/education combos. We have: "Clearance Must currently have and maintain an active Secret U.S. Government Security Clearance; U.S. Citizenship required." Also "Experience Five plus (5+) years of experience in DevOps Engineering or Software Development and Bachelors in related field; or three (3) years relevant experience with Masters in related field; or High School Diploma or equivalent and nine (9) years relevant experience." Also "Must be able to work in a hybrid environment, spending an average of 1-2 days per week at our San Antonio, TX office. Flexibility is essential to adapt to schedule changes as needed. Onsite frequency and locations may vary based on customer/company support requirements and contract needs" That could be schedule but also requirement. We'll put clearance, citizenship, experience/education under Requirements. Now Qualifications: maybe we could treat education/experience as qualifications. But we already used them in Requirements. Could separate: Requirements = mandatory (clearance, citizenship, experience/education). Qualifications = desired? But we have Desired Skills separate. Better: Use Requirements for mandatory (clearance, citizenship, experience/education). Use Qualifications for desired? But they have Desired Skills section. We'll follow typical: Requirements = mandatory qualifications; Qualifications = preferred? However they have Desired Skills separate. We'll put Desired Skills under Skills? Actually they have Skills heading for required skills list. We'll have Skills for required skills. Desired Skills could be under Skills as well? But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where each piece fits. Let's map: - About the role: company + role overview. - Responsibilities: duties list. - Requirements: mandatory: clearance, citizenship, experience/education, maybe also hybrid work requirement? Could be schedule. - Qualifications: maybe education/experience combos? But we already used them. Could treat qualifications as the education/experience combos, and requirements as clearance/citizenship? But ambiguous. Better: Use Requirements for clearance/citizenship and hybrid work requirement. Use Qualifications for experience/education combos. Use Skills for required skills list. Use Desired Skills maybe also under Skills? But we have only one Skills heading allowed. Could include both required and desired under Skills, but we need to not invent headings. We could put desired skills under Skills as a sub-list? Might be okay. But we have a separate "Desired Skills" block in the posting. We could incorporate that into Skills section as well, maybe label as "Desired skills" within the same section? However the instruction says use headings for sections like Skills. It doesn't forbid subheadings. But we should avoid extra headings not listed. Could just put all skills (required and desired) under Skills heading, maybe separate paragraphs. Let's do:

Skills

Required skills:

... required skills list ...

Desired skills:

... desired skills list ...

That seems okay. Now Benefits: we have benefits paragraph. Pay: salary range. Schedule: hybrid environment mention (1-2 days a week). Could be under Schedule heading. We already mentioned hybrid in About the role; but we can still have Schedule section with details. We must not repeat info unnecessarily but it's okay to repeat? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid repetition, but better to avoid duplication. However we can keep schedule details in Schedule section and maybe not repeat in About the role. But we already included hybrid in About the role; we could remove from About the role to avoid duplication. Let's adjust: In About the role we can keep generic description but maybe omit hybrid detail; we can keep it brief. Let's rewrite About the role without hybrid detail. About the role paragraph: company description + role overview (seeking DevOps Engineer, ideal candidate knowledge, responsibilities). We'll keep responsibilities generic? Actually we have separate Responsibilities section, so we can keep About the role short: company overview and that we are seeking DevOps Engineer. Let's craft:

Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking a highly motivated and experienced DevOps Engineer to join our fast-paced development team.

Then Responsibilities section will have the detailed duties. Now Requirements: clearance, citizenship, maybe also hybrid work requirement? Actually hybrid is schedule. We'll put clearance and citizenship under Requirements. Qualifications: experience/education combos. Skills: required and desired. Benefits: benefits paragraph. Pay: salary range. Schedule: hybrid environment details. Now we must ensure we don't include boilerplate like EEO, referral, etc. Let's extract each piece precisely. About the role: - "Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers." - Then "We are seeking a highly motivated and experienced DevOps Engineer to join our fast-paced development team." Combine. Now Responsibilities list: as above. Now Requirements: - "Clearance Must currently have and maintain an active Secret U.S. Government Security Clearance; U.S. Citizenship required." We could phrase: "Must currently have and maintain an active Secret U.S. Government Security Clearance. U.S. Citizenship required." Now Qualifications: - "Experience Five plus (5+) years of experience in DevOps Engineering or Software Development and Bachelors in related field; or three (3) years relevant experience with Masters in related field; or High School Diploma or equivalent and nine (9) years relevant experience." We could format as sentences. Now Skills: Required Skills list: - Strong knowledge of Kubernetes or other container orchestration platforms - Strong knowledge of AWS services (EC2, EBS, S3, Lambda) and their application to deployment and management of infrastructure - Proficient in configuration management tools such as Terraform and Ansible - Experience with application, container, and OS deployment, scaling, and management - Ability to develop in multiple programming languages such as Python, Bash, or Go - Familiarity with Git, Flux, and other development and deployment tools - Must be comfortable in a terminal-based environment - Proficient knowledge of Linux, including system administration and troubleshooting - Excellent problem-solving skills and the ability to identify and troubleshoot complex issues - Excellent oral and written communication skills - Understanding of AGILE software development methodologies and use of standard software development tool suites - Must have a DoD 8140 / 8570 compliance certifications (i.e. Security+) or willing to obtain within 60 days of hire Desired Skills list: - Current Clearance: TS/SCI level clearance is a strong plus - Experience with big data technologies like: Hadoop, Accumulo, Ceph, Spark, NiFi, Kafka, PostgreSQL, ElasticSearch, Hive, Drill, Impala, Trino, Pr