- Company Name
- Collibra
- Job Title
- Production Engineer
- Job Description
-
<think>
Okay, so the user wants me to normalize a job description into a concise job profile for matching purposes. Let me start by understanding the requirements. They mentioned excluding company details, location, benefits, and fluff. The output needs to be in English, even if the original is in another language, but here it's already in English. I need to focus on specific sections: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, and Required Education & Certifications. It should be factual, concise, and ATS-friendly, meaning no fancy words, just straightforward keywords.
First, the job title is clear: Production Engineer. The role summary should encapsulate the main purpose. The original description mentions being a bridge between development, operations, and stakeholders, driving continuous improvement. So maybe start with that. Role Summary: Bridge Development, Operations, and stakeholders to ensure seamless delivery of cloud services through automation and process improvements.
Next, Expectations. They provided some metrics for success, like within first month, third month, sixth month. But the user said to exclude fluff, so maybe just state the high-level expectations. Perhaps "Identify process improvements, build cross-team trust, and deliver measurable impact on DORA metrics."
Key Responsibilities: From the original, things like researching new technologies, integrating them, being a liaison, leading discussions, collaborating, participating in design reviews, using visual tools, supporting release automation, and infrastructure. Need to condense these into bullet points. Maybe group similar tasks together.
Required Skills: The job requires 5+ years in Release Engineering or DevOps, cloud platforms (AWS, Azure, GCP), CI/CD tools (Jenkins, GitLab CI, etc.), scripting (Python, Go, Bash), containerization (Docker, Kubernetes), IaC (Terraform), monitoring tools, and Elasticsearch experience. Education isn't specified, just certifications maybe if any. The original doesn't mention specific degrees or certifications, so maybe just note that a bachelor's is required if inferred, but the user said to exclude fluff, so maybe leave education blank unless stated. Wait, the job description mentions "You Have" which includes experience but not education. So Required Education & Certs might be "Bachelor’s degree in Computer Science or related field. Certifications in cloud platforms or DevOps (optional but preferred)." But the user said to exclude unless required. Since the original doesn't specify, maybe omit that unless I can infer. Wait, in the "You Are" section, they mention communication and problem-solving but not education. So maybe leave education as "Bachelor’s degree in Computer Science or related field." Even if not explicitly mentioned, sometimes it's standard. But the user says to exclude fluff. Hmm, tricky. Since the job description doesn't mention it, maybe omit it unless the user wants it. The instruction is to provide it, so if it's not there, maybe leave it blank? But the example might expect it. Maybe include it as a standard field, assuming that it's a common requirement. Alternatively, the user might prefer accuracy, so better to leave it out if not present. Let me check the original input again. The job description under "You Have" lists experience but not education. So no mention of education or certifications. Therefore, Required Education & Certifications might not be applicable. So perhaps leave it as "Bachelor’s degree in Computer Science or related field." Or maybe omit it. The user says to exclude company details, location, benefits, or fluff, so if it's not there, we don't add it. So perhaps leave that section blank. Wait, the user did include the example in the instruction: "Required Skills, Required Education & Certifications." So they expect those sections. So if the job description doesn't specify education, but in reality, it's common for such roles to require a degree, maybe it's okay to infer, but without explicit mention, better to omit. Wait, maybe the instruction says "Exclude company details, location, benefits, or fluff." If the job description doesn't mention education, perhaps it's not part of the required skills. But the user wants the summary to be factual. So maybe not include education if it's not stated. However, sometimes in ATS-friendly profiles, education is expected. Hmm. Maybe the user expects it even if not stated. But in the given example, the job description does have a "You Have" section, so perhaps the required skills are in there. Let me check again. The job description under "You Have" lists experience but not education. So the original doesn't specify education or certifications. Therefore, in the output, I should not add them unless the job requires it. So required education would be absent. But the user instructions specify to include it, so maybe leave it blank. Alternatively, maybe the user expects it as a standard field. This is a bit of a dilemma. Let me see. For the sake of completeness, I might include a standard education requirement if it's typical. However, since the user emphasizes factual and excludes fluff, better to omit it if not present. So, in the output, Required Education & Certifications: [None specified] or just omit the section? Wait, the user's instruction says "Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So even if not present, need to include those sections. If not mentioned, maybe write "None specified" or leave it empty. But the user might prefer the section to exist but be empty. Let me check the example they provided in the instruction. Looking back, the user provided an example input where they want the output in a specific format. Since the example job description doesn't include education, but the user included the education section as part of the output, maybe I should list it as "Bachelor’s degree in Computer Science or related field" if it's common for such a role. But given the user's instruction to keep it factual, perhaps not. Alternatively, if the original job post does not mention education, but in reality, such roles often require a degree, maybe include. This is tricky. Since the user's original job description does not mention education or certifications, perhaps the correct approach is to leave that section empty. However, to follow the format, maybe include "None specified." But the user's example might have included it. Alternatively, maybe the job description's "You Have" section requires 5 years of experience, so maybe the education is implied. Hmm. I think I'll proceed by including the bachelor's degree as a common requirement, even though the job description doesn't mention it explicitly, since it's a standard for such positions. Alternatively, maybe the user wants only what's in the job description. Given the strict instructions, perhaps safer to omit unless explicitly stated. Let's proceed with what's in the job description. The job description doesn't mention education, so I'll leave that section blank.
Let me compile all that. The job title is clear. Role Summary: Bridge between dev and ops, ensuring smooth delivery through automation. Expectations: Identify improvements, build trust, deliver metric impact. Key Responsibilities: Research tech, integrate into processes, lead discussions, collaborate, design reviews, use tools, support automation. Required Skills: 5+ years in relevant role, cloud platforms, CI/CD tools, scripting, containers, IaC, monitoring. Required Education: Not specified. Certifications: Not specified.
I need to make sure each section is concise and fits under 500 words. Also, the user wants it in a specific order: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. Let me check that I haven't missed anything. The job description mentions DevOps Engineer, but the title is Production Engineer. Maybe the summary should clarify that they might have DevOps responsibilities. Also, the job is remote, but the user says to exclude location. So no mention of that.
Now, putting it all together, making sure each section is factual, concise, and follows the structure. Avoid any markdown, just plain text. No explanations, just bullet points as specified. Let me verify each part again. Key responsibilities should be in bullet points but the user said to exclude markdown, so maybe use semicolons. Wait, the user's example shows bullet points with asterisks? The user's instruction says to output only the sections, but the example in the problem uses bullet points. However, the user's instruction says to output only the sections and exclude markdown, so perhaps use semicolons or commas. Let me check the exact instruction. The user says: "Provide a concise summary... Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications. Keep it factual, concise, ATS-friendly, and globally neutral. Do not add any introduction, explanation, or extra text." So, the format should be those sections in order, with each line as a separate entry. The example in the problem uses bullet points with asterisks, but the user says to output in English and exclude markdown. Wait, no, the user says "Output only:..." and "keep it factual, concise, ATS-friendly, and globally neutral." So perhaps structure each section with a label and the content, perhaps using commas or semicolons for separation. For example, for Key Responsibilities, list each as a separate line with a semicolon or something. But the user might expect bullet points. However, since markdown is to be excluded, perhaps use numbered or unnumbered lists with asterisks but without markdown. Hmm. Let me look at the example given in the user's instructions. The user provided an example in their instruction where they have sections like "Role Summary:..." followed by a brief paragraph. So probably each section is separated with labels, and the content is in sentences or bullet points without markdown. The user