Sr Applied AI/ML Software Developer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits unless stated. The posting does not mention pay, schedule, benefits explicitly. So we should not include those sections.
We have content: Job Summary (maybe "About the role") includes description: Sr Applied AI/ML Software Developer will join thermal engineering team for development of AI/ML-powered control systems, digital twins, simulation infrastructure for data center cooling equipment. Work closely with mechanical and controls engineers to develop and implement intelligent system control strategies. Work primarily in Python and C/C++ on Linux-based platforms, leveraging containerized development environments and CI/CD pipelines.
Responsibilities: listed bullet points: Simulation Development: Support simulation environments used for controls development and testing purposes, utilizing simulation industry standards such as FMU/FMI and equipment reduced Order Models (ROMs). Creation of Reduced Order Models (ROMs) based on real or synthetic unit/system/environment data. Support Digital Twin development and implementation Maintain FMU packages for simulation deployment Control Development Investigate alternate control strategies involving machine learning models, reinforcement learning, model-predictive control (MPC), and other data based solutions Develop, train, and validate ML models for adaptive control of thermal systems, predictive maintenance, and anomaly detection Deploy ML inference pipelines on Linux-based industrial platforms System Integration Interface with equipment and simulations utilizing various industrial protocols, pub-sub messaging, API's (Modbus, CAN, MQTT, REST, HTTP/REST etc.)
Requirements: Bachelor’s or Master’s Degree (MS or higher) in Computer Science and Engineering or Electrical and Computer Engineering, with a strong emphasis on software 8+ Years experience in similar position Python Programming C/C++ Programming TensorFlow or PyTorch Git/GitLab Linux Docker/Containerization Industrial Communication Protocols, including MQTT, Modbus, and CAN
Also there is "The successful candidate will embrace Vertiv’s Core Principals & Behaviors to help execute our Strategic Priorities." Then list of core principals and strategic priorities and behaviors. This could be considered "About the role" or maybe "Qualifications"? But it's more about company values. Could be placed under "About the role" as prose. However we need to avoid duplication: The text repeats later again "About Vertiv" etc. We need to preserve substantive info but remove duplicated lines. There's duplication of the core principals, strategic priorities, behaviors, About Vertiv, Work Authorization, Equal Opportunity Employer. We should keep only one instance each.
We need to decide sections: Perhaps "About the role" (job summary), "Responsibilities", "Requirements". Could also have "Qualifications" but requirements already cover qualifications. Could have "Skills" but requirements list skills. Might combine.
We should not create sections with filler. So we will output:
About the role
Sr Applied AI/ML Software Developer will join our thermal engineering team for the development of AI/ML-powered control systems, digital twins, and simulation infrastructure for data center cooling equipment. You will work closely with mechanical and controls engineers to help develop and implement intelligent system control strategies. You will work primarily in Python and C/C++ on Linux-based platforms, leveraging containerized development environments and CI/CD pipelines.
Responsibilities
- Support simulation environments used for controls development and testing purposes, utilizing simulation industry standards such as FMU/FMI and equipment reduced Order Models (ROMs).
- Creation of Reduced Order Models (ROMs) based on real or synthetic unit/system/environment data.
- Support Digital Twin development and implementation.
- Maintain FMU packages for simulation deployment.
- Investigate alternate control strategies involving machine learning models, reinforcement learning, model-predictive control (MPC), and other data‑based solutions.
- Develop, train, and validate ML models for adaptive control of thermal systems, predictive maintenance, and anomaly detection.
- Deploy ML inference pipelines on Linux‑based industrial platforms.
- Interface with equipment and simulations utilizing various industrial protocols, pub‑sub messaging, and APIs (Modbus, CAN, MQTT, REST, HTTP/REST etc.).
Requirements
- Bachelor’s or Master’s Degree (MS or higher) in Computer Science and Engineering or Electrical and Computer Engineering, with a strong emphasis on software.
- 8+ years of experience in a similar position.
- Proficiency in Python programming.
- Proficiency in C/C++ programming.
- Experience with TensorFlow or PyTorch.
- Experience with Git/GitLab.
- Linux operating system expertise.
- Docker/containerization experience.
- Knowledge of industrial communication protocols, including MQTT, Modbus, and CAN.
We could also include a section about company values if we consider it substantive. The posting includes "The successful candidate will embrace Vertiv’s Core Principals & Behaviors to help execute our Strategic Priorities." Then lists core principals, strategic priorities, behaviors, About Vertiv. This is substantive but could be placed under "About Vertiv" or "Company Overview". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "About the company" but we could still add a heading if we think it's appropriate? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But we should prefer a few substantive sections over many thin ones. The company description could be part of "About the role" or maybe a separate "About Vertiv". However we already have "About the role" describing the job. Adding another section about company might be thin but still substantive. However we risk duplication because the text repeats later. We could include a short paragraph about Vertiv under "About the role" after the job summary. But we already used that paragraph for job summary. Could we extend that paragraph to include company overview? The job summary currently is about the role; we could add a sentence about Vertiv after that. But the instruction says preserve ALL substantive information; we must not omit the company description. So we need to include it somewhere.
We could add a section "About Vertiv" as an (though not in the examples but acceptable). However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the spirit: use those headings for typical sections. Adding "About Vertiv" might be okay but could be considered extra. However we could incorporate the company description into the "About the role" section as prose, making it more substantive but not too thin. That would satisfy preserving all info without extra heading.
Thus we can expand the About the role paragraph to include: "Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries."
We also need to include the core principals, strategic priorities, behaviors? That is also substantive but could be considered part of company culture. Could we include them as a list under "About Vertiv"? Might be too thin but still substantive. However we already have many lists; adding another list may be okay. But we need to avoid filler. The core principals list: Safety. Integrity. Respect. Teamwork. Inclusion. Strategic Priorities: High-Performance Culture Customer Focus Operational Excellence Innovation Financial Strength. Behaviors: Own it Act with urgency Foster a customer-first mindset Think big and execute Lead by example Drive continuous improvement Learn and seek out development Promote transparent & open communication.
These are substantive but could be considered boilerplate? They are specific to Vertiv, not generic EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not EEO; it's company values. So we could keep it.
But we already have a lot of content; adding another list may be okay. However we need to decide if we want to create a new section like "Company Culture" or incorporate into About Vertiv.
Given the instruction to prefer a few substantive sections over many thin ones, maybe we should keep only three sections: About the role (including job summary and company overview), Responsibilities, Requirements. That would be three sections, which is few. The company overview and values could be included in About the role as prose, making it substantive but not a separate thin section.
Thus we will embed the Vertiv description and maybe the core principals/strategic priorities/behaviors as a paragraph or list within About the role. However that may make the About the role section long but still okay.
We need to ensure we don't duplicate content: The posting repeats the core principals etc twice. We'll include once.
Let's craft About the role paragraph:
Sr Applied AI/ML Software Developer will join our thermal engineering team for the development of AI/ML-powered control systems, digital twins, and simulation infrastructure for data center cooling equipment. You will work closely with mechanical and controls engineers to help develop and implement intelligent system control strategies. You will work primarily in Python and C/C++ on Linux-based platforms, leveraging containerized development environments and CI/CD pipelines. Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries. The successful candidate will embrace Vertiv’s Core Principles & Behaviors to help execute our Strategic Priorities. Our Core Principles: Safety, Integrity, Respect, Teamwork, Inclusion. Our Strategic Priorities: High-Performance Culture, Customer Focus, Operational Excellence, Innovation, Financial Strength. Vertiv Behaviors: Own it, Act with urgency, Foster a customer-first mindset, Think big and execute, Lead by example, Drive continuous improvement, Learn and seek out development, Promote transparent & open communication.
That seems to capture all.
Now Responsibilities and Requirements as above.
Check for any other substantive content: There's also "Work Authorization No calls or agencies please. Vertiv will only employ those who are legally authorized to work in the United States. This is not a position for which sponsorship will be provided. Individuals with temporary visas such as E, F-1, H-1, H-2, L, B, J, or TN or who need sponsorship for work authorization now or in the future, are not eligible for hire." This is work authorization info. Should we keep it? It's substantive but maybe considered boilerplate? It's not EEO but it's about eligibility
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits unless stated. The posting does not mention pay, schedule, benefits explicitly. So we should not include those sections. We have content: Job Summary (maybe "About the role") includes description: Sr Applied AI/ML Software Developer will join thermal engineering team for development of AI/ML-powered control systems, digital twins, simulation infrastructure for data center cooling equipment. Work closely with mechanical and controls engineers to develop and implement intelligent system control strategies. Work primarily in Python and C/C++ on Linux-based platforms, leveraging containerized development environments and CI/CD pipelines. Responsibilities: listed bullet points: Simulation Development: Support simulation environments used for controls development and testing purposes, utilizing simulation industry standards such as FMU/FMI and equipment reduced Order Models (ROMs). Creation of Reduced Order Models (ROMs) based on real or synthetic unit/system/environment data. Support Digital Twin development and implementation Maintain FMU packages for simulation deployment Control Development Investigate alternate control strategies involving machine learning models, reinforcement learning, model-predictive control (MPC), and other data based solutions Develop, train, and validate ML models for adaptive control of thermal systems, predictive maintenance, and anomaly detection Deploy ML inference pipelines on Linux-based industrial platforms System Integration Interface with equipment and simulations utilizing various industrial protocols, pub-sub messaging, API's (Modbus, CAN, MQTT, REST, HTTP/REST etc.) Requirements: Bachelor’s or Master’s Degree (MS or higher) in Computer Science and Engineering or Electrical and Computer Engineering, with a strong emphasis on software 8+ Years experience in similar position Python Programming C/C++ Programming TensorFlow or PyTorch Git/GitLab Linux Docker/Containerization Industrial Communication Protocols, including MQTT, Modbus, and CAN Also there is "The successful candidate will embrace Vertiv’s Core Principals & Behaviors to help execute our Strategic Priorities." Then list of core principals and strategic priorities and behaviors. This could be considered "About the role" or maybe "Qualifications"? But it's more about company values. Could be placed under "About the role" as prose. However we need to avoid duplication: The text repeats later again "About Vertiv" etc. We need to preserve substantive info but remove duplicated lines. There's duplication of the core principals, strategic priorities, behaviors, About Vertiv, Work Authorization, Equal Opportunity Employer. We should keep only one instance each. We need to decide sections: Perhaps "About the role" (job summary), "Responsibilities", "Requirements". Could also have "Qualifications" but requirements already cover qualifications. Could have "Skills" but requirements list skills. Might combine. We should not create sections with filler. So we will output:
About the role
Sr Applied AI/ML Software Developer will join our thermal engineering team for the development of AI/ML-powered control systems, digital twins, and simulation infrastructure for data center cooling equipment. You will work closely with mechanical and controls engineers to help develop and implement intelligent system control strategies. You will work primarily in Python and C/C++ on Linux-based platforms, leveraging containerized development environments and CI/CD pipelines.
Responsibilities
- Support simulation environments used for controls development and testing purposes, utilizing simulation industry standards such as FMU/FMI and equipment reduced Order Models (ROMs).
- Creation of Reduced Order Models (ROMs) based on real or synthetic unit/system/environment data.
- Support Digital Twin development and implementation.
- Maintain FMU packages for simulation deployment.
- Investigate alternate control strategies involving machine learning models, reinforcement learning, model-predictive control (MPC), and other data‑based solutions.
- Develop, train, and validate ML models for adaptive control of thermal systems, predictive maintenance, and anomaly detection.
- Deploy ML inference pipelines on Linux‑based industrial platforms.
- Interface with equipment and simulations utilizing various industrial protocols, pub‑sub messaging, and APIs (Modbus, CAN, MQTT, REST, HTTP/REST etc.).
Requirements
- Bachelor’s or Master’s Degree (MS or higher) in Computer Science and Engineering or Electrical and Computer Engineering, with a strong emphasis on software.
- 8+ years of experience in a similar position.
- Proficiency in Python programming.
- Proficiency in C/C++ programming.
- Experience with TensorFlow or PyTorch.
- Experience with Git/GitLab.
- Linux operating system expertise.
- Docker/containerization experience.
- Knowledge of industrial communication protocols, including MQTT, Modbus, and CAN.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But we should prefer a few substantive sections over many thin ones. The company description could be part of "About the role" or maybe a separate "About Vertiv". However we already have "About the role" describing the job. Adding another section about company might be thin but still substantive. However we risk duplication because the text repeats later. We could include a short paragraph about Vertiv under "About the role" after the job summary. But we already used that paragraph for job summary. Could we extend that paragraph to include company overview? The job summary currently is about the role; we could add a sentence about Vertiv after that. But the instruction says preserve ALL substantive information; we must not omit the company description. So we need to include it somewhere.
We could add a section "About Vertiv" as an (though not in the examples but acceptable). However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the spirit: use those headings for typical sections. Adding "About Vertiv" might be okay but could be considered extra. However we could incorporate the company description into the "About the role" section as prose, making it more substantive but not too thin. That would satisfy preserving all info without extra heading.
Thus we can expand the About the role paragraph to include: "Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries."
We also need to include the core principals, strategic priorities, behaviors? That is also substantive but could be considered part of company culture. Could we include them as a list under "About Vertiv"? Might be too thin but still substantive. However we already have many lists; adding another list may be okay. But we need to avoid filler. The core principals list: Safety. Integrity. Respect. Teamwork. Inclusion. Strategic Priorities: High-Performance Culture Customer Focus Operational Excellence Innovation Financial Strength. Behaviors: Own it Act with urgency Foster a customer-first mindset Think big and execute Lead by example Drive continuous improvement Learn and seek out development Promote transparent & open communication.
These are substantive but could be considered boilerplate? They are specific to Vertiv, not generic EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not EEO; it's company values. So we could keep it.
But we already have a lot of content; adding another list may be okay. However we need to decide if we want to create a new section like "Company Culture" or incorporate into About Vertiv.
Given the instruction to prefer a few substantive sections over many thin ones, maybe we should keep only three sections: About the role (including job summary and company overview), Responsibilities, Requirements. That would be three sections, which is few. The company overview and values could be included in About the role as prose, making it substantive but not a separate thin section.
Thus we will embed the Vertiv description and maybe the core principals/strategic priorities/behaviors as a paragraph or list within About the role. However that may make the About the role section long but still okay.
We need to ensure we don't duplicate content: The posting repeats the core principals etc twice. We'll include once.
Let's craft About the role paragraph:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the spirit: use those headings for typical sections. Adding "About Vertiv" might be okay but could be considered extra. However we could incorporate the company description into the "About the role" section as prose, making it more substantive but not too thin. That would satisfy preserving all info without extra heading. Thus we can expand the About the role paragraph to include: "Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries." We also need to include the core principals, strategic priorities, behaviors? That is also substantive but could be considered part of company culture. Could we include them as a list under "About Vertiv"? Might be too thin but still substantive. However we already have many lists; adding another list may be okay. But we need to avoid filler. The core principals list: Safety. Integrity. Respect. Teamwork. Inclusion. Strategic Priorities: High-Performance Culture Customer Focus Operational Excellence Innovation Financial Strength. Behaviors: Own it Act with urgency Foster a customer-first mindset Think big and execute Lead by example Drive continuous improvement Learn and seek out development Promote transparent & open communication. These are substantive but could be considered boilerplate? They are specific to Vertiv, not generic EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not EEO; it's company values. So we could keep it. But we already have a lot of content; adding another list may be okay. However we need to decide if we want to create a new section like "Company Culture" or incorporate into About Vertiv. Given the instruction to prefer a few substantive sections over many thin ones, maybe we should keep only three sections: About the role (including job summary and company overview), Responsibilities, Requirements. That would be three sections, which is few. The company overview and values could be included in About the role as prose, making it substantive but not a separate thin section. Thus we will embed the Vertiv description and maybe the core principals/strategic priorities/behaviors as a paragraph or list within About the role. However that may make the About the role section long but still okay. We need to ensure we don't duplicate content: The posting repeats the core principals etc twice. We'll include once. Let's craft About the role paragraph:
Sr Applied AI/ML Software Developer will join our thermal engineering team for the development of AI/ML-powered control systems, digital twins, and simulation infrastructure for data center cooling equipment. You will work closely with mechanical and controls engineers to help develop and implement intelligent system control strategies. You will work primarily in Python and C/C++ on Linux-based platforms, leveraging containerized development environments and CI/CD pipelines. Vertiv (NYSE: VRT) brings together hardware, software, analytics and ongoing services to enable its customers’ vital applications to run continuously, perform optimally and grow with their business needs. Vertiv solves the most important challenges facing today’s data centers, communication networks and commercial and industrial facilities with a portfolio of power, cooling and IT infrastructure solutions and services that extend from the cloud to the edge of the network. Headquartered in Westerville, Ohio, USA, Vertiv employs around 34,000 people and does business in more than 130 countries. The successful candidate will embrace Vertiv’s Core Principles & Behaviors to help execute our Strategic Priorities. Our Core Principles: Safety, Integrity, Respect, Teamwork, Inclusion. Our Strategic Priorities: High-Performance Culture, Customer Focus, Operational Excellence, Innovation, Financial Strength. Vertiv Behaviors: Own it, Act with urgency, Foster a customer-first mindset, Think big and execute, Lead by example, Drive continuous improvement, Learn and seek out development, Promote transparent & open communication.
That seems to capture all. Now Responsibilities and Requirements as above. Check for any other substantive content: There's also "Work Authorization No calls or agencies please. Vertiv will only employ those who are legally authorized to work in the United States. This is not a position for which sponsorship will be provided. Individuals with temporary visas such as E, F-1, H-1, H-2, L, B, J, or TN or who need sponsorship for work authorization now or in the future, are not eligible for hire." This is work authorization info. Should we keep it? It's substantive but maybe considered boilerplate? It's not EEO but it's about eligibility