Manager, Cloud Platforms

We need to output HTML fragment with headings

for 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 as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The introductory paragraph(s) describing role: "As the Manager, Cloud Platforms at Phillips 66, you will lead the strategy, design, delivery, and operational support of shared cloud platforms that help teams safely and efficiently use Azure and AWS. You will shape standards and reusable services, strengthen reliability and security, and guide a team that enables technology delivery across the company. This is an opportunity to influence cloud adoption at enterprise scale while building practical, resilient, and cost-conscious platform capabilities. At Phillips 66, Lead Forward is our leadership approach..." This is about role and leadership approach. Could be "About the role". We'll include that. - Responsibilities: The "What You'll Do" bullet list. We'll list each bullet as

. - Requirements: The "What You'll Bring - Required" bullet list: Legally authorized to work..., Bachelors degree..., 3 or more of experience..., 3 or more years of experience planning and managing resources or leading teams. We'll include. - Qualifications: Possibly "What Makes You Stand Out - Preferred" list. Could be Qualifications or Skills. The instruction says use headings for Qualifications, Skills, Benefits, Pay, Schedule. We can treat "What Makes You Stand Out - Preferred" as Qualifications or Skills. Since it's a list of preferred experience, we could put under Qualifications. Or we could split: Qualifications (preferred) and Skills (maybe some overlapping). But we should avoid thin sections. Better to combine preferred experience into a single "Qualifications" section (or "Skills"). We need to decide: The posting includes both required and preferred. Required we can put under Requirements. Preferred we can put under Qualifications (or Skills). Since they are experience/skills, maybe Qualifications. - Benefits: The "Total Rewards Benefits" section lists benefits: Annual Variable Cash Incentive Program (VCIP) bonus, 8% 401k company match, Cash Balance Account pension, Medical, Dental, and Vision benefits with annual company contribution to HSA for employees on HDHP, Total well-being programs and incentives, including Employee Assistance Plan, well-being reimbursement, and backup family care services. Also mention "Learn more about Phillips 66 Total Rewards." We'll include those as list. - Pay: The "Compensation Range" section: base salary range $160,200 – $195,800. Also mention pay transparency etc. We'll include that as

maybe. - Schedule: Not mentioned. No schedule info. So we should NOT include Schedule section. We must not include boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive info. Ensure we don't invent or summarize away detail. Use

for prose,

