IT Systems Integration Consultant
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use these headings only if content exists. We need to map content to appropriate headings.
We have:
- About the role: Could be "Position Summary". Use heading "About the role" maybe? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. So we need sections: About the role (position summary), Responsibilities (essential duties), Requirements (education/experience/certifications maybe?), Qualifications (desired experience/certifications?), Skills (maybe combine?), Benefits (company benefits), Pay (none), Schedule (none). We should only include sections with real content.
We have no explicit Pay or Schedule info, so omit those sections.
We have Benefits: "Hybrid Work Options, Paid Time Off, and Paid HolidaysMedical, Dental, Vision, and 401(k) with employer match contributionsStability to grow alongside hard-workers in a collaborative environment with opportunities to grow professionally". This is a run-on sentence; we need to preserve all substantive information. We'll parse: Hybrid Work Options, Paid Time Off, Paid Holidays, Medical, Dental, Vision, 401(k) with employer match contributions, Stability to grow alongside hard-workers in a collaborative environment with opportunities to grow professionally. We'll put as list items.
Responsibilities: list of duties.
Requirements: Education/Experience/Certifications (2-4 years experience, basic knowledge etc). Qualifications: Desired Experience/Certifications (certifications plus etc). Skills: maybe we can include communication skills, team player etc. But we have "Excellent written/verbal communication skillsMust be a team player with outstanding client service skills". That's under Desired Experience/Certifications? Actually appears after "Desired Experience/Certifications". We'll treat as Skills.
We need to avoid repeating job title as heading. No Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We must not create sections with filler like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's craft:
About the role
About the role
[Position Summary text]
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- Excellent written/verbal communication skills
- Must be a team player with outstanding client service skills
Benefits
- Hybrid Work Options
- Paid Time Off
- Paid Holidays
- Medical
- Dental
- Vision
- 401(k) with employer match contributions
- Stability to grow alongside hard-workers in a collaborative environment with opportunities to grow professionally
. Responsibilities list: Let's copy each bullet from "Essential Duties And Responsibilities". The text: "Responsible for approved technology integration of acquired customers and acquired team with accuracy and minimal disruption Execute deployment in compliance with established technology policies Responsible for cooperation and partnership with support team during and after system integration Validate data integrity and operational readiness after migrations Problem management and escalation of issues in a timely manner Assessment of client environments Assist with change-management activities Assist with decommission of legacy platforms once approved Participate in clean handoffs to steady-state operations teams Prioritizing tasks and meeting deadlines Mentoring and training acquired team members on various technologies Provide recommendations on integration processes Prepare and deliver complete and concise documentation for all projects Provide daily updates on completed tasks or progress reports to Manager" We'll make each a
- . Nested lists? The instruction didn't forbid nested lists but we can keep flat. Simpler: each bullet as separate line.
We'll flatten:
- 2-4 years’ experience in IT related study or field
- 2-4 years of field experience
- Basic knowledge and experience with Windows 7/8/10/11
- Basic knowledge and experience with Microsoft Office suite
- Basic knowledge and experience with Microsoft Windows Administration tools (AD Users and Computers, DHCP, DNS, Group Policy, Sites and Services, etc.)
- Basic knowledge and experience with Microsoft Office 365 Admin portal
- Understanding of basic network concepts
- Understanding of application, desktop, and server virtualization
- Understanding of Desktop Deployment / Imaging
- Bachelor’s Degree a plus
Qualifications: "Desired Experience/Certifications CertificationsCompTIA A+ Certification a plusMDAA, MCSAWindows Server 2012 through 2026Understanding of File Permissions (NTFS & Sharing)Excellent written/verbal communication skillsMust be a team player with outstanding client service skills"
We need to separate: Certifications: CompTIA A+ Certification a plus; MDAA, MCSA Windows Server 2012 through 2026; Understanding of File Permissions (NTFS & Sharing); Excellent written/verbal communication skills; Must be a team player with outstanding client service skills.
We'll put under Qualifications as list items.
Skills: we already separated communication and team player; but those are also in Qualifications. Actually they appear after "Understanding of File Permissions (NTFS & Sharing)" and before "Work Environment". They could be considered Skills. We'll keep them under Skills as earlier.
But we must not duplicate content. If we put them under Skills, we should not also list them under Qualifications. The Qualifications section should contain certifications and maybe file permissions. Let's decide.
We have Desired Experience/Certifications includes: CertificationsCompTIA A+ Certification a plusMDAA, MCSAWindows Server 2012 through 2026Understanding of File Permissions (NTFS & Sharing)Excellent written/verbal communication skillsMust be a team player with outstanding client service skills
Thus we could treat all as Qualifications. But we also have a separate Skills heading optional. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Certifications and Skills into Qualifications. However we have already a Requirements section for basic knowledge. Qualifications could be certifications and desired experience. Skills could be communication/teamwork. But that would be thin. Better to merge communication/teamwork into Qualifications as well, making Qualifications substantive. Then we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Let's craft Qualifications list:
- CompTIA A+ Certification a plus
- MDAA, MCSA Windows Server 2012 through 2026
- Understanding of File Permissions (NTFS & Sharing)
- Excellent written/verbal communication skills
- Must be a team player with outstanding client service skills
Now Benefits list as earlier.
Check we haven't missed any info: "Stability to grow alongside hard-workers in a collaborative environment with opportunities to grow professionally" included.
Now ensure we didn't include any boilerplate like "Work Environment and Physical Demands". That section includes details about work environment: climate-controlled, occasional lifting up to 50 pounds, reasonable accommodations, noise level moderate, occasional local travel required. This is substantive info; we should include it. The instruction says include a section only when posting has real specific content. This is real content. Should we create a section for Work Environment? The allowed headings list includes Benefits, Pay, Schedule but not Work Environment. However we can still use
with a custom heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says use
for section headings (e.g. ...). Likely we should stick to those headings; but we could also create a heading like "Work Environment" if needed. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings. They didn't forbid other headings but gave examples. Safer to stick to those. However we have substantive content about work environment; we could fold it into Benefits or Responsibilities? Not appropriate. Could create a section "Work Environment" using
but not in examples; risk. But maybe they expect us to include it as a section with heading "Work Environment". The examples are not exhaustive; they just show typical headings. I'd include a Work Environment section. Similarly we have "Work Environment and Physical Demands". We'll make heading "Work Environment". Use
Work Environment
and list items. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Work Environment. Check we didn't miss any: "Occasional local travel required." included. Now ensure we didn't include any fluff like "commensurate with experience". Not present. Now produce HTML. We'll need to escape any HTML special characters? The text includes parentheses, ampersand in "NTFS & Sharing". Need to escape & as &