- Company Name
- KTek Resourcing
- Job Title
- DevSecOps Engineer
- Job Description
-
<think>
Okay, let me start by understanding the user's request. They want a normalized job profile for a DevSecOps Engineer position, extracted from a given job description. The output needs to be concise, under 500 words, and structured with specific sections: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. They also mentioned excluding company details, location, benefits, and fluff. Plus, it should be ATS-friendly and globally neutral.
First, I'll parse the provided job description. The key elements here are the job title, experience required, technical skills, and preferred qualifications. The user wants this information condensed without unnecessary details. The original job description mentions Azure, AWS, Terraform, OCI, Ansible, and other tools. The role emphasizes security in DevOps processes, CI/CD pipelines, Infrastructure as Code, and cloud platforms.
I need to structure the Role Summary to capture the essence of the position: a DevSecOps Engineer with a focus on security across multiple cloud environments. The Expectations section should highlight the years of experience and the primary areas of focus—like designing secure CI/CD pipelines, security best practices, and infrastructure code.
Key Responsibilities will include the main tasks: designing and implementing CI/CD, integrating security practices, using Terraform and Ansible. Required Skills should list the must-have tools (Azure, AWS, Terraform, Ansible) and cloud platforms. They also mention OCI as a good to have in the original, but since the user wants to focus on required, maybe OCI is optional here, but the original says "good to have" so perhaps it's better to exclude it unless it's required.
Education and Certifications: They mention preferred certifications, but the user wants required. However, the job description lists preferred qualifications as non-mandatory, so maybe some of them can be in the required if they're part of the "must have." Wait, in the job description, the "Must have skillset" includes Terraform and OCI as good to have. So actually, Azure, AWS, Terraform are required, OCI is optional. Need to clarify that.
Wait, the job description says "Must have skillset - Solid in Azure, AWS, Terraform and OCI (good to have)." Hmm, that's a bit confusing. Maybe the user meant that Azure, AWS, Terraform are required, and OCI is optional. So I'll parse that accordingly. So in Required Skills, list Azure, AWS, Terraform as required, and OCI as a good to have but since the user says to exclude fluff, perhaps omit it unless it's required. Wait, the original says "Must have skillset - Solid in Azure, AWS, Terraform and OCI (good to have)". So maybe the parentheses indicate that OCI is not required. So perhaps the required skills are Azure, AWS, Terraform, and the others are optional. Therefore, I'll list Azure, AWS, Terraform as required. The other ones might be in the preferred section but the user wants only required in the output. Since the user's instruction is to exclude preferred qualifications unless they're required, perhaps only list the required ones in the skills section. But the job description lists "Must have skillset" as Azure, AWS, Terraform and OCI (good to have). So maybe the required skills are Azure, AWS, Terraform, and OCI is a plus but not required. Therefore, in Required Skills, list Azure, AWS, Terraform.
Education and Certifications: The job requires 5+ years in DevOps, SRE, or Cloud Engineering roles with security focus. The preferred certifications are listed, but since they're preferred, the user probably wants to exclude them unless they're required. However, the original job description does not list any required education or certifications, so perhaps the Required Education & Certifications section can be omitted. Wait, the user's prompt says "Required Education & Certifications," so maybe we can list that a bachelor's degree is required, as that's common in many engineering roles, even though it's not mentioned in the original. But the user also said to be factual, so if the original doesn't mention education, maybe not include it. Alternatively, since the user provided "Experience: 5+ years...", maybe that can be under Required Education as a substitute, but the user's structure has separate sections. Hmm. Let me check the instructions again. The user says "Exclude company details, location, benefits, or fluff," so if the original doesn't mention education or certifications as required, then these sections might be left blank. But the user's example output includes "Required Education & Certifications," so perhaps we can state "Not specified" or omit it. Wait, the original job description does not mention any formal education requirements, just 5+ years of experience. However, the user's example might expect something in Education. But the user might want us to infer based on industry standards. Maybe a bachelor's degree is a safe assumption, but that's not specified. To be safe, perhaps omit it unless the original mentions it. Given the original does not, perhaps leave it as "Not required" or exclude the section. But the user's structure requires "Required Education & Certifications," so maybe it's better to put "Not specified" or "None." Alternatively, maybe list the 5+ years as part of the Requirements. Hmm. Alternatively, the instructions say "Required Education & Certifications," so for this case, since the job description doesn't mention education, but does mention experience, maybe move the experience under Role Summary or Expectations. However, the original user's example output may include "Required Education & Certifications" even if it's not in the job description. But since the user said "Do not add any introduction, explanation, or extra text," perhaps we shouldn't add inferred information. Therefore, if the education isn't mentioned in the job description, perhaps exclude that section. But the user's example output might have it. Hmm. The original job description does mention experience (5+ years), so maybe include that in the "Expectations" or "Experience" section. Let's check the user's example output structure again. The sections are: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So if the job description doesn't specify education, then perhaps just leave that section blank. Alternatively, write "Not specified" or omit it. Since the user says "exclude fluff," perhaps omit it. But the user wants all sections. Wait, the user's instruction says "only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So even if the job description doesn't have education, we need to include that section. Therefore, if the job description doesn't mention education, perhaps list "Not required" or leave it as an empty line. However, the user said to be factual. The original job description does not mention any formal education requirement, so perhaps the answer should reflect that. Therefore, under Required Education & Certifications, we can put "Not specified." But the user might prefer to have that section included.
Also, regarding certifications: the job description lists preferred qualifications, including cloud certifications and security certifications. But since they are preferred, not required, the Required Education & Certifications section only includes those that are mandatory. The original job description does not specify any required certifications, only preferred ones, so this section can be omitted or noted as none.
Putting it all together:
Job Title: DevSecOps Engineer
Role Summary: Designs and implements secure CI/CD pipelines and infrastructure across multi-cloud environments (Azure, AWS, GCP). Integrates security practices into DevOps workflows. Requires extensive experience in cloud security, infrastructure automation, and configuration management.
Expectations: Minimum 5+ years in DevOps, SRE, or Cloud Engineering roles with a focus on security.
Key Responsibilities:
- Design, implement, and maintain secure CI/CD pipelines across Azure, AWS, and GCP.
- Integrate security best practices into build, deployment, and runtime environments.
- Develop Infrastructure as Code (Terraform) in production settings.
- Use Ansible for configuration management and automation.
- Evaluate and adopt security tools and practices across cloud platforms.
Required Skills:
- Proficiency in Azure and AWS cloud platforms.
- Expertise in Terraform for Infrastructure as Code.
- Strong knowledge of CI/CD pipeline security.
- Experience with Ansible configuration management.
- Familiarity with GCP and OCI as additional cloud environments.
Required Education & Certifications: Not specified (the job description does not mention any formal education or certification requirements, only preferred ones).
Wait, but in the job description, under Experience it says 5+ years in a DevOps (Azure), SRE, or Cloud Engineering role with a strong focus on security. So the Expectations section can include the 5+ years, but the Education part is not mentioned. Therefore, Required Education would be "Not specified" or omitted. However, the user wants the output to include all sections. Therefore, perhaps in the Required Education & Certifications section, we can say "Not specified" or leave it as is. Alternatively, if the user expects some entry, perhaps write "None" in that section.
Additionally, the original mentions "Deep understanding and hands-on experience with Azure, AWS cloud platforms with a strong willingness to work across all four(Azure, AWS, OCI and GCP)." So in Required Skills, GCP is now needed? The original says willingness to work across all four, but in the job description, it's listed as a required experience. So perhaps include GCP as a required skill since the job requires the candidate to work across all four. However, the user's job description says "deep understanding and hands-on experience with Azure, AWS, and willingness to work across all four." So