Network Technician

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. Full Job Description includes: - Salary Grade: Hourly 16 | H-16 (but we should not create Pay section unless posting actually states them. It says "Salary Grade: Hourly 16 | H-16" and references salary schedule. That's not a specific pay amount. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does not give actual pay amount, just grade. So we should not create Pay section. - Benefits: mentions "For more information on our comprehensive benefits packages, please visit our Compensation and Benefits website." That's not specific benefits; it's a generic reference. According to rule: do not create Benefits section unless posting actually states them. It does not list specific benefits. So we should not include Benefits. - Schedule: not mentioned. - About the role: we have Position Summary and Key Functions. That can be "About the role" or "Responsibilities". We need to decide headings. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have Position Summary: description of role. Could be "About the role". Then Key Functions: list of duties. Could be "Responsibilities". Then Education Minimum Qualifications: could be "Qualifications" or "Requirements". Then Experience: could be part of Qualifications. Then Licenses And Certifications: could be "Qualifications". Then Knowledge, Skills, And Abilities: could be "Skills". Then About Our District: could be omitted? It's boilerplate? It's about district mission, values. Might be considered "About the role"? But it's more about organization. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Our District" is not exactly boilerplate but could be considered generic. However it's substantive about mission and values. Might be okay to include as a section like "About the district" but not in the list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About Our District" could be considered part of "About the role"? Not exactly. But we could omit it if not fitting. However we must preserve ALL substantive information; do not invent or summarize away detail. If we omit the About Our District paragraph, we lose substantive info about mission and values. But maybe we can include it under "About the role" as a paragraph describing the organization. The heading "About the role" could encompass both role summary and district info. But the rule says "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put the Position Summary and About Our District under "About the role". However we also have Key Functions separate; maybe we put those under "Responsibilities". That seems fine. Now we need to output HTML fragment with

headings and appropriate

• for lists,

  for prose. We must not repeat the job title as a heading (the page already shows it). So no heading for "Network Technician". Also do not put Job ID/requisition numbers as headings. We need to preserve all substantive information: Salary Grade info? It's not a specific pay amount, but it's substantive. Should we include it? The instruction says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary Grade: Hourly 16 | H-16. That's not a pay amount but it's a salary grade. Could be considered Pay info. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Salary Grade, which is related to pay. But they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Salary Grade, so we could include a Pay section with that info. However they also said "Prefer a few substantive sections over many thin ones." And they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Salary Grade is not filler; it's specific. So we could include a Pay section with that info. But the example headings list includes Pay. So we could add a

  Pay

  with a

  containing the salary grade info. Similarly, Benefits: they mention "For more information on our comprehensive benefits packages, please visit our Compensation and Benefits website." That's not specific benefits; it's a referral. That could be considered filler? It's not a list of benefits. According to rule, we should not create Benefits section unless posting actually states them. It does not state specific benefits, just a referral. So we should not include Benefits. Schedule: not mentioned. Thus we can have sections: About the role (includes Position Summary and About Our District), Responsibilities (Key Functions), Qualifications (Education Minimum Qualifications, Experience, Licenses And Certifications), Skills (Knowledge, Skills, And Abilities), Pay (Salary Grade). Possibly also Requirements? But Qualifications covers that. The instruction list includes Requirements and Qualifications as separate headings. We could split: Requirements could be Education Minimum Qualifications and Experience; Qualifications could be Licenses And Certifications. But we can also combine. To avoid many thin sections, we prefer few substantive sections. So we can combine Education, Experience, Licenses under Qualifications. And Skills separate. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay. Now we need to format. About the role: combine Position Summary paragraph and About Our District paragraph. Use

  for each? Could combine into one

  with two sentences? Better to keep separate

  elements. Responsibilities: Key Functions list: items: Network hardware and software installation and maintenance; Network cabling infrastructure installation and maintenance; Work order completion and technical troubleshooting; Process and repair documentation; State testing standards and operations support; After-hours support for essential network equipment. Use

  • . Qualifications: Education Minimum Qualifications: High School Diploma or equivalent. Experience: Three (3) years of experience with TIA cabling standards and procedures (Cat 6/6a, Fiber); Three (3) years of CCNA, Microsoft server, or related experience, such as cable pulling, switch configuration, wireless access point configuration, or VoIP configuration; Three (3) years of VoIP hardware and software configuration experience preferred. Licenses And Certifications: CompTIA Network+ (N+) certification, required at the time of hire; Valid Oklahoma driver's license. Also note Bilingual in Spanish preferred is under Skills? Actually it's under Knowledge, Skills, And Abilities: Bilingual in Spanish preferred. So we will include that in Skills. Thus Qualifications: we can have
    • for each bullet? Could group Education as

      then Experience as

      etc. But rule: Use
      • for any list of duties/requirements/benefits, and

        for prose. So for Education Minimum Qualifications (a single line) we could use

        . For Experience (multiple items) we could use

        . For Licenses And Certifications (multiple items) we could use
        . Or we could combine all into one list? Better to keep separate. Skills: Knowledge, Skills, And Abilities list: Strong problem-solving and analytical skills; Ability to communicate effectively, calmly, and patiently with both technical and non-technical audiences; Ability to quickly respond to events in a fast-paced environment and manage problem escalation when required; Ability to create extensive spreadsheets for department projects; Ability to remain open to change and apply critical thinking while developing solutions based on new guidelines, methods, techniques, and technologies; Ability to build buy-in from individuals with diverse perspectives and backgrounds for new ideas and approaches; Ability to work effectively both independently and collaboratively; Proficient in Microsoft Office Suite and Google Office Suite; Bilingual in Spanish preferred. Use
        • . Pay: Salary Grade: Hourly 16 | H-16 Tulsa Public Schools’ existing salary schedules provide career increment adjustments based on education/experience and/or years of creditable service. For more information about the salary for this specific position, please review the Salary Schedule for the corresponding Salary Grade (listed above). That's the prose. We can put that in a

          . Note we should not include boilerplate like "For more information about the salary for this specific position, please review the Salary Schedule..." but that's part of the posting. It's substantive? It's a referral. Might be considered filler but it's part of the salary description. We'll keep it. Now we need to ensure we don't include any navigation/legal/EEO etc. The posting includes "About Our District:" which we included under About the role. That's fine. Now produce HTML fragment:

          About the role

          Position Summary: The Network Technician provides technical expertise in support of the Information Technology (IT) infrastructure, systems, and services for Tulsa Public Schools. The role installs and maintains network hardware, software, and cabling infrastructure and completes assigned work orders at district and non-district sites. As a member of the Network Engineering Support Team, the Network Technician supports existing IT systems in meeting performance targets, coordinates with district technology vendors, and provides after-hours support for essential network equipment to maintain reliable network service across district sites.

          About Our District: At Tulsa Public Schools, our mission is to inspire and prepare every student to love learning, achieve ambitious goals, and make positive contributions to our world. We are the destination for extraordinary educators and staff who work with our community and families to ignite the joy of learning and prepare every student for the greatest success in college, careers, and life. Our core values of equity, character, excellence, team, and joy guide how we work and interact with each other and our community.

          Responsibilities

          • Network hardware and software installation and maintenance
          • Network cabling infrastructure installation and maintenance
          • Work order completion and technical troubleshooting
          • Process and repair documentation
          • State testing standards and operations support
          • After-hours support for essential network equipment

          Qualifications

          Education Minimum Qualifications: High School Diploma or equivalent.

          • Three (3) years of experience with TIA cabling standards and procedures (Cat 6/6a, Fiber)
          • Three (3) years of CCNA, Microsoft server, or related experience, such as cable pulling, switch configuration, wireless access point configuration, or VoIP configuration
          • Three (3) years of VoIP hardware and software configuration experience preferred
          • CompTIA Network+ (N+) certification, required at the time of hire
          • Valid Oklahoma driver's license

          Skills

          • Strong problem-solving and analytical skills
          • Ability to communicate effectively, calmly, and patiently with both technical and non-technical audiences
          • Ability to quickly respond to events in a fast-paced environment and manage problem escalation when required
          • Ability to create extensive spreadsheets for department projects
          • Ability to remain open to change and apply critical thinking while developing solutions based on new guidelines, methods, techniques, and technologies
          • Ability to build