Information Technology Support Technician I (Temporary Substitute)

We need to output HTML fragment with sections only if real content. The posting includes Salary, Job Type, Division, Opening Date, Location, Job Number, Department, Bargaining Unit, Definition, Employment Information, Duties And Responsibilities, Knowledge, Skills, and Abilities, Minimum Qualifications, Physical Demands, Environmental Elements, Required Application Materials, District Statement, Vision Statement, Mission Statement, EEO Statement, Conditions of Employment, etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove EEO statement? The instruction says remove EEO/equal-opportunity boilerplate. So we should drop EEO Statement. Also remove Conditions of Employment? That may be considered legal boilerplate? Possibly keep if substantive? It includes pre-employment requirements etc. Might be considered boilerplate. Safer to remove Conditions of Employment as it's legal. Also remove Required Application Materials? That's application instructions, should be removed. Also remove District Statement, Vision Statement, Mission Statement? Those are generic about college, maybe considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. District Statement etc are not exactly those categories, but they are generic college description; might be considered boilerplate but not explicitly prohibited. However we should preserve ALL substantive information; not invent or summarize away detail. The district statement is substantive about college; but maybe it's considered boilerplate? The instruction only mentions specific types to remove; district statement not listed. So we keep it? However we need to prefer few substantive sections over many thin ones. Could combine some. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. We must not repeat job title as heading. No Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. We have Salary: $38.23 - $42.16 Hourly. That's Pay. So we need a Pay section with that info. Job Type: Temporary. That could be Schedule? Actually Schedule maybe not given. Could put under Schedule? But we only create Schedule if posting actually states them. It does not state schedule (hours per week, etc). So we should not create Schedule section. Benefits: The posting says: This position is not eligible for medical, dental, or vision benefits through the District. Holidays and vacations are unpaid. Sick leave is accrued in accordance with applicable state law. Employees who work over 1,000 hours in a fiscal year will be enrolled in CalPERS. That's benefits info. So we can create Benefits section with that. Division: Administrative Services. Could be part of About the role? Maybe we put under About the role a short paragraph. Opening Date: 09/08/2026. Minor metadata; could be in a short p. Location: Fremont Campus and/or Newark Center. Could be in About the role. Department: Administrative Services. Could be in About the role. Bargaining Unit: N/A. Minor metadata; maybe drop. Definition: Under the supervision... serve as point of contact... Provide technical assistance... That's essentially role description. Could be About the role. Employment Information: This is a temporary substitute position, limited to max 165 working days within a fiscal year. Not eligible for benefits etc (already covered). Holidays/vacations unpaid. Sick leave accrued per state law. Employees over 1000 hours enrolled in CalPERS. This is also benefits/employment details. Could merge with Benefits. Duties And Responsibilities: list of duties. We'll put under Responsibilities. Knowledge, Skills, and Abilities: split into Knowledge, Skills, Abilities. Could map to Skills section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Skills heading. Knowledge and Abilities could be part of Skills or Qualifications? Possibly Qualifications heading for minimum qualifications. Requirements maybe for knowledge/skills? But we have separate headings: Requirements, Qualifications, Skills. We need to decide mapping. We have Minimum Qualifications: Any combination of a Bachelor's degree in a related field and job experience or training in network and/or computer systems and technologies. Experience working in an educational setting and among users with varying levels of familiarity with technology. AND Must have evidence of responsiveness to and understanding of the diverse academic, socioeconomic, cultural, disability, gender identity, sexual orientation, and ethnic backgrounds of community college students, as these factors relate to the need for equity-minded practices. That's qualifications. Knowledge: A wide variety of hardware and software including ERP systems; Incident/ticket management systems; Software and hardware troubleshooting techniques; Skills: Use knowledge of computer systems, mobile devices, applications, ERP systems, incident resolution, troubleshooting techniques, incident/ticket management systems, IT products, and common technological equipment to assist users and troubleshoot basic problems, including but not limited to: log in issues, printer problems, and hardware malfunctions; Use incident/ticket management systems to prioritize and respond to requests for assistance; Use general office software and equipment to complete logs and document activities; Provide in-person and remote assistance to users. Ability: Ensure effective customer service in diagnosing and resolving basic technical issues; Remain calm under stressful situations; thrive in a team atmosphere; Apply critical thinking techniques to assist users in resolving technical issues with computer hardware and software; Effectively prioritize and complete work assignments; Communicate effectively, orally and in writing; Develop and maintain effective relationships with coworkers of varying technological skill levels. Thus we could map Knowledge to Requirements? Or maybe Requirements heading for knowledge/skills/abilities combined. But we have separate Skills heading; we could put Skills under Skills heading, and Knowledge and Abilities under Requirements or Qualifications? However Qualifications already used for minimum qualifications. Could use Requirements for knowledge and abilities. But the instruction says we can use those headings if there is real content. We'll create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. No Schedule. We must not create empty sections. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

