Unified Communications Technician

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. We need to parse the description. First, we have description: "Penn Medicine is dedicated to our tripartite mission..." That's about the organization, maybe "About the role"? Actually "About the role" could be a summary of the role. The posting includes "Position Summary:" and then description of UC Technician responsibilities. So we can put that under "About the role" or maybe "Responsibilities". The instructions: Use

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: - Position Summary: description of UC Technician role. That could be "About the role". - Accountabilities: bullet list of duties (Unified Communications Support, End User Support, Project Support, On-Call Support, Other duties). That's responsibilities. - Minimum Required Education and Experience: that's requirements/qualifications. - Benefits: mention of employee benefits programs, comprehensive compensation and benefits program, prepaid tuition assistance. That's benefits. - Pay: Not mentioned explicitly. No salary. So we should NOT include Pay section. - Schedule: "Hours: Remote, M-F, 8am-5pm". That's schedule info. So we can include Schedule section. - Skills: maybe not explicit list; but we could infer from responsibilities: technical skills, but we should not invent. The posting does not have a separate "Skills" section. So we should not include Skills unless there is explicit content. There's no explicit skills list. So omit. - Qualifications: Could be same as Requirements. The posting has "Minimum Required Education and Experience". That's qualifications. We could put that under "Requirements" or "Qualifications". The instruction says use headings like Requirements, Qualifications. We need to decide which to include. We have content for education/experience. Could put under "Requirements". Also there is "1+ years of End user support experience (PCs, Mobility Devices, Telephony support) is preferred." That's a preferred qualification. So we can include that. Thus sections: About the role (position summary), Responsibilities (accountabilities), Requirements (minimum required education and experience + preferred), Benefits, Schedule. We must not repeat job title as heading. The job title is "Unified Communications Technician". Not to be used as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO statement, etc. Remove the equal opportunity employer paragraph. Also remove "Live Your Life's Work" maybe? That's a tagline but not boilerplate? It's part of the posting but not a section; we can keep as prose maybe under About the role? It's not essential but we can keep if it's not boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO paragraph is to be removed. The "Live Your Life's Work" is a slogan; not sure if considered boilerplate. It's not legal; it's a motivational tagline. Might keep as part of About the role. Also "We believe that the best care for our patients starts with the best care for our employees." That's part of benefits description; we can keep. Now we need to format. We'll produce:

About the role

Position Summary: A Unified Communications (UC) Technician is responsible for managing and supporting an organization's communication systems, which includes voice, messaging, fax and collaboration platforms. Their role ensures that all these systems work seamlessly together to enable efficient and effective communication across the organization. The UC Technician is responsible for organizing and completing the technical day-to-day operations assigned through service request work orders and incident trouble calls. Support is often coordinated with internal departments and various telecommunications service partners and carriers.

Maybe also include the mission statement? Could be part of About the role. But we can keep as separate paragraph. Better to include the initial description about Penn Medicine mission? That's not about the role but about the organization. Could be part of About the role? Might be considered boilerplate? It's not legal; it's organizational description. Might keep. But we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the mission statement? It's substantive about the organization. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that paragraph about Penn Medicine's tripartite mission, etc. However, we need to decide where to place it. Could be part of About the role or maybe a separate section like "About Penn Medicine". But we only allowed headings from the list. We could incorporate it into About the role paragraph. Thus About the role could include both the Penn Medicine mission description and the Position Summary. Now Responsibilities: we need to list the accountabilities bullet points. Use

