Sr. Cloud & Infrastructure Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: Intro: "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for a Sr. Cloud & Infrastructure Engineer to join our ever evolving IT Infrastructure team and help shape the future of global commerce. The primary responsibility of this role is to design, optimize, support and further automate the cloud infrastructure supporting our business platforms, and to continuously improve the platforms to meet the evolving needs of Global Payments." That's prose about role. Could be "About the role" section. Then "What you’ll own:" list of responsibilities. Then "What you’ll bring:" list of requirements/qualifications. Then "It’s a bonus if you have:" list of bonus skills. Then "About The Team" paragraph. Then "What makes a Globalpayer?" paragraph. Then "Does this sound like you? Then you sound like a Globalpayer. Apply now to take your career global." (application instruction, remove) Then "Our Perks - What We’ll Bring For You" with bullet list of benefits. Then "Applicant must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; We will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)." This is a requirement about work authorization, could be part of Requirements. Then "Diversity and EEO Statements ..." remove. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Pay or Schedule info. So we should NOT create those sections. We have Benefits: list under "Our Perks - What We’ll Bring For You". So Benefits section. We have Responsibilities: "What you’ll own:" list. We have Requirements/Qualifications/Skills: The posting lumps "What you’ll bring:" includes degree, experience, etc. Also "It’s a bonus if you have:" list. Also "About The Team" maybe not needed. Could treat "What you’ll bring:" as Requirements and Qualifications combined. But we need separate sections if content exists. We could split: Requirements (mandatory) and Qualifications (maybe same) and Skills (bonus). However we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But the instruction says use headings for those categories if they have content. We could have Requirements (mandatory), Qualifications (maybe same as Requirements?), Skills (bonus). But we risk duplication. Better: Use Requirements for mandatory items (degree, experience, etc.), Skills for bonus items (network principles, monitoring, storage, communication skills, etc.). Qualifications maybe not needed if same as Requirements. But we could still include Qualifications with same content? Might be redundant. We could treat "What you’ll bring:" as Requirements (including degree, experience, etc.) and "It’s a bonus if you have:" as Skills. Then we could omit Qualifications section (or combine with Requirements). The instruction: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements, Skills, Benefits. That's five sections. We need to ensure we don't create empty sections. Let's extract content precisely. About the role: The introductory paragraph(s) before "What you’ll own:" includes first two sentences? Actually: "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for a Sr. Cloud & Infrastructure Engineer to join our ever evolving IT Infrastructure team and help shape the future of global commerce. The primary responsibility of this role is to design, optimize, support and further automate the cloud infrastructure supporting our business platforms, and to continuously improve the platforms to meet the evolving needs of Global Payments." We'll put that in

