Sr. Cloud Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes a description about McKesson and then "Key Responsibilities" etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Content: - Intro paragraph about McKesson: "McKesson is an impact-driven...". That's about the company, not necessarily "About the role". Could be considered "About the role"? Usually "About the role" is description of the job. The posting includes "What you do at McKesson matters...". That's more about culture. Might be considered "About the role"? But we need to decide. We have "Key Responsibilities" heading then a list of responsibilities (multiple paragraphs). So we will have a Responsibilities section with

• items. Then "Minimum Requirements" heading then list of requirements. That could be Requirements section. Then "Technical Skills" heading then list of skills. Could be Skills section. Then "Certifications & Education" heading then list. Could be Qualifications section? Usually Qualifications includes education and certifications. So we can put that under Qualifications. Then "About McKesson Medical-Surgical" paragraph describing the subsidiary. That's more about the company, maybe not needed as a section. Could be part of About the role? But we already have intro about McKesson. Might combine into About the role? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include About the role if we have content. The intro paragraphs about McKesson and culture could be considered About the role. We'll include that as About the role. Then we have "Our Base Pay Range for this position $115,300 - $192,100". That's Pay info. So we need a Pay section with that content. Benefits: The posting mentions "We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards." and "In addition to base pay, other compensation, such as an annual bonus or long-term incentive opportunities may be offered." Also "For more information regarding benefits at McKesson, please click here." That's vague but we have some benefits mention. However we should only include Benefits section if posting has real specific content. It mentions competitive compensation package, annual bonus, long-term incentive opportunities. That's somewhat specific but not detailed. Might still count as Benefits. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here we have some specifics: competitive compensation package, annual bonus, long-term incentive opportunities. That's not placeholder. So we can include Benefits section with that info. Schedule: No mention of schedule (full-time, part-time, remote). Not present, so omit Schedule. We must not include Job ID etc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, requirements, technical skills, certifications & education, pay, benefits, about the role. We need to format as HTML fragment: use

  for each section heading, then content: either

  for prose,

  • for lists. We need to ensure we don't repeat job title as heading. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the scam warning, EEO statements, etc. Also remove the "Join us at McKesson!" maybe? That's application instruction? It's a call to action; maybe considered boilerplate. Safer to remove. Also remove the "Our Base Pay Range for this position $115,300 - $192,100" is pay info, keep. Remove the "For more information regarding benefits at McKesson, please click here." That's a link instruction; maybe considered application instruction? It's about benefits; but it's a directive to click. Might be considered application instruction? It's not exactly applying; but it's a link. Might be okay to keep as part of benefits? However it's a generic instruction; maybe we should drop it as it's not substantive benefit detail. We'll keep the benefit description before that. We also need to drop the "McKesson has become aware of online recruiting-related scams..." etc. That's scam-warning boilerplate; remove. Also remove the EEO paragraphs. Also remove "Note that McKesson does rely on a virtual assistant (Gia) for certain recruiting-related communications with candidates." etc. That's also part of scam warning; remove. Also remove "McKesson job postings are posted on our career site: careers.mckesson.com." That's application instruction; remove. Also remove "McKesson is an Equal Opportunity Employer" etc. Also remove "If you need a reasonable accommodation..." etc. Also remove "Join us at McKesson!" at end. Now we need to extract the substantive content. Let's copy the posting and extract. Original text: "McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care. What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you. Key Responsibilities GCP Foundation, Landing Zones & Infrastructure-as-Code Cloud Architecture & Automation: Design, build, and maintain enterprise GCP infrastructure using Terraform/Terragrunt, enforcing Infrastructure-as-Code (IaC) and GitOps practices for all cloud environments.Landing Zone Governance: Own the configuration and security baseline of GCP Organization structures, Projects, Folders, Resource Hierarchies, and IAM roles/permissions using least-privilege principles.Network & Hybrid Connectivity: Configure and maintain GCP Shared VPCs, VPC Service Controls (VPC-SC), Cloud Interconnect, Cloud VPN, Cloud DNS, Firewall Rules, and load balancers to support secure, low-latency hybrid connectivity between GCP services, Apigee X, and Oracle Exadata / JDE ERP environments. Apigee X & Oracle Exadata / JDE ERP Integration Support Apigee X Platform Engineering: Provision, configure, and maintain Apigee X runtime environments, API gateways, PSC (Private Service Connect) attachments, and load balancers in accordance with enterprise security baselines.Oracle Exadata & JDE Interconnect: Engineer and maintain high-performance, resilient hybrid network topology (Cloud Interconnect/Partner Interconnect) linking GCP applications and Apigee gateways directly to Oracle Exadata database systems and JDE backend services.API Security & Traffic Controls: Work alongside Integration Architects to enforce mTLS, VPC Service Controls, rate limiting, and secure endpoints across Apigee X, GCP microservices, and Exadata/JDE integration boundaries. Containerization, Compute & Serverless GKE & Kubernetes Management: Deploy, secure, and operate Google Kubernetes Engine (GKE) clusters powering enterprise Spring Boot microservices, AI workloads, and internal developer platforms.Serverless Execution: Configure and support serverless workloads using Cloud Run, Cloud Functions, and App Engine, optimizing performance and latency for transactional database and API flows.Platform Reliability: Build automated deployment pipelines using GitHub Actions or Cloud Build to support seamless infrastructure provisioning and application cutovers. FinOps & Cloud Cost Optimization Cost Allocation & Visibility: Establish FinOps standards across GCP projects, implementing label/tagging enforcement, budget alerts, and showback/chargeback reporting for business units.Resource Tuning: Analyze resource utilization (Compute Engine, GKE, Cloud SQL, BigQuery) to right-size instances, optimize committed use discounts (CUDs), and eliminate unused infrastructure. Security, Compliance & Observability Cloud Security Posture: Implement CISO security standards, including GCP Secret Manager, KMS, mTLS, SAST/DAST container vulnerability scanning, and binary authorization.Observability Baseline: Build and maintain centralized logging, monitoring, and distributed tracing across all GCP environments, Apigee instances, and Exadata/JDE connectivity paths using Google Cloud Operations Suite (Cloud Logging, Cloud Monitoring, Cloud Trace). Minimum Requirements Experience: 10+ years of enterprise IT/infrastructure experience, with at least 4+ years dedicated to designing, engineering, and operating production environments on Google Cloud Platform (GCP).Apigee & Database/ERP Interconnect: Hands-on experience provisioning and supporting Apigee X / Apigee Edge environments and managing hybrid interconnectivity to high-performance database infrastructure (Oracle Exadata) and enterprise ERP systems (JD Edwards).IaC & Automation Mastery: Expert-level hands-on skills with Terraform, Git, and CI/CD pipelines (GitHub Actions, Cloud Build, or GitLab CI).Kubernetes & Containers: Strong experience deploying and managing production Google Kubernetes Engine (GKE) clusters and Docker containerized applications.GCP Networking & Security: Deep understanding of GCP VPC networking, Shared VPCs, Private Service Connect (PSC), VPC Service Controls, Cloud Interconnect, IAM, and GCP security controls.Scripting: Proficiency in Python, Bash, or Go for cloud automation and tooling development.FinOps Understanding: Practical experience implementing cloud cost optimization, quota management, and resource right-sizing strategies. Technical Skills Google Cloud Services: GKE, Cloud Run, Cloud SQL, BigQuery, Cloud Storage, VPC Service Controls, Secret Manager, IAM, Cloud Logging, Cloud Monitoring, Cloud Trace.API Management & Hybrid Database/ERP: Apigee X, Apigee Edge, Private Service Connect (PSC), Cloud Interconnect, Oracle Exadata database connectivity, JD Edwards (JDE) hybrid interconnectivity.Infrastructure-as-Code: Terraform, Terragrunt, Helm, Docker, Kubernetes.Networking & Security: Shared VPC, Cloud VPN, Cloud Interconnect, Firewalls, mTLS, OAuth 2.0, KMS, Least Privilege IAM.CI/CD & DevOps: GitHub Actions, Cloud Build, GitHub Advanced Security (GHAS), Git, Linux/Unix administration.Scripting & Tooling: Python, Bash, Go, gcloud CLI. Certifications & Education Certifications:Google Professional Cloud Architect or Google Professional Cloud DevOps Engineer (required or to be obtained within 6 months).Education: Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related technical field, or equivalent practical experience. About McKesson Medical-Surgical McKesson Medical-Surgical (MMS), which is expected to become Wellverse in early 2027, is a subsidiary and publicly reported segment of the McKesson Corporation. MMS distributes medical-surgical supplies, pharmaceuticals, diagnostic equipment and supplies, along with other solutions and services to virtually every type of healthcare setting and provider outside of the traditional hospital. These markets – often referred to as Alternate Care or Non-Acute Care – include physician offices, surgery centers, long-term care providers, laboratories, home health and hospice agencies, health systems, government facilities and online marketplaces and retailers. Alternate Care markets are growing rapidly and MMS is proud to be a leader in this space. With a team of approximately 8,000 employees, a network of 15 distribution centers and approximately 900 delivery vehicles, we collaborate with more than 2,200 leading manufacturers and serve over 200,000 customer accounts across the U.S. Our catalog includes more than 270,000 SKUs of branded