Manager, Cloud FinOps Engineer
Bristol Myers Squibb · Princeton, NJ · 1 mo ago
Engineering$119k–$145k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Working with Us" intro, "Position Summary", "Key Responsibilities", "Qualifications & Experience", "Compensation Overview", "Benefits". Also maybe "On-site Protocol Responsibilities" etc but those are boilerplate? The instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also "On-site Protocol Responsibilities" maybe not boilerplate but it's about work location; could be considered part of role? Might be considered relevant but not requested headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly.
We have Position Summary (could be About the role). Key Responsibilities (Responsibilities). Qualifications & Experience (Qualifications). Skills maybe part of Qualifications. Benefits (Benefits). Pay (Compensation Overview). Schedule? Not present; there is mention of flexible time off etc but that's benefits. No explicit schedule. So we should not create Schedule section.
We need to include h3 headings only when real specific content. Use
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: "Working with Us Challenging..." intro maybe considered marketing but it's substantive? It's about company culture; could be considered About the role? Might keep as part of About the role paragraph. However instructions: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The intro is not a heading; we can keep as paragraph under About the role. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
About the role
Working with Us Challenging. Meaningful. Life-changing.... (the intro paragraph) plus Position Summary paragraph.
But we need to avoid duplication: The intro and Position Summary both talk about role. Could combine. Better: About the role: include the introductory paragraph and Position Summary. Then Responsibilities: list from Key Responsibilities bullet points. Qualifications: include Qualifications & Experience required and maybe Preferred. Skills: maybe separate? But we can combine into Qualifications. Benefits: list from Benefits. Pay: include Compensation Overview. We must not create sections with filler like "commensurate with experience". Not present. Let's extract details. Intro paragraph: "Working with Us Challenging. Meaningful. Life-changing. Those aren’t words that are usually associated with a job. But working at Bristol Myers Squibb is anything but usual. Here, uniquely interesting work happens every day, in every department. From optimizing a production line to the latest breakthroughs in cell therapy, this is work that transforms the lives of patients, and the careers of those who do it. You’ll get the chance to grow and thrive through opportunities uncommon in scale and scope, alongside high-achieving teams. Take your career farther than you thought possible. Bristol Myers Squibb recognizes the importance of balance and flexibility in our work environment. We offer a wide variety of competitive benefits, services and programs that provide our employees with the resources to pursue their goals, both at work and in their personal lives. Read more: careers.bms.com/working-with-us." We can keep that as prose. Position Summary paragraph: "The Cloud FinOps Engineer is an IT and cloud engineering role responsible for enabling cost‑efficient, scalable, and well‑governed cloud usage across BMS’s multi‑cloud platforms (AWS, Azure, GCP). This role applies FinOps principles through technology, automation, and platform design, rather than traditional financial execution. The engineer works within the Cloud / SRE / Platform organization, embedding cost visibility, optimization, and governance directly into cloud architectures, infrastructure‑as‑code, CI/CD pipelines, and operational workflows. The position focuses on building and operating technical solutions for cost allocation, tagging enforcement, anomaly detection, optimization insights, and reporting—ensuring these capabilities are reliable, scalable, and consumable by engineering and application teams. The Cloud FinOps Engineer partners closely with SRE, Platform Engineering, Security, Network, Application Owners, and Finance, translating cloud usage and architectural decisions into actionable insights and automated controls that improve efficiency and value realization across BMS." We'll combine. Responsibilities: list bullet points from Key Responsibilities sections. Let's extract bullet points: - Perform day‑to‑day cloud cost and usage analysis across AWS, Azure, and GCP, focusing on tagging enforcement, anomaly detection, and optimization follow‑up. - Operate and enhance cloud cost observability solutions, including dashboards, scorecards, unit‑economics views, and usage trends. - Investigate cost spikes and usage anomalies by correlating architecture, utilization, and operational events. - Ensure continuous operational coverage by identifying gaps in cost governance processes and implementing technical improvements - Serve as a technical point of contact for cloud consumers and application teams, translating cost, utilization, and architectural patterns into clear engineering guidance. - Facilitate recurring cloud consumption and optimization reviews, focusing on how design choices impact scalability, reliability, and cost. - Influence teams across IT to adopt engineering‑led FinOps best practices, embedded into provisioning, deployment, and runtime operations. - Partner with Finance teams by providing reliable cloud cost data, tooling, and automation, while ownership remains within IT. - Independently analyze cloud usage to identify waste, inefficiencies, and optimization opportunities, including: - Compute and database rightsizing - Storage tiering and lifecycle policies - Kubernetes and container cost drivers - Data transfer and networking patterns - Lead small‑to‑medium engineering‑driven optimization initiatives, ensuring measurable and sustainable impact. - Support commitment strategies (Savings Plans, Reserved Instances, CUDs) through data analysis and tooling enablement. - Promote a shift from reactive cost reduction to continuous, automated optimization. - Build and maintain automation solutions using Python to improve accuracy, speed, and scalability of FinOps operations. - Develop solutions in AWS using services such as: - AWS Lambda - Databases (RDS, DynamoDB, Redshift) - Step Functions - Create and manage CloudFormation templates and support infrastructure‑as‑code standards. - Integrate cost controls, tagging validation, and reporting into CI/CD pipelines. - Leverage APIs and scripting to automate: - Cost anomaly reporting - Scheduled usage and spend analysis - Data ingestion from cloud billing systems (Optional) - Contribute to or enhance Auto Remediation Frameworks to correct inefficient or non‑compliant configurations. - Apply knowledge of Identity and Access Management (IAM), especially role‑based access, to support secure and accountable cloud usage. - Ensure cost attribution and ownership data are technically enforced and auditable. - Support compliance and audit needs by enabling system‑generated evidence and traceability. - Collaborate with Security and Compliance teams to embed FinOps controls into platform standards. - Work with SRE, Security, Network, Engineering, Product, and Procurement teams to integrate cost considerations into technical decisions. - Represent the FinOps engineering function on cross‑functional initiatives. - Communicate complex technical and cost‑related concepts clearly across engineering, operational, and leadership audiences. We need to format as- for any list of duties/requirements/benefits. So we can have a single
- with many
- items, each containing the responsibility text. For nested lists (like under "including:"), we could embed another
- inside the
- . That's okay.
Qualifications & Experience Required:
- Bachelor’s degree in Computer Science, Engineering, Information Systems, Data Analytics, or related technical field.
- 4–5+ years of experience in cloud engineering, platform operations, SRE, FinOps engineering, or cloud operations roles.
- Strong understanding of cloud platforms and cost drivers, including:
- Compute (EC2, VMs, Kubernetes)
- Storage (S3, Blob, GCS)
- Databases (RDS, DynamoDB, SQL)
- Networking (data transfer, load balancers)
- Hands‑on experience with Python, including writing clean, efficient, maintainable code.
- Experience with:
- BMS Internal
- AWS services (Lambda, databases, Step Functions)
- CloudFormation
- CI/CD pipeline concepts
- Strong data and analytics skills, including:
- Advanced Excel
- SQL
- Cost modeling and analysis
- Experience with data visualization tools (Power BI, Tableau, QuickSight).
- Working knowledge of GitHub and version control practices.
- Understanding of tagging strategies, cost allocation, and showback/chargeback models.
- Ability to independently scope and deliver moderately complex technical solutions.
- Strong communication and collaboration skills
Preferred:
- FinOps Certified Practitioner or Analyst certification.
- Experience with cloud billing and cost tools:
- AWS Cost Explorer, CUR, Billing Conductor, Budgets
- Azure Cost Management
- GCP Billing exports
- Enterprise tools (Apptio Cloudability, Flexera, Finout)
- Experience with Python and React for internal tools or dashboards.
- Understanding of Savings Plans, Reserved Instances, and commitment strategies.
- Familiarity with monitoring/observability tools (CloudWatch, Datadog, Prometheus, Grafana).
- Experience working in large enterprise or regulated environments.
- Familiarity with Auto Remediation Frameworks.
We can combine required and preferred into Qualifications section, maybe separate subheadings? But only allowed headings are from list; we could keep Qualifications and maybe Skills separate. However we can put all under Qualifications.
Benefits: list from Benefits section.
Benefits text includes many items; we can create
- for each benefit category. Let's extract: - Health Coverage: Medical, pharmacy, dental, and vision care. - Wellbeing Support: Programs such as BMS Well-Being Account, BMS Living Life Better, and Employee Assistance Programs (EAP). - Financial Well-being and Protection: 401(k) plan, short- and long-term disability, life insurance, accident insurance, supplemental health insurance, business travel protection, personal liability protection, identity theft benefit, legal support, and survivor support. - Work-life Benefits Include Paid Time Off US Exempt Employees: flexible time off (unlimited, with manager approval, 11 paid national holidays (not applicable to employees in Phoenix, AZ, Puerto Rico or Rayzebio employees) Phoenix, AZ, Puerto Rico and Rayzebio Exempt, Non-Exempt, Hourly Employees: 160 hours annual paid vacation for new hires with manager approval, 11 national holidays, and 3 optional holidays Based on eligibility*, additional time off for employees may include unlimited paid sick time, up to 2 paid volunteer days per year, summer hours flexibility, leaves of absence for medical, personal, parental, caregiver, bereavement, and military needs and an annual Global Shutdown between Christmas and New Years Day. All global employees full and part-time who are actively employed at and paid directly by BMS at the end of the calendar year are eligible to take advantage of the Global Shutdown. Eligibility Disclosure: The summer hours program is for United States (U.S.) office-based employees due to the unique nature of their work. Summer hours are generally not available for field sales and manufacturing operations and may also be limited for the capability centers. Employees in remote-by-design or lab-based roles may be eligible for summer hours, depending on the nature of their work, and should discuss eligibility with their manager. Employees covered under a collective bargaining agreement should consult that document to determine if they are eligible. Contractors, leased workers and other service providers are not eligible to participate in the program. That's a lot; we can keep as prose or list. Since it's a list of benefits, we can break into
- items. Pay: Compensation Overview paragraph: "Princeton - NJ
- . That's okay.
Qualifications & Experience Required:
- Bachelor’s degree in Computer Science, Engineering, Information Systems, Data Analytics, or related technical field.
- 4–5+ years of experience in cloud engineering, platform operations, SRE, FinOps engineering, or cloud operations roles.
- Strong understanding of cloud platforms and cost drivers, including:
- Compute (EC2, VMs, Kubernetes)
- Storage (S3, Blob, GCS)
- Databases (RDS, DynamoDB, SQL)
- Networking (data transfer, load balancers)
- Hands‑on experience with Python, including writing clean, efficient, maintainable code.
- Experience with:
- BMS Internal
- AWS services (Lambda, databases, Step Functions)
- CloudFormation
- CI/CD pipeline concepts
- Strong data and analytics skills, including:
- Advanced Excel
- SQL
- Cost modeling and analysis
- Experience with data visualization tools (Power BI, Tableau, QuickSight).
- Working knowledge of GitHub and version control practices.
- Understanding of tagging strategies, cost allocation, and showback/chargeback models.
- Ability to independently scope and deliver moderately complex technical solutions.
- Strong communication and collaboration skills
Preferred:
- FinOps Certified Practitioner or Analyst certification.
- Experience with cloud billing and cost tools:
- AWS Cost Explorer, CUR, Billing Conductor, Budgets
- Azure Cost Management
- GCP Billing exports
- Enterprise tools (Apptio Cloudability, Flexera, Finout)
- Experience with Python and React for internal tools or dashboards.
- Understanding of Savings Plans, Reserved Instances, and commitment strategies.
- Familiarity with monitoring/observability tools (CloudWatch, Datadog, Prometheus, Grafana).
- Experience working in large enterprise or regulated environments.
- Familiarity with Auto Remediation Frameworks.
We can combine required and preferred into Qualifications section, maybe separate subheadings? But only allowed headings are from list; we could keep Qualifications and maybe Skills separate. However we can put all under Qualifications.
Benefits: list from Benefits section.
Benefits text includes many items; we can create
- items, each containing the responsibility text. For nested lists (like under "including:"), we could embed another
- for any list of duties/requirements/benefits. So we can have a single