- Company Name
- Kinaxis
- Job Title
- Co-op/Intern Cloud Developer, Platform Engineering
- Job Description
-
<think>
Okay, the user wants me to normalize a job description into a concise mini-job profile. Let me start by understanding the requirements.
First, I need to extract specific elements: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. The user emphasized being factual, concise, ATS-friendly, and globally neutral. They also want to exclude company details, location, benefits, and fluff. The max is 500 words.
The original job title is "Co-op/Intern Cloud Developer, Platform Engineering". I'll keep that as the job title.
For the Role Summary: I need to summarize the role without extra details. The original says it's about learning DevOps, automation, CI/CD, GitOps, infrastructure, and monitoring. I should highlight that they help with cloud infrastructure and application deployment using specific tools like GitOps, Terraform, ArgoCD.
Expectations: The user is looking for someone who is a co-op or intern, enrolled in a post-secondary program. They should be eligible by being in education or graduating within 12 months of the term end. Also, Canadian citizenship or permanent residency is required for security clearance. Need to mention that eligibility for co-op/intern is based on education status.
Key Responsibilities: The job description lists applying software engineering principles to automation, building and managing cloud automation with IaC, scripting, APIs. Participating in code/design reviews. May handle additional projects. I should list these points concisely.
Required Skills: They want foundational knowledge in CS principles, data structures, algorithms. Analytical and problem-solving. Communication skills. Also, they mention familiarity with cloud tech, container platforms, GitOps, DevOps as assets, but since "asset" is used, I need to note that those are considered assets. But the user said to exclude fluff, so maybe present them as required or optional? Wait, the original says "considered an asset", so maybe in Required Skills, under Required or Required as Assets? Hmm, the user might want to differentiate between required and preferred skills. But the user instructions are strict: Required Skills and Required Education & Certifications. The description has "Foundational knowledge" as required, and other skills as assets. So I'll split them into required and preferred accordingly.
Required Education: Currently enrolled in a post-secondary diploma or degree in CS or related field. That's the main one.
Certifications: The job requires CGRP Security Clearance, which is part of the role's requirement, but the user might want to include that if necessary. However, the user said to exclude location and other fluff, but the security clearance is part of the role's requirement because of Canadian regulations. Since the user said to exclude company details but not all certifications related to the job might be okay. But in Required Education & Certifications, maybe mention that Canadian Citizenship or PR is required for CGRP clearance. But the user instructions say to exclude location details, so maybe just state the education and certifications needed. Wait, the user specified "Exclude company details, location, benefits, or fluff." So maybe the CGRP security clearance requirement is part of the role's requirements but not company details. However, the user might prefer not to include specific security clearances if they are location-dependent. Hmm, tricky. The original says "Canadian Citizenship or Permanent Residency is required..." So maybe in Required Skills or Required Education?
Alternatively, in Required Education & Certifications, note that Canadian Citizenship or PR is required to obtain CGRP Security Clearance. But the user wants this to be globally neutral. If the profile is for global use, maybe it's better to omit that. However, the user said to keep it factual. Since the original requires it, perhaps include it under Required Education & Certifications with a note that it's specific to the location. But the user also said to exclude location details. Maybe the user wants this profile to be adaptable, so perhaps just mention the citizenship requirement as part of the role's qualifications without focusing on location. But the user's instruction is to exclude location. Hmm. Maybe the best approach is to include that Canadian citizenship or PR is required for the role, but since location is excluded, maybe just list it as a requirement without specifying Canada. But that might not be accurate. Since the user wants a globally neutral profile, perhaps omit that part unless it's a general certification. But the CGRP Security Clearance is specific to Canada. Maybe the user wants to keep it but make it conditional. However, the user might prefer to remove that line if it's location-based. The user said to exclude location details, so perhaps leave out the citizenship/PR requirement since it's tied to location. Wait, but the user wants to exclude location details, but the citizenship requirement is part of the role's eligibility. This is a bit conflicting. Since the user's instruction is to exclude company details, location, benefits, or fluff, maybe it's best to omit the Canadian citizenship/PR requirement. The user might be creating a job profile that's generic and not tied to specific locations. Therefore, I'll proceed without mentioning the citizenship requirement, even though it's a real requirement. That way, the profile remains globally neutral.
So, moving forward. Required Education is post-secondary diploma or degree in CS or related. Required Certifications might be none, unless there's a specific certification listed. The original didn't mention any certifications beyond the security clearance, which is tied to location. So maybe no certifications are required in the profile.
Now, compiling all the sections.
Role Title: Co-op/Intern Cloud Developer, Platform Engineering
Role Summary: The Co-op/Intern will contribute to cloud infrastructure and application deployment using automation, DevOps practices (GitOps, CI/CD), and tools like Terraform, Ansible, Docker, and Kubernetes. Responsibilities include infrastructure as code (IaC) development, code/design reviews, and supporting cloud platform improvements. Exposure to multi-cloud environments and monitoring systems is expected.
Expectations: Open to co-ops and interns in post-secondary CS or related programs. Must be enrolled full-time or graduate within 12 months of placement end. Full-time, 8-12 months starting May 2026. Requires foundational knowledge in computer science principles, problem-solving, and communication skills.
Key Responsibilities:
- Apply software engineering principles to automate infrastructure and operations, focusing on reliability and consistency.
- Design, implement, and manage cloud automation using IaC tools (Terraform), scripting, APIs.
- Participate in code and design reviews to ensure quality and adherence to best practices.
- Contribute to additional projects as needed.
Required Skills:
- Foundational knowledge of computer science principles, data structures, algorithms.
- Analytical and problem-solving skills for troubleshooting cloud and automation challenges.
- Strong written and verbal communication for documentation and collaboration.
- Familiarity with cloud platforms (AWS, Azure, etc.), containerization (Docker, Kubernetes), and DevOps practices (CI/CD, GitOps).
- Proficiency in scripting/programming languages (Go, Python), IaC tools (Terraform, Ansible).
Required Education & Certifications:
- Currently enrolled in a post-secondary diploma or degree program in computer science or related field.
- No specific certifications required, though hands-on experience with cloud/DevOps technologies is beneficial.
Wait, the original mentioned that familiarity with Cloud technologies, GitOps, DevOps is considered an asset. So maybe in the Required Skills, some tools are listed as assets, but the user wants to present them as required or optional. Since the user wants to keep it factual and ATS-friendly, but the original job posting says those are considered assets, I should note that. However, the user wants to present it under "Required Skills" but the job lists them as optional. Maybe split into Required Skills and Preferred Skills? But the user's instruction is to provide Required Skills and Required Education & Certifications. Since the user's example includes "Required", maybe list the assets as part of the "Required Skills" even if they are optional. But that could be misleading. Alternatively, since the user says to exclude fluff, maybe present the required skills as per the job description, which is fundamental CS knowledge, analytical skills, communication. The other skills are considered assets but perhaps in the job summary mention them as preferred even though the user's format doesn't have a "Preferred Skills" section. However, the user's instructions only ask for Required Skills. So maybe include them under Required Skills. Alternatively, since the user might not want to include assets, but the original job description lists them, maybe include them in Required Skills with a note, but the user's instruction says to keep it factual and not add extra text. Hmm.
Wait, the user's example response for "Key Responsibilities" includes things that are in the job description, even if they are listed as 'may perform'. The example includes them as part of the key responsibilities. Similarly, for the skills, even if they are 'considered an asset', the user might want to include them as part of the required skills. But in the job description, they are not stated as required. So, perhaps better to list the required skills as those explicitly stated as required, and under key responsibilities, include the actual tasks, even if some are optional. For example, the job says "foundational knowledge... is required" and the other tools are assets. So in Required Skills, list the foundational knowledge, analytical, problem-solving, communication. Under the Responsibilities, include the use of cloud, GitOps, etc., but note that they are considered assets. However, the user's instruction says to exclude fluff and to be concise, so perhaps just list the required skills and then in the responsibilities include the tools as part of the tasks. But the user wants the "Required Skills" section. Since the job says that experience with Go, Python, Terraform, etc., is considered an asset, but not required, perhaps