Lead Cloud Engineer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions, contact info, privacy statement, stay connected. Keep substantive info.
We need to parse the posting.
Content:
- Intro about LyondellBasell: description of company, mission, etc. Could be "About the role"? Actually "About the role" maybe includes description of role and company? Usually "About the role" includes overview of role and maybe company. We'll include a section About the role with the introductory paragraphs about LyondellBasell and the role purpose.
- Responsibilities: bullet list from "A Day in the Life" and earlier description: "Implement, configure, and support cloud infrastructure solutions within Azure and AWS environments. Support daily cloud operations and production environments. Troubleshoot and resolve cloud-related incidents and service requests. Develop and maintain automation scripts and workflows. Support administration and maintenance of the enterprise GitHub environment. Assist with cloud migration and modernization initiatives. Participate in security, governance, and compliance activities. Collaborate with technical and business teams to support cloud requirements." Also earlier: "The Lead Cloud Engineer is responsible for supporting, implementing, and continuously improving the company cloud technology platforms across Microsoft Azure and Amazon Web Services (AWS). The role works closely with Cloud Services team members, application teams, infrastructure teams, security teams, and business stakeholders to deliver reliable, secure, and scalable cloud solutions. This position contributes to cloud infrastructure deployments, operational support, automation initiatives, and platform modernization efforts while developing expertise in enterprise cloud technologies and best practices. The Lead Cloud Engineer also assists in supporting the enterprise GitHub platform and contributes to governance, standardization, and automation initiatives." Could combine.
- Requirements: "You Bring This Value" bullet list: Bachelor degree in Computer Science, Information Technology, Engineering, or related field, or equivalent experience. 3 to 5 years of experience in cloud infrastructure, systems engineering, or related technology disciplines. Experience supporting production IT environments. Experience with Microsoft Azure and/or Amazon Web Services (AWS). Experience with scripting or automation tools such as PowerShell, Python, or Bash. Understanding of Infrastructure as Code concepts and tools.
- Qualifications: "Preferred Qualifications" list: Experience supporting both Azure and AWS environments. Experience with Terraform, Bicep, CloudFormation, or similar tools. Experience with GitHub Enterprise and GitHub Actions. Experience with container technologies such as Docker or Kubernetes. Relevant Azure, AWS, GitHub, or Terraform certifications.
- Skills: "Competencies" list: Drive Innovation Technical Skills Grow Capabilities Promote Inclusion Motivational Fit Build Partnerships Deliver Results. These are maybe competencies/skills. Could put under Skills.
- Benefits: "What We Offer" paragraph: environment encouraging personal and professional growth, rewarded for performance, possibility to work with specialists, extend network, competitive salary and benefits package, Global Remote Work Policy allows up to three days a week from home, commitment to DEI. So we have benefits: competitive salary and benefits package, remote work up to 3 days/week, DEI commitment, personal/professional growth, networking, working with specialists. We'll put as bullet list.
- Pay: Not explicitly stated; only "competitive salary". That's vague but maybe considered pay info? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "competitive salary and benefits package" - that is a statement about pay (competitive salary) but not specific number. Is that considered stating pay? It says "competitive salary". That is a statement about pay but not a specific figure. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salary". That's a statement about pay, albeit vague. Should we include Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include Pay with that statement. However also they say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that line.
- Schedule: The posting mentions "The Company's Global Remote Work Policy allows eligible employees the option to work up to three days a week from home." That's schedule/remote work info. Could be considered schedule. So we could include Schedule section with that detail.
But we already have Benefits section that could include remote work policy. However schedule is separate. Might be better to put remote work under Benefits or Schedule. Since they said schedule section only if posting actually states them. It does state remote work policy. So we could include Schedule.
But we need to avoid duplication. Let's decide: Benefits: competitive salary and benefits package, personal/professional growth, networking, working with specialists, DEI commitment. Schedule: remote work up to 3 days per week.
Pay: competitive salary (maybe redundant with benefits). Could combine pay and benefits? But they said separate headings allowed. However we could omit Pay if we consider salary part of benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, but also benefits package. Could we put both under Benefits? Probably okay. But to follow instruction, we could include Pay with the competitive salary line, Benefits with other benefits, Schedule with remote work. However that creates many thin sections. They said prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section that includes competitive salary and other benefits. Schedule separate maybe.
Let's think: The posting says: "In addition, we offer you a competitive salary and benefits package. The Company's Global Remote Work Policy allows eligible employees the option to work up to three days a week from home." So we have two statements: compensation and remote work. Could make Benefits section with both compensation and remote work? But remote work is schedule. However they said schedule section only if posting actually states them. It does state remote work policy. So we could have Schedule section with that line. Benefits section with competitive salary and benefits package, personal/professional growth, networking, DEI, etc.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule.
Now we need to format.
Use for each heading. Then content:
for prose,
- for lists.
We must not repeat job title as heading. No job ID.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details.
Let's extract details precisely.
About the role: Should include company description and role purpose.
Company description: "LyondellBasell is a leader in the global chemical industry creating solutions for everyday sustainable living. With a nearly 70-year legacy that includes a Nobel Prize in Chemistry and our proprietary MoReTec recycling technology, LYB is enabling a more sustainable future for generations to come. LYB develops high-quality and innovative products for applications ranging from sustainable transportation and food safety to clean water and quality healthcare. LYB places high priority on diversity, equity and inclusion and is Advancing Good with an emphasis on our planet, the communities where we operate and our future workforce. We're addressing the global challenges of ending plastic waste, taking climate action, and supporting a thriving society, while generating value for our customers, investors, and society."
Role purpose: "Come Join an Inclusive Team The Lead Cloud Engineer is responsible for supporting, implementing, and continuously improving the company cloud technology platforms across Microsoft Azure and Amazon Web Services (AWS). The role works closely with Cloud Services team members, application teams, infrastructure teams, security teams, and business stakeholders to deliver reliable, secure, and scalable cloud solutions. This position contributes to cloud infrastructure deployments, operational support, automation initiatives, and platform modernization efforts while developing expertise in enterprise cloud technologies and best practices. The Lead Cloud Engineer also assists in supporting the enterprise GitHub platform and contributes to governance, standardization, and automation initiatives."
We can combine into a paragraph or multiple paragraphs. Use
for prose. Responsibilities: list from "A Day in the Life" plus earlier responsibilities maybe overlapping. We'll combine unique items. List items: - Implement, configure, and support cloud infrastructure solutions within Azure and AWS environments. - Support daily cloud operations and production environments. - Troubleshoot and resolve cloud-related incidents and service requests. - Develop and maintain automation scripts and workflows. - Support administration and maintenance of the enterprise GitHub environment. - Assist with cloud migration and modernization initiatives. - Participate in security, governance, and compliance activities. - Collaborate with technical and business teams to support cloud requirements. - Supporting, implementing, and continuously improving the company cloud technology platforms across Microsoft Azure and Amazon Web Services (AWS). - Working closely with Cloud Services team members, application teams, infrastructure teams, security teams, and business stakeholders to deliver reliable, secure, and scalable cloud solutions. - Contributing to cloud infrastructure deployments, operational support, automation initiatives, and platform modernization efforts while developing expertise in enterprise cloud technologies and best practices. - Assisting in supporting the enterprise GitHub platform and contributing to governance, standardization, and automation initiatives. Some duplicates; we can keep unique but preserve all. Might be okay to keep as is but avoid redundancy. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep all statements, even if similar. But we can combine similar into one bullet if they are essentially same? That would be summarizing away detail? Might be considered summarizing. Safer to keep each distinct sentence as separate bullet. Let's list each distinct sentence from the text: From earlier paragraph: 1. supporting, implementing, and continuously improving the company cloud technology platforms across Microsoft Azure and Amazon Web Services (AWS). 2. works closely with Cloud Services team members, application teams, infrastructure teams, security teams, and business stakeholders to deliver reliable, secure, and scalable cloud solutions. 3. contributes to cloud infrastructure deployments, operational support, automation initiatives, and platform modernization efforts while developing expertise in enterprise cloud technologies and best practices. 4. assists in supporting the enterprise GitHub platform and contributes to governance, standardization, and automation initiatives. From "A Day in the Life": 5. Implement, configure, and support cloud infrastructure solutions within Azure and AWS environments. 6. Support daily cloud operations and production environments. 7. Troubleshoot and resolve cloud-related incidents and service requests. 8. Develop and maintain automation scripts and workflows. 9. Support administration and maintenance of the enterprise GitHub environment. 10. Assist with cloud migration and modernization initiatives. 11. Participate in security, governance, and compliance activities. 12. Collaborate with technical and business teams to support cloud requirements. We'll keep all 12 bullets. Requirements: list from "You Bring This Value": - Bachelor degree in Computer Science, Information Technology, Engineering, or related field, or equivalent experience. - 3 to 5 years of experience in cloud infrastructure, systems engineering, or related technology disciplines. - Experience supporting production IT environments. - Experience with Microsoft Azure and/or Amazon Web Services (AWS). - Experience with scripting or automation tools such as PowerShell, Python, or Bash. - Understanding of Infrastructure as Code concepts and tools. We'll keep as bullets. Qualifications: Preferred Qualifications list: - Experience supporting both Azure and AWS environments. - Experience with Terraform, Bicep, CloudFormation, or similar tools. - Experience with GitHub Enterprise and GitHub Actions. - Experience with container technologies such as Docker or Kubernetes. - Relevant Azure, AWS, GitHub, or Terraform certifications. Skills: Competencies list: - Drive Innovation - Technical Skills - Grow Capabilities - Promote Inclusion - Motivational Fit - Build Partnerships - Deliver Results We'll keep as bullets. Benefits: from "What We Offer": - environment where we encourage personal and professional growth - rewarded for your performance and results - possibility to work with specialist on all fields to develop innovative solutions and to extend your national and international network - competitive salary and benefits package - Company's Global Remote Work Policy allows eligible employees the option to work up