Mechanical Subject Matter Expert
. - Responsibilities: list of duties after "Mechanical Subject Matter Expert Responsibilities:" then bullet list. Need to extract each bullet. Let's list them: - Serve as an onsite technical resource of mechanical infrastructure systems and equipment, with an emphasis on practical field operation - Ensure appropriate cross-functional collaboration between local mechanical team and applicable local and global teams - Contribute to mechanical safety program for the site - Plan resource, author or approve work procedures to cover mechanical troubleshooting, repair, retrofit, and maintenance activities, with an emphasis on assessing & mitigating personnel and critical systems and operational risk - Conduct or oversee hands-on troubleshooting, repair, retrofit, and maintenance of mechanical equipment - Oversee mechanical system configurations and component upgrades to ensure system integrity is maintained and that all modifications to existing systems comply with best practices, including change control processes - Provide Quality Assurance/Quality Control (QAQC) oversight of construction projects & maintenance activity - Lead and/or participate in root-cause analysis activities in area of expertise - Provide training to Critical Facility Engineers and other cross functional teams on mechanical equipment, systems, procedures, and changes to include mechanical/fire & life safety/industrial water equipment/systems and procedures - Manage vendor relationships for mechanical maintenance and retrofit work - Provide feedback on global mechanical maintenance strategies and global electrical system design improvements - Travel expectations can be significant during the first 1-3 months for initial training and onboarding. After initial onboarding, travel expectations are 10-15%, with ongoing occasional travel for factory witness tests, collaboration, training, etc We need to keep travel expectations as part of responsibilities? It's a separate bullet but we can include as a bullet. - Minimum Qualifications: list. Let's extract: - 7+ years relevant mechanical industry experience or mechanical trade level experience - Bachelor’s degree in related field plus 3+ years relevant mechanical industry experience will be considered in lieu of 7+ year mechanical industry experience - Experience in critical environments - Experience interpreting blueprints/CAD drawings - Experience comprehending mechanical plans, specifications, and equipment shop drawings - Working knowledge of psychrometric charts and refrigeration cycles - Theoretical & practical understanding of mechanical equipment & systems, with expertise in mechanical equipment design, maintenance, troubleshooting, testing, and/or construction - Working knowledge of critical facility operations with experience or understanding of procedure-based work - Working knowledge of electrical, controls and fire / life safety systems - Experience working in a highly collaborative, cross-functional environment - Preferred Qualifications: list. - Familiarity with American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) standards - Trade Certification or state license in Mechanical Heating, Ventilation, and Air Conditioning (HVAC) - Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies - Experience in data center industry - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) - Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews) - Equipment field service engineering or representative experience - About Meta: description paragraph. - Pay: "$114,000/year to $168,000/year + bonus + equity + benefits". Also note: "Individual compensation is determined by skills, qualifications, experience, and location. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, equity or sales incentives, if applicable." We can include that as part of Pay section. - Benefits: "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." That's vague but we have mention of benefits. Should we include Benefits section? The posting mentions benefits generically. It says " + bonus + equity + benefits". Also "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." That's not specific detail but it's still mention of benefits. According to rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: they say "Meta offers benefits." That's vague but it's stating that benefits exist. Is that considered specific? It's not detailed but it's a statement that benefits are offered. Might be considered real content (they mention benefits). However they also say "Learn more about benefits at Meta." That's a pointer. I'd include Benefits section with a short
that says Meta offers benefits (health, retirement, etc.)? But we cannot invent details. We can only repeat what's there: "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." That's the content. That's not filler; it's actual statement. So we can include Benefits section with that sentence. - Schedule: travel expectations already covered under responsibilities; there is no explicit schedule like full-time, shift, etc. Not given. So we should not create Schedule section. - Also we might have a section "About Meta" but rule says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About Meta as a heading option. Should we include it? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we could also use other headings? Probably we should stick to those. The "About Meta" description could be placed under "About the role"? Actually "About the role" is for role description. The "About Meta" is company description. Could we put it under "About the role"? Might be okay but better to include as a separate section maybe "About Meta" but not in list. The instruction says use those headings for section headings; maybe we should only use those. If we include other headings, might violate. Safer to incorporate Meta description into "About the role" or maybe omit? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings. So we should only use those. So we need to fit all content under those headings.
Thus:
- About the role: include role description + maybe Meta description? Could combine.
But we have "About Meta" paragraph separate. Could we put it under "About the role"? Might be odd but acceptable. Or we could create a section "About the role" for role description, and then maybe another section "About Meta" not allowed. Better to incorporate into About the role: we can start with role description then add a paragraph about Meta.
Alternatively we could omit Meta description as it's not required? But we must preserve ALL substantive information. So we need to include it somewhere. We'll put it under About the role after role description.
- Responsibilities: as list.
- Requirements: could combine Minimum Qualifications and Preferred Qualifications? The headings include Requirements, Qualifications, Skills. We could use Requirements for minimum qualifications, Qualifications for preferred, Skills for maybe specific skills? But we have both minimum and preferred. We could use Requirements for minimum, Qualifications for preferred. Or we could combine both under Requirements. But better to follow examples: Requirements (minimum), Qualifications (preferred), Skills (maybe specific skills like ASHRAE, AI, etc). However we already have many skill-like items in preferred. Let's decide:
- Requirements (Requirements
) for Minimum Qualifications.
- Qualifications (Qualifications
) for Preferred Qualifications.
- Skills (Skills
) maybe for specific technical skills like "Experience interpreting blueprints/CAD drawings", "Working knowledge of psychrometric charts", etc. But those are already in minimum qualifications. Could split but risk duplication. Better to keep simple: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications, Skills maybe not needed. But we need to include all substantive info; if we omit Skills section, that's okay as long as we didn't create a heading with filler. We can omit Skills.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if any content left: Travel expectations already in Responsibilities. Good.
Now produce HTML.
We need to wrap each section in heading then content: for lists use - . For prose use
.
We must not include any extra tags like or . Just fragment.
Let's craft.
About the role:
Meta is seeking a Mechanical Subject Matter Expert to support the design, operation, and continuous improvement of mechanical systems across its global data center infrastructure. In this role, you will serve as a technical authority on mechanical systems including cooling infrastructure, HVAC, chilled water plants, computer room air handlers, and precision cooling technologies that are critical to maintaining the reliability and efficiency of hyperscale data center facilities. You will partner with engineering, construction, and operations teams to drive system-level improvements, resolve complex mechanical failures, and shape long-term infrastructure strategy.
Meta builds technologies that help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further empowered billions around the world. Now, Meta is moving beyond 2D screens toward immersive experiences like augmented and virtual reality to help build the next evolution in social technology. People who choose to build their careers by building with us at Meta help shape a future that will take us beyond what digital connection makes possible today—beyond the constraints of screens, the limits of distance, and even the rules of physics.
That's the About Meta paragraph.
Now Responsibilities:
Responsibilities
- Serve as an onsite technical resource of mechanical infrastructure systems and equipment, with an emphasis on practical field operation
- Ensure appropriate cross-functional collaboration between local mechanical team and applicable local and global teams
- Contribute to mechanical safety program for the site
- Plan resource, author or approve work procedures to cover mechanical troubleshooting, repair, retrofit, and maintenance activities, with an emphasis on assessing & mitigating personnel and critical systems and operational risk
- Conduct or oversee hands-on troubleshooting, repair, retrofit, and maintenance of mechanical equipment
- Oversee mechanical system configurations and component upgrades to ensure system integrity is maintained and that all modifications to existing systems comply with best practices, including change control processes
- Provide Quality Assurance/Quality Control (QAQC) oversight of construction projects & maintenance activity
- Lead and/or participate in root-cause analysis activities in area of expertise
- Provide training to Critical Facility Engineers and other cross functional teams on mechanical equipment, systems, procedures, and changes to include mechanical/fire &
Requirements
) for Minimum Qualifications. - Qualifications (Qualifications
) for Preferred Qualifications. - Skills (Skills
) maybe for specific technical skills like "Experience interpreting blueprints/CAD drawings", "Working knowledge of psychrometric charts", etc. But those are already in minimum qualifications. Could split but risk duplication. Better to keep simple: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications, Skills maybe not needed. But we need to include all substantive info; if we omit Skills section, that's okay as long as we didn't create a heading with filler. We can omit Skills. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any content left: Travel expectations already in Responsibilities. Good. Now produce HTML. We need to wrap each section in heading then content: for lists use - . For prose use
.
We must not include any extra tags like or . Just fragment.
Let's craft.
About the role:
Meta is seeking a Mechanical Subject Matter Expert to support the design, operation, and continuous improvement of mechanical systems across its global data center infrastructure. In this role, you will serve as a technical authority on mechanical systems including cooling infrastructure, HVAC, chilled water plants, computer room air handlers, and precision cooling technologies that are critical to maintaining the reliability and efficiency of hyperscale data center facilities. You will partner with engineering, construction, and operations teams to drive system-level improvements, resolve complex mechanical failures, and shape long-term infrastructure strategy.
Meta builds technologies that help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further empowered billions around the world. Now, Meta is moving beyond 2D screens toward immersive experiences like augmented and virtual reality to help build the next evolution in social technology. People who choose to build their careers by building with us at Meta help shape a future that will take us beyond what digital connection makes possible today—beyond the constraints of screens, the limits of distance, and even the rules of physics.
That's the About Meta paragraph.
Now Responsibilities:
Responsibilities
- Serve as an onsite technical resource of mechanical infrastructure systems and equipment, with an emphasis on practical field operation
- Ensure appropriate cross-functional collaboration between local mechanical team and applicable local and global teams
- Contribute to mechanical safety program for the site
- Plan resource, author or approve work procedures to cover mechanical troubleshooting, repair, retrofit, and maintenance activities, with an emphasis on assessing & mitigating personnel and critical systems and operational risk
- Conduct or oversee hands-on troubleshooting, repair, retrofit, and maintenance of mechanical equipment
- Oversee mechanical system configurations and component upgrades to ensure system integrity is maintained and that all modifications to existing systems comply with best practices, including change control processes
- Provide Quality Assurance/Quality Control (QAQC) oversight of construction projects & maintenance activity
- Lead and/or participate in root-cause analysis activities in area of expertise
- Provide training to Critical Facility Engineers and other cross functional teams on mechanical equipment, systems, procedures, and changes to include mechanical/fire &
. We must not include any extra tags like or . Just fragment. Let's craft. About the role:
Meta is seeking a Mechanical Subject Matter Expert to support the design, operation, and continuous improvement of mechanical systems across its global data center infrastructure. In this role, you will serve as a technical authority on mechanical systems including cooling infrastructure, HVAC, chilled water plants, computer room air handlers, and precision cooling technologies that are critical to maintaining the reliability and efficiency of hyperscale data center facilities. You will partner with engineering, construction, and operations teams to drive system-level improvements, resolve complex mechanical failures, and shape long-term infrastructure strategy.
Meta builds technologies that help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further empowered billions around the world. Now, Meta is moving beyond 2D screens toward immersive experiences like augmented and virtual reality to help build the next evolution in social technology. People who choose to build their careers by building with us at Meta help shape a future that will take us beyond what digital connection makes possible today—beyond the constraints of screens, the limits of distance, and even the rules of physics.
That's the About Meta paragraph. Now Responsibilities:Responsibilities
- Serve as an onsite technical resource of mechanical infrastructure systems and equipment, with an emphasis on practical field operation
- Ensure appropriate cross-functional collaboration between local mechanical team and applicable local and global teams
- Contribute to mechanical safety program for the site
- Plan resource, author or approve work procedures to cover mechanical troubleshooting, repair, retrofit, and maintenance activities, with an emphasis on assessing & mitigating personnel and critical systems and operational risk
- Conduct or oversee hands-on troubleshooting, repair, retrofit, and maintenance of mechanical equipment
- Oversee mechanical system configurations and component upgrades to ensure system integrity is maintained and that all modifications to existing systems comply with best practices, including change control processes
- Provide Quality Assurance/Quality Control (QAQC) oversight of construction projects & maintenance activity
- Lead and/or participate in root-cause analysis activities in area of expertise
- Provide training to Critical Facility Engineers and other cross functional teams on mechanical equipment, systems, procedures, and changes to include mechanical/fire &