Classroom Technology Support Technician

We need to output HTML fragment with sections: About the role? Actually the job description includes sections: About This Opportunity, Key Responsibilities (with subparts), Required Qualifications (with Minimum Qualifications, Additional Qualifications, Preferred Qualifications), Conditions Of Employment (includes schedule, full-time, etc.), About The Team, Compensation, Benefits And Position Details (includes Pay Range, Benefits link, Shift, Temporary/Regular, FTE, Union). Also maybe "About The UW" and "Our Commitment" but those are boilerplate EEO etc. We must remove boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal. Also remove duplicated lines. Also we must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? Probably we should use those headings where appropriate. We need to include a section only when posting has real, specific content for it. So we need sections: About the role (maybe from About This Opportunity), Responsibilities (Key Responsibilities), Requirements (maybe Minimum Qualifications?), Qualifications (Additional Qualifications? Actually they separate Requirements and Qualifications; maybe Requirements = Minimum Qualifications, Qualifications = Additional/Preferred?), Skills (maybe from Additional Qualifications?), Benefits, Pay, Schedule. We need to avoid filler like "commensurate with experience". We have actual pay range numbers, so Pay section is valid. Schedule: we have Conditions Of Employment includes full-time 40 hours per week, regular work schedule is four weekdays plus a required Saturday shift. Some overtime and off-hours may be required. So we can include Schedule section. Benefits: we have a link to benefits info; we can include Benefits section with that link and maybe mention "Other Compensation: For information about benefits..." but we should not invent details. So we can include a