• for lists. We must not include headings with filler text. So only include sections with content. Thus output:

  About the role

  ... (the paragraph(s) about role and leadership approach).

  Responsibilities

  • Lead cloud platform strategy and roadmaps for Azure and AWS, aligned with approved enterprise and stream architecture, service delivery, lifecycle planning, and business needs.
  • Translate enterprise and stream architecture into secure, reusable cloud platform patterns covering connectivity, identity, compute, storage, automation, resiliency, and operational services
  • Establish platform engineering standards, reusable patterns, infrastructure-as-code automation, self-service capabilities, and onboarding guidance.
  • Govern cloud adoption through security guardrails, policy, tagging, access, secrets management, compliance controls, and technical-debt reduction.
  • Drive reliability, availability, performance, observability, and operational excellence using service metrics, monitoring, alerting, incident readiness, and continuous improvement.
  • Coordinate cross-functional delivery and integration across DevOps, security, infrastructure, identity, application, and vendor teams, serving as a senior escalation point for complex issues.
  • Manage cloud platform programs through planning, prioritization, resource coordination, change execution, and outcome measurement, including migrations, upgrades, deprecations, disaster recovery, and business continuity.
  • Improve cost visibility and optimization through FinOps practices, and support budget planning and vendor relationships as needed.
  • Lead, coach, and develop team members by setting priorities, building capability, holding the team accountable for results, and removing barriers to delivery.

  Requirements

  • Legally authorized to work in the job posting country
  • Bachelors degree or equivalent
  • 3 or more years of experience in cloud, infrastructure, platform engineering, or related disciplines
  • 3 or more years of experience planning and managing resources or leading teams

  Qualifications

  • Experience leading enterprise cloud platforms in a large, distributed environment
  • Experience with FinOps, cost management, forecasting, and cloud optimization
  • Familiarity with hybrid cloud patterns and shared platform operating models
  • Experience with disaster recovery, business continuity, and resiliency planning for cloud services
  • Cloud certifications such as AWS Solutions Architect, Azure Administrator, or equivalent
  • Experience supporting regulated, security-conscious, or operationally critical environments
  • Experience with enterprise integration patterns, API gateways, Azure platform services, REST services, or similar cloud connectivity technologies
  • Hands-on experience with Azure and AWS
  • Experience with cloud architecture, networking, identity, security, automation, infrastructure as code, and enterprise operational support
  • Experience with DevOps practices, reusable platform patterns, and cloud governance
  • Experience with observability and reliability practices, including logging, metrics, alerting, incident response, and service health management
  • Experience with cloud security controls, least-privilege access, policy guardrails, and secrets management

  Benefits

  • Annual Variable Cash Incentive Program (VCIP) bonus
  • 8% 401k company match
  • Cash Balance Account pension
  • Medical, Dental, and Vision benefits with an annual company contribution to a Health Savings Account for employees on HDHP
  • Total well-being programs and incentives, including Employee Assistance Plan, well-being reimbursement, and backup family care services

  Pay

  This position has a base salary range of $160,200 – $195,800. At Phillips 66, we are committed to pay transparency and competitive, equitable compensation. Each role is assigned a salary grade with a defined pay range, benchmarked against industry peers. Where a candidate offer falls within the posted range depends on the candidate's experience, skills, and alignment with the role’s requirements. Offers are made to ensure internal equity and market competitiveness. Our compensation programs are designed to reward performance and support career growth.

  We must not include Schedule. Check for any duplicated lines: Ensure we didn't repeat any content inadvertently. Check that we preserved all substantive info: The introductory paragraphs about role and leadership approach: we included them in About the role. Did we miss any sentences? Let's capture the exact text: "As the Manager, Cloud Platforms at Phillips 66, you will lead the strategy, design, delivery, and operational support of shared cloud platforms that help teams safely and efficiently use Azure and AWS. You will shape standards and reusable services, strengthen reliability and security, and guide a team that enables technology delivery across the company. This is an opportunity to influence cloud adoption at enterprise scale while building practical, resilient, and cost-conscious platform capabilities. At Phillips 66, Lead Forward is our leadership approach. It defines how leaders show up, make decisions, and support their teams while delivering results in a complex, fast‑changing environment. Leaders at this level focus on setting clear direction, building trust, and helping their teams succeed. You’re expected to act with integrity, make timely and thoughtful decisions, and take ownership of outcomes while supporting collaboration across teams. This role is about leading people well, even when priorities change or the path forward isn’t always clear." We need to include all that. We'll put in a single

  maybe with line breaks? It's okay as one paragraph. Now check responsibilities list: we captured each bullet. Ensure we didn't miss any: The original list: - Lead cloud platform strategy and roadmaps for Azure and AWS, aligned with approved enterprise and stream architecture, service delivery, lifecycle planning, and busniess needs. (typo busniess -> business but we keep as is? Should we preserve exactly? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep the typo? It's part of the posting. We'll keep "busniess needs" as is. - Translate enterprise and stream architecture into secure, reusable cloud platform patterns covering connectivity, identity, compute, storage, automation, resiliency, and operational services - Establish platform engineering standards, reusable patterns, infrastructure-as-code automation, self-service capabilities, and onboarding guidance. - Govern cloud adoption through security guardrails, policy, tagging, access, secrets management, compliance controls, and technical-debt reduction. - Drive reliability, availability, performance, observability, and operational excellence using service metrics, monitoring, alerting, incident readiness, and continuous improvement. - Coordinate cross-functional delivery and integration across DevOps, security, infrastructure, identity, application, and vendor teams, serving as a senior escalation point for complex issues. - Manage cloud platform programs through planning, prioritization, resource coordination, change execution, and outcome measurement, including migrations, upgrades, deprecations, disaster recovery, and business continuity. - Improve cost visibility and optimization through FinOps practices, and support budget planning and vendor relationships as needed. - Lead, coach, and develop team members by setting priorities, building capability, holding the team accountable for results, and removing barriers to delivery. We have all. Requirements: The original: "What You'll Bring - Required Legally authorized to work in the job posting countryBachelors degree or equilvalent3 or more of experience in cloud, infrastructure, platform engineering, or related disciplines3 or more years of experience planning and managing resources or leading teams" There are missing spaces and typos. We need to preserve substantive info but we can format nicely? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say we must keep exact formatting, but we should not change the meaning. Adding spaces and fixing typos could be considered altering detail? The typos are part of the posting but they are likely errors. However, "preserve ALL substantive information" means we should not lose any info; correcting typos doesn't lose info, but might be considered altering the original text. Safer to keep the exact wording? But the text as given is jammed: "Legally authorized to work in the job posting countryBachelors degree or equilvalent3 or more of experience in cloud, infrastructure, platform engineering, or related disciplines3 or more years of experience planning and managing resources or leading teams". That's hard to read. We could add spaces for readability but not change words. The instruction says "do NOT invent or summarize away detail". Adding spaces is not inventing detail; it's just formatting. I think it's okay to add spaces for readability. However, we must be careful not to "summarize away detail". Adding spaces doesn't remove detail. I'll add spaces and line breaks. Thus each bullet: - Legally authorized to work in the