Systems Administrator Mr Price Group Technology

for intro paragraphs and general text. Use

for section headers. The job description includes multiple paragraphs and two

lists. Need to identify sections: maybe "Responsibilities" and "Qualifications" etc. But the description doesn't have explicit headers. We need to create appropriate headers? The rules: Use

for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). We need to map content to appropriate headers. The content includes responsibilities (the first paragraphs) and then a list of duties (the second ul). Also there are many bullet points that seem like responsibilities. The first two paragraphs describe purpose and responsibilities. Then there are two ul lists: first list seems like requirements/qualifications (minimum 2-3 years, Windows Server, Linux, hardware, virtualization, patching, vulnerability, Azure AD, Intune, M365, backup, monitoring, troubleshooting, data centre ops). The second ul list seems like more detailed responsibilities (document standards, capacity planning, troubleshoot, maintain, backup, patch, upgrade, admin Azure AD/Intune/M365, endpoint compliance, identity, work with senior engineers, secure ops, change management, documentation, BCDR, data centre support, continuous improvement). So we need to decide headers. Probably first paragraph(s) are "About the Role" or "Key Duties". The second list is "Responsibilities". The first list could be "Qualifications" or "Requirements". Let's see: The first list includes "Minimum 2–3 years in a technical role covering implementation and maintenance of enterprise systems and infrastructure" (experience requirement). Then "Strong hands-on knowledge of Microsoft Windows Server..." etc. Those are qualifications/experience. So we can label that as

Qualifications

or

Requirements

. The second list is more duties, so

Key Duties

or

Responsibilities

. The first paragraphs could be "About the response. Let me check again. The original text: first three

tags. Then two

lists. The first
has items that are requirements (minimum years, Windows, Linux, hardware, etc.). The second
has more detailed responsibilities (document standards, capacity planning, troubleshoot, maintain, backup, patch, upgrade, admin Azure AD/Intune/M365, endpoint compliance, identity, work with senior engineers, secure ops, change management, documentation, BCDR, data centre support, continuous improvement). So we need to map these to appropriate headers. The first three paragraphs collectively describe the role's purpose and tasks. They could be considered "About the Role" or "Key Duties". But the second list is more detailed tasks. The first list is more like "Requirements". Let's see: The first list items are: - Minimum 2–3 years in a technical role covering implementation and maintenance of enterprise systems and infrastructure - Strong hands-on knowledge of Microsoft Windows Server operating system administration - Working knowledge of Linux operating systems (RHEL, Ubuntu or similar distributions) - Good working knowledge of server hardware platforms, hypervisors, networking and storage infrastructure - Experience with virtualisation platforms - Hands-on experience with installation, upgrades and patching of server hardware, platform software and third-party applications - Experience with vulnerability identification and remediation across enterprise environments - Experience administering Microsoft Entra ID (Azure AD) including user lifecycle management, RBAC, conditional access and SSO configuration - Hands-on experience with Microsoft Intune for device enrolment, compliance policy management and application deployment - Experience managing the Microsoft 365 suite including Exchange Online, SharePoint, Teams, OneDrive and licensing administration - Core understanding of data backup solutions, restore procedures and disaster recovery planning and testing - Familiarity with enterprise backup tools such as Veeam or Commvault advantageous - Experience using enterprise monitoring tools to proactively manage system health and performance - Ability to troubleshoot, performance tune and optimise enterprise systems and infrastructure - Exposure to Data Centre operations including racking, cabling, decommissioning and asset documentation - (then the second list) more detailed tasks. So the first list is indeed requirements/qualifications. The second list is responsibilities. The first three paragraphs are description/intro. Thus we need to create appropriate headers. The description does not have explicit headers, so we need to infer. The first three paragraphs could be "About the Role" or "Key Duties". But the second list is more specific duties. The first list is requirements. Let's decide: - The first three paragraphs: they describe the purpose and tasks. Could be "About the Role" (maybe "Key Duties" is more appropriate). But the second list is also duties. Hmm. Maybe we can treat the first three paragraphs as "About the Role" (intro). Then the first list as "Requirements". Then the second list as "Responsibilities". Or we could combine them all under "Key Duties" and "Qualifications". The instruction says we must use

for section headers, and they gave examples: "