Safety Manager 1

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: POSITION SUMMARY (we can map to About the role). MAJOR DUTIES & RESPONSIBILITIES (Responsibilities). JOB SKILLS & ABILITIES GUIDELINES (Skills). MINIMUM QUALIFICATIONS (Qualifications). WORKING CONDITIONS AND PHYSICAL EFFORTS (maybe Requirements? Actually Requirements could be qualifications; but we have Qualifications already. Could also have Requirements as separate but we can combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for About the role (POSITION SUMMARY). Responsibilities (MAJOR DUTIES & RESPONSIBILITIES). Skills (JOB SKILLS & ABILITIES GUIDELINES). Qualifications (MINIMUM QUALIFICATIONS). Requirements maybe not separate; we could treat WORKING CONDITIONS AND PHYSICAL EFFORTS as Requirements? But Requirements heading is for list of duties/requirements/benefits. Could include physical requirements under Requirements. However we already have Qualifications for education/experience/certifications. The physical demands could be under Requirements (maybe "Physical Requirements" but heading must be exactly "Requirements"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those exact headings. So we should use those headings if we have content. For Requirements we could include physical demands and maybe other requirements like travel, driver's license. That seems appropriate. Benefits: The posting mentions "Competitive pay and benefits." but no specific benefits listed. It says "We offer large company benefits and professional development opportunities". Not specific. The instruction says never create Benefits section unless posting actually states them. It does mention benefits generally but not specific. Likely we should not include Benefits because no specific details. Pay: mentions "Competitive pay". Not specific amount, so we should not include Pay. Schedule: not mentioned. So we omit Benefits, Pay, Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include the content from the posting under each heading. Let's extract: About the role (POSITION SUMMARY): The Safety Manager 1 is responsible for enforcing company safety, health, and environmental policies. This role oversees, leads, directs, and enforces safety and work practices on construction projects to identify, eliminate, and control hazardous conditions that may lead to injury and/or property damage using job specific safety standards, best management practices and injury free environment techniques. We can put that as a

  . Responsibilities (MAJOR DUTIES & RESPONSIBILITIES): The list includes many items. We need to preserve all substantive information. The text: "All qualities, responsibilities, and requirements of a Safety Engineer 2, plus:Proven success as a Safety EngineerConduct weekly project safety training meetings. Supervision of & administration of safety/first aid & rescue activities. Conduct incident investigation & reporting. Thoroughly understands 29 CFR 1926 and 1910 OSHA standards and other relevant regulatory requirements at the federal, state, and local levels. Participate in developing & conducting safety training for the project. Provide mentorship and development to assigned Safety EngineersLeads investigation of incidents and near-misses to determine root causes and develop corrective and preventive measures. Advises Sr. Safety Manager on safety compliance concerns and preventative actions. Coordinates with Safety personnel in your region on requirement updates, announcements on awards, incidents, and other significant eventsCollaborate with project managers, subcontractors, and employees to promote and enforce a culture of safety. Maintains safety files and records. Responsible for conducting themselves in accordance with our Guiding Principles and exhibiting attributes matching the Way We Work. Other duties as assigned." We need to split into list items. Each sentence separated by periods. We'll create

  • for each duty. We must ensure we don't lose any detail. Let's list them: - All qualities, responsibilities, and requirements of a Safety Engineer 2 - Proven success as a Safety Engineer - Conduct weekly project safety training meetings - Supervision of & administration of safety/first aid & rescue activities - Conduct incident investigation & reporting - Thoroughly understands 29 CFR 1926 and 1910 OSHA standards and other relevant regulatory requirements at the federal, state, and local levels - Participate in developing & conducting safety training for the project - Provide mentorship and development to assigned Safety Engineers - Leads investigation of incidents and near-misses to determine root causes and develop corrective and preventive measures - Advises Sr. Safety Manager on safety compliance concerns and preventative actions - Coordinates with Safety personnel in your region on requirement updates, announcements on awards, incidents, and other significant events - Collaborate with project managers, subcontractors, and employees to promote and enforce a culture of safety - Maintains safety files and records - Responsible for conducting themselves in accordance with our Guiding Principles and exhibiting attributes matching the Way We Work - Other duties as assigned We need to keep the ampersand etc. Now Skills (JOB SKILLS & ABILITIES GUIDELINES): list: - Strong analytical skills with the ability to identify hazards and assess risks. - Advanced computer knowledge - Function effectively as part of a team - Excellent communication skills, both verbal and written. - Continual training and professional development from an accredited industry association, i.e., OSHA outreach, Board of Certified Safety Professionals, etc. We'll put each as
  • . Qualifications (MINIMUM QUALIFICATIONS): list: - 4-year bachelor's degree or relevant safety experience - Board of Certified Safety Professional STS(C) and/or CHST or equivalent. - 5+ years of industry experience - First aid & CPR certified instructor We'll put each as
  • . Requirements (WORKING CONDITIONS AND PHYSICAL EFFORTS): list: - Must be adaptable to all types of weather conditions and traverse and inspect all areas of a construction job site, including walking, climbing, reaching, bending, crawling, or stretching. - Ability to physically stand, bend, sit for long periods, and squat throughout the day. - Ability to repeat the same movements. - Ability to communicate effectively to participate fully in meetings, video conferences, and phone calls. - Ability to compose, send, and reply to emails and written correspondence. - Must be able to lift, pull, or move up to 50 pounds at a time. - Travel may be required occasionally, primarily in the metropolitan area but sometimes domestically (must have a valid Driver’s License). - Exposure to characteristic construction site hazards. We'll put each as
  • . We need to ensure we don't include any boilerplate like "Attention All Third-Party Agencies..." etc. Remove that. Also remove the "About Manhattan" section? That's not a heading we need; but it's substantive info about company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Should we include that? It's not under the specified headings but we could include as a

    maybe under a generic section? But we only allowed headings from list. However we could include it as a

    before the headings? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside headings. It said 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 can have prose paragraphs outside headings. The "About Manhattan" is substantive info about the company; we should preserve it. It's not a list, so we can put it in a

      . However we need to decide where to place it. Probably after the headings or before. The instruction didn't forbid extra sections. We'll include a

      with that content. But we must remove boilerplate like "Attention All Third-Party Agencies..." etc. Also remove the "Check out the details in our Career Development Booklet..." maybe that's not boilerplate but it's a call to action; but it's not a list; it's prose. However it's basically an invitation to share resume; might be considered application instruction? It says "If Manhattan sounds like the place for you, share your resume with us!" That's application instruction; we should remove application instructions. Also the line "Check out the details in our Career Development Booklet on our website: www.manhattanconstructioncareers.com" is also maybe not needed. We'll remove those. Also remove the "Why Manhattan?" heading at top? That's not needed; we can ignore. We need to preserve the initial paragraph about Manhattan: "Why Manhattan? Manhattan Construction Company is a family of builders committed to developing teams who do the right thing for our projects, our clients, and each other. Every year, we celebrate team members who have been with the company for 10, 20, 30, and even 40-plus years. What is it about Manhattan that makes people stick around for decades? We offer large company benefits and professional development opportunities with the care and concern of a family-owned business. At Manhattan, you get: Competitive pay and benefits. A positive, friendly, and team-oriented workplace with caring leadership. Professional development and leadership programs. To work on exciting projects for your community. Security and stability working for a financially strong company. More opportunities to grow your career through our multiple U.S. office locations and affiliated companies." That's substantive info about the company; we should keep it. It's a list of bullet points after "At Manhattan, you get:" but it's not formatted as list; we could turn into

      • . However the instruction says use
        • for any list of duties/requirements/benefits. This is a list of benefits/attributes; could be considered benefits. But we already decided not to create Benefits section unless specific. However this is a list of what you get; could be considered benefits. But the instruction says never create Benefits section unless posting actually states them. It does state them: "Competitive pay and benefits. A positive, friendly, and team-oriented workplace with caring leadership. Professional development and leadership programs. To work on exciting projects for your community. Security and stability working for a financially strong company. More opportunities to grow your career through our multiple U.S. office locations and affiliated companies." That's a list of benefits. So we could include a Benefits section with those items. However earlier we thought not to include Benefits because not specific; but they are specific enough: competitive pay and benefits (vague), positive workplace, professional development programs, work on exciting projects, security and stability, more opportunities to grow career via multiple locations. Those are specific enough. The instruction says never create Benefits section unless posting actually states them. It does state them. So we should include Benefits section. But we also have Pay and Schedule sections; we should not create them unless posting actually states them. Pay: they mention "Competitive pay and benefits." That's mention of pay but not specific amount. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does