Tech Enablement Manager

We need to output HTML fragment with sections: About the role? Actually we have Company Overview, Position Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Pre-Employment Requirements, Physical Requirements, Work Schedule, Company Benefits, Additional Responsibilities (maybe not needed). We must not repeat job title as heading. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map sections accordingly. The posting includes Company Overview, Position Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Pre-Employment Requirements, Physical Requirements, Work Schedule, Company Benefits, Additional Responsibilities. We need to decide which headings to use. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use headings like "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits", "Schedule". We should not create sections without real content. We need to preserve all substantive information. We need to decide how to split content: "Company Overview" could be "About the role"? Actually "About the role" is more about the role, not company overview. But we can still use "About the role" heading for company overview + position summary? The instruction says we can use those example headings, but not required to exactly match; we just need to use

for section headings. Probably we should create headings that reflect content: "About the role" could contain Company Overview and Position Summary. "Responsibilities" for Key Responsibilities. "Qualifications" could contain Required and Preferred Qualifications (maybe separate subheadings? But we can't use

? Not prohibited but we should stick to

for sections; we could have nested

but not required. Simpler: have "Required Qualifications" and "Preferred Qualifications" as separate

sections. That's okay. "Pre-Employment Requirements" maybe could be under "Requirements"? But we have a heading "Requirements" example. Could use "Requirements" for Pre-Employment Requirements plus maybe Physical Requirements? But Physical Requirements is separate. Could combine? Better to keep separate sections if they have content. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible. We have: Required Qualifications, Preferred Qualifications, Pre-Employment Requirements (Driver's license, background check, drug test, E-Verify), Physical Requirements, Work Schedule, Company Benefits, Additional Responsibilities (maybe not needed as it's generic). Also Company Overview and Position Summary. We could create sections: - About the role (Company Overview + Position Summary) - Responsibilities (Key Responsibilities) - Qualifications (Required Qualifications + Preferred Qualifications) maybe split into Required and Preferred as subheadings

but we can keep as

each? That would be many sections. Perhaps combine into one "Qualifications" section with two

lists: Required and Preferred. That's substantive. - Requirements (Pre-Employment Requirements + Physical Requirements) maybe combine. - Benefits (Company Benefits) - Schedule (Work Schedule) We should omit Additional Responsibilities as it's generic boilerplate. We must not include Pay section because not specified. We must not include Skills section unless present; we have skills implied in qualifications but not separate. We need to preserve all substantive information: So we need to include all details from each area. Let's extract content. Company Overview: Since 1994, Diversified Fall Protection (DFP) has been a full-service fall protection provider and trusted partner, dedicated to making workplaces safer. Our core purpose is simple yet powerful: Saving Lives. As safety-minded professionals, we deliver integrated fall protection solutions with a focus on reducing risk and keeping workers safe. At DFP, we believe that being Easy to Work With isn't just a pledge it's a principle we live by every day. Guided by our Core Values Resolven, Do the right thing, Be versatile, and Take people to higher ground we strive to build trust with our customers, industry partners, and each other. Everything we do is driven by the belief that the worker is at the center of our brand. When faced with decisions, we ask: Which choice ensures that a worker makes it home at the end of the day? Our culture, commitment, and creative expression all serve this core purpose, often reflected in the message we stand behind: #NoFalls. Position Summary: The Technology Enablement Manager is DFP's internal owner for daily technology support, vendor coordination, asset management, and end-user enablement. This role bridges employees, leadership, and the external MSP by resolving appropriate issues, escalating effectively, and improving documentation, onboarding, security hygiene, and IT service quality. Key Responsibilities: list bullet points. We need to convert each bullet into
• inside
  . Let's list them: - Provide help desk support for Windows and macOS users, including software installs, peripherals, mailbox access, Teams, OneDrive/SharePoint, and basic hardware issues. - Administer user lifecycle tasks in Active Directory/Entra ID and Microsoft 365, including accounts, passwords, groups, licensing, and basic security settings. - Triage Wi-Fi, VPN, DNS, DHCP, and ISP issues; resolve directly when appropriate and escalate when needed. - Support endpoint and mobile devices, including laptop setup, MDM enrollment, patch awareness, endpoint protection checks, and warranty/repair coordination. - Own asset, license, renewal, hardware refresh, SaaS, M365, and related IT spend tracking. - Serve as DFP's primary MSP contact for escalation, follow-up, SLA/scope awareness, recurring issues, and service reporting. - Maintain IT documentation, including SOPs, onboarding/offboarding checklists, network diagrams, asset records, and credential vaulting practices. - Communicate technology changes, outages, security reminders, and basic training in plain language. - Support security and compliance hygiene, including MFA awareness, patch follow-up, endpoint reporting, and CMMC-type coordination. - Participate in IT planning, budget tracking, vendor renewals, and roadmap discussions with the MSP. Required Qualifications: list bullet points. - Hands-on IT support experience, including Windows and/or macOS troubleshooting, M365 user support, hardware setup, and peripherals. - Working knowledge of Active Directory and/or Entra ID for accounts, passwords, unlocks, and group changes. - Familiarity with Microsoft 365 administration and Outlook, Teams, OneDrive, and SharePoint support. - Basic networking knowledge, including Wi-Fi, VPN, DNS, DHCP, and issue triage. - Ticketing system experience with clear documentation, categorization, prioritization, and user updates. - Strong customer service skills and clear communication with non-technical employees. - Ability to manage interruptions, prioritize competing requests, and choose direct resolution or MSP escalation appropriately. - Strong documentation habits and willingness to own runbooks, checklists, asset records, and process improvements. - Ability to explain technical issues, risks, and tradeoffs in business terms. Preferred Qualifications: list bullet points. - Experience with MDM tools such as Intune, JAMF, Hexnode, or similar platforms. - Experience tracking IT assets, licenses, refresh cycles, renewals, vendor contracts, or IT budget items. - Exposure to MSP/vendor management, including SLA review, escalation, recurring-issue analysis, and service follow-up. - Basic PowerShell or scripting experience for repetitive provisioning or administration tasks. - Awareness of MFA, patching, endpoint protection, incident communication, and CMMC-type requirements. - Experience supporting onboarding/offboarding, new-hire technology orientation, or security-awareness training. - Interest and aptitude to grow into IT planning, vendor negotiation, budget ownership, and incident coordination. Pre-Employment Requirements: list bullet points. - Valid Drivers License & Evidence of Ability to Insure - Criminal Justice Background Check (state and federal) - Drug Test (5-panel) - E-Verify eligibility verification Physical Requirements: paragraph. "This is a largely sedentary role. This position may require employees to sit at a computer station/desk for prolonged periods of time up to 8 hours a day. The employee is regularly required to read, count and write to accurately complete documentation required for position. Employees must be able to use hands and fingers to operate keyboard and phone and to file and operate office equipment. This position may require some walking, bending, reaching and standing." Work Schedule: paragraph. "This is a full-time salary exempt position with a typical Monday through Friday schedule, following a standard 40-hour workweek. Regular business hours apply, generally within the range of 8:00 a.m. to 5:00 p.m., and may vary based on company needs." Company Benefits: paragraph. "Benefit eligibility begins on the first of the month following the completion of 30 days of employment Benefits offered are: Medical, Dental, Vision, Long-term Disability, Short-term Disability, Life Insurance 401(k) contribution eligibility is the start of the first pay period following the completion of 30 days of employment through John Hancock employer match is 5% at enrollment" We need to preserve that exactly. Now we need to output HTML fragment with

  headings and

  or

  • . We must not include any extra text like explanations. We'll produce:

    About the role

    Company Overview ... Position Summary ...

    But we need to combine Company Overview and Position Summary into one

    maybe two paragraphs? Could be two

    elements under same heading. That's fine. Then

    Responsibilities

    ...
    Then

    Qualifications

    We could have two subheadings

    but not required. Could just have two

    with preceding

    indicating Required and Preferred. But we need to preserve all info. Could do:

    Qualifications

    Required

    ...

    Preferred

    ...
    But the instruction only says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could stick to

    only. However we need to differentiate Required vs Preferred. Could embed them as inside a

    then

    . Eg:

    Qualifications

    Required:

    ...

    Preferred:

    ...
    That preserves info and uses only

    for section heading. Similarly for Requirements (Pre-Employment + Physical). Could do:

    Requirements

    Pre‑Employment Requirements:

    ...

    Physical Requirements:

    ...

    But Physical Requirements is a paragraph not a list. Could keep as

    . For Benefits:

    Benefits

    ...

    For Schedule:

    Schedule

    ...

    We must not include Pay. Now ensure we don't include boilerplate like EEO, Additional Responsibilities, etc. Check that we haven't missed any substantive info: The company overview and position summary are included. Responsibilities included. Qualifications included. Pre-employment requirements included. Physical requirements included. Work schedule included. Benefits included. We omitted "Additional Responsibilities" and "EEO statement". Good. Now produce HTML. We need to be careful with HTML escaping: The content includes apostrophes, ampersands, etc. We'll keep as is; it's fine. Let's craft. First, About the role: combine company overview and position summary