Sr Manager of Cloud and Platform Ops
Love's Travel Stops · Oklahoma City, OK · 1 mo ago
ManufacturingFull-time
We need to output HTML fragment with sections only when content exists. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
Given text includes "Benefits:" list. Also includes description of role (Welcome to Love's: The Sr. Manager...). That's about the role. Responsibilities: many bullet points under Major Responsibilities etc. Requirements: maybe Education And Experience. Qualifications: maybe Education And Experience? Actually Education And Experience is likely qualifications. Skills: there is a Skills section. Benefits: we have list. Pay: not explicitly stated (Competitive Pay mentioned under Benefits? Actually "Competitive Pay" appears in Benefits bullet list. So we have pay info: "Competitive Pay". That's a benefit but also could be Pay section. The instruction: include Pay section only if posting actually states them. It does state "Competitive Pay". So we can create a Pay section with that line. Schedule: there is "Hybrid work schedule: 4 workdays onsite...". So we have schedule info. So we can create Schedule section.
We must not repeat job title as heading. No Job ID etc.
We need to remove boilerplate: EEO etc. At end there is "Love's is an Equal Opportunity Employer. Veterans encouraged to apply." Remove.
Also remove duplicated lines.
We need to preserve all substantive info.
We need to format lists with
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
Given text includes "Benefits:" list. Also includes description of role (Welcome to Love's: The Sr. Manager...). That's about the role. Responsibilities: many bullet points under Major Responsibilities etc. Requirements: maybe Education And Experience. Qualifications: maybe Education And Experience? Actually Education And Experience is likely qualifications. Skills: there is a Skills section. Benefits: we have list. Pay: not explicitly stated (Competitive Pay mentioned under Benefits? Actually "Competitive Pay" appears in Benefits bullet list. So we have pay info: "Competitive Pay". That's a benefit but also could be Pay section. The instruction: include Pay section only if posting actually states them. It does state "Competitive Pay". So we can create a Pay section with that line. Schedule: there is "Hybrid work schedule: 4 workdays onsite...". So we have schedule info. So we can create Schedule section.
We must not repeat job title as heading. No Job ID etc.
We need to remove boilerplate: EEO etc. At end there is "Love's is an Equal Opportunity Employer. Veterans encouraged to apply." Remove.
Also remove duplicated lines.
We need to preserve all substantive info.
We need to format lists with - . For prose use
.
We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe Education And Experience?), Qualifications (maybe certifications?), Skills (list), Benefits (list), Pay (maybe just "Competitive Pay"), Schedule (Hybrid work schedule...).
But we must avoid thin sections. However we have substantive content for each.
Let's extract:
About the role: The paragraph starting "Welcome to Love's: The Sr. Manager of Cloud and Platform Operations leads the strategy..." That's a description. We'll put that in
.
Responsibilities: The bullet points under "Major Responsibilities" and subheadings like Leadership and Organizational Development, Strategy and Platform Modernization, Platform Engineering, Platform Operations, Database Administration, Financial and Vendor Management, Service Management and Continuous Improvement, Collaboration and Communication. We need to capture all duties. Could combine into a single list of responsibilities, preserving details. Might be long but okay.
We need to avoid repeating headings inside list? We'll just make a
with each responsibility as - . Could include sub-bullets? Might be okay to keep as plain text.
Requirements: Education And Experience section includes Education bullet and Experience bullet. Could treat as Requirements.
Qualifications: maybe certifications? But Education And Experience already includes certifications as plus. Could combine.
But we have separate Skills section.
We need to avoid duplication. Let's decide:
- About the role: intro paragraph.
- Responsibilities: all major responsibilities bullet points (the ones under Major Responsibilities and subpoints). We'll extract each bullet as a list item.
- Requirements: Education And Experience (Education bullet, Experience bullet). We'll put as list.
- Skills: Skills section (including Skills and Physical Demands, Technical Skills, etc). We'll put as list.
- Benefits: list given.
- Pay: "Competitive Pay" (maybe also mention "competitive pay" as benefit but we can put as Pay section with that line).
- Schedule: "Hybrid work schedule: 4 workdays onsite at the corporate office in Oklahoma City, and 1 workday remote (subject to change depending on business needs). Ability to be on-call and handle escalated situations outside normal business hours. Occasional travel to data center and field locations as required."
We must not include filler like "commensurate with experience". Not present.
Now we need to ensure we don't include boilerplate like "Our Culture ..."? That's substantive? It's about company culture; could be considered About the role? But it's not directly about role. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Our Culture" paragraph is not explicitly listed as boilerplate but could be considered company description. Might be okay to keep? It's not about the role but could be considered extra. However we already have About the role section; we could incorporate that culture paragraph into About the role? But the instruction: "Prefer a few substantive sections over many thin ones." The culture paragraph is substantive but not about role. Might be okay to include as part of About the role? But we already have About the role description; adding culture may be okay.
But we need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep the culture paragraph somewhere. Could add another section like "About the Company" but we only allowed headings from list. Not allowed to add other headings. So we must fit into allowed headings. Could put it under About the role as additional paragraph.
Thus About the role will have two paragraphs: the role description and the culture paragraph.
Now we need to ensure we don't include the EEO line at end.
Now let's extract details precisely.
Original text:
"Benefits: * Fuel Your Growth with Love's - company funded tuition assistance * Paid Time Off * 401(k) – 100% Match up to 5% * Medical/Dental/Vision Insurance after 30 days * Competitive Pay * Career Development * Welcome to Love's: The Sr. Manager of Cloud and Platform Operations leads the strategy, engineering, delivery, and operational performance of Love’s cloud and on-premises platform estate, and the administration of the enterprise database platforms that run on it. This position directly leads the Platform Engineering, Platform Operations, and Database Administration teams, and is accountable for the availability, security, scalability, and cost-effectiveness of the compute, storage, virtualization, cloud, and database services the business depends on. This role balances two mandates: keeping a large hybrid estate running reliably day to day, and advancing that estate toward modern, automated, product-oriented platform delivery. The Sr. Manager is responsible for stabilizing and reducing risk in legacy systems, driving engineering discipline and infrastructure-as-code practices, maturing database administration into a disciplined and automated operational service, and building the leadership bench beneath them. Database engineering and development are owned by a separate team; this role owns the administration, availability, and supportability of those database platforms in production. Success requires a strategic thinker with deep understanding of platform architecture and cloud operating models, strong financial and vendor acumen, and proven ability to lead managers, supervisors, engineers, architects, systems administrators, and database administrators. Major Responsibilities Leadership and Organizational Development Lead, mentor, and develop the Platform Engineering, Platform Operations, and Database Administration teams, including subordinate managers and supervisors. Provide role clarity, coaching, performance management, and accountability frameworks for managers, team leads, and senior technical contributors. Build succession depth and technical career paths across platform engineering, platform operations, and database administration disciplines. Foster a collaborative, accountable, and innovative culture that partners effectively with cybersecurity, application development, data, and business teams. Plan staffing levels, skills mix, and use of contract or managed-service resources to meet service commitments. Strategy and Platform Modernization Develop and execute a multi-year strategy for cloud and platform services, including cloud adoption, hybrid operating model, virtualization, compute and storage, and the operational estate of enterprise database platforms. Define and maintain the architectural direction and standards for platform services, and the operational standards for database services; ensure alignment with enterprise architecture, security, and business objectives. Lead initiatives in infrastructure modernization, automation, platform standardization, and self-service enablement for application teams. Own the remediation, upgrade, or retirement roadmap for high-risk, end-of-life, and low-value legacy systems. Stay current with industry trends and emerging technologies; evaluate and recommend tools, technologies, and processes that improve efficiency, reliability, and effectiveness. Platform Engineering Direct the design and implementation of scalable, highly available, secure, and automated platform solutions across cloud and on-premises environments. Drive adoption of infrastructure as code, configuration management, and CI/CD practices for platform delivery (e.g., Terraform, Ansible, Git-based pipelines). Establish reusable patterns, golden images, landing zones, and guardrails that let application teams consume platform capabilities safely and quickly. Partner with stakeholders to translate business and application requirements into technical designs and capacity plans. Ensure platform designs meet security, compliance, resiliency, and disaster recovery requirements. Platform Operations Oversee daily operations and maintenance of infrastructure platforms including AWS, Azure, VMware, and Windows and Linux server estates. Ensure availability of mission-critical services through effective monitoring, incident management, and escalation processes, including on-call coverage. Enforce adherence to change, configuration, problem, and patch management standards. Develop and maintain runbooks, standard operating procedures, and operational documentation to ensure consistent service delivery. Drive root cause analysis, post-incident reviews, and corrective actions that reduce repeat incidents and manual effort. Review application requirements and anticipate system needs to ensure capacity, performance, and scalability. Database Administration Lead the day-to-day administration and lifecycle management of enterprise database platforms across on-premises and cloud-hosted environments. Establish standards for database provisioning, patching, version currency, high availability, replication, backup, and recovery. Monitor database health, performance, and capacity; identify issues and trends and escalate tuning or design needs to the database engineering team. Ensure database security, access control, encryption, auditing, and compliance with regulatory and internal policy requirements. Advance automation of routine database administration tasks to reduce manual effort, improve consistency, and shorten provisioning and maintenance cycles. Ensure recoverability through tested backup and restore procedures aligned to business RPO and RTO requirements. Partner with the database engineering team, which owns database design, schema, and development, by providing operational, supportability, and capacity input into new and changing database platforms. Manage database change, release, and maintenance windows in coordination with application, data, and engineering teams. Financial and Vendor Management Develop and manage CapEx and OpEx budgets spanning hardware refresh, data center and cloud consumption, licensing, database licensing, support contracts, and professional services. Apply FinOps discipline to optimize cloud and platform spend, improve unit economics, and increase business value delivered per dollar. Evaluate and negotiate vendor contracts, licensing models, and service-level agreements; manage vendor performance and escalations. Track operational and financial KPIs and report on service cost, consumption trends, and forecast accuracy. Service Management and Continuous Improvement Define and manage service level objectives and operational metrics for platform and database administration services. Drive standardization, automation, and elimination of recurring manual work across all three teams. Support audit, compliance, and cybersecurity initiatives by ensuring systems and processes meet applicable standards and controls. Lead proactive identification and remediation of performance bottlenecks, single points of failure, and reliability risks. Collaboration and Communication Work closely with other technology leaders, business units, and external partners to align platform initiatives with business objectives. Communicate complex technical concepts clearly to non-technical stakeholders and executive leadership. Prepare and present reports, proposals, roadmaps, business cases, and technical documentation. Ensure clear, consistent communication during major incidents, maintenance events, and platform changes. Education And Experience Education Bachelor’s degree in Information Technology, Computer Science, or a related field. Master’s degree preferred. Relevant certifications such as AWS or Azure Solutions Architect / SysOps, VMware, Microsoft or Oracle database certifications, or ITIL are a plus. Experience 10+ years of experience in IT infrastructure, cloud, or platform services roles, including 5+ years of people leadership. Experience leading multiple technical teams, including managers or supervisors. Demonstrated experience managing an enterprise database administration function, including availability, backup and recovery, patching, and database security operations. Demonstrated experience in budget ownership, service level management, and vendor negotiation and oversight Proven experience operating hybrid cloud environments at enterprise scale (AWS and/or Azure alongside on-premises data centers). Skills Skills and Physical Demands Oversight of both CapEx (e.g., hardware refresh, data center buildouts) and OpEx (e.g., licensing, cloud spend, support contracts) budgets. Quality supervision: overseeing processes and organization, communication, coaching and providing feedback
. We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe Education And Experience?), Qualifications (maybe certifications?), Skills (list), Benefits (list), Pay (maybe just "Competitive Pay"), Schedule (Hybrid work schedule...). But we must avoid thin sections. However we have substantive content for each. Let's extract: About the role: The paragraph starting "Welcome to Love's: The Sr. Manager of Cloud and Platform Operations leads the strategy..." That's a description. We'll put that in
. Responsibilities: The bullet points under "Major Responsibilities" and subheadings like Leadership and Organizational Development, Strategy and Platform Modernization, Platform Engineering, Platform Operations, Database Administration, Financial and Vendor Management, Service Management and Continuous Improvement, Collaboration and Communication. We need to capture all duties. Could combine into a single list of responsibilities, preserving details. Might be long but okay. We need to avoid repeating headings inside list? We'll just make a
- with each responsibility as
- . Could include sub-bullets? Might be okay to keep as plain text. Requirements: Education And Experience section includes Education bullet and Experience bullet. Could treat as Requirements. Qualifications: maybe certifications? But Education And Experience already includes certifications as plus. Could combine. But we have separate Skills section. We need to avoid duplication. Let's decide: - About the role: intro paragraph. - Responsibilities: all major responsibilities bullet points (the ones under Major Responsibilities and subpoints). We'll extract each bullet as a list item. - Requirements: Education And Experience (Education bullet, Experience bullet). We'll put as list. - Skills: Skills section (including Skills and Physical Demands, Technical Skills, etc). We'll put as list. - Benefits: list given. - Pay: "Competitive Pay" (maybe also mention "competitive pay" as benefit but we can put as Pay section with that line). - Schedule: "Hybrid work schedule: 4 workdays onsite at the corporate office in Oklahoma City, and 1 workday remote (subject to change depending on business needs). Ability to be on-call and handle escalated situations outside normal business hours. Occasional travel to data center and field locations as required." We must not include filler like "commensurate with experience". Not present. Now we need to ensure we don't include boilerplate like "Our Culture ..."? That's substantive? It's about company culture; could be considered About the role? But it's not directly about role. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Our Culture" paragraph is not explicitly listed as boilerplate but could be considered company description. Might be okay to keep? It's not about the role but could be considered extra. However we already have About the role section; we could incorporate that culture paragraph into About the role? But the instruction: "Prefer a few substantive sections over many thin ones." The culture paragraph is substantive but not about role. Might be okay to include as part of About the role? But we already have About the role description; adding culture may be okay. But we need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep the culture paragraph somewhere. Could add another section like "About the Company" but we only allowed headings from list. Not allowed to add other headings. So we must fit into allowed headings. Could put it under About the role as additional paragraph. Thus About the role will have two paragraphs: the role description and the culture paragraph. Now we need to ensure we don't include the EEO line at end. Now let's extract details precisely. Original text: "Benefits: * Fuel Your Growth with Love's - company funded tuition assistance * Paid Time Off * 401(k) – 100% Match up to 5% * Medical/Dental/Vision Insurance after 30 days * Competitive Pay * Career Development * Welcome to Love's: The Sr. Manager of Cloud and Platform Operations leads the strategy, engineering, delivery, and operational performance of Love’s cloud and on-premises platform estate, and the administration of the enterprise database platforms that run on it. This position directly leads the Platform Engineering, Platform Operations, and Database Administration teams, and is accountable for the availability, security, scalability, and cost-effectiveness of the compute, storage, virtualization, cloud, and database services the business depends on. This role balances two mandates: keeping a large hybrid estate running reliably day to day, and advancing that estate toward modern, automated, product-oriented platform delivery. The Sr. Manager is responsible for stabilizing and reducing risk in legacy systems, driving engineering discipline and infrastructure-as-code practices, maturing database administration into a disciplined and automated operational service, and building the leadership bench beneath them. Database engineering and development are owned by a separate team; this role owns the administration, availability, and supportability of those database platforms in production. Success requires a strategic thinker with deep understanding of platform architecture and cloud operating models, strong financial and vendor acumen, and proven ability to lead managers, supervisors, engineers, architects, systems administrators, and database administrators. Major Responsibilities Leadership and Organizational Development Lead, mentor, and develop the Platform Engineering, Platform Operations, and Database Administration teams, including subordinate managers and supervisors. Provide role clarity, coaching, performance management, and accountability frameworks for managers, team leads, and senior technical contributors. Build succession depth and technical career paths across platform engineering, platform operations, and database administration disciplines. Foster a collaborative, accountable, and innovative culture that partners effectively with cybersecurity, application development, data, and business teams. Plan staffing levels, skills mix, and use of contract or managed-service resources to meet service commitments. Strategy and Platform Modernization Develop and execute a multi-year strategy for cloud and platform services, including cloud adoption, hybrid operating model, virtualization, compute and storage, and the operational estate of enterprise database platforms. Define and maintain the architectural direction and standards for platform services, and the operational standards for database services; ensure alignment with enterprise architecture, security, and business objectives. Lead initiatives in infrastructure modernization, automation, platform standardization, and self-service enablement for application teams. Own the remediation, upgrade, or retirement roadmap for high-risk, end-of-life, and low-value legacy systems. Stay current with industry trends and emerging technologies; evaluate and recommend tools, technologies, and processes that improve efficiency, reliability, and effectiveness. Platform Engineering Direct the design and implementation of scalable, highly available, secure, and automated platform solutions across cloud and on-premises environments. Drive adoption of infrastructure as code, configuration management, and CI/CD practices for platform delivery (e.g., Terraform, Ansible, Git-based pipelines). Establish reusable patterns, golden images, landing zones, and guardrails that let application teams consume platform capabilities safely and quickly. Partner with stakeholders to translate business and application requirements into technical designs and capacity plans. Ensure platform designs meet security, compliance, resiliency, and disaster recovery requirements. Platform Operations Oversee daily operations and maintenance of infrastructure platforms including AWS, Azure, VMware, and Windows and Linux server estates. Ensure availability of mission-critical services through effective monitoring, incident management, and escalation processes, including on-call coverage. Enforce adherence to change, configuration, problem, and patch management standards. Develop and maintain runbooks, standard operating procedures, and operational documentation to ensure consistent service delivery. Drive root cause analysis, post-incident reviews, and corrective actions that reduce repeat incidents and manual effort. Review application requirements and anticipate system needs to ensure capacity, performance, and scalability. Database Administration Lead the day-to-day administration and lifecycle management of enterprise database platforms across on-premises and cloud-hosted environments. Establish standards for database provisioning, patching, version currency, high availability, replication, backup, and recovery. Monitor database health, performance, and capacity; identify issues and trends and escalate tuning or design needs to the database engineering team. Ensure database security, access control, encryption, auditing, and compliance with regulatory and internal policy requirements. Advance automation of routine database administration tasks to reduce manual effort, improve consistency, and shorten provisioning and maintenance cycles. Ensure recoverability through tested backup and restore procedures aligned to business RPO and RTO requirements. Partner with the database engineering team, which owns database design, schema, and development, by providing operational, supportability, and capacity input into new and changing database platforms. Manage database change, release, and maintenance windows in coordination with application, data, and engineering teams. Financial and Vendor Management Develop and manage CapEx and OpEx budgets spanning hardware refresh, data center and cloud consumption, licensing, database licensing, support contracts, and professional services. Apply FinOps discipline to optimize cloud and platform spend, improve unit economics, and increase business value delivered per dollar. Evaluate and negotiate vendor contracts, licensing models, and service-level agreements; manage vendor performance and escalations. Track operational and financial KPIs and report on service cost, consumption trends, and forecast accuracy. Service Management and Continuous Improvement Define and manage service level objectives and operational metrics for platform and database administration services. Drive standardization, automation, and elimination of recurring manual work across all three teams. Support audit, compliance, and cybersecurity initiatives by ensuring systems and processes meet applicable standards and controls. Lead proactive identification and remediation of performance bottlenecks, single points of failure, and reliability risks. Collaboration and Communication Work closely with other technology leaders, business units, and external partners to align platform initiatives with business objectives. Communicate complex technical concepts clearly to non-technical stakeholders and executive leadership. Prepare and present reports, proposals, roadmaps, business cases, and technical documentation. Ensure clear, consistent communication during major incidents, maintenance events, and platform changes. Education And Experience Education Bachelor’s degree in Information Technology, Computer Science, or a related field. Master’s degree preferred. Relevant certifications such as AWS or Azure Solutions Architect / SysOps, VMware, Microsoft or Oracle database certifications, or ITIL are a plus. Experience 10+ years of experience in IT infrastructure, cloud, or platform services roles, including 5+ years of people leadership. Experience leading multiple technical teams, including managers or supervisors. Demonstrated experience managing an enterprise database administration function, including availability, backup and recovery, patching, and database security operations. Demonstrated experience in budget ownership, service level management, and vendor negotiation and oversight Proven experience operating hybrid cloud environments at enterprise scale (AWS and/or Azure alongside on-premises data centers). Skills Skills and Physical Demands Oversight of both CapEx (e.g., hardware refresh, data center buildouts) and OpEx (e.g., licensing, cloud spend, support contracts) budgets. Quality supervision: overseeing processes and organization, communication, coaching and providing feedback