Employee Safety Administrator

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: 1. About the Role - there's an "About The Role" section 2. Key Responsibilities - there's a "Key Responsibilities" section with subsections 3. Qualifications - there's a "Qualifications" section 4. Preferred Qualifications - there's a "Preferred Qualifications" section 5. Knowledge, Skills, & Abilities - there's a "Knowledge, Skills, & Abilities" section 4. Supplemental Information & Working Conditions - there's a "Supplemental Information & Working Conditions" section 5. Why You Should Join Our Team - there's a "Why You Should Join Our Team" section 6. The Agency - brief mention 7. EEO Statement - boilerplate, should be removed Also there's position information: Salary Range, FT/PT Status, Background Check, Schedule Code, Location, Recruiter, Application Deadline. These are metadata that should be folded into a short

or dropped. The rules say: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So I should include the key metadata in a paragraph. The rules: 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. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings. Preserve ALL substantive information. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting has Salary Range, Schedule Code, etc. Should I create a Pay section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Salary Range and Schedule Code. But the example headings include Pay and Schedule. However, the rule says only include if the posting actually states them. The posting does state salary range and schedule code. But the rule also says "Prefer a few substantive sections over many thin ones." I could fold the metadata into a paragraph under About the Role or a separate short section. But the rule says "fold minor metadata into a short

  or drop it." So I'll include a paragraph with the key details: salary, full-time, location, schedule, background check, deadline. Now, the Key Responsibilities section has subsections: Strategic Leadership & Program Management, Technical Compliance & Hazard Oversight, Resource Management & Continuous Improvement, Incident Prevention & Data Analysis. Each has bullet points. I should keep those as sub-lists? The rule says use

  • for any list of duties/requirements/benefits. I could make each subsection a heading? But the rule says use

    for section headings. The subsections are not top-level sections; they are part of Key Responsibilities. I could keep them as

    ? But the rule only mentions

    for section headings. It doesn't forbid

    , but the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other heading levels. However, to keep it simple, I could make the main sections as

    and the subsections as

    or just bold text. But the rule says "use

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

      for prose." It doesn't specify subheadings. I think it's okay to use

      for subsections within Responsibilities. But the output should be a fragment, not a full HTML document. I'll use

      for main sections, and for subsections within Responsibilities, I'll use

      to maintain hierarchy. Alternatively, I could flatten: make each responsibility area a separate

      ? But the posting groups them under Key Responsibilities. The rule says "include a section ONLY when the posting has real, specific content for it". The subsections have real content. I'll keep Key Responsibilities as an

      and then each subsection as an

      with its own list. Similarly, Qualifications has a paragraph and a note. Preferred Qualifications is a list. Knowledge, Skills, & Abilities is a list. Supplemental Information & Working Conditions has two subsections: Work Environment and Physical Demands. Why You Should Join Our Team has two paragraphs. The Agency is just a link. EEO Statement is boilerplate, remove. Now, I need to output ONLY the HTML fragment — no /, no markdown code fences. Let me structure:

      About the Role

      ... (the paragraph about reporting to Director, leading team of 12, etc.)

      Salary Range: $44.22 - $70.14 per hour. Full Time. Background check required. Schedule: AX - Career service exempt (at-will). Location: Calvin Rampton Building - 4501 South 2700 West, Taylorsville, UT (primarily on-site office / field / flex schedule). Application deadline: 11/2/2026 (may close earlier).

      Responsibilities

      Strategic Leadership & Program Management

      • Direct Safety Programs: Plan, coordinate, implement, and evaluate statewide safety initiatives, performance goals, and operational action plans.
      • Team Supervision: Lead and mentor a statewide team of 12 safety specialists. Responsibilities include workload balancing, performance reviews, hiring, and staff development.
      • Cross-Agency Collaboration: Partner with agency divisions, regional teams, external organizations, and committees to align safety initiatives with daily field operations.
      • Clear Communication: Present technical findings and safety updates to field staff, senior management, and executives in a manner that aligns with UDOT’s Core Values (Respect, Integrity, and Caring).

      Technical Compliance & Hazard Oversight

      • Regulatory Oversight: Ensure agency compliance with state and federal OSHA and UOSH standards, transportation safety rules, and internal policies.
      • Site Inspections & Audits: Oversee workplace audits, incident investigations, root-cause analyses, and the implementation of corrective actions.
      • High-Hazard Controls: Establish safety protocols for high-risk environments, including highway work zones, heavy equipment operation, trenching/excavation, and fall protection.

      Resource Management & Continuous Improvement

      • Budget & Resources: Evaluate staffing, equipment, technology, and funding needs to deliver effective safety programs statewide.
      • Data-Backed Recommendations: Develop business cases, cost-benefit analyses, and educational media to justify safety investments and process upgrades.
      • Performance Tracking: Measure program success, identify operational gaps, and introduce long-term preventive solutions.

      Incident Prevention & Data Analysis

      • Risk Analytics: Analyze injury data, worker claims, and safety trends to identify hazards and prioritize preventive measures.
      • Cross-Departmental Alignment: Work closely with Workers’ Compensation, Fleet Operations, and training departments to decrease workplace injuries and lower public costs.
      • Emergency Response: Respond to major incidents on-site when required, converting findings into actionable improvements to safety policies and training programs.
      • Digital Tools: Maintain and improve safety software, digital reporting tools, automated workflows, and executive dashboards.

      Qualifications

      A Bachelor’s degree (or higher) in Occupational Safety and Health, Industrial Hygiene, Environmental Health, Safety Engineering, Public Administration, or a closely related field, plus six (6) years of full-time OSH experience, including verifiable supervisory or team leadership responsibilities.

      Note: Directly related professional experience may be substituted for the education requirement on a year-for-year basis (e.g., 10 years of total related experience if no degree is held).

      Valid driver’s license and ability to travel statewide.

      Preferred Qualifications

      • Advanced Degree: Master’s degree in an occupational safety or business-related discipline.
      • Primary Board Certifications: Certified Safety Professional (CSP), Certified Industrial Hygienist (CIH), Certified Safety and Health Manager (CSHM), or Safety Management Professional (SMP).
      • Trainer & Field Credentials: OSHA Authorized Trainer credentials (e.g., OSHA 500/501), Certified Safety & Health Official (CSHO), or related university safety center certifications.

      Skills

      • Leadership & Strategy: Proven ability to manage multi-faceted safety programs, assign resources effectively, and lead organizational change across diverse workgroups.
      • Communication & Interpersonal Skills: High emotional intelligence and professional judgment. Strong skill in writing clear technical documentation, building organizational trust, and resolving workplace conflicts.
      • Technical Expertise: Thorough understanding of occupational health regulations, risk assessment methods, and safety mitigation strategies. Ability to analyze financial and statistical data to support practical program changes.
      • Digital Literacy: Proficiency with standard office productivity suites (Microsoft Office, Google Workspace) and familiarity with safety databases, reporting dashboards, and basic spatial coordinate tools.

      Working Conditions

      Work Environment

      A combination of office work and field visits to highway work zones, construction sites, and maintenance facilities. Occasional emergency site response and travel is required.

      Physical Demands

      Must be able to travel statewide and lift up to 30 pounds during field assessments.

      Why Join Us

      A Mission That Matters – At the Utah Department of Transportation (UDOT), our mission is to “Enhance quality of life through transportation." We help the traveling public get where they want, when they want, as safely as possible. By joining our team, you contribute to the framework of Good Health, Connected Communities, Better Mobility, and a Strong Economy for all of Utah.

      Our Culture and Values – We aren't just a state agency; we are a team built on an internal culture of Trust, Teamwork, and Flexibility. We live by the values of Respect, Integrity, and Caring. If these values resonate with you, you will find a home here!

      I should not include The Agency link or EEO Statement. Now, check for any duplicate or boilerplate. The recruiter info and deadline are in the metadata paragraph. The schedule code is included. The background check is included. The rule: "Do NOT repeat the job title as a heading (the page already shows it)" - I didn't. "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." I folded into a paragraph. "Preserve ALL substantive information; do NOT invent or summarize away detail." I kept all details. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." I removed EEO statement and application instructions (the recruiter email is in metadata, but that's contact info;