TECHNICIAN-TECHNOLOGY SERVICE

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive info from posting. Let's parse: School/Center: TECHNOLOGY SUPPORT SERVICES Location: 2700 Judge Fran Jamieson Viera Job Number: 000029 School Year: 2027 FY Position: TECHNICIAN-TECHNOLOGY SERVICE Subtitle/Areas: Beginning Salary Based on classification and pay plan for Professional/Technical Hourly employees: Grade LL $20.70 per hour TECH I Grade MM $21.15 per hour TECH II Please apply online in "Beacon". Apply By: 09/29/2026 Date Available: 10/05/2026 Status: All Applicants Contract: 12 Month Hours/Day: 8.000 Qualifications/Certifications: Please apply online in "Beacon". QUALIFICATIONS TECH I – TECHNOLOGY SERVICE EDUCATION AND RELEVANT EXPERIENCE REQUIREMENTS: HS diploma or equivalent. Six (6) months’ experience in computer and/or multimedia related field. Hardware and software platforms experience, consistent with the District’s Information Services Strategic Plan. PREFERRED One (1) year of customer support and/or technical support. A+ Certification, or technical certification approved by the Assistant Superintendent of Information Services or Designee required. QUALIFICATIONS: TECH II – TECHNOLOGY SERVICE EDUCATION AND RELEVANT EXPERIENCE REQUIREMENTS: Two (2) year degree from an accredited educational institution required. Relevant experience may substitute for Associate’s Degree, two (2) years’ experience for one (1) year of college. Two (2) years’ experience in computer and multimedia related field. Hardware and software platforms experience, consistent with the District’s Information Services Strategic Plan. A+ Certification, or technical certification approved by the Asst Superintendent of Information Services or Designee required. PREFERRED Degree in Computer Science, Math, Science, or related technical field preferred. REQUIRED: Valid State Driver’s License Please view full job description at: https://files-backend.assets.thrillshare.com/documents/asset/uploaded_file/4493/Bps/482ce0ae-ff95-4989-b271-5b2f02eca974/Technician-Tech-Service-I,-II_-L675 Job Type: Support Personnel Instructional Subject: N/A Support Personnel Area: Computer/Technical Career and Technology Ed Subject: N/A Coaching Activity: N/A We need to remove boilerplate: "Please apply online in 'Beacon'." appears twice; also "Please view full job description at:" maybe considered application instructions? It's a link; we might drop it as application instructions. Also "Job Type: Support Personnel" etc maybe minor metadata; we can fold into a short

  or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short paragraph with location, job type, contract, hours/day, etc. We need sections: maybe "About the role" (description), "Qualifications" (list), maybe "Pay" (since salary info given). Also "Schedule" (Hours/Day: 8.000, Contract: 12 Month). Also maybe "Benefits" not given, so omit. We must not create sections with filler. So we need to see if we have substantive content for each. We have: - About the role: maybe we can summarize role: TECHNICIAN-TECHNOLOGY SERVICE, location, job type, contract, hours. But we must not invent detail; we can state the role title and maybe location etc. That's okay. - Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create a Responsibilities section. - Requirements: Could be qualifications. But we have Qualifications section already. Could combine Requirements and Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have qualifications details. We could put them under "Qualifications". Could also put "Requirements" but that would duplicate. Better to use "Qualifications" for the detailed qualification lists. Could also include "Skills" maybe from preferred qualifications: customer support, technical support, A+ Certification, etc. But those are already in qualifications. Might be okay to just have Qualifications. - Pay: we have salary info: Grade LL $20.70 per hour TECH I; Grade MM $21.15 per hour TECH II. That's substantive. So we can create Pay section. - Schedule: we have Hours/Day: 8.000, Contract: 12 Month. That's schedule info. So we can create Schedule section. - Benefits: none given, so omit. - Skills: maybe we could extract from qualifications: hardware and software platforms experience, customer support, technical support, A+ Certification, etc. But those are already in qualifications; we could still have a Skills section but risk duplication. Better to keep Qualifications only. Thus we will output sections: About the role (maybe short paragraph), Qualifications (with two sublists for TECH I and TECH II), Pay, Schedule. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. For qualifications we have lists; we can make
    with items. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all qualification details exactly as given. Let's extract qualification details precisely: TECH I – TECHNOLOGY SERVICE EDUCATION AND RELEVANT EXPERIENCE REQUIREMENTS: - HS diploma or equivalent. - Six (6) months’ experience in computer and/or multimedia related field. - Hardware and software platforms experience, consistent with the District’s Information Services Strategic Plan. - PREFERRED One (1) year of customer support and/or technical support. - A+ Certification, or technical certification approved by the Assistant Superintendent of Information Services or Designee required. TECH II – TECHNOLOGY SERVICE EDUCATION AND RELEVANT EXPERIENCE REQUIREMENTS: - Two (2) year degree from an accredited educational institution required. - Relevant experience may substitute for Associate’s Degree, two (2) years’ experience for one (1) year of college. - Two (2) years’ experience in computer and multimedia related field. - Hardware and software platforms experience, consistent with the District’s Information Services Strategic Plan. - A+ Certification, or technical certification approved by the Asst Superintendent of Information Services or Designee required. - PREFERRED Degree in Computer Science, Math, Science, or related technical field preferred. - REQUIRED: Valid State Driver’s License We need to preserve all that. Pay: "Beginning Salary Based on classification and pay plan for Professional/Technical Hourly employees: Grade LL $20.70 per hour TECH I Grade MM $21.15 per hour TECH II". We'll present as list maybe. Schedule: "Contract: 12 Month Hours/Day: 8.000". Could present as list. About the role: we can include location, job type, etc. Let's gather: School/Center: TECHNOLOGY SUPPORT SERVICES; Location: 2700 Judge Fran Jamieson Viera; Job Type: Support Personnel; Support Personnel Area: Computer/Technical; Contract: 12 Month; Hours/Day: 8.000. Also maybe School Year: 2027 FY. But we should not repeat job title as heading; we can mention it in paragraph. We need to avoid duplication: we already have Contract and Hours/Day in Schedule section; we might not repeat them in About the role. But we can still mention location, job center, job type, area. Thus About the role paragraph: "Position: TECHNICIAN-TECHNOLOGY SERVICE within the Technology Support Services department, located at 2700 Judge Fran Jamieson Viera. This is a Support Personnel role in the Computer/Technical area." That's fine. Now we need to output HTML fragment only, no /, no markdown fences. Let's construct:

    About the role

    Position: TECHNICIAN-TECHNOLOGY SERVICE within the Technology Support Services department, located at 2700 Judge Fran Jamieson Viera. This is a Support Personnel role in the Computer/Technical area.

    Qualifications

    • TECH I – TECHNOLOGY SERVICE EDUCATION AND RELEVANT EXPERIENCE REQUIREMENTS:
      • HS diploma or equivalent.
      • Six (6) months’ experience in computer and/or multimedia related field.
      • Hardware and software platforms experience, consistent with the District’s Information Services Strategic Plan.
      • PREFERRED One (1) year of customer support and/or technical support.
      • A+ Certification, or technical certification approved by the Assistant Superintendent of Information Services or Designee required.
    • TECH II – TECHNOLOGY SERVICE EDUCATION AND RELEVANT EXPERIENCE REQUIREMENTS:
      • Two (2) year degree from an accredited educational institution required.
      • Relevant experience may substitute for Associate’s Degree, two (2) years’ experience for one (1) year of college.
      • Two (2) years’ experience in computer and multimedia related field.
      • Hardware and software platforms experience, consistent with the District’s Information Services Strategic Plan.
      • A+ Certification, or technical certification approved by the Asst Superintendent of Information Services or Designee required.
      • PREFERRED Degree in Computer Science, Math, Science, or related technical field preferred.
      • REQUIRED: Valid State Driver’s License
    But note: we have nested
    inside
    • . That's okay but maybe better to have separate sections for each tech level. Could also have

      but not allowed; only

      for section headings. We could just have two separate

      lists with headings inside

      ? But instruction: Use

      for section headings. Use

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

        for prose. It didn't forbid headings inside list items. But we could