. Responsibilities: list under "What you’ll own:" each bullet. Let's capture each bullet: - Formulate and carry-out business impacting cloud infrastructure-related designs, primarily in AWS and Azure, to meet the strategic direction and standards of the company and the cloud team, including ancillary services and on-premises services and hybrid solutions. - Support automated methodologies for build activities, such as for resource provisioning, hardening, leveraging PaaS offerings, load balancer rules and firewall policies. - Partake in ownership of engineering efforts, including new solutions design and optimization, for multiple engineering projects, concurrently, working closely with the business owners, product teams and applications teams. - Maintain installation and configuration procedures, and drive automation around these areas - Provide cross-training and mentoring with other members of the team. - Develop shared knowledge of leveraged tools on the team, eliminating single points of knowledge and dependencies. - Work with management and technical peers to establish and support technical policies and procedures. - Continuously provide procedures to operational teams and work with these teams to ensure details are up-to-date, accurate and understood - Drive compliance and security efforts related to systems managed by the team - Support and continuously improve upon methods to improve stability and availability of infrastructure services - Work with the Project Managers and Infrastructure Coordinators on project progress, issues and solutions We need to preserve all. Requirements (mandatory): from "What you’ll bring:" list: - Bachelor’s degree in Computer Science or similar field, or equivalent work experience. - Design and operations experience in both AWS and Azure environments. - 5-7 years of systems administration, design, engineering or commensurate IT technical experience. - Experience with enterprise repositories, namely GitHub Enterprise, as well as deployment management and CI/CD pipelines, namely through Jenkins and Harness. - Experience with multiple active scripting languages and strong IaC, including and especially Terraform, Ansible, PowerShell and Python. - Strong knowledge of multiple flavors of Linux and Windows Server, along with the experience in administering these systems through scripted/automated processes. - Strong knowledge with infrastructure services and systems, including Active Directory, DHCP, DNS, DFS and Group Policy (automation, setup, implementation, optimization, etc.) - Understanding of the workings and operation of virtual environments, including VMware ESXi, vCenter, vCAC, VDIs, etc.) - Working knowledge of implementing automation orchestration across all life cycle environments - Understanding of configuration management and software deployment principles (experience with one or more configuration management and/or software deployment systems preferred) Also the work authorization requirement: "Applicant must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; We will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)." This is a requirement; we can include in Requirements. Skills (bonus): from "It’s a bonus if you have:" list: - Experience with network principles and architecture - Experience with enterprise monitoring solutions - Experience with storage technologies and principles and SANs (e.g. Pure, Netapp, EMC) - Excellent communication skills are a must, such as to lead design discussions, planning sessions and triage. - A track record and understanding of what it means for full ownership of task, project and responsibilities - Ability to work independently, as well as part of a team. - Analytical and problem-solving skills; ability to demonstrate a proven troubleshooting methodology - Willing to work off-hours, including as part of an on-call schedule and during project release windows - Willingness to provide innovative ideas and solutions, even when they may initially seem unpopular - Possess and demonstrate good organization skills, task and time management skills, while understanding the importance of good work/life balance Also maybe "About The Team" paragraph could be included in About the role or separate? But we already have About the role; we could add a short paragraph about team under About the role or maybe a separate section "About the Team". However instruction: only include sections when posting has real specific content. The "About The Team" paragraph is substantive. Could be a section "About the Team". But we have limited set of allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Team" is not in list, so we should not create a custom heading. We could incorporate that content into About the role or maybe into Responsibilities? Probably better to add to About the role as additional paragraph. Similarly "What makes a Globalpayer?" paragraph could be added to About the role or maybe to Benefits? Not exactly. Could incorporate into About the role as cultural description. We must not invent headings not in list. So we will embed those paragraphs into About the role. Thus About the role will contain multiple paragraphs: intro, team description, Globalpayer description. Now Benefits: list from "Our Perks - What We’ll Bring For You": - A competitive salary and benefits package that recognizes your contribution - Opportunities to grow your skills and build your career within a global business - Access to learning, development and on-the-job experiences that expand your expertise - A supportive, inclusive team environment where your ideas and input matter - Time to give back through community and charity initiatives - A global employee assistance programme to support your wellbeing - Recognition through a global platform that celebrates your achievements Also there is a link: https://jobs.globalpayments.com/en/why-global-payments/benefits/ - that's a URL; we could keep as part of benefits? It's a link to benefits page. Might be considered boilerplate? It's a link to more info; we could keep as part of benefits paragraph maybe. But it's not a benefit per se; it's a reference. Could be included as a link in benefits section. Probably safe to keep as a link. We must not include application instructions, EEO, etc. Now we need to output HTML fragment with headings

for each section, and

• for lists,

  for prose. We must not include or . Let's craft. Structure:

  About the role

  Intro paragraph(s).

  Team paragraph.

  Globalpayer paragraph.

  Responsibilities

  • ... each bullet

  Requirements

  • ... each mandatory bullet
  • ... work authorization bullet

  Skills

  • ... each bonus bullet

  Benefits

  • ... each benefit bullet
  • Learn more about our benefits
  We should not include Pay or Schedule. Check that we haven't missed any substantive content: The "What you’ll own:" list we captured. The "What you’ll bring:" list we captured. The "It’s a bonus if you have:" list we captured. The "About The Team" paragraph we embedded. The "What makes a Globalpayer?" paragraph we embedded. The "Our Perks - What We’ll Bring For You" list we captured. The work authorization requirement we added. Check for any other content: The initial invitation "Ready to take your career global? Make your mark at one of the biggest names in payments." included. Now ensure we didn't include any boilerplate like "Diversity and EEO Statements", "Applicant must be authorized..." we kept as requirement. Good. Now ensure we didn't