Senior Engineering Operations Manager
JLL · San Jose, CA · 4 wk ago
On-siteEngineering$175k–$201k/yrFull-time
We need to output HTML fragment with sections using for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Location: San Jose, CA 95134
- Work Schedule: Onsite, M-F ~8:00 AM - 5:00 PM + on call expectation for emergencies
- Travel Requirements: splitting time between other buildings within a large corporate campus
- Reports to: Regional Facilities Manager - West Region
- Estimated base salary range: $175,000 - $200,500 + annual salary bonus
- What this job involves: description (strategic leadership etc.)
- What your day-to-day will look like: list of duties.
- Required qualifications: bullet list (but in paragraph). We need to extract into sections: Requirements, Qualifications, Skills maybe.
We need to decide which sections to include.
We have content for:
- About the role: maybe a summary paragraph: "Transform at JLL as a Senior Engineering Operations Manager on a prominent Fortune 500 technology client account! You will lead the hard services delivery at our clients global corporate headquarters." That's about role.
- Responsibilities: the "What this job involves" and "What your day-to-day will look like" sections.
- Requirements: maybe the "Required qualifications" list.
- Qualifications: maybe "Preferred qualifications" list.
- Skills: maybe combine required skills? Could be part of Requirements.
- Pay: we have salary range + bonus.
- Schedule: we have work schedule and travel.
- Benefits: not mentioned explicitly. No benefits details. So we should not create Benefits section.
We must not create sections with filler like "not specified". So only include sections with real content.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
Potentially also Skills? Could embed within Requirements. But we could create Skills section if we have explicit skill list: "Strong leadership, communication, problem-solving, and stakeholder-management skills Proficiency with CMMS software, energy management systems, and Microsoft Office Suite". That's skills. Could be separate.
But we need to avoid thin sections. Let's see if we have enough for Skills: we have leadership, communication, problem-solving, stakeholder-management, proficiency with CMMS, EMS, MS Office. That's substantive. Could be Skills.
Qualifications: Preferred qualifications: Master's degree, experience with central utility plants, Corrigo CMMS preferred, certifications.
Requirements: Required qualifications list.
Thus we can have:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Location: San Jose, CA 95134
- Work Schedule: Onsite, M-F ~8:00 AM - 5:00 PM + on call expectation for emergencies
- Travel Requirements: splitting time between other buildings within a large corporate campus
- Reports to: Regional Facilities Manager - West Region
- Estimated base salary range: $175,000 - $200,500 + annual salary bonus
- What this job involves: description (strategic leadership etc.)
- What your day-to-day will look like: list of duties.
- Required qualifications: bullet list (but in paragraph). We need to extract into sections: Requirements, Qualifications, Skills maybe.
We need to decide which sections to include.
We have content for:
- About the role: maybe a summary paragraph: "Transform at JLL as a Senior Engineering Operations Manager on a prominent Fortune 500 technology client account! You will lead the hard services delivery at our clients global corporate headquarters." That's about role.
- Responsibilities: the "What this job involves" and "What your day-to-day will look like" sections.
- Requirements: maybe the "Required qualifications" list.
- Qualifications: maybe "Preferred qualifications" list.
- Skills: maybe combine required skills? Could be part of Requirements.
- Pay: we have salary range + bonus.
- Schedule: we have work schedule and travel.
- Benefits: not mentioned explicitly. No benefits details. So we should not create Benefits section.
We must not create sections with filler like "not specified". So only include sections with real content.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
Potentially also Skills? Could embed within Requirements. But we could create Skills section if we have explicit skill list: "Strong leadership, communication, problem-solving, and stakeholder-management skills Proficiency with CMMS software, energy management systems, and Microsoft Office Suite". That's skills. Could be separate.
But we need to avoid thin sections. Let's see if we have enough for Skills: we have leadership, communication, problem-solving, stakeholder-management, proficiency with CMMS, EMS, MS Office. That's substantive. Could be Skills.
Qualifications: Preferred qualifications: Master's degree, experience with central utility plants, Corrigo CMMS preferred, certifications.
Requirements: Required qualifications list.
Thus we can have:
About the role
...
Responsibilities
- ... each duty
Requirements
- ... required qualifications
Qualifications
- ... preferred qualifications
Skills
- ... skills
Pay
Estimated base salary range: $175,000 - $200,500 + annual salary bonus
Schedule
Onsite, M-F ~8:00 AM - 5:00 PM + on call expectation for emergencies; travel: splitting time between other buildings within a large corporate campus.
We must not include location? Could be part of About the role or maybe separate but not required. The instruction: do not repeat job title as heading; we can include location in a paragraph maybe under About the role or as separate? Not required to have location heading. Could embed in About the role paragraph. We must preserve all substantive information. So include location, reports to, travel requirements. Let's craft About the role paragraph: "Senior Engineering Operations Manager (M2) at JLL supporting a prominent Fortune 500 technology client account. Lead hard services delivery at the client's global corporate headquarters in San Jose, CA 95134. Reports to the Regional Facilities Manager – West Region. Position is onsite Monday‑Friday ~8:00 AM‑5:00 PM with on‑call expectations for emergencies and requires splitting time between other buildings on a large corporate campus." That includes location, reports to, schedule, travel. But schedule also appears in Schedule section; we might duplicate. Better to keep schedule details only in Schedule section, and About the role just high-level. However we need to preserve all info; duplication is okay? Might be considered redundant but not prohibited. But we can avoid duplication by putting location and reporting in About the role, and schedule in Schedule section. Thus About the role: "Senior Engineering Operations Manager (M2) at JLL supporting a prominent Fortune 500 technology client account. Lead hard services delivery at the client's global corporate headquarters in San Jose, CA 95134. Reports to the Regional Facilities Manager – West Region." Schedule section: "Onsite, M-F ~8:00 AM - 5:00 PM + on call expectation for emergencies; travel: splitting time between other buildings within a large corporate campus." Now Responsibilities: need to capture the duties from "What this job involves:" and "What your day-to-day will look like:". We can combine into bullet list. Let's extract duties: From "What this job involves:": - Provide strategic leadership for Engineering Operations, maintenance, reliability, compliance, and continuous improvement across the clients HQ. - Partner with the Chief Engineer and Engineering leadership to prioritize maintenance, repairs, infrastructure needs, staffing, safety, and operational requirements. - Oversee preventive, predictive, corrective, and reactive maintenance programs to improve equipment reliability, extend asset life, and minimize downtime. - Apply reliability and asset-management practices including RCM, root-cause analysis, asset criticality, lifecycle planning, and repair-versus-replace recommendations. - Provide oversight of major building systems including HVAC, electrical, plumbing, fire/life safety, BAS/BMS, generators, emergency power, controls, and related infrastructure. - Ensure work affecting critical laboratories, IDF/telecommunications spaces, and other technology-sensitive environments is appropriately planned, risk-assessed, and coordinated to protect business continuity. - Oversee planned shutdowns, critical maintenance activities, operational risk assessments, and restoration activities. - Provide governance of the Engineering CMMS/work-order program, including PM completion, corrective maintenance, backlog, SLA performance, documentation, and data integrity. - Utilize Corrigo, operational dashboards, KPIs, and performance data to identify trends, recurring issues, resource needs, and improvement opportunities. - Lead, coach, and develop Engineering staff while establishing clear expectations for performance, accountability, safety, customer service, and professional development. - Ensure appropriate staffing, scheduling, technical coverage, and resource allocation across SJC facilities. - Manage and monitor Engineering OPEX, including maintenance expenses, service contracts, vendors, overtime, purchase orders, accruals, forecasts, and financial variances. - Provide Engineering and IFM support for client-managed capital projects, including asset information, technical input, operational-impact assessments, shutdown planning, commissioning, turnover, and integration into ongoing operations. - Manage performance of third-party contractors, technical vendors, and specialty service providers against established KPIs, SLAs, safety requirements, and service expectations. - Serve as a senior Engineering Operations point of contact for client SJC stakeholders and communicate facility conditions, risks, performance, priorities, and recommended actions. - Ensure compliance with applicable local, state, and federal requirements, as well as client and JLL policies, JCAP, HSSE, safety requirements, and standard operating practices. - Serve as a senior escalation point for significant facility incidents, infrastructure failures, and business-impacting events; coordinate response, recovery, communication, root-cause review, and corrective actions, during business and after hours. - Identify and implement opportunities to improve Engineering performance through technology, analytics, automation, predictive maintenance, AI-enabled tools, and continuous-improvement practices. - Perform additional duties as required in support of client SJC Campus Engineering Operations. - Serves as the primary liaison between Global and AMER engineering teams for site-level engineering initiatives, coordinating data collection and implementations while providing technical expertise to achieve JLL and Client objectives. - Manages union employees and serves as the primary liaison with local union stakeholders for labor relations, staffing coordination, and collective bargaining agreement administration. From "What your day-to-day will look like:" seems to be similar but we already covered many. Might be redundant but we can incorporate. We'll create a bullet list of responsibilities (maybe combine similar). Ensure we don't miss any. Now Requirements (required qualifications): List: - Bachelor's degree in Engineering, Facilities Management, or related technical field, or equivalent combination of education and experience - 10+ years of progressive experience in facilities engineering, building maintenance, facilities operations, or related technical operations - Strong background in commercial building maintenance and Engineering Operations - 5+ years of people-leadership experience managing multidisciplinary Engineering or maintenance teams - Experience supporting large campuses, complex corporate environments, or critical operating environments - Strong knowledge of HVAC, electrical, plumbing, fire/life safety, BAS/BMS, generators, emergency power, controls, and related building systems - Knowledge of RCM, Root Cause Analysis, asset lifecycle management, and preventive/predictive maintenance practices, incident management handling - Strong analytical capability and experience using KPIs and operational data to drive decisions and improvement - Demonstrated experience with operating budgets, forecasting, expense management, and cost control - Experience supporting capital projects, shutdowns, commissioning, and project turnover into facilities operations - Experience managing and working with Union Team members will be key in this role - Strong leadership, communication, problem-solving, and stakeholder-management skills - Proficiency with CMMS software, energy management systems, and Microsoft Office Suite Note: Some of these are skills; but we can keep them in Requirements. Qualifications (preferred): - Master's degree in Engineering, Business Administration, or Facilities Management - Experience supporting large or complex central utility plants and chilled water systems. - Corrigo CMMS preferred - Relevant industry certifications such as IFMA, BOMA, AFE, or SMRP/CMRP preferred Skills: maybe we separate leadership etc. But we already have many skills in Requirements. To avoid duplication, we could put skills in Requirements and not have separate Skills. But the instruction: we can have Skills section if we have real specific content. We have skills list: "Strong leadership, communication, problem-solving, and stakeholder-management skills Proficiency with CMMS software, energy management systems, and Microsoft Office Suite". That's specific. However those also appear in Requirements. To avoid duplication, we could keep them only in Requirements and not create Skills. But we need to decide. Given we already have a Requirements section with many items, we could keep Skills separate for leadership etc. But that would duplicate some content. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. It didn't forbid duplication. However better to avoid redundancy. We could move the leadership/communication etc to Skills and keep other qualifications in Requirements. Thus: Requirements: education, years experience, background, people leadership, campus experience, knowledge of systems, RCM, analytical, budgeting, capital projects, union experience. Skills: leadership, communication, problem-solving, stakeholder-management, proficiency with CMMS, energy management, MS Office. Qualifications (preferred): master's degree, central utility plants experience, Corrigo CMMS, certifications. Now Pay: as given. Schedule: as given. Now About the role: short paragraph. Now ensure we don't include boilerplate like "Please submit your application..." etc. Remove. Now produce HTML fragment. We'll need to wrap each section inand then
or
- .
Let's craft.
About the role:
Senior Engineering Operations Manager (M2) at JLL supporting a prominent Fortune 500 technology client account. Lead