IT Support Technician II
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate like E-Verify line? That's minor metadata; we can fold into short
or drop. Probably drop.
We need sections only when posting has real specific content. We have sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe Minimum Required Education, Experience & Skills), Preferred Qualifications (list), maybe Organizational Expectations (list). Also maybe Security & Compliance etc but those are part of responsibilities.
We need to decide sections: Could have About the role (p), Responsibilities (ul), Requirements (ul), Preferred Qualifications (ul), Organizational Expectations (ul). Also maybe System Administration etc but those are part of responsibilities.
We must not create Pay/Schedule/Benefits sections because not present.
We need to preserve all substantive info. So we need to capture all bullet points from responsibilities, requirements, preferred, organizational expectations.
Let's extract.
Responsibilities list (from "Key Responsibilities"): bullet points:
- Provide end-user support, fulfilling requests and troubleshooting hardware/software incidents.
- Address escalated incidents from the IT Service Desk and Tier I technicians
- Visit regional office locations as needed to address on-site support issues, engaging with customers.
- Utilize remote tools and utilities for efficient support resolution, ensuring service level standards of timely response and quality assurance are maintained.
- Document incidents using service desk systems or tools.
- Effectively communicate with end-users, providing customer service excellence through expectation management.
- Identify and recommend automation or self-service enhancements to improve support efficiency.
- Deliver onboarding and training sessions for new users.
- Educate staff on IT best practices, processes, and preventive measures.
- Perform root cause analysis and implement long-term solutions.
- Troubleshoot basic Network connectivity problems for both wired and wireless configurations.
- Travel to physician practices, clinics, regional offices, and other company locations as required to perform on-site support, equipment deployment, troubleshooting, maintenance, and project-related activities.
- Participate in the IT after-hours on-call rotation and respond to critical incidents, outages, and urgent business needs outside of normal business hours.
- System Administration: Perform administrative tasks and troubleshoot enterprise systems delivery to end-users, i.e Microsoft 365, Azure Active Directory, Intune, Windows, etc.
- Manage user accounts, permissions, and group policies.
- Support endpoint management, imaging, and deployment processes.
- Support enterprise applications and backend infrastructure.
- Security & Compliance: Ensure adherence to HIPAA and internal data protection policies.
- Maintain endpoint security through enterprise tools, ensuring alignment to standards and policy.
- Support backup and recovery operations.
- Organizational Expectations: Work closely with peer teams to collaborate on cross-functional issues or escalated items.
- Document solutions and contribute to the internal knowledge base.
- Monitor system performance and availability using enterprise tools.
- Effectively communicate with leadership regarding observations, situations, and expected needs
- Actively participate in department meetings, quarterlies, and annual evaluations
- Embrace the mission and vision of the technology department, in support of meeting the organizational goals and initiatives.
But note that "System Administration", "Security & Compliance", "Organizational Expectations" are subheadings within responsibilities. However we can keep them as part of responsibilities list; but they are headings inside. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a section for Responsibilities with Responsibilities
and then a containing all responsibility items. We can include sub-items as list items; we don't need nested headings.
Similarly for Requirements: Minimum Required Education, Experience & Skills list.
Preferred Qualifications list.
Organizational Expectations could be its own section or part of responsibilities; but it's listed under "Organizational Expectations". Could be separate section. However we need to avoid thin sections; but it's substantive.
We'll create sections: About the role (p), Responsibilities (ul), Requirements (ul), Preferred Qualifications (ul), Organizational Expectations (ul).
Now extract each.
About the role: The first sentence(s) before "Key Responsibilities": "InnovaCare Management Services Company, LLC The IT Support Technician II will play a critical role in delivering advanced technical support across InnovaCare Health’s clinical care delivery environment. This position ensures the stability, security, and performance of end-user systems and services, with a strong focus on Microsoft technologies, healthcare compliance, and customer-centric service delivery."
We need to preserve that. Probably combine into a paragraph.
Now Requirements list: "Minimum Required Education, Experience & Skills Industry related education, training, or certifications.3+ years in service desk or technical support rolesExperience supporting C-level users and distributed teams.Proficiency in Microsoft 365, Azure AD, Intune, Windows, ITIL, ITSMExcellent communication skills with clients and peers; verbal, written, listening, and phone skills.Strong organizational, multitasking, and documentation abilities.Self-motivated with an ability to work and effectively prioritize in a fast-paced environment.Advanced computer literacy skills.Ability to travel to assigned clinics and company locations throughout the service area as needed.Must be available to participate in a rotating after-hours on-call support schedule and respond to critical incidents outside of standard business hours."
We need to split into list items. The text is concatenated without spaces after periods. We'll parse manually.
Items:
- Industry related education, training, or certifications.
- 3+ years in service desk or technical support roles
- Experience supporting C-level users and distributed teams.
- Proficiency in Microsoft 365, Azure AD, Intune, Windows, ITIL, ITSM
- Excellent communication skills with clients and peers; verbal, written, listening, and phone skills.
- Strong organizational, multitasking, and documentation abilities.
- Self-motivated with an ability to work and effectively prioritize in a fast-paced environment.
- Advanced computer literacy skills.
- Ability to travel to assigned clinics and company locations throughout the service area as needed.
- Must be available to participate in a rotating after-hours on-call support schedule and respond to critical incidents outside of standard business hours.
Now Preferred Qualifications list: "Associate degree in a technical discipline (Bachelor’s preferred).Industry-related certifications and trainings are a plus, ie A+, Network+, SecurityPrevious experience working within a distributed organization, across multiple geographic sitesPrevious experience working within a healthcare or research environment, dealing with sensitive data standard compliance, such as HIPAA, NIST, PII, PCI, etc"
Split:
- Associate degree in a technical discipline (Bachelor’s preferred).
- Industry-related certifications and trainings are a plus, ie A+, Network+, Security
- Previous experience working within a distributed organization, across multiple geographic sites
- Previous experience working within a healthcare or research environment, dealing with sensitive data standard compliance, such as HIPAA, NIST, PII, PCI, etc
Now Organizational Expectations list: from after "Organizational Expectations Work closely with peer teams..." Actually the text: "Organizational Expectations Work closely with peer teams to collaborate on cross-functional issues or escalated items.Document solutions and contribute to the internal knowledge base.Monitor system performance and availability using enterprise tools.Effectively communicate with leadership regarding observations, situations, and expected needsActively participate in department meetings, quarterlies, and annual evaluationsEmbrace the mission and vision of the technology department, in support of meeting the organizational goals and initiatives."
Split:
- Work closely with peer teams to collaborate on cross-functional issues or escalated items.
- Document solutions and contribute to the internal knowledge base.
- Monitor system performance and availability using enterprise tools.
- Effectively communicate with leadership regarding observations, situations, and expected needs
- Actively participate in department meetings, quarterlies, and annual evaluations
- Embrace the mission and vision of the technology department, in support of meeting the organizational goals and initiatives.
Now Responsibilities list: we need to include all items from the responsibilities section, including subheadings but as list items.
Let's list them clearly:
- Provide end-user support, fulfilling requests and troubleshooting hardware/software incidents.
- Address escalated incidents from the IT Service Desk and Tier I technicians
- Visit regional office locations as needed to address on-site support issues, engaging with customers.
- Utilize remote tools and utilities for efficient support resolution, ensuring service level standards of timely response and quality assurance are maintained.
- Document incidents using service desk systems or tools.
- Effectively communicate with end-users, providing customer service excellence through expectation management.
- Identify and recommend automation or self-service enhancements to improve support efficiency.
- Deliver onboarding and training sessions for new users.
- Educate staff on IT best practices, processes, and preventive measures.
- Perform root cause analysis and implement long-term solutions.
- Troubleshoot basic Network connectivity problems for both wired and wireless configurations.
- Travel to physician practices, clinics, regional offices, and other company locations as required to perform on-site support, equipment deployment, troubleshooting, maintenance, and project-related activities.
- Participate in the IT after-hours on-call rotation and respond to critical incidents, outages, and urgent business needs outside of normal business hours.
- Perform administrative tasks and troubleshoot enterprise systems delivery to end-users, i.e Microsoft 365, Azure Active Directory, Intune, Windows, etc.
- Manage user accounts, permissions, and group policies.
- Support endpoint management, imaging, and deployment processes.
- Support enterprise applications and backend infrastructure.
- Ensure adherence to HIPAA and internal data protection policies.
- Maintain endpoint security through enterprise tools, ensuring alignment to standards and policy.
- Support backup and recovery operations.
- Work closely with peer teams to collaborate on cross-functional issues or escalated items.
- Document solutions and contribute to the internal knowledge base.
- Monitor system performance and availability using enterprise tools.
- Effectively communicate with leadership regarding observations, situations, and expected needs
- Actively participate in department meetings, quarterlies, and annual evaluations
- Embrace the mission and vision of the technology department, in support of meeting the organizational goals and initiatives.
Note some items duplicate with Organizational Expectations list; but they appear also under responsibilities? Actually the "Organizational Expectations" subheading appears after Security & Compliance. The items listed under Organizational Expectations are same as we extracted. But they also appear in responsibilities list? The text after Security & Compliance includes those items. So we should not duplicate. Better to keep responsibilities list up to Security & Compliance items, and then have a separate Organizational Expectations section for those items. Let's verify original text:
"Organizational Expectations Work closely with peer teams to collaborate on cross-functional issues or escalated items.Document solutions and contribute to the internal knowledge base.Monitor system performance and availability using enterprise tools.Effectively communicate with leadership regarding observations, situations, and expected needsActively participate in department meetings, quarterlies, and annual evaluationsEmbrace the mission and vision of the technology department, in support of meeting the organizational goals and initiatives."
Thus those items belong to Organizational Expectations, not responsibilities. So responsibilities list should stop before that. Let's separate.
Responsibilities items (up to Security & Compliance):
- Provide end-user support, fulfilling requests and troubleshooting hardware/software incidents.
- Address escalated incidents from the IT Service Desk and Tier I technicians
- Visit regional office locations as needed to address on-site support issues, engaging with customers.
- Utilize remote tools and utilities for efficient support resolution, ensuring service level standards of timely response and quality assurance are maintained.
- Document incidents using service desk systems or tools.
- Effectively communicate with end-users, providing customer service excellence through expectation management.
- Identify and recommend automation or self-service enhancements to improve support efficiency.
- Deliver onboarding and training sessions for new users.
- Educate staff on IT best practices
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate like E-Verify line? That's minor metadata; we can fold into short
or drop. Probably drop. We need sections only when posting has real specific content. We have sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe Minimum Required Education, Experience & Skills), Preferred Qualifications (list), maybe Organizational Expectations (list). Also maybe Security & Compliance etc but those are part of responsibilities. We need to decide sections: Could have About the role (p), Responsibilities (ul), Requirements (ul), Preferred Qualifications (ul), Organizational Expectations (ul). Also maybe System Administration etc but those are part of responsibilities. We must not create Pay/Schedule/Benefits sections because not present. We need to preserve all substantive info. So we need to capture all bullet points from responsibilities, requirements, preferred, organizational expectations. Let's extract. Responsibilities list (from "Key Responsibilities"): bullet points: - Provide end-user support, fulfilling requests and troubleshooting hardware/software incidents. - Address escalated incidents from the IT Service Desk and Tier I technicians - Visit regional office locations as needed to address on-site support issues, engaging with customers. - Utilize remote tools and utilities for efficient support resolution, ensuring service level standards of timely response and quality assurance are maintained. - Document incidents using service desk systems or tools. - Effectively communicate with end-users, providing customer service excellence through expectation management. - Identify and recommend automation or self-service enhancements to improve support efficiency. - Deliver onboarding and training sessions for new users. - Educate staff on IT best practices, processes, and preventive measures. - Perform root cause analysis and implement long-term solutions. - Troubleshoot basic Network connectivity problems for both wired and wireless configurations. - Travel to physician practices, clinics, regional offices, and other company locations as required to perform on-site support, equipment deployment, troubleshooting, maintenance, and project-related activities. - Participate in the IT after-hours on-call rotation and respond to critical incidents, outages, and urgent business needs outside of normal business hours. - System Administration: Perform administrative tasks and troubleshoot enterprise systems delivery to end-users, i.e Microsoft 365, Azure Active Directory, Intune, Windows, etc. - Manage user accounts, permissions, and group policies. - Support endpoint management, imaging, and deployment processes. - Support enterprise applications and backend infrastructure. - Security & Compliance: Ensure adherence to HIPAA and internal data protection policies. - Maintain endpoint security through enterprise tools, ensuring alignment to standards and policy. - Support backup and recovery operations. - Organizational Expectations: Work closely with peer teams to collaborate on cross-functional issues or escalated items. - Document solutions and contribute to the internal knowledge base. - Monitor system performance and availability using enterprise tools. - Effectively communicate with leadership regarding observations, situations, and expected needs - Actively participate in department meetings, quarterlies, and annual evaluations - Embrace the mission and vision of the technology department, in support of meeting the organizational goals and initiatives. But note that "System Administration", "Security & Compliance", "Organizational Expectations" are subheadings within responsibilities. However we can keep them as part of responsibilities list; but they are headings inside. The instruction: Use