Cloud Platform Infrastructure Engineer
Emerson · Austin, TX · 3 wk ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the job description.
Content:
- Intro: "Job Description If you are a Cloud Platform Infrastructure Engineer professional looking for an opportunity to grow your career, this role offers an exciting opportunity to contribute to innovative cloud-native solutions across Emerson. You will be based in Austin, TX, and will work alongside a collaborative global team to design, build, and optimize infrastructure that enables Emerson’s digital transformation."
- Then "IN THIS ROLE, YOUR RESPONSIBILITIES WILL BE:" followed by list:
Build, optimize, and manage cloud-native systems such as Kubernetes clusters and cloud resources
Document, maintain, improve, and validate work products
Participate in agile development process as part of a scrum team including planning, retrospectives, and continuous improvement
Coordinate and participate in cyber-security reviews
Coordinate and participate in architecture reviews
Work with global team to execute project initiatives
- Then "WHO YOU ARE:" paragraph describing traits.
- Then "FOR THIS ROLE, YOU WILL NEED:" list:
Bachelor’s degree in Computer Science or any STEM-related degree
5+ years of experience with large-scale infrastructure systems in a production environment
Proficiency in modern programming and scripting languages such as Go, Python, Bash, C#, Java, JavaScript/TypeScript, or others.
Proficiency with Kubernetes (cluster lifecycle, networking, upgrades) and containerization technologies like Docker.
Experience with infrastructure as code (IaC) tools such as Terraform.
Experience working within an Agile development framework.
Authorized to work in the United States without sponsorship now and in the future
Individuals with temporary visas such as E, F-1 (including those with OPT or CPT), H-1, H-2, L-1, B, J or TN, or who need sponsorship for work authorization now or in the future, are not eligible for hire.
- Then "PREFERRED QUALIFICATIONS THAT SET YOU APART:" list:
Advanced training in cloud services and configuration management (Azure, AWS, GCP).
Strong understanding of network architecture and security protocols.
Experience optimizing performance and scalability in infrastructure systems.
Knowledgeable in service discovery and load-balancing technologies.
Experience with GitOps tools, such as Argo CD or Flux.
Proficiency in DevSecOps CI/CD automation environments.
Expertise in backup and disaster recovery strategies within a cloud setting.
Experience with the Scaled Agile Framework (SAFe).
- Then "Our Culture & Commitment to You" paragraph about benefits: mention market-leading 401(k) and profit-sharing plan, variety of medical insurance plans, dental and vision coverage, family formation benefits, paid parental leave (maternal and paternal), Employee Assistance Program, tuition reimbursement, employee resource groups, recognition, flexible time off plans inclusive of vacation, holiday, sick leave. Also mention culture prioritizes work-life balance, flexible time off plans.
- Then "Learn more about our Culture & Values and about Diversity, Equity & Inclusion at Emerson ." (maybe ignore as boilerplate? It's about culture but not benefits; but we can include as part of About the role? Might be considered culture but not needed. We can include as part of About the role or maybe as a separate section? The instruction: include a section only when posting has real specific content for it. We have content about benefits, culture, training programs. Could create sections: About the role (intro), Responsibilities, Requirements (maybe combine required qualifications), Qualifications (preferred), Skills (maybe list of technical skills?), Benefits (benefits description), Pay (none), Schedule (none). Since no explicit pay or schedule, we should not create those sections.
We need to decide mapping:
- About the role: intro paragraph (first paragraph). Could also include location Austin, TX and global team.
- Responsibilities: list as above.
- Requirements: maybe the "FOR THIS ROLE, YOU WILL NEED:" list (required qualifications). Could also include work authorization statement.
- Qualifications: "PREFERRED QUALIFICATIONS THAT SET YOU APART:" list.
- Skills: maybe combine technical skills from requirements and preferred? But we already have those in Requirements and Qualifications. Could create a Skills section summarizing technical proficiencies (programming languages, Kubernetes, IaC, Agile, etc.) but that would duplicate. Better to not create Skills if content already covered; but we could still create a Skills section if we have specific skill list not elsewhere. However we have those in Requirements and Qualifications. To avoid duplication, maybe we skip Skills section.
- Benefits: paragraph about benefits (401k, medical, dental, vision, family formation, parental leave, EAP, tuition reimbursement, employee resource groups, recognition, flexible time off, work-life balance). Also mention culture & commitment to you.
- Pay: none -> omit.
- Schedule: none -> omit.
We must not include boilerplate like EEO, legal, accessibility, etc. Also must not include "Learn more about our Culture & Values and about Diversity, Equity & Inclusion at Emerson ." That's maybe part of culture but could be considered boilerplate? It's a link; but it's still substantive? It's a referral; but we can keep as part of About the role or Culture? Might be considered not essential; but we can keep it as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more about our Culture & Values and about Diversity, Equity & Inclusion at Emerson ." is not exactly EEO but it's a link to culture; could be considered part of culture description. I'd keep it as a sentence in About the role or maybe in a separate Culture section but we don't have a heading for Culture; we could incorporate into About the role.
Also there is a section "Our Culture & Commitment to You" which we already used for benefits. There's also later "About Us WHY EMERSON Our Commitment to Our People ..." which is more boilerplate about company mission; could be considered boilerplate but also substantive about company values. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" section is likely boilerplate corporate description; but it's not explicitly listed as to remove. However it's likely generic marketing; but we might keep it as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine the company description into About the role as well.
But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the details about Emerson's mission, etc. However that might be considered boilerplate but it's still substantive about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove generic company description. So we should keep it.
Thus About the role could include: initial paragraph about role, location, global team, plus the "About Us" section describing Emerson's mission, etc. Also the "Learn more about our Culture & Values and about Diversity, Equity & Inclusion at Emerson ." could be included.
We need to avoid duplication: there is also "Our Culture & Commitment to You" which we used for benefits; there is also later "Our training programs and initiatives focus on end-to-end development..." That's about training programs; could be part of Benefits or maybe a separate section like Development opportunities. But we don't have a heading for Training; we could incorporate into Benefits or About the role. Since we have limited headings, we could add a section "Benefits" that includes benefits and also training programs? But the instruction says include a section only when posting has real specific content for it. The training programs paragraph is substantive; we could include it under Benefits or maybe under a separate section like "Development" but not in allowed headings. Allowed headings are only those listed. So we must fit into those headings. Could put training info under Benefits (as part of employee development) or under About the role (as part of company offerings). Probably better to put under Benefits as it's about employee benefits and development.
Thus Benefits section will include: market-leading 401(k) and profit-sharing plan, medical insurance plans, dental and vision coverage, family formation benefits, paid parental leave (maternal and paternal), Employee Assistance Program, tuition reimbursement, employee resource groups, recognition, flexible time off plans (vacation, holiday, sick leave), work-life balance, culture prioritizes work-life balance, training programs (face-to-face and virtual training, mentorship and coaching, project management, on-the-job training). Also mention commitment to diversity, equity, inclusion.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML:
About the role
... (intro + location + global team + company description + culture/values link + maybe training? but training we put in Benefits).
Responsibilities
- ... ...
Requirements
- Bachelor’s degree in Computer Science or any STEM-related degree
- 5+ years of experience with large-scale infrastructure systems in a production environment
- Proficiency in modern programming and scripting languages such as Go, Python, Bash, C#, Java, JavaScript/TypeScript, or others.
- Proficiency with Kubernetes (cluster lifecycle, networking, upgrades) and containerization technologies like Docker.
- Experience with infrastructure as code (IaC) tools such as Terraform.
- Experience working within an Agile development framework.
- Authorized to work in the United States without sponsorship now and in the future.
- Individuals with temporary visas such as E, F-1 (including those with OPT or CPT), H-1, H-2, L-1, B, J or TN, or who need sponsorship for work authorization now or in the future, are not eligible for hire.
Qualifications
- Advanced training in cloud services and configuration management (Azure, AWS, GCP).
- Strong understanding of network architecture and security protocols.
- Experience optimizing performance and scalability in infrastructure systems.
- Knowledgeable in service discovery and load-balancing technologies.
- Experience with GitOps tools, such as Argo CD or Flux.
- Proficiency in DevSecOps CI/CD automation environments.
- Expertise in backup and disaster recovery strategies within a cloud setting.
- Experience with the Scaled Agile Framework (SAFe).
Benefits
- Market-leading 401(k) and profit-sharing plan
- Variety of medical insurance plans, with dental and vision coverage
- Family formation benefits
- Paid parental leave (maternal and paternal)
- Employee Assistance Program
- Tuition reimbursement
- Employee resource groups
- Recognition programs
- Flexible time off plans inclusive of vacation, holiday, and sick leave
- Work‑life balance focus
- Training and development opportunities: face‑to‑face and virtual training, mentorship and coaching, project management, on‑the‑job training
- Commitment to diversity, equity, and inclusion