Information Technology Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" and "Position Overview". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting includes "About Us" (company description) and "Position Overview". Could map "About Us" to "About the role"? Probably "About the role" is appropriate. Then "Duties and Responsibilities" -> Responsibilities. "Minimum Qualifications" and "Preferred Qualifications" -> Requirements/Qualifications/Skills? We need to decide. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills. But we should avoid thin sections. We can combine similar content. We have: - About Us: description of company. Could be About the role? Actually About the role is more about the job, but we have Position Overview describing role. So we could use About the role for Position Overview. - Responsibilities: Duties and Responsibilities list. - Requirements: Minimum Qualifications (citizenship, clearance, degree, years experience, etc.) - Qualifications: Preferred Qualifications (certifications, etc.) - Skills: maybe we could extract technical skills from responsibilities and qualifications? But we already have them in qualifications. Could create Skills section summarizing technical skills: Microsoft 365, AWS, Azure, VMware, networking, etc. But we must not invent or summarize away detail; we can list them as they appear. However we already have them in responsibilities and qualifications. Might be redundant. Better to have sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred). Possibly also Skills if distinct content. But we can combine qualifications and skills? The instruction says prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including both minimum and preferred). But they said we can have Requirements, Qualifications, Skills as separate headings. We need to decide based on content. We have substantial content for Minimum Qualifications and Preferred Qualifications. Could split into Requirements (minimum) and Qualifications (preferred). Skills could be derived from responsibilities but we already have them listed there; maybe we can omit Skills to avoid thin. Benefits, Pay, Schedule: The posting mentions hybrid schedule: three days in office, two days remote. That's schedule info. So we can include Schedule section with that detail. No explicit benefits or pay mentioned. So we omit Benefits and Pay. Thus sections: About the role (Position Overview), Responsibilities, Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Schedule. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from each section. Let's extract: About the role (Position Overview): "Sealing Technologies, a Parsons Company, is looking for an IT Manager to join our Corporate IT team in Columbia, MD. Reporting to the Director of IT, this role leads the IT team in executing the objectives, priorities, and project portfolio established by the Director, ensuring projects and operational initiatives are driven through completion. This is a hands on management role rather than a personnel management role. Prior experience leading or supervising IT staff is required (but this position has no direct reports; all IT staff continue to report to the Director of IT). The IT Manager provides technical direction, advises and unblocks the team, owns escalations, and executes technical work directly when the situation calls for it.The role demands a broad technical skill set across varying levels of infrastructure and enterprise technology, including Microsoft 365, AWS, Azure, VMware, networking, and systems administration. The ideal candidate moves comfortably between running a project plan, advising the team, and solving a problem personally, and communicates clearly with leadership, engineers, and non-technical users alike. The position is hybrid and based entirely out of our Columbia, MD headquarters: three days per week in office, with two days remote. Occasional travel may be required as business needs dictate." We need to avoid repeating job title as heading (already not). Also we should not include Job ID etc. Not present. We need to remove boilerplate like About Us? Actually we used About the role from Position Overview. The About Us paragraph at start: "Sealing Technologies, a Parsons company, innovates and delivers high-performance deployable anywhere technologies..." That's company description. Should we include that? It's substantive but not about the role. Could be part of About the role? Might be considered company overview. The instruction: Use headings for section headings (e.g. About the role, Responsibilities...). It didn't forbid including company description. Could include it in About the role section as prose. But we already have Position Overview; we could combine both About Us and Position Overview into About the role. However we must not invent or summarize away detail; we can include both paragraphs. Thus About the role section will contain two paragraphs: first the About Us description, second the Position Overview details. Now Responsibilities: list of duties from "Duties and Responsibilities:" bullet points (each line starts with a verb). We need to put each as