Under the supervision of an administrator, serve as a point of contact for the Information Technology Services (ITS) Department for technical support issues on hardware, applications and related technologies. Provide technical assistance to troubleshoot basic problems with computer hardware and software. This is a temporary substitute position, limited to a maximum of 165 working days within a fiscal year. Located at the Fremont Campus and/or Newark Center, within the Administrative Services Division and Department.

Responsibilities

• Troubleshoot software and hardware issues through diagnostic techniques
• Direct advanced technical issues to the next level of ITS support
• Conduct follow-up communication with users; identify recurring problems and recommend improvements
• Carefully document all problems and resolutions
• Conduct inventories of District software and hardware as directed; reconcile inventories with purchase orders as assigned
• Provide excellent service; communicate professionally and efficiently in all interactions
• Configure and deliver computer hardware and provide set up of equipment as assigned
• Organize and support ITS-related trainings by completing tasks including, but not limited to: reserving conference rooms and duplicating training materials
• Enter data into appropriate databases; maintain records as directed
• Demonstrate sensitivity to and respect for the diverse academic, socioeconomic, cultural, disability, and ethnic backgrounds of the College's students, faculty, staff, and community
• Effectively engage and support historically disproportionately impacted groups by addressing issues of equity and improving culturally responsive service-oriented practices
• Performs related duties as assigned

Requirements

Knowledge of a wide variety of hardware and software including enterprise resource planning systems; incident/ticket management systems; software and hardware troubleshooting techniques.

Qualifications

• Any combination of a Bachelor's degree in a related field and job experience or training in network and/or computer systems and technologies.
• Experience working in an educational setting and among users with varying levels of familiarity with technology.
• Must have evidence of responsiveness to and understanding of the diverse academic, socioeconomic, cultural, disability, gender identity, sexual orientation, and ethnic backgrounds of community college students, as these factors relate to the need for equity‑minded practices.

Skills

• Use knowledge of computer systems, mobile devices, applications, ERP systems, incident resolution, troubleshooting techniques, incident/ticket management systems, IT products, and common technological equipment to assist users and troubleshoot basic problems, including but not limited to: log in issues, printer problems, and hardware malfunctions.
• Use incident/ticket management systems to prioritize and respond to requests for assistance.
• Use general office software and equipment to complete logs and document activities.
• Provide in‑person and remote assistance to users.
• Ensure effective customer service in diagnosing and resolving basic technical issues.
• Remain calm under stressful situations; thrive in a team atmosphere.
• Apply critical thinking techniques to assist users in resolving technical issues with computer hardware and software.
• Effectively prioritize and complete work assignments.
• Communicate effectively, orally and in writing.
• Develop and maintain effective relationships with coworkers of varying technological skill levels.

Benefits

• Not eligible for medical, dental, or vision benefits through the District.
• Holidays and vacations are unpaid.
• Sick leave is accrued in accordance with applicable state law.
• Employees who work over 1,000 hours in a fiscal year will be enrolled in CalPERS.

Pay

$38.23 – $42.16 per hour

We omitted Schedule as not specified. We also omitted Opening Date, Job Number etc as minor metadata; could be included in About the role paragraph? Might be okay to drop. Check for any duplicated lines: we have not duplicated. Check for boilerplate removed: EEO statement removed, Conditions of Employment removed, Required Application Materials removed, District Statement etc removed? We removed District Statement, Vision, Mission. Did we lose substantive info? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The District Statement etc are substantive about college. Are we allowed to remove them? The instruction only says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does NOT say to remove district statement. So we should keep it. However we already removed it. We need to add it back as a section maybe "About the college" but we don't have a heading for that. We could incorporate into About the role? But that would be mixing role description with college description. Might be okay but could be considered not specific to role. However we need to preserve it. Perhaps we can add a section "About Ohlone College" but we don't have a predefined heading list; we can use

for any section 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. So we could add a heading like "About Ohlone College". That seems acceptable. Thus we should include a section with college description. Let's add:

About Ohlone College

Found