with link. Skills: maybe we can extract from Additional Qualifications: in depth knowledge of AV systems, hands-on experience supporting computer systems, ability to troubleshoot complex problems, good judgment, etc. Also Preferred Qualifications list skills. So we can include Skills section. Qualifications: maybe we combine Minimum Qualifications and Additional Qualifications? But we already have Requirements for minimum, Qualifications for additional/preferred. Let's follow: Requirements = Minimum Qualifications. Qualifications = Additional Qualifications (maybe also Preferred). Skills = maybe from Additional Qualifications that are skill-based. But to avoid duplication, we can put Additional Qualifications under Qualifications, and Preferred Qualifications also under Qualifications or Skills? The instruction says prefer a few substantive sections over many thin ones. So we could combine Additional and Preferred into Qualifications. Skills could be separate if we have distinct skill statements. But we might just have Qualifications and Skills overlapping. Let's think: The posting includes "Required Qualifications" with Minimum and Additional. Then "Preferred Qualifications". So we could have Requirements (Minimum Qualifications) and Qualifications (Additional + Preferred). Skills maybe not needed separately if we already covered in Qualifications. But the instruction expects we may include Skills section if there is real specific content. There is content about skills: "Excellent technical and interpersonal skills", "team-oriented and collaborative approach", "desire to continue to develop and refine your skills", "Excellent customer service and technical skills", "Ability to troubleshoot complex problems", "Good judgment, discretion", "Ability to work with varied constituents", "Experience in handling difficult high-pressure support situations", "Enthusiasm about technology and strong aptitude to learn new technologies". Those are skills. So we could have Skills section. Thus sections: About the role (from About This Opportunity), Responsibilities (Key Responsibilities), Requirements (Minimum Qualifications), Skills (from Required Qualifications Additional Qualifications and maybe some from Preferred), Qualifications (Preferred Qualifications? Actually we already used Additional for Skills; maybe Qualifications for Preferred). Benefits, Pay, Schedule. We must not include headings with empty content. Ensure each section has substantive content. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details like percentages (45%, 35%, 20%) maybe as part of responsibilities prose. We should keep them. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About The UW", "Our Commitment", etc. Also remove "Interested in learning more about UW Bothell IT and the work we do? Visit https://www.uwb.edu/it/ to explore our team and services." That's maybe not boilerplate but could be considered a link; but it's not a required section; we could keep it under About the role? It's about the team; maybe we can keep it under About The Team section but we are not including About The Team as a heading (we have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule). The instruction says use those headings as examples; we could also add other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those. Thus we need to map content to those headings. Let's extract: About the role: Could be the paragraph(s) describing the opportunity: "UW Bothell Information Technology has an outstanding opportunity for Classroom Technology Support Technician ... to join their team. UWB IT is seeking a dynamic and energetic individual that loves technology and new challenges and can work in a diverse university environment. Ideal candidates will bring excellent technical and interpersonal skills, a team-oriented and collaborative approach, and a desire to continue to develop and refine your skills. As a member of our team, you will have opportunities to grow technically and professionally." Also maybe "About This Opportunity Reporting to the Director, Academic & Collaborative Technology, the Classroom Technology Support Technician is responsible for providing critical technical support to the UW Bothell classroom technology infrastructure. The Classroom Technology Support Technician is a member of the Academic & Collaborative Technology group in UW Bothell IT. This position utilizes excellent customer service and technical skills to provide timely response to classroom technical issues and related audio-visual environments (e.g. conference rooms and event spaces) in support of UW Bothell’s mission." That seems appropriate for About the role. Responsibilities: The "Key Responsibilities" block with percentages and bullet-like sentences. We need to turn into

  • . Keep the percentages maybe inside each li. Requirements: Minimum Qualifications: "One year of experience as a Computer Maintenance Technician II OR Five years of experience as a computer maintenance technician. Equivalent education and/or experience may substitute for minimum qualifications except when there are legal requirements, such as a license, certification, and/or registration. Applicants who do not meet these qualifications WILL NOT be forwarded to the Hiring Manager". Also maybe include "To be considered for this opportunity your application must demonstrate you meet both the minimum qualifications and additional qualifications listed below." But that's procedural; we can include. Skills: From Additional Qualifications: list of items: "In depth knowledge of audio-visual systems; including installation, testing, configuration, and support. Experience supporting audio visual equipment for events, conferencing or in a classroom/educational environment. Hands on experience supporting computer systems (Hardware and Operating Systems): Microsoft Windows OS imaging, troubleshooting, and software management. Familiarity with MacOS support and troubleshooting Mobile device support (iPad/iOS/Android) Ability to troubleshoot complex problems, identify, and implement solutions. Good judgment, discretion and the ability to maintain confidentiality. Ability to work with varied constituents with varying levels of technical acumen. Experience in effectively handling difficult and high-pressure support situations in a fast-paced and dynamic environment, on the phone, via email, and in person. Enthusiasm about technology and a strong aptitude and desire to learn new technologies." Also maybe from Preferred Qualifications: "Experience with both AMX and Extron audio-visual control systems Direct experience working within help desk ticketing systems. Experience with media hardware and warranty support structures Attention to detail, timely and appropriate follow-up, proactive and constructive problem solving, openness to new approaches. Strong communication and customer service skills and an ability to remain calm, friendly, and relaxed in a fast-paced environment." We could split: Skills = the list from Additional Qualifications (technical skills and soft skills). Qualifications = Preferred Qualifications (maybe). But we already have Requirements for minimum; Qualifications for preferred; Skills for additional? However the instruction says we can have Qualifications section; we could put both Additional and Preferred there, but then Skills might be redundant. Let's decide: We'll have Requirements (minimum), Qualifications (additional + preferred), Skills (maybe not needed). But we need to include a Skills section only if there is real specific content. There is definitely skill content; we could put skill content under Skills and keep Qualifications for preferred only. But then we would duplicate some content (like attention to detail etc.) maybe okay. Better: Use Requirements = Minimum Qualifications. Skills = Additional Qualifications (technical and soft skills). Qualifications = Preferred Qualifications. That yields three sections plus About the role, Responsibilities, Benefits, Pay, Schedule. Now Benefits: we have "Benefits Other Compensation: For information about benefits for this position, visit https://www.washington.edu/jobs/benefits-for-uw-staff/". Also maybe "Pay Range Minimum: $75,084.00 annual Pay Range Maximum $100,992.00 annual". That's Pay. Schedule: from Conditions Of Employment: "Full-time 40 hours per week. Regular work schedule is four weekdays plus a required Saturday shift. Some overtime and off-hours may be required as needed. Currently primarily on-site work with some remote, subject to change based on Unit need. Individuals in this position may need to lift and move computer and audio-visual systems or other technology. Work will be performed across UW Bothell campus. This role is required to walk/travel to other buildings on campus as needed. Primary workspace is in a shared space office environment." We can include schedule details (hours, shift, overtime, on-site/remote). The other details like lifting, travel, workspace maybe not schedule but could be part of Conditions; but we only have Schedule heading; we could include all that under Schedule as it's about working conditions. Might be okay. Now we need to ensure we don't include boilerplate like "About The UW", "Our Commitment", EEO statement, etc. Also remove duplicated lines. Also remove "To request disability accommodation..." etc. Now produce HTML fragment. Structure:

    About the role

    ...

    Responsibilities

    • ... (each bullet)
    ...

    Requirements

    ... (minimum qualifications)

    Skills

    • ... (each skill from Additional Qualifications)
    ...

    Qualifications

    • ... (each from Preferred Qualifications)
    ...

    Benefits

    For information about benefits for this position, visit https://www.washington.edu/jobs/benefits-for-uw-staff/.

    Pay

    Pay Range Minimum: $75,084.00 annual. Pay