• . We need to capture all bullet points: Under Accountabilities: - Unified Communications Support * Install, configure, and maintain Unified Communications (UC) hardware and software systems (e.g., Avaya VoIP and voicemail systems, mobile devices, voice dialing support for Microsoft Teams. * Troubleshoot and resolve issues related to telephony platforms including interacting with service providers and support vendors as required. * Support mobile devices (smartphones, basic phones and pagers), including hardware and operating systems (iOS, iPadOS, Android). * Troubleshooting and configuration for deployment. * Work closely with IT teams to ensure the UC systems are integrated with other IT infrastructure * Supports and Troubleshoots Enterprise Fax solutions, including monitoring and maintenance. * Supports MS Teams Voice dialing environment, including account creation and end user support throughout the organization. * Inventory management (receiving, shipping, notifications and deployment of hardware) - End User Support * Provides support to customers internally and externally as needed. * Performs basic troubleshooting and analysis of systems. * Answers end user questions and resolves issues. * Assist in instructing end users in the operation and maintenance of systems/equipment. * Updates tickets and assignments according to established procedures. * Escalates complex service issues to UC Engineer or Senior UC Technician for assistance. - Project Support * Refers issues/questions to appropriate personnel/manager for follow-up, testing and troubleshooting. * Participates in new equipment installations and large move projects coordinated by management. - On-Call Support * Provides on-call support for the UC environment on a rotating schedule. * Performs duties in accordance with Penn Medicine and entity values, policies, and procedures - Other duties as assigned to support the unit, department, entity, and health system organization We need to preserve all that. We can structure as a single list or grouped under headings? The instruction: Use
  • for any list of duties/requirements/benefits. So we can just make a flat list of all duties. But we might lose grouping. However, we can keep grouping by using
    • and maybe include subheadings inside
    • ? Not allowed? We could embed headings inside
    • . That's okay. Simplify: create a
      with each duty as
      • . Could be long but okay. Now Requirements: Minimum Required Education and Experience: H.S. Diploma / GED required and 2+ years of Information Technology experience Or Bachelor’s Degree and 1+ years Information Technology experience. 1+ years of End user support experience (PCs, Mobility Devices, Telephony support) is preferred. We can put as
        • items. Now Benefits: The paragraph: "We believe that the best care for our patients starts with the best care for our employees. Our employee benefits programs help our employees get healthy and stay healthy. We offer a comprehensive compensation and benefits program that includes one of the finest prepaid tuition assistance programs in the region. Penn Medicine employees are actively engaged and committed to our mission. Together we will continue to make medical advances that help people live longer, healthier lives." We can put that as

          under Benefits. Now Schedule: "Hours: Remote, M-F, 8am-5pm". We can put as

          under Schedule. Now we must not include Pay section. Now ensure we removed EEO paragraph and any duplicated lines. Check for duplicated lines: The description includes "Live Your Life's Work" appears twice? Actually appears once near the end after benefits? It appears: "Live Your Life's Work We are an Equal Opportunity employer." Actually the text: "Live Your Life's Work We are an Equal Opportunity employer. Candidates are considered..." So we need to remove the EEO paragraph but keep "Live Your Life's Work"? It's attached to EEO. Might be safer to remove the whole sentence "Live Your Life's Work We are an Equal Opportunity employer...." as it's mostly EEO. But "Live Your Life's Work" is a tagline; but it's attached to EEO. The instruction: Remove EEO/equal-opportunity boilerplate. So we should remove that entire sentence. So we will not include "Live Your Life's Work". That's okay. Now also remove any navigation/cookie etc. Not present. Now produce HTML fragment. Let's craft. We'll start with

          About the role

          then a

          containing the Penn Medicine mission description and Position Summary. Mission description: "Penn Medicine is dedicated to our tripartite mission of providing the highest level of care to patients, conducting innovative research, and educating future leaders in the field of medicine. Working for this leading academic medical center means collaboration with top clinical, technical and business professionals across all disciplines. Today at Penn Medicine, someone will make a breakthrough. Someone will heal a heart, deliver hopeful news, and give comfort and reassurance. Our employees shape our future each day." Then Position Summary: "A Unified Communications (UC) Technician is responsible for managing and supporting an organization's communication systems, which includes voice, messaging, fax and collaboration platforms. Their role ensures that all these systems work seamlessly together to enable efficient and effective communication across the organization. The UC Technician is responsible for organizing and completing the technical day-to-day operations assigned through service request work orders and incident trouble calls. Support is often coordinated with internal departments and various telecommunications service partners and carriers." We can combine into one paragraph or two. Probably two paragraphs. Now Responsibilities:

          Responsibilities

          then
          • ... each duty. We need to ensure we capture all duty statements exactly as in text. Let's extract each bullet: From Unified Communications Support: - Install, configure, and maintain Unified Communications (UC) hardware and software systems (e.g., Avaya VoIP and voicemail systems, mobile devices, voice dialing support for Microsoft Teams. - Troubleshoot and resolve issues related to telephony platforms including interacting with service providers and support vendors as required. - Support mobile devices (smartphones, basic phones and pagers), including hardware and operating systems (iOS, iPadOS, Android). - Troubleshooting and configuration for deployment. - Work closely with IT teams to ensure the UC systems are integrated with other IT infrastructure - Supports and Troubleshoots Enterprise Fax solutions, including monitoring and maintenance. - Supports MS Teams Voice dialing environment, including account creation and end user support throughout the organization. - Inventory management (receiving, shipping, notifications and deployment of hardware) End User Support: - Provides support to customers internally and externally as needed. - Performs basic troubleshooting and analysis of systems. - Answers end user questions and resolves issues. - Assist in instructing end users in the operation and maintenance of systems/equipment. - Updates tickets and assignments according to established procedures. - Escalates complex service issues to UC Engineer or Senior UC Technician for assistance. Project Support: - Refers issues/questions to appropriate personnel/manager for follow-up, testing and troubleshooting. - Particip