• inside
  . Preserve all. Let's copy them exactly: - Lead execution of the IT objectives, priorities, and project portfolio established by the Director of IT, driving projects and operational initiatives through completion. - Provide day-to-day technical direction to the IT team; this position has no direct reports, as all IT staff report to the Director of IT. - Define project scope, schedule, and task breakdown; track milestones and risks; provide bi-weekly status reporting to the Director of IT and other stakeholders. - Serve as a senior escalation point for complex technical issues across Windows and macOS workstations, business applications, identity, and network connectivity. - Administer and maintain the Microsoft 365 environment, including Entra ID, Active Directory, Intune, and endpoint management across Windows and macOS. - Support corporate network infrastructure, including Wi-Fi, VPN, VLANs, switching, routing, and firewalls. - Support cloud and virtualization platforms, including AWS, Azure, and VMware, along with Windows Server and supporting infrastructure services. - Support day-to-day IT operations, monitoring ticket queue health and stepping in directly when volume or complexity requires it. - Support onboarding and offboarding execution, including account provisioning, equipment issuance, access requests, and timely access removal. - Maintain IT asset lifecycle activities, including inventory accuracy, imaging standards, refresh planning, and equipment disposal. - Coordinate with vendors and resellers on quotes, renewals, licensing, and support cases; make recommendations to the Director of IT. - Track IT spend against the budget set by the Director of IT and provide input and justification for planned purchases. - Implement and enforce corporate IT policies, endpoint standards, and access control procedures defined by the Director of IT and the Security team. - Support compliance efforts, including DoD STIG implementation on workstations and servers, NIST 800-171, CMMC, and internal audit requirements. - Administer the ticketing and ITSM function, including intake, prioritization, service levels, queue hygiene, and metrics reporting to the Director of IT. - Support conference room and AV technology, including Teams Rooms, displays, cameras, microphones, and meeting platforms. - Maintain accurate technical documentation, runbooks, user guides, and standard operating procedures. - Plan and execute upgrades, migrations, and office build-out or reconfiguration work under the direction of the Director of IT. - Support backup, business continuity, and disaster recovery execution and testing for corporate systems. - Serve as a primary IT point of contact when the Director of IT is unavailable, escalating as appropriate. - Other duties as assigned. Now Requirements (Minimum Qualifications): list: - U.S. Citizenship. - Must hold or be able to obtain and maintain a Secret security clearance. - Bachelor’s degree in Information Technology, Computer Science, or a related field. - 6- 8 years of experience in IT operations or systems administration, including at least 2 years directly supervising or leading a team. - Demonstrated ownership of IT projects from planning through completion. - Ability to work in-office from the Columbia, MD headquarters three days per week, with two days remote. - Experience administering Microsoft 365 services, including Entra ID and Active Directory. - Experience with Intune and endpoint management across Windows and macOS, including baselines, imaging, and software deployment for onsite and remote users. - Experience providing escalation-level desktop support across Windows and macOS. - Working knowledge of Windows Server administration and networking fundamentals, including switching, routing, VLANs, Wi-Fi, firewalls, and VPN technologies. - Working knowledge of cloud and virtualization platforms such as AWS, Azure, or VMware. - Experience managing IT asset lifecycle, procurement, vendor relationships, and software licensing. - Experience with a ticketing or ITSM platform, and with tracking spend against a departmental budget. - Experience writing and enforcing corporate IT policies and creating technical and non-technical procedures. - Familiarity with DoD STIGs and their implementation on workstations and servers. - Strong written and verbal communication skills, including the ability to report project status to leadership. - Strong customer service orientation and the ability to support users with varying levels of technical experience. Note: The "Ability to work in-office..." is also schedule info; but we already have schedule section. Might duplicate. We'll keep it in Requirements as it's a qualification. But we could also move schedule to Schedule section and remove duplicate. However we must preserve all substantive information; we can keep it in both places? That would be duplication. Better to avoid duplication: we can note schedule in Schedule section and not repeat in Requirements. But the requirement includes ability to work in-office... which is essentially schedule. We could keep it in Requirements as it's a qualification, and also have Schedule section summarizing. That would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but could be considered redundant. However they said remove duplicated lines. So we should avoid duplicating the same sentence. So we should place the schedule info only once. Where? Probably in Schedule section. Then we should remove it from Requirements. But the requirement list includes that sentence; we need to preserve it. If we remove it, we lose that info. So we need to keep it somewhere. We could keep it in Requirements and not have a separate Schedule section, but we also have schedule info in Position Overview (three days per week in office, with two days remote). That's also schedule. So we could keep schedule info in About the role (Position Overview) and not have separate Schedule section. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Schedule section if we have specific content. We have schedule info in Position Overview and also in Minimum Qualifications. To avoid duplication, we could keep schedule info only in About the role (Position Overview) and not repeat in Minimum Qualifications. But we would be removing that sentence from Minimum Qualifications, which is substantive. However we could rephrase: we could keep the sentence but note that it's about schedule; duplication would be if we also have Schedule section with same sentence. If we don't have Schedule section, we keep it only once in Minimum Qualifications. That satisfies no duplication. Then we don't need Schedule section. But we also have schedule info in Position Overview; that would be duplicate if we keep both. So we could remove schedule sentence from Position Overview? But that is also substantive. We need to keep all substantive info; we can keep it in either place but not both. Choose one place to keep schedule info. Perhaps keep it in Minimum Qualifications as it's explicitly a requirement. Then we can omit schedule mention from Position Overview?