Technology Systems Specialist
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have Schedule info: "Full-time, 12-month position. Monday through Friday, 8:00 a.m. to 4:30 p.m. (includes a ½ hour unpaid lunch period). Occasional evening and/or weekend work as needed. This is an in-person position." So we can have a Schedule section.
Pay: "Anticipated starting hourly rate range: $26 - $28.50". So we can have Pay section.
Benefits: Not mentioned. So we should not include Benefits.
Qualifications: There's a Qualifications section with bullet-like paragraphs. We can treat as Qualifications.
Responsibilities: There's a Responsibilities section with sub-sections (Help Desk & End User Support, Print Management, Classroom Audiovisual Systems, General Systems & Hardware). We can include Responsibilities as a heading and then list items maybe as - . The content includes paragraphs; we can break into list items for each bullet? The instructions: Use
- for any list of duties/requirements/benefits. So we need to convert duties into list items. We'll extract each duty sentence.
Also we have "About Kent School" description; maybe we can put as About the role? Actually "About the role" is suggested but we have "Position Summary". Could use "About the role" heading and put the Position Summary paragraph there. Or we could use "About Kent School" but not in list. The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We have content for About the role (position summary). We have Responsibilities. We have Qualifications. We have Pay. We have Schedule. We do not have Requirements separate from Qualifications? Could treat Qualifications as Requirements? But we have Qualifications section already. We'll include Qualifications heading.
We should not repeat job title as heading. No Job ID.
We need to remove boilerplate: EEO, application instructions, etc. Also remove "Physical Requirements", "Additional Requirements" maybe those are requirements? They could be part of Requirements section. The rules: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements section that includes physical requirements and additional requirements. But we also have Qualifications. Might be overlapping. Better to follow the posting: they have Qualifications, Physical Requirements, Additional Requirements. We could combine Physical Requirements and Additional Requirements into a Requirements section. But we also have Qualifications separate. The instructions: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include both Requirements and Qualifications if content exists. We'll create Requirements section for physical and additional requirements. Qualifications section for qualifications.
We need to preserve all substantive information. So we need to include the physical requirements and additional requirements text.
We need to format as - for any list of duties/requirements/benefits. For Requirements we can list each requirement as
- . For Qualifications we can list each qualification as
- . For Responsibilities we list each duty as
- . For About the role we can use
.
Pay: we can use
with the rate.
Schedule: we can use
with schedule details.
We must not include filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We need to output only HTML fragment.
Let's extract content.
About the role (Position Summary):
"Kent School seeks a versatile, service-minded Technology Systems Specialist to join our Technology Department. This is a front-line support role for someone who thrives on variety, stays composed when priorities shift, and enjoys being the person who keeps the day-to-day technology of a busy campus working. Working as one of two technicians on the help desk team, the Technology Systems Specialist provides responsive support to faculty, staff, and students across a wide range of needs, including devices, accounts, connectivity, and classroom technology. Strong support here means more than closing tickets. This person helps users understand both the how and the why behind a solution, building their confidence to handle small issues on their own next time. Because Kent runs a Bring Your Own Device (BYOD) program, this role handles a significant share of personal device support for students and staff. Alongside the help desk work, this position owns two hands-on campus technology domains: print management and classroom audiovisual systems. Success in this role depends less on a rigid, single-track focus and more on nimbleness: the ability to move between the classroom, an administrative office, and a dorm in the same morning, and to judge what needs attention first. It is a role for an experienced support professional who is genuinely energized by service, has already thrived amid the ebb and flow of a busy environment, and wants to keep growing their skills over time."
We'll put that in a
.
Responsibilities: We have subheadings but we can just list duties.
From Responsibilities section:
Help Desk & End User Support:
- Serve as one of two technicians on the help desk team, monitoring, resolving, and escalating support requests through the school’s ticketing system (FreshService) with timely, professional service to the entire Kent community.
- Provide hands-on support for school-owned and personally owned devices under Kent’s BYOD program, including Mac, PC, iOS, Chrome, and Android devices, which account for a significant share of the school’s personal-device support.
- Assist end users with network connectivity, account access, authentication, and MFA support within established procedures.
- Support onboarding and offboarding procedures for faculty, staff, and students in coordination with the IT Manager.
- Provide comfortable, capable Level 1 support for the academic technology platforms used across the school, including Canvas and Google Workspace, and escalate instructional and curriculum questions to the Director of Academic Technology.
- Record technical problems and their resolutions accurately in the ticketing system, and communicate clear, timely status updates to affected users.
- Contribute user help articles to the school’s online knowledge base, building self-service resources that reduce recurring requests.
Print Management:
- Own the day-to-day administration of the school’s print environment, including PaperCut and printer server administration.
- Manage the Xerox fleet, including supplies and consumables, and coordinate repairs and vendor services.
- Monitor the print infrastructure for recurring issues and proactively work to reduce disruptions and downtime.
Classroom Audiovisual Systems:
- Own the support and maintenance of classroom audiovisual technology, including projectors and interactive flat panel (IFP) boards.
- Respond promptly to time-sensitive classroom technology issues that affect teaching and learning.
- Coordinate installations, replacements, and vendor service for AV equipment as needed, and maintain documentation of classroom configurations.
General Systems & Hardware:
- Prepare, image, and deploy new and loaner devices for faculty, staff, and students.
- Support and maintain school-owned devices on an ongoing, day-to-day basis.
- Support the accurate inventory and tracking of IT assets, including school-owned hardware, loaner computers, and peripherals.
- Assist with the maintenance and monitoring of systems and infrastructure as directed by the IT Manager.
- Identify and suggest improvements to IT procedures and support processes based on recurring issues and user feedback.
We'll put each bullet as
- under a
inside Responsibilities section.
Requirements: Physical Requirements + Additional Requirements.
Physical Requirements:
- Must be able to work in an office environment and travel between multiple buildings across campus.
- Requires substantial use of keyboard and visual display equipment.
- Ability to lift and transport equipment up to 40 lbs. without assistance, and to access classroom AV and print equipment (including reaching, bending, and occasional use of a step stool or ladder).
Additional Requirements:
- Occasional driving may be required; qualified candidates should have reliable transportation and a valid driver’s license. Any travel requiring the use of a personal vehicle will be reimbursed.
- Successful completion of a post-offer, pre-employment criminal background check.
- Maintain punctual and regular attendance.
- Work is performed on a smoke-free campus.
We'll list each as - .
Qualifications: list each qualification.
From Qualifications section:
- Proven experience as a help desk or front-line support technician, including hands-on management of tickets in a support ticketing system; ideally three to five years in a school, campus, or comparably high-volume, multi-departmental environment with seasonal peaks.
- Demonstrated success managing competing priorities and high ticket volume during busy periods, while maintaining a professional, service-oriented demeanor.
- Proficiency with Apple (macOS, iOS) and Microsoft (Windows) operating systems, with strong macOS troubleshooting skills, and comfort supporting Chrome and Android devices.
- Experience supporting personal devices in a BYOD environment.
- Familiarity with print management (PaperCut or comparable) and classroom AV technology, or a demonstrated ability to take ownership of these systems quickly.
- Comfort with academic technology platforms such as Canvas and Google Workspace for Education.
- A temperament suited to a fast-changing, multi-constituency environment: able to reprioritize across competing demands, move fluidly between different types of work, and stay composed under pressure.
- Excellent verbal and written communication skills, with the ability to explain technology clearly and patiently to users of all ages and skill levels.
- A collaborative, low-ego approach to teamwork and a genuine commitment to helping users succeed.
- A lifelong learner mindset, able to learn independently by reading documentation and finding online resources.
- Bachelor’s degree in IT, Computer Science, or a related field, or an equivalent combination of education and relevant work experience.
- Experience working in an independent school setting is a plus, but is not required.
We'll list each as
- .
Pay: "Anticipated starting hourly rate range: $26 - $28.50". We'll put in
.
Schedule: "Full-time, 12-month position. Monday through Friday, 8:00 a.m. to 4:30 p.m. (includes a ½ hour unpaid lunch period). Occasional evening and/or weekend work as needed. This is an in-person position." We'll put in
.
We must not include any other sections like Benefits, Skills.
We need to output only HTML fragment, no or . We'll wrap sections in appropriate tags.
We'll produce something like:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Pay
Anticipated starting hourly rate range: $26 - $28.50
Schedule
Full-time, 12-month position. Monday through Friday, 8:00 a.m. to 4:30 p.m. (includes a ½ hour unpaid lunch period). Occasional evening and/or weekend work as needed. This is an in-person position.
Check for any duplicated content: Ensure we didn't repeat any sentences.
We need to ensure we preserve all substantive information: Did we miss any? The "About Kent School" paragraph about the school history etc. That is substantive but not part of position summary. Should we include that? The instructions: preserve ALL substantive information. The "About Kent School" paragraph is about the school, not the role. It's substantive. Should we include it? Possibly under About the role? But we already used About the role for position summary
- for any list of duties/requirements/benefits. So we need to convert duties into list items. We'll extract each duty sentence.
Also we have "About Kent School" description; maybe we can put as About the role? Actually "About the role" is suggested but we have "Position Summary". Could use "About the role" heading and put the Position Summary paragraph there. Or we could use "About Kent School" but not in list. The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We have content for About the role (position summary). We have Responsibilities. We have Qualifications. We have Pay. We have Schedule. We do not have Requirements separate from Qualifications? Could treat Qualifications as Requirements? But we have Qualifications section already. We'll include Qualifications heading. We should not repeat job title as heading. No Job ID. We need to remove boilerplate: EEO, application instructions, etc. Also remove "Physical Requirements", "Additional Requirements" maybe those are requirements? They could be part of Requirements section. The rules: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements section that includes physical requirements and additional requirements. But we also have Qualifications. Might be overlapping. Better to follow the posting: they have Qualifications, Physical Requirements, Additional Requirements. We could combine Physical Requirements and Additional Requirements into a Requirements section. But we also have Qualifications separate. The instructions: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include both Requirements and Qualifications if content exists. We'll create Requirements section for physical and additional requirements. Qualifications section for qualifications. We need to preserve all substantive information. So we need to include the physical requirements and additional requirements text. We need to format as
- for any list of duties/requirements/benefits. For Requirements we can list each requirement as
- . For Qualifications we can list each qualification as
- . For Responsibilities we list each duty as
- . For About the role we can use
. Pay: we can use
with the rate. Schedule: we can use
with schedule details. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. We need to output only HTML fragment. Let's extract content. About the role (Position Summary): "Kent School seeks a versatile, service-minded Technology Systems Specialist to join our Technology Department. This is a front-line support role for someone who thrives on variety, stays composed when priorities shift, and enjoys being the person who keeps the day-to-day technology of a busy campus working. Working as one of two technicians on the help desk team, the Technology Systems Specialist provides responsive support to faculty, staff, and students across a wide range of needs, including devices, accounts, connectivity, and classroom technology. Strong support here means more than closing tickets. This person helps users understand both the how and the why behind a solution, building their confidence to handle small issues on their own next time. Because Kent runs a Bring Your Own Device (BYOD) program, this role handles a significant share of personal device support for students and staff. Alongside the help desk work, this position owns two hands-on campus technology domains: print management and classroom audiovisual systems. Success in this role depends less on a rigid, single-track focus and more on nimbleness: the ability to move between the classroom, an administrative office, and a dorm in the same morning, and to judge what needs attention first. It is a role for an experienced support professional who is genuinely energized by service, has already thrived amid the ebb and flow of a busy environment, and wants to keep growing their skills over time." We'll put that in a
. Responsibilities: We have subheadings but we can just list duties. From Responsibilities section: Help Desk & End User Support: - Serve as one of two technicians on the help desk team, monitoring, resolving, and escalating support requests through the school’s ticketing system (FreshService) with timely, professional service to the entire Kent community. - Provide hands-on support for school-owned and personally owned devices under Kent’s BYOD program, including Mac, PC, iOS, Chrome, and Android devices, which account for a significant share of the school’s personal-device support. - Assist end users with network connectivity, account access, authentication, and MFA support within established procedures. - Support onboarding and offboarding procedures for faculty, staff, and students in coordination with the IT Manager. - Provide comfortable, capable Level 1 support for the academic technology platforms used across the school, including Canvas and Google Workspace, and escalate instructional and curriculum questions to the Director of Academic Technology. - Record technical problems and their resolutions accurately in the ticketing system, and communicate clear, timely status updates to affected users. - Contribute user help articles to the school’s online knowledge base, building self-service resources that reduce recurring requests. Print Management: - Own the day-to-day administration of the school’s print environment, including PaperCut and printer server administration. - Manage the Xerox fleet, including supplies and consumables, and coordinate repairs and vendor services. - Monitor the print infrastructure for recurring issues and proactively work to reduce disruptions and downtime. Classroom Audiovisual Systems: - Own the support and maintenance of classroom audiovisual technology, including projectors and interactive flat panel (IFP) boards. - Respond promptly to time-sensitive classroom technology issues that affect teaching and learning. - Coordinate installations, replacements, and vendor service for AV equipment as needed, and maintain documentation of classroom configurations. General Systems & Hardware: - Prepare, image, and deploy new and loaner devices for faculty, staff, and students. - Support and maintain school-owned devices on an ongoing, day-to-day basis. - Support the accurate inventory and tracking of IT assets, including school-owned hardware, loaner computers, and peripherals. - Assist with the maintenance and monitoring of systems and infrastructure as directed by the IT Manager. - Identify and suggest improvements to IT procedures and support processes based on recurring issues and user feedback. We'll put each bullet as
- under a
- inside Responsibilities section.
Requirements: Physical Requirements + Additional Requirements.
Physical Requirements:
- Must be able to work in an office environment and travel between multiple buildings across campus.
- Requires substantial use of keyboard and visual display equipment.
- Ability to lift and transport equipment up to 40 lbs. without assistance, and to access classroom AV and print equipment (including reaching, bending, and occasional use of a step stool or ladder).
Additional Requirements:
- Occasional driving may be required; qualified candidates should have reliable transportation and a valid driver’s license. Any travel requiring the use of a personal vehicle will be reimbursed.
- Successful completion of a post-offer, pre-employment criminal background check.
- Maintain punctual and regular attendance.
- Work is performed on a smoke-free campus.
We'll list each as
- . Qualifications: list each qualification. From Qualifications section: - Proven experience as a help desk or front-line support technician, including hands-on management of tickets in a support ticketing system; ideally three to five years in a school, campus, or comparably high-volume, multi-departmental environment with seasonal peaks. - Demonstrated success managing competing priorities and high ticket volume during busy periods, while maintaining a professional, service-oriented demeanor. - Proficiency with Apple (macOS, iOS) and Microsoft (Windows) operating systems, with strong macOS troubleshooting skills, and comfort supporting Chrome and Android devices. - Experience supporting personal devices in a BYOD environment. - Familiarity with print management (PaperCut or comparable) and classroom AV technology, or a demonstrated ability to take ownership of these systems quickly. - Comfort with academic technology platforms such as Canvas and Google Workspace for Education. - A temperament suited to a fast-changing, multi-constituency environment: able to reprioritize across competing demands, move fluidly between different types of work, and stay composed under pressure. - Excellent verbal and written communication skills, with the ability to explain technology clearly and patiently to users of all ages and skill levels. - A collaborative, low-ego approach to teamwork and a genuine commitment to helping users succeed. - A lifelong learner mindset, able to learn independently by reading documentation and finding online resources. - Bachelor’s degree in IT, Computer Science, or a related field, or an equivalent combination of education and relevant work experience. - Experience working in an independent school setting is a plus, but is not required. We'll list each as
- .
Pay: "Anticipated starting hourly rate range: $26 - $28.50". We'll put in
. Schedule: "Full-time, 12-month position. Monday through Friday, 8:00 a.m. to 4:30 p.m. (includes a ½ hour unpaid lunch period). Occasional evening and/or weekend work as needed. This is an in-person position." We'll put in
. We must not include any other sections like Benefits, Skills. We need to output only HTML fragment, no or . We'll wrap sections in appropriate tags. We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Pay
Anticipated starting hourly rate range: $26 - $28.50
Schedule
Full-time, 12-month position. Monday through Friday, 8:00 a.m. to 4:30 p.m. (includes a ½ hour unpaid lunch period). Occasional evening and/or weekend work as needed. This is an in-person position.
Check for any duplicated content: Ensure we didn't repeat any sentences. We need to ensure we preserve all substantive information: Did we miss any? The "About Kent School" paragraph about the school history etc. That is substantive but not part of position summary. Should we include that? The instructions: preserve ALL substantive information. The "About Kent School" paragraph is about the school, not the role. It's substantive. Should we include it? Possibly under About the role? But we already used About the role for position summary