Jobs · Management · Arizona

Safety Manager - Mission Critical (Mon - Fri, 1:00pm start)

Lease Crutcher Lewis · Phoenix, AZ · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with sections: About the role (already present), Responsibilities (maybe "What You’ll Do"), Requirements (maybe "What You Bring" and "Requirements"), Benefits (benefits info), Pay (none), Schedule (maybe shift info). Must only include sections with real specific content. No filler like "commensurate with experience". We must preserve all substantive info, not invent. We need to parse the posting. Sections: - About The Role (heading). Content: paragraph(s) describing role. - What Success Looks Like (maybe could be part of About the role? But it's a separate section with content. Could be considered part of responsibilities? But we can treat as separate section maybe "What Success Looks Like". However instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not limited to those? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. Likely we should have sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly Qualifications/Skills could be merged. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, etc. We need to keep all substantive info. Let's extract content: About The Role paragraph: "As a Safety Manager with our Data Center division in the Phoenix Metro area, you will be a daily field partner to the people who are building some of our most complex work. You will work alongside superintendents, project managers, MEP leaders, quality managers, site safety coordinators, trade partners, owner representatives, and commissioning teams to help plan the work, identify risk, coach safe behaviors, and keep safety expectations clear as the project evolves. This position is specifically aligned to a Monday through Friday shift-based project coverage, with a 1:00pm start. This is hands-on, project-based safety leadership in a data center environment where sequencing, energization, commissioning, logistics, and trade coordination all matter. You will spend your time in the field, in planning conversations, and with project leaders turning observations and data into practical actions that help teams work safely and effectively." What Success Looks Like: bullet-like sentences: "You are a visible, trusted safety partner to project teams, field leaders, and trade partners.You help teams plan work safely before it begins and adjust quickly when site conditions change.You are comfortable in mission critical environments where the pace is quick, details matter, and safety depends on thoughtful planning, disciplined execution, and strong coordination across trades.You communicate clearly, coach effectively, and build credibility through follow-through and sound judgment.You use audits, observations, incident data, and field conversations to identify trends and recommend meaningful corrective action.You help create a jobsite culture where safety expectations are clear, consistently reinforced, and owned by everyone." What You’ll Do: list of duties broken into sub-sections: Safety Planning and Field Support, Training and Coaching, Audits, Inspections, and Compliance, Incident Investigation and Safety Analytics, Documentation, Reporting, and Administration. Each with bullet points. We need to output
  • for any list of duties/requirements/benefits. So we can combine all duties into a single list? Or we could keep subheadings? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
    • for any list of duties/requirements/benefits, and

      for prose. So we likely need a Responsibilities section with

      • items enumerating duties. Could also keep subheadings inside? Probably not; just list. Similarly Requirements: combine "What You Bring" and "Requirements" sections into a list. Benefits: we have benefits paragraph: "A 100% employee-owned general contractor, Lease Crutcher Lewis offers a comprehensive healthcare plan with medical, dental, and vision coverage. Our employer-funded Lifestyle Spending Account supports physical wellness for employees. We also offer a generous Health Savings Account with annual employer-sponsored contributions. Lease Crutcher Lewis provides support for a financially healthy future, including our Employee Stock Ownership Plan, enrollment covered at no cost to you, and a 401(k) with a competitive matching program. To support employee philanthropic efforts, employees are eligible for volunteer PTO and charitable giving matching programs." Schedule: we have shift info: "This position is specifically aligned to a Monday through Friday shift-based project coverage, with a 1:00pm start." Also later: "This role requires shift-based onsite coverage specifically aligned to a Monday through Friday schedule with a 1:00pm start." Also travel expectations. So schedule section can include that. Pay: none, so omit. Qualifications/Skills: maybe we can combine with Requirements. But we could have a Skills section if we want. However we should avoid thin sections. Better to have Requirements covering qualifications, skills, experience. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Now we need to extract all substantive info and put into appropriate format. Let's draft About the role paragraph(s). Could be two paragraphs: first paragraph as above, second maybe "What Success Looks Like" could be part of About the role? But we already have About the role heading; we could include the success looks like as part of About the role prose. However the instruction: "Prefer a few substantive sections over many thin ones." So we could merge What Success Looks Like into About the role as additional prose. That seems okay. Thus About the role: combine the initial description and the success looks like sentences. Now Responsibilities: list all duties from What You’ll Do sub-sections. Let's enumerate: Safety Planning and Field Support: - Help project teams plan work before it begins, with attention to mission critical hazards, phased work, commissioning activities, energy management, logistics, and high-risk trade coordination. - Maintain a strong working knowledge of federal, state, local, owner, project-specific, and DCAT safety requirements and serve as a resource to Phoenix data center project teams. - Be a visible field partner—walking the site, listening for concerns, asking good questions, coaching in the moment, and helping teams adjust safely as conditions change. - Support preconstruction efforts by reviewing safety considerations, project requirements, and planned work approaches. - Coordinate onsite medical services or related safety vendors when needed. Training and Coaching: - Identify and deliver practical safety training that supports regulatory, owner, DCAT, and mission critical data center expectations while helping employees and trade partners build safer work habits. - Assess safety training needs, evaluate training effectiveness, and help implement programs that create lasting knowledge and changed behaviors. - Support project-specific regulatory training needs and maintain accurate training and certification records. - Coach and mentor site safety coordinators, field leaders, and project team members to strengthen Lewis’ safety culture. Audits, Inspections, and Compliance: - Conduct routine jobsite safety audits and inspections for active projects and review findings with project teams. - Document audits, observations, hazards, violations, and corrective actions in Lewis’ safety management systems. - Review safety plans, observations, hazards, and corrective actions with a practical eye toward what is happening in the field and what will help teams execute safely. - Monitor open safety issues and partner with project teams to ensure timely correction. - Support compliance audits or regulatory agency interactions as requested by the Safety Director. Incident Investigation and Safety Analytics: - Support project teams with accident, injury, and property damage investigations in accordance with Lewis policy. - Help facilitate Root Cause Analysis meetings and ensure learnings, recommendations, and corrective actions are documented and communicated. - Review safety observations, incident reports, injury logs, and audit results to identify recurring hazards and trends. - Prepare and distribute project-specific safety reports, dashboards, and communications that promote transparency, accountability, and continuous improvement. - Provide safety data, analysis, and recommendations to the Safety Director, project teams, and operations leadership. Documentation, Reporting, and Administration: - Maintain accurate safety documentation, including plans, procedures, inspections, training records, violations, corrective actions, and project safety reports. - Create and distribute project-specific safety performance reports and dashboards as needed. - Support clear, organized safety communications and resources that are easy for project teams to access and use. Now Requirements: combine What You Bring and Requirements. What You Bring: - 5+ years of experience in a construction safety role, preferably with a general contractor or on complex commercial building projects. - Experience supporting safety on complex commercial, mission critical, data center, advanced technology, healthcare, life sciences, energy, or similarly fast-paced construction projects. - Bachelor’s or Associate’s degree in Environmental Health and Safety, Occupational Safety, Construction Management, or a related field preferred; equivalent experience will be considered. - OSHA 30 required; OSHA 510 and current CPR/First Aid certification strongly preferred. - Working knowledge of OSHA and applicable federal, state, and local safety regulations, including Arizona safety requirements. - Experience conducting safety audits, inspections, incident investigations, Root Cause Analysis, and corrective action follow-up. - Technical knowledge of key construction safety topics such as fall protection, electrical safety, energy isolation, crane and lift operations, rigging/signaling, confined space, scaffolding, trenching/excavation, respirator fit training, hazardous materials, flammable storage, blood-borne pathogens, defensive driving, flagging, and related field exposures. - Experience with safety tracking and reporting systems; SafetyNet or similar system experience preferred. - Strong computer proficiency, including Microsoft Office and the ability to prepare safety reports, JHAs, pre-task plans, and work plans. - KEY ATTRIBUTES: Strong written, verbal, facilitation, and presentation skills. - Comfortable communicating with employees, field leaders, trade partners, clients, owner representatives, commissioning teams, and project stakeholders with diverse backgrounds and experience levels. - Practical, solutions-oriented approach to identifying hazards, solving problems, and supporting safe production. - Strong attention to detail, organization, accountability, and follow-through. - Ability to work independently while staying closely connected to project and safety leadership. - Data-informed mindset with the ability to interpret safety trends and recommend practical actions. - Responsive to jobsite needs and committed to building trust through field presence and partnership. Requirements (the later section): - Current driver’s license and clean driving record in accordance with company vehicle policy. - Successful completion of required pre-employment screening is a conditional requirement of the employment process. - Physical requirements include regular communication; the ability to see, talk, and hear; frequent standing, walking, and use of hands, fingers, and arms; sitting, climbing, and balancing; and the ability to frequently lift and move up to 25 pounds. - This posting is intended to give candidates a clear picture of the opportunity, but it is not an exhaustive list of responsibilities. The role may evolve based on project needs, business priorities, and the realities of complex data center work. We should keep all that. Now Benefits: as above. Schedule: shift-based Monday-Friday 1:00pm start. Also travel expectations: "Primarily project-based travel to and work within Phoenix-area DCAT/data center project sites; travel expectations may vary based on project assignment, phase, shift coverage, and business needs." Could include in schedule. Now we need to output HTML fragment with

        headings and

        or

        • . We must not include any boilerplate like EEO etc. Already removed. Now ensure we don't repeat content unnecessarily. Let's craft. HTML:

          About the role

          As a Safety Manager with our Data Center division in the Phoenix Metro area, you will be a daily field partner to the people who are building some of our most complex work. You will work alongside superintendents, project managers, MEP leaders, quality managers, site safety coordinators, trade partners, owner representatives, and commissioning teams to help plan the work, identify risk, coach safe behaviors,

Similar jobs

Safety Manager

McKenney's, Inc.Atlanta, GA· 3 mo ago
Manufacturingapply on mckenneys.applytojob.com

Safety Manager

MasTec Clean Energy & InfrastructureGreater Birmingham, Alabama Area· 2 mo ago
Manufacturing$115k/yrapply on ceisvcareers-mastec.icims.com

Safety Manager

City of Burlington, VermontBurlington, VT· 2 mo ago
$88k–$98k/yrapply on click2apply.net

Safety Manager

Pratt IndustriesStatesville, NC· 2 mo ago
Managementapply on myjobs.adp.com

Safety Manager

Casella Waste Systems, Inc.Auburn, MA· 3 mo ago
Management$93k–$122k/yrapply on careers-casella.icims.com

Safety Manager

IES CommunicationsSterling, VA· 2 mo ago
Management$100k/yrapply on joinus.ies